Blog
Notes on buildingsoftware that lasts.
How we scope, price and build custom systems, and the arguments behind the way we work.
MethodMap the workflow before you scope the buildTwo weeks watching how the work actually happens changes what gets built more than any requirements document we have ever been handed.4 min readHow we workWhat a fixed-price milestone plan looks like from the insideFixed price is usually a sales position. It only works as a promise if the exclusions list is as specific as the deliverables.3 min readStrategyConfiguration is a build with a worse debuggerChoosing the platform and configuring it to fit is not the alternative to building. It is building, on someone else’s assumptions, with none of the tools.3 min readFractional CTOWhen a startup should hire a CTO instead of renting oneA fractional CTO is the right answer for a specific stretch of a company’s life, and the wrong one on either side of it. Here is where the boundaries sit.3 min readSecuritySeven security questions worth asking any software vendorCertifications tell you a vendor passed an audit. These questions tell you how they build. The difference matters most for the small suppliers a certification cannot reach.4 min readMethodHandover is a deliverable, not an emailThe cheapest moment to change a technical decision is before it is made. The most expensive is after the people who made it have left.3 min read