Blog

Five SLA requirements for your dev shop contract: response times, fix windows, uptime, a definition of done, and a penalty clause that actually bites.

How to switch development agencies without losing your code: the 30-day overlap, the cold-start deploy drill, and what the next team needs on day one.

Retros for non-technical founders: what a retrospective is, what the one-page summary should say, and why a repeated action item is your best warning sign.

Under US copyright law the code your dev shop writes is not yours by default - a signed clause makes it yours. Five clauses to check, plus one command to run first.

You asked for a simple admin panel and got an over-engineered MVP. The feature-noun check to run on your own spec, and the 90-minute rewrite that stops it.

Cheap developers turn into expensive mistakes when nobody senior reads their code. A 20-minute pull request check plus ways to add review without a CTO salary.

Most founders use SCIPAB to brief their board. Use it to interrogate your dev shop instead. Six questions that turn fuzzy weekly updates into transparency.