Topic
Small business software
Software decisions sized for a business of ten to two hundred people, not an enterprise. These pieces cover finding where AI or software actually pays off before you build anything, and what to do once a no-code platform or an old system has hit its ceiling — porting the product a team actually uses, not the platform underneath it.
Oct 14, 2026NoteFor companiesDraft
"Done" is a ticked checklist, not a feeling
Software projects drag on because the client is asked "is this how you want it?" instead of "does it work, as specified?" Only the second has an answer. One yes/no test per scope requirement, on a page the client ticks, and every "could it also" goes somewhere else.
Oct 14, 2026NoteFor companiesDraft
The page that lets a software project end
Every "could it also" raised during a build needs a home, or the phase never closes. One page holds everything raised but not in scope, in ordered waves with the ordering rules written at the top, and every item on it is a change request.
Oct 3, 2026PlaybookFor companies
Before you hire someone to build with AI
The questions to ask an AI-assisted developer or agency before work starts, what a good answer sounds like, and the red flags. About the people building your software, not the AI product you might buy.
Oct 3, 2026PlaybookFor companies
Before your staff build with AI
The fifteen-minute conversation to have before an employee builds something with an AI coding tool: nine questions for the manager, the matching line the builder checks first, and three tiers so saying yes stays cheap.
Sep 11, 2026NoteFor companies
The build is the cheap part
A tool built in 48 hours feels free until the first API change. The initial build was always the small share of the cost of owning software, and AI just made that share smaller.
Sep 11, 2026NoteFor companies
The tool nobody in IT knows about
Shadow IT used to be a spreadsheet. Now it is a working app that runs part of the business, built by one person with an AI tool, and that person is the only one who can change it.
Sep 5, 2026NoteFor both
Porting the product, not the platform
Moving a CRM off a no-code tool means documenting every screen and automation first, then rebuilding the flows the team already knows, not the workarounds the platform forced.
Sep 5, 2026PlaybookFor companies
Finding where AI actually pays off in a small business
A two-week method for working out where software or AI would save real time or money in a business of ten to two hundred people: map the workflows, score by payoff and effort, check readiness, write it up so the owner can act.
Sep 5, 2026PlaybookFor both
Moving a business off a no-code platform without losing anything
The teardown-first method for replacing a no-code app that has hit its ceiling: inventory every screen and automation, treat the product as the spec, sort mechanisms into decisions and workarounds, rebuild the flows the team knows, run both side by side.
Sep 5, 2026BuildFor AI-coders
Replacing a no-code CRM that could not keep up
Rebuilt as a modern application with Stripe billing and automatic payment reconciliation.