I join early-stage ventures as a technical co-founder and build the first version. Domain research, product definition, architecture, code, and launch. Equity-based — I'm building something with you, not for you.
What I Build
Every engagement follows the same sequence, regardless of domain:
| Phase | What | Output |
|---|
| 1 | Domain Decomposition | Competitive landscape, industry standards, data sources, edge cases. I go from zero to competent in the domain in days, not months. |
| 2 | Product Definition | Problem framing, stakeholder map, MVP scope, requirements, BDD scenarios, data model, delivery plan. The full BA deliverable — what to build and what not to. |
| 3 | Architecture + Build | Technical architecture, infrastructure, backend, frontend, data pipeline, API integrations. Working code deployed to staging. |
| 4 | Launch Infrastructure | CI/CD, monitoring, DNS, email, project boards, documentation. The operational scaffolding between "demo" and "functioning product." |
How this works: I use AI agents as my engineering team. One person produces the output of a small engineering org — domain research, product definition, architecture, full-stack code, DevOps, and operational setup. The method is the same across every domain.
Deal Structure
Every partnership is structured around equity and shared outcomes. The specifics depend on company stage, funding, and what each party brings.
Duration: 3–12 months to MVP · Ongoing post-launch
| Component | Range |
|---|
| Equity | 10–30% depending on stage, contribution scope, and cash component. Vesting: standard 4-year / 1-year cliff. |
| Cash base (optional) | $0–$8,000/month depending on company funding. Cash-constrained ventures trade higher equity for lower base. Funded ventures pay closer to market. |
| IP | Work product belongs to the venture. General methodology, tools, and frameworks remain mine. |
| Commitment | 10–30 hours/week depending on phase. Heavy during build. Lighter post-launch. |
| Term | Minimum 6 months. Month-to-month after initial commitment with 30-day notice. |
What Each Party Brings
| You Bring | I Bring |
|---|
| Domain expertise — you know the industry, the customers, the pain points | Technical execution — architecture, code, infrastructure, launch |
| Customer relationships or a path to first customers | Product definition — turning domain knowledge into a buildable spec |
| Market access and distribution | AI-native development method — one person producing the output of a small team |
| Business development, sales, partnerships | Operational scaffolding — CI/CD, monitoring, email, project management |
| Capital (if funded) or shared bootstrap commitment | Building software since 1994 across EdTech, government, digital media, fleet management, maritime logistics, and enterprise messaging |
What Drives the Equity Split
| Factor | Lower equity (10–15%) | Higher equity (20–30%) |
|---|
| Stage | Existing codebase, team in place | Greenfield — I'm building from scratch |
| Cash base | Market-rate monthly retainer paid | Below-market or no cash — equity compensates |
| Scope | Architecture guidance + oversight | Full-stack build: product, code, infrastructure, launch |
| Duration | 3–6 month engagement | 12+ months, through launch and beyond |
| Revenue stage | Post-revenue, proven model | Pre-revenue, building the first version together |
How equity is decided: After an initial conversation, I propose a structure based on these factors. We negotiate once and put it in writing before work starts. No "show value first, discuss terms later."
How It Works
| Step | What | Details |
|---|
| 1 | Discovery | One call to understand the domain, the opportunity, and your situation. I ask hard questions about market, team, funding, and timeline. Free, no obligation. |
| 2 | Due Diligence | I assess the technical landscape — existing code (if any), competitive products, data sources, feasibility. You assess me — references, GitHub, prior work. Both sides evaluate fit. |
| 3 | Terms | Equity split, cash component (if any), vesting schedule, IP terms, commitment level. Written agreement before work starts. |
| 4 | Build | Domain decomposition → product definition → architecture → code → launch infrastructure. Weekly syncs. Working software in weeks, not months. |
| 5 | Launch | Production deployment, monitoring, first customers. Transition to ongoing technical leadership or defined exit. |
Good Fit / Not a Fit
| Good Fit | Not a Fit |
|---|
| You have domain expertise and customers but no technical co-founder | You want a contractor to execute a detailed spec you already wrote |
| Idea stage or early MVP — need someone to figure out what to build and build it | Growth stage with an engineering team — you need a VP Eng, not a co-founder |
| Willing to put terms in writing before work starts | "Show value first, then we'll discuss equity" |
| Comfortable with AI-native development (I work with agents, not a team of humans) | Need a team of 5+ visible engineers for investor optics |
| Want a partner who has opinions about the product, not just the code | Want someone who codes what they're told |
What This Is Not
- Not staff augmentation. I'm a partner, not a resource. I have opinions about what to build and how to build it.
- Not a dev shop. No project managers, no account executives, no handoffs. One person with AI-native leverage.
- Not free work. Terms are agreed in writing before the first commit. Equity and any cash component are defined upfront.