Technical Partnership for Early-Stage Founders
I work directly on every engagement — no account layers, no junior developers executing while someone else takes the meetings. Every service below is scoped and delivered personally.
Technical Audit
An independent, no-obligation look at your codebase — a clear before/after benchmark and a set of prioritized recommendations you can act on immediately, with or without hiring me further.
This is the lowest-risk way to see how I work before committing to anything larger.
Typical turnaround: 1–3 weeks depending on codebase size and scope.
What you get
- Architecture assessment with clear risk ratings
- Prioritized list of technical debt issues
- Recommended next steps — actionable, not generic
- Written report you keep regardless of next steps
Good fit for
- Pre-seed founders validating technical decisions
- Funded startups before hiring a CTO
- Founders who've been burned and want a second opinion
TTCF — Temporary Technical Co-Founder
I join your company under a partnership arrangement, functioning as a hands-on technical lead — MVP development, architecture decisions, and fundraising-readiness — directly and personally.
Tenure is flexible and scoped to your actual needs, not a fixed template.
Equity discussed for longer-term TTCF arrangements. Typically preceded by a Technical Audit.
What I own during tenure
- Technical architecture and stack decisions
- MVP development and iteration
- Investor technical diligence readiness
- All documentation, written as I build
Good fit for
- Non-technical founders pre-seed or seed stage
- Founders raising and needing tech credibility
- Early startups without a permanent CTO yet
BOT — Build-Operate-Transfer
I take ownership of building or fixing your product within a fixed tenure (typically 6–12 months), working solo and communicating transparently about pace. The engagement concludes with full IP and documentation transfer.
Nothing lives only in my head — documentation happens as I build, not retrofitted at the end.
Typically 6–12 months. Monthly retainer engagement.
What happens at exit
- Full IP transfer — code, credentials, accounts
- Documentation clean enough for your next hire
- I help you think through what that hire needs to walk into
- Defined post-handover window for questions
Good fit for
- Funded startups needing interim technical leadership
- Founders rebuilding after a bad agency experience
- Series A bridge period before a permanent CTO hire
Technical Capabilities
A compact reference for technical due diligence. These are the stacks and tools I actually use — not a marketing list.
Web & Frontend
- React / Next.js (App Router)
- Tailwind CSS / CSS Modules
- TypeScript
- Framer Motion
Backend & Data
- Node.js / Express / NestJS
- MongoDB / PostgreSQL
- REST APIs & GraphQL
- Redis Caching
AI & LLM
- OpenAI / Anthropic / Gemini APIs
- LangChain / LlamaIndex
- RAG Pipelines & Vector DBs
- Agentic Workflow Architecture
Integrations & DevOps
- Docker / Vercel / Railway
- GitHub Actions CI/CD
- Stripe / Webhooks
- Telegram / WhatsApp APIs
Data Science & ML
- Python / FastAPI
- Pandas / NumPy
- Whisper / Local LLM (Ollama)
- ChromaDB / Pinecone
How I handle solo-operator risk, upfront
Documentation is written as I go, not reconstructed at handover. Response-time expectations are set in the engagement scope. Any period of reduced availability is flagged in advance.
At the end of an engagement, you get full IP transfer and documentation clean enough that whoever comes next — your first hire or another vendor — can pick it up without needing me on a call.
I'll help you structure what that next hire looks like — role definitions, interview structure, technical evaluation criteria — but the hiring and final decisions are yours. I don't run a recruiting pipeline.