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.
Code audit: what a non-technical founder is actually buying
Your developer quit or your agency wants more money, and you need to know if the code is sound. What a code audit checks, who should run it,…
System integration: the non-technical founder’s guide to connecting your operation
System integration explained for the non-technical founder: when to connect your tools and how to choose between Zapier, an iPaaS, and custom code.
How to launch an app: the non-technical founder’s playbook
Launching an app is an engineering event before it's a marketing event. A non-technical founder's playbook for go-live: the readiness test, the four launch calls that are yours,…
Scope creep: why your software project balloons, and who pays for it
Scope creep is your project's scope growing out of control after it starts. Why it happens on every outsourced build, and how to stop it.
Acceptance criteria: how a non-technical founder defines done
Acceptance criteria, rewritten for the founder paying for the build: a plain-language way to define done for each feature, agreed before the work starts.
The product roadmap a non-technical founder actually needs
Most founders build the wrong roadmap: a fixed-date schedule that goes stale in two weeks. The product roadmap you need sequences by risk, not by calendar.