Introduction — Eleven Databases and Six People Who Used It
A hundred and twenty hours, thirty buyers, and six who entered any of their own data. Nobody complained; several apologised.
⚠ Sol spent about a hundred and twenty hours building the most impressive thing they had ever made. In month four they asked thirty buyers whether they had put any of their own data into it. Six had.
What Sol built
| ⚠ Component | ⚠ Count |
|---|---|
| ⚠ Databases | ⚠ ⚠ 11 |
| ⚠ Relations and rollups | ⚠ ⚠ 34 |
| ⚠ Formulas | ⚠ ⚠ 22 |
| ⚠ Views | ⚠ ⚠ 40 |
| ⚠ Total moving parts | ⚠ ⚠ 107 |
| ⚠ Build hours | ⚠ ⚠ ~120 |
⚠ It linked tasks to projects to areas to goals to notes to people to meetings. A weekly review page pulled from six of the databases. There was a formula that calculated a completion percentage weighted by priority.
⚠ It demonstrated beautifully. That was the problem, and it took four months to see it.
The question Sol asked
⚠ Not "how are you getting on?", which produces politeness.
⚠ "Have you put any of your own real data into it?"
| ⚠ Line | ⚠ Figure |
|---|---|
| ⚠ Buyers asked | ⚠ ⚠ 30 |
| ⚠ Replied | ⚠ ⚠ 19 |
| ⚠ Had entered any of their own data | ⚠ ⚠ 6 |
| ⚠ Still using it at week six | ⚠ 2 |
| ⚠ Had asked Sol for help | ⚠ 1 |
| ⚠ Had asked for a refund | ⚠ 0 |
| ⚠ Reviews at that point | ⚠ ⚠ Positive |
⚠ Nineteen people replied and thirteen of them had duplicated a system, looked at it, and closed the tab.
⚠ Not one had complained. Several apologised for not having got round to it.
What they actually said
| ⚠ Reply | ⚠ What it meant |
|---|---|
| ⚠ ⚠ "I haven't had a chance to set it up properly" | ⚠ ⚠ Setup was too long |
| ⚠ ⚠ "I wasn't sure where to start" | ⚠ ⚠ No first screen |
| ⚠ ⚠ "It's amazing, I just need to sit down with it" | ⚠ ⚠ It required an appointment |
| ⚠ ⚠ "I put a few tasks in but it felt like a lot" | ⚠ ⚠ Eleven databases |
| ⚠ ⚠ "I went back to my old list" | ⚠ ⚠ The habit did not change |
⚠ Sol's note: "Every single one of them was apologetic. They thought they had failed my template. My template had failed them, and it had done it politely enough that nobody noticed."
The rebuild
⚠ Month nine. Sol rebuilt the same idea with a fixed instruction: nothing goes in unless it earns its place.
| ⚠ Component | ⚠ Original | ⚠ Rebuilt |
|---|---|---|
| ⚠ Databases | ⚠ ⚠ 11 | ⚠ 3 |
| ⚠ Relations and rollups | ⚠ ⚠ 34 | ⚠ ⚠ 6 |
| ⚠ Formulas | ⚠ ⚠ 22 | ⚠ ⚠ 4 |
| ⚠ Views | ⚠ ⚠ 40 | ⚠ ⚠ 9 |
| ⚠ Moving parts | ⚠ ⚠ 107 | ⚠ ⚠ 22 |
| ⚠ Build hours | ⚠ ⚠ ~120 | ⚠ ⚠ ~14 |
| ⚠ Setup time for a stranger | ⚠ ⚠ Over an hour | ⚠ ⚠ ~18 minutes |
| ⚠ Measure | ⚠ Original | ⚠ Rebuilt |
|---|---|---|
| ⚠ First-week completion rate | ⚠ ⚠ ~20% | ⚠ ⚠ ~68% |
| ⚠ Still in use at week six | ⚠ ⚠ Very few | ⚠ ⚠ Most of those who completed |
| ⚠ Reviews mentioning ease of setup | ⚠ ⚠ None | ⚠ ⚠ Many |
| ⚠ Revenue | ⚠ ⚠ Baseline | ⚠ ⚠ Higher |
⚠ "Fourteen hours beat a hundred and twenty. I deleted about four fifths of my best work and it became the first thing I made that people actually used." Chapter 6.
The four rules
⚠ This trade has four structural facts that do not go away.
⚠ You are selling a habit change, not a workspace. Nobody needs a database; they need to work differently, and no template can do that part. Rule 1.
⚠ Complexity sells and complexity kills. The features that make a demo impressive are the ones that make a system abandoned in week two, and every relation and formula is a thing you must keep alive forever. Rule 2.
⚠ You cannot update a copy with somebody's data in it. Duplication is divergence: the moment a customer touches their copy it is theirs, and every fix you make reaches new buyers only. Rule 3.
⚠ The platform is a moving floor. Formulas, features, plan limits and pricing change without consulting you, and your entire catalogue is built on top of them. Rule 4.
The two numbers
⚠ The economic unit is revenue per moving part — what a template earns divided by every database, relation, rollup, formula and view you have promised to keep working. Chapter 30.
⚠ The leading indicator is the first-week completion rate: the share of buyers who finish setup and get their own real data into the system within seven days. It rises when you delete things and falls when you add them, and it moves about a season before reviews and revenue do. Chapter 24.
The update that could not be shipped
⚠ Month seventeen. Sol found an error in a formula.
| ⚠ Line | ⚠ Detail |
|---|---|
| ⚠ Time to fix in the master | ⚠ ⚠ Ten minutes |
| ⚠ Buyers who could receive the fix | ⚠ ⚠ New ones only |
| ⚠ Why | ⚠ ⚠ Existing copies contained their own data |
| ⚠ What Sol could send instead | ⚠ ⚠ A change note with manual instructions |
| ⚠ Length of those instructions | ⚠ ⚠ Four steps |
| ⚠ Buyers who confirmed applying it | ⚠ ⚠ A minority |
⚠ "I could fix it in ten minutes and I could not deliver the fix at all. That is the shape of this business and nobody mentions it until it happens to them." Chapter 7.
Where to start
⚠ Read Chapters 5 to 8 first, in order.
⚠ Then Chapter 21, before you publish anything, and Chapter 6 before you add a single relation.
⚠ Then count the moving parts in your current template. That takes fifteen minutes and it is the most useful fifteen minutes in this book. Resource 30.
⚠ Sol's last note on month four: "Thirty people bought the best thing I have ever built and six of them opened it twice. Nobody was rude about it. The politeness is what cost me four months."
©2026 James Henderson / https://localhandyman.work