Technical Due Diligence
The guide investors and acquirers wish existed, how to assess a codebase, team, and architecture for risk before you write the check, with a repeatable checklist and red-flag catalogue.
Read guideStrategy, build-vs-buy, branding, and running a business.
The guide investors and acquirers wish existed, how to assess a codebase, team, and architecture for risk before you write the check, with a repeatable checklist and red-flag catalogue.
Read guideA decision framework for founders drowning in "should we build this with AI or pay for it", when to build, when to buy, when to wait, and how the economics changed once agents could write the code.
Read guideEvery piece of good advice about running a business alone used to come back to one constraint: there is one of you, and you have a fixed number of hours. Don't build software that needs support, because questions scale with customers and you can't hire. Sell content instead, because content is finished once you publish it. That advice was right, and it stopped being right. This is a guide to building a small, durable business on your own in 2026, using leverage that didn't exist when most of the advice you've read was written. One person plus a fleet: a handful of narrow, well-guarded agents handling the parts of a company that used to need headcount, run by someone who stays close enough to the customer to notice when it's going wrong. It covers choosing what to build now that the content-versus-software split has been rearranged, what a fleet actually costs in money and attention, the parts of the job you must never delegate, pricing when your marginal cost of delivery approaches zero, and the specific ways this fails. It includes the year I grossed ten thousand dollars, because a version of this genre that skips to the good part is worse than useless. _This is a living document and will be updated as the tools and the economics keep moving._
Read guide