CSS frameworks
How we decide what to fix, and how we prove it worked.
Eight rules we apply to every client. Each one has a number attached and a person accountable for it. Start with the first two; they are the whole method in two phrases.
- Framework 01
The Owner Tax
Every time you touch a job or client that someone else could have handled, the business pays a tax. We count it, price it, and track it down.
The number: Owner touches per job, in dollars a month
Read the framework - Framework 02
The Tuesday Test
A system earns the right to go live by surviving one ordinary Tuesday. We design from the messy version of your workflow and sign off by walking a real day through it.
The number: Failure modes found before launch
Read the framework - Framework 03
Rules Before Robots
A decision that isn't a written rule can't be drafted by AI, and a draft that isn't reliable shouldn't become software. Work climbs one rung at a time.
The number: Decisions moved to a written rule, per month
Read the framework - Framework 04
Nothing Leaves Unsigned
AI drafts, a named person approves, and every edit teaches the next draft. The loop is the product; the model is a part.
The number: Approval rate, edit rate, time to first draft
Read the framework - Framework 05
Write It Once
Each stage of the client journey reads and writes one record. A fact that lives in two places will be wrong in one of them, and you will be the person who notices.
The number: Re-keying events per job
Read the framework - Framework 06
The Payback Rank
Every fix is ranked on dollars recovered per month, effort to ship, risk if it misfires, and whether your data and tools can support it today. Readiness is the score most consultants skip, and the one that sinks projects.
The number: Projected vs. realized payback per fix
Read the framework - Framework 07
The Never List
Before anything goes live, you sign the list of what AI never sends, never decides and never touches. The permission register is its ledger.
The number: Permission changes per month, with approver
Read the framework - Framework 08
Four Ways It Breaks
AI systems fail from four directions and only four: the model changes, the prompt drifts, the data changes, or a vendor changes a connection. Reliability watches all four and ignores everything else.
The number: Incidents caught before a customer, by source
Read the framework
Start with your own Owner Tax.
The Owner Tax calculated on one workflow in 15 minutes.