What is a sprint? A non-technical founder’s guide
What is a sprint? The fixed two-week cycle that turns an outsourced build into something you control, without becoming a tech manager.
What a Statement of Work Really Is (and How Not to Sign a Bad One)
A statement of work defines exactly what you're paying a vendor to build. Here's how to read one, and the clauses that decide who eats the cost.
What is a backlog? A non-technical founder’s guide
A backlog is the prioritized list of what's still left to build in your product. Why it's yours, not your dev's, and how to prioritize it without code.
Two-sided marketplace: what to build first (and what to fake)
A two-sided marketplace is two products plus a matching engine. A non-technical founder's guide to the cold-start problem, what to build first, and what to fake.
What is a tech stack? A non-technical founder’s guide
What is a tech stack? A plain-language guide for non-technical founders: how to read the stack you were handed, spot the red flags, and ask the right questions.
Micro SaaS: what it is and when it’s worth building one
Micro SaaS is lean, niche subscription software that solves one problem. What it is, when it's worth building one, and the trap to avoid.
Change request: how to change a software build mid-project
A change request is how a non-technical founder changes a software build on purpose, before the change becomes scope creep or a surprise invoice. The five-part framework.
How much does an app cost? Why the price depends on you
How much an app costs isn't a question with a price list. The number is the output of decisions the founder hasn't made yet. A four-question framework to…
How to choose a software development company when you can’t read the code
Three vendors, three near-identical pitches, no way to tell them apart. The honest way to choose a software development company: grade behavior, not the portfolio.
Project scope: what to define before you hire a developer
Project scope defines what's in and what stays out before you hire whoever builds your software. How to write one that protects the budget.