How I Work
Methodology, sprint execution, and human-AI collaboration for domain founders
I'm a technical partner for domain founders. You bring expertise in your industry's problems. I bring execution capability - team-level output from one person, using a systematic process where you see and control every step.
The Methodology
Research-Before-Build
- • Competitive landscape analysis
- • Domain research and validation
- • Strategic framework development
- • Kill decisions that save 300+ hours per avoided project
Sprint Execution
- • 4-day average to functional prototype
- • Proven across multiple 2025 projects
- • Daily progress visibility
- • Human judgment + AI execution at every step
Sustained Development
- • Long-term project capability (170-day example)
- • Polyglot development across domains
- • Documentation-first approach
- • Handoff-ready codebases
You See and Control Every Step
No black-box magic - a systematic process you can follow and understand
Research Before Code
Before any code gets written, deep research transforms broad ideas into focused, actionable plans:
Market Research
Broad exploratory phase. Competitive analysis, domain investigation, opportunity mapping. Much of this gets discarded.
Vision
Filter what matters. Extract signal from noise. Define what success looks like and what we're NOT building.
Scope
Focused problem definition. Architecture decisions. Trade-off analysis. Risk identification. This is where bad ideas get killed.
Instructions
Precise, actionable context. Implementation plan with clear success criteria. AI works from distilled instructions.
Deep research before any code means by the time I build, the problem is clear and focused. Bad ideas get killed early. You don't pay for wasted effort.
❌ Black-Box Approach
Unclear process, unclear results
- • Throw problem at developer, hope for best
- • When it breaks, no idea where it failed
- • Can't explain why something works
- • Process isn't repeatable
✓ You See Every Step
Clear stages - you understand what's happening
- • Know what happens at each stage
- • Know exactly where adjustments are needed
- • Can verify and guide the output
- • Process is documented and repeatable
The Result: Team-Level Output, Solo Execution
In 2025: 4 substantial builds plus prototypes and research. What used to require a full engineering team, delivered by one technical partner. The systematic process means when something needs adjustment, you know exactly where - no black-box guessing.
What You Get
Tangible Deliverables
- ✓Functional prototypes in days
- ✓Production-ready systems for sustained projects
- ✓Complete documentation and architecture decisions
- ✓Handoff-ready codebases
Strategic Value
- ✓Technical validation before major capital commitment
- ✓Domain research and competitive analysis
- ✓Opportunity evaluation using proven frameworks
- ✓Technical due diligence from someone with skin in the game
How We Can Work Together
Three ways to engage, aligned with how projects actually progress
Compression Phase
2-5 days
What you get:
- • Competitive landscape analysis
- • Opportunity validation
- • Kill/go decision with research to back it
Good for: "I have an idea but need technical validation before investing time and money"
Sprint Execution
4-10 days
What you get:
- • Functional prototype
- • Working software to show investors
- • Something real to test with users
Good for: "I need to prove this works before raising or hiring a team"
Sustained Partnership
Weeks to months
What you get:
- • Ongoing development + strategic input
- • Production-ready product
- • Handoff-ready codebase
Good for: "I need a technical partner, not just a contractor"
Investment capability: I can participate with capital when strategically aligned - but technical partnership is the primary value. Most investors can't debug your production server at 2am. I can.
Ready to Discuss Your Project?
Let's talk about your domain expertise and how we can turn it into working software