Hard-won lessons from co-founding 6+ startups across 3 continents, on co-founder dynamics, product decisions, hiring engineers, and going from 0 to paying customers. On-site and Medium, all in one place. Back to the blog.
Technical debt in startups is a tool, not a sin. The three buckets I sort every debt into, how to prioritise by what each one blocks, how much of each cycle to spend paying it down, why AI-written code piles it up faster, how to explain it to your board and investors, and who should own it at your stage.
Rebuild or refactor an agency-built MVP? Usually refactor. The signs your MVP needs rescuing, the ownership checklist to run before anything else, how I audit an inherited codebase in two weeks, the rare cases where a rebuild is right, why rewrites get proposed so often, and who should own the rescue.
What a SaaS MVP really costs in 2026: market lanes, worked examples from my MVP cost calculator, the three decisions (tenancy, roles, billing) that decide whether v1 survives its first customers, which enterprise features to price but defer, realistic timelines, and the running costs that aren't code.
What a marketplace MVP really costs in 2026: why two-sided products cost more than a SaaS app with the same screens, worked examples from my MVP cost calculator, why payouts are the line that moves the budget, what to leave out of v1, realistic timelines, and the running costs that aren't code.
What a mobile app MVP really costs in 2026: why one cross-platform build costs about the same as the web version of the same screens, what the App Store and Play Store add, worked examples from my MVP cost calculator, the running costs nobody quotes, and when you should ship a web app first.
The best tech stack for an MVP is the boring one: widely used, easy to hire for, and managed wherever possible. Here is the MVP tech stack I point founders at in 2026 (web, mobile, backend, data, AI), the rule that matters more than any framework, when no-code is the right call, and the stack choices that quietly cost you a rebuild.
What an AI MVP really costs in 2026, from someone who runs a multi-LLM platform: the build is usually smaller than founders expect, and the inference bill is usually bigger. Here are the four cost lines of an AI app, how to work out cost per user before launch, what to leave out of v1, and how to get an honest quote.
How long it takes to build an MVP, from someone who builds them: most real MVPs take 8 to 12 weeks once the scope is counted. Here is the MVP development timeline week by week, what makes it longer, what genuinely makes it faster, and how to tell a realistic timeline from a sales promise.
Your MVP budget is more than the build quote. Here is how to set one: the eight lines a real first-year MVP budget needs, the five MVP pricing models (fixed price, hourly, monthly team, per screen, equity) and who each one protects, how to compare two quotes, and how much of your runway the build should take.
A startup CTO owns every technical decision the company cannot afford to get wrong: what to build, how to build it, who builds it, and how it stays secure. The job changes completely with stage. Here is what a CTO actually does at pre-seed, seed, Series A and beyond, the core responsibilities, how the role differs from a VP of Engineering, and when you need one.
You can build an MVP without a technical co-founder if your product is a well-understood build and the technology is not your moat. Here is the step-by-step path for non-technical founders: validate first, scope in screens, pick the right builder, rent technical judgment instead of giving away equity, and keep ownership of the code.
A full-time startup CTO hired at seed to Series A typically earns $180,000 to $260,000 in salary plus 1 to 4 percent equity on a four-year vest. Here is how startup CTO compensation really moves with stage, salary, and timing, how much equity a CTO should get in each shape of the role, and where fractional CTO equity fits.
Hiring a CTO is the most expensive hire most founders ever make, and most of them make it in the wrong shape at the wrong time. Here is the whole process: deciding whether you need one, choosing between co-founder, full-time, fractional, and interim, finding candidates, evaluating them when you are non-technical, and paying them without giving away the company.
A fractional CTO gives you the same seniority for two or three days a week, no equity, and an exit. A full-time CTO gives you forty hours and total ownership, at roughly $260,000 a year plus equity. Here is the honest decision rule, from someone who has been both.
If a technical co-founder is building the entire product and you are pre-revenue, the defensible range is 40 to 50 percent of the founder pool. Here is what actually moves that number, why vesting matters more than the split, and the three patterns that turn a fair deal into resentment.
A fractional AI officer owns your model strategy, your inference economics, and your AI security posture, part-time. A fractional CTO owns your whole engineering org, AI included. Here's the honest difference, from someone who runs a production multi-LLM platform and holds an M.Tech in cybersecurity.
Most fractional CTO retainers fail quietly: hours get billed, nothing ships, and nobody can say why. Here is how I structure mine so that does not happen, including the one clause I refuse to put in a contract.
An MVP costs anywhere from $5,000 to $150,000+ in 2026 depending on who builds it and how the scope is controlled. Here are the real market numbers, the hidden costs nobody quotes, and why I price MVPs per screen so founders know the total before a single screen is built.
A fractional CTO is a senior technology executive who leads your engineering part-time, typically 2 to 3 days a week, for a fraction of a full-time CTO's cost. Here's what the role actually involves, what it doesn't, and how to tell if you need one. Written by someone who does this for a living.
Investors doing technical diligence on an AI startup now ask about model dependency, eval rigour, inference economics, and prompt injection, not just team background and burn rate. Here is what actually gets checked, from someone who has prepared for it and sat on the other side of the call.
Every technical person who looked at this problem walked away. It needed Linux, MERN, DevOps, Python, AI, security, and custom protocols in one head. Here's how we built it, went from processing thousands to 500,000 assessments in an hour, the one wrong AWS line that almost sank the launch, and why competitors now keep calling.
Every fractional CTO's website tells you why to hire one. Almost none of them tell you when not to. I have been on both sides of this decision six times as a founder and I am not going to sell you a retainer you don't need. Here is the honest version.
Most advice on finding a technical co-founder is written by people who have never been one. I've said yes six times and no far more often. Here's what actually makes engineers commit, what founders get wrong, and when you shouldn't look for one at all.
Most of the founders who ask me this do not need me yet, and I tell them so on the call. Here is the checklist I actually use: the signs you need a fractional CTO now, the signs you need something cheaper, and the signs you need something more expensive.
Most CTO interview question lists are written by recruiters who have never hired one. I have hired technical leaders for six companies I co-founded and been the candidate on the other side of this table more times than that. Here are the questions that actually separate a strong CTO from someone who interviews well.
Everyone wants the success story. The failures taught me more. Here's an honest look at the startups I co-founded that didn't make it - and the simple mistakes I kept repeating.
The skills that make you a great engineer can quietly undermine you as a founder. Here's the trap most technical founders fall into - and how to get out of it.