Notes from the team.
Practical writing on building software, hiring engineers, and shipping product without adding headcount.
AI writes the code now. That's exactly why you need senior engineers.
Generative AI made software cheaper to produce and easier to get wrong. The bottleneck moved from writing code to knowing which code is right. Here's why the human in the loop matters more than ever, not less.
Latest posts
The most expensive software is the kind nobody needed
Founders worry about whether their engineers can build it. The more dangerous question is whether it should be built at all. Here's why deciding what to build is the work that actually determines the outcome.
The real cost of your first engineering hire (and it isn't the salary)
A senior engineer's base pay is the number on the offer letter. It's also the smallest line in the budget. Here's the full cost of the first hire, and why so many founders get it wrong.
Who maintains it when you leave? The custom-software question you're right to ask.
It's the best question an owner asks in a sales call, and the one lazy agencies fumble. The fear behind it is healthy. The conclusion most owners draw from it, just buy SaaS and never build, is wrong.
Should you hire an engineer or hire a team?
Every founder reaches the point where the spreadsheet stops scaling and the product needs to get built. The instinct is to hire. Sometimes that's right. Often it isn't. Here's how to tell.
AI specialist, application engineer, full-stack: what are you actually hiring for?
The titles have multiplied faster than the clarity. Before you write the job post, it helps to separate the label from the work you actually need done.
Ship your MVP before you make a single hire
The default order is hire, then build. Reversing it lowers your risk, saves your runway, and means that if you do hire, you hand them a working product instead of a blank page.
How an on-demand engineering network beats a fixed headcount
A hire is one person at a fixed cost forever. A network flexes to the project. Here's how we staff work, keep quality high, and let you scale up and down without managing a team.
Why we shipped a working AI voice agent in 36 hours
A client needed inbound calls answered, qualified, and routed before the weekend. We had a real system in production in a day and a half. Here's how, and why speed like that is an engineering decision, not a miracle.
Build, buy, or borrow a team: a founder's framework for getting software made
There are really only three ways to get software built, and most founders only seriously consider one of them. A clear-eyed look at the trade-offs of each.
Ready when you are
Tell us what you're building.
Thirty minutes with the engineers who'd do the work. Bring the problem you're trying to solve and we'll tell you, honestly, whether and how we can build it.