Notes from real work.
Frameworks and build case studies on running a small business better — practical operations, systems, and honest AI. Everything here comes from work I've actually done, not theory. Fewer, better, and worth citing.
Frameworks
Time, Money, Momentum: find the loss before you fix anything
The diagnostic I run before proposing anything — locate where a business loses time, money, or momentum across three lenses, then fix the highest-leverage one first.
Framework · OperationsOne View: one place that tells the truth
Turn a dozen scattered tools into a single source of truth — the principle, the method, and when not to use it.
Framework · MethodologyMap-Then-Build: do the thinking and the building
A reusable methodology for improvement — map the real state, design, build in reversible steps, validate. Keep it in one hand.
Framework · Practical AIFit-First: choose technology that fits the business
A decision model for technology, automation, and AI — fit the tool to the business, not the reverse. Process first, then automation, then AI, and an honest no when nothing fits.
Framework · DocumentationBuild-to-Last: a system isn't done until it can run without you
The quality bar that turns a working thing into a durable one — documented, transferable, and designed to survive the next tool or staff change.
Framework · AutomationLeverage-over-Labor: buy back time by designing leverage in
Reduce recurring manual work by choosing the right form of leverage — eliminate, document, delegate, automate, AI — not automation for its own sake.
Case studies
Mission Control: one view for a whole operation
How I pulled a dozen scattered tools into a single, self-hosted command center — and the repeatable pattern behind it.
Case study · Map-Then-BuildSEO Foundation: fixing the plumbing without touching the brand
Disciplined technical problem-solving on a frozen brand — audit, build, validate, document — with proof you can verify yourself.
Case study · Fit-FirstBoring on Purpose: choosing Mission Control's stack with Fit-First
Why I chose Python stdlib and SQLite over the modern stack for a one-person tool — the real options, and everything I deliberately left out.
Case study · Build-to-LastInstitutional Memory: building an operation that doesn't live in one head
A documented, versioned knowledge base — architecture, decisions, and incident post-mortems — so systems stay transferable and survive change.
Case study · Leverage-over-LaborPublishing Without the Grind: applying Leverage-over-Labor to weekly content
Turning a recurring weekly chore into right-sized leverage — mechanical parts systematized, AI on one rung, and the judgment kept human.
More frameworks and case studies are added here over time — deliberately slowly, one well-evidenced piece at a time.