GitHub - teal-sea/why-your-ai-startup-dies-at-customer-six: An essay on why bespoke deployments stop scaling, and the semantic / kinetic / rulebook split that fixes it. · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
teal-sea
why-your-ai-startup-dies-at-customer-six
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>1 Commit<br>1 Commit
README.md
README.md
View all files
Repository files navigation
Why your AI startup dies at customer six (and the three-layer fix)
Customer one is easy. Their rules are the product: you hardcode their deposit policy, their<br>hours, their quirks, and the demo looks like magic because it's their own business looking<br>back at them.
Customer two needs three things different, and you're busy, so their exceptions go where<br>the code already is. A branch in the workflow, a paragraph in the prompt, a special case in<br>the tool. By customer six there's a folder with client names on it, and onboarding turns<br>into development, quoted in weeks.
I'm not writing this from a distance. I run operations for a US limo booking service, an AI<br>answers its phone on live calls, and I recently went looking for the rule that says a<br>reservation can't be confirmed without an authorized deposit. Confirmed, in my system,<br>means a card authorization verified against the payment processor seconds before the state<br>changes. I found that rule in three places: one version in the booking workflow, one in the<br>agent's booking tool, one in the dashboard's validation, written months apart, by three<br>different moods of me. They agreed, mostly. Nothing had blown up yet, and that was the<br>scary part: nothing was checking. Change the rule and the copy you miss doesn't throw an<br>error, it just keeps enforcing the old rule on real customers until something expensive<br>happens. And I only have one tenant: me. Now imagine the folder with six client names on<br>it.
The numbers explain the temptation. ChartMogul's retention report has AI-native companies<br>at a median net revenue retention of 48 percent against 82 for ordinary B2B SaaS, and the<br>segmentation is the interesting part: above 250 dollars a month, AI retention looks like<br>normal SaaS again, 85 percent. What retains at that tier, on ChartMogul's own reading, is<br>deeper workflow fit and tighter integration, and hold even that loosely: price is also a<br>proxy for enterprise buyers, annual contracts and procurement inertia, and the AI-native<br>cohort mixes consumer products into the comparison. Still, deep<br>workflow fit is exactly the temptation, because the fastest way to fit a workflow is to<br>absorb the client's every quirk into the code where they can never leave. Do it without a<br>platform underneath and Marc Andrusko at a16z has already named where you land: "thousands<br>of bespoke deployments that are impossible to maintain or upgrade." At that point, in his<br>words, you aren't Palantir for X. You're "Accenture for X" with a nicer front-end.
The diagnosis is one sentence: the rule doesn't live inside the thing that owns it. Three<br>drifting copies of a deposit rule and an agent reaching for book without the deposit step<br>are the same bug in two costumes. The fix starts with naming the layers.
A business system has three.
The semantic layer is what things are. Reservation, vehicle, rate, customer: one official<br>shape each, one set of legal states. The nouns. My three drifting copies were, among other<br>things, three private definitions of the legal state called confirmed.
The kinetic layer is what can be done. Quote, book, cancel: the verbs of the business, with<br>the rules inside them and no other door to the tables. The deposit rule lives inside book,<br>once, for every caller, and it guards the state, not the verb: if a second verb ever<br>learns to confirm a reservation, a manual override, an import, it inherits the same rule<br>at the same door.
The rulebook layer is where anyone is allowed to be different: rates, thresholds,<br>schedules, toggles. A rulebook per client that the verbs read at...