The renewal report has two columns. Renewed on the left, did not on the right. The first time I lined it up against our usage data, expecting the two to explain each other, they did not.

Several accounts in the right-hand column had excellent engagement numbers. Logins most days, high satisfaction scores, friendly conversations with our team throughout. Several accounts on the left were quieter than average and renewed without a discussion.

The variable that separated them was not how much they used the product. It was what would have had to change in their organization if they stopped.

Engagement is not a marketing metric

Logins are attendance. They tell you somebody opened the door. They do not tell you whether anything inside the building matters.

What matters is depth, and depth is now a formal diligence question in this category. Investors assessing AI companies specifically ask whether customers are embedded in a daily workflow or running an experiment, because the two produce identical-looking activity charts and completely different renewal outcomes. It sits alongside compute economics and pilot conversion as a layer applied on top of the standard software metrics.

The context is worth knowing. Retention among AI-native companies has generally run below classic software norms, and investors are not currently expecting parity. What they look for is the trajectory and the evidence that customers who embed deeply do stay and expand. That is a more forgiving standard than it sounds, and it puts the emphasis exactly where it belongs: on depth rather than on breadth.

The question that predicts renewal

Satisfaction surveys are close to useless for this, and Lesson 12 explains why. A customer can be entirely satisfied and completely indifferent, and no standard question distinguishes those states.

The question that works is this: if this stopped working on Monday, what would you do?

Answers cluster into two groups almost immediately. One group describes a problem: a process that would stall, a person who would have to go back to something, a commitment they would miss. The other group says some version of we would manage, we would go back to the spreadsheet, it would be annoying.

Only the first group renews reliably. The second group renews while budgets are comfortable and disappears in the quarter when they are not.

Score every account on that question, quarterly, recorded by whoever owns the relationship. It takes minutes per account and it forecasts revenue better than any usage dashboard I have used.

Four kinds of stickiness, in ascending order

Habit. The product is part of somebody’s daily routine. Real, and the weakest of the four, because habits break during holidays, reorganizations and any week that is unusually busy.

Data. Their history lives inside your product. Past decisions, corrections, context accumulated over months. Leaving means leaving that behind, and the longer they stay the more expensive that becomes. This is the compounding asset from Lesson 5 showing up on the revenue side.

Workflow. Other people’s work now depends on your output. A report you generate feeds a meeting. An approval you route is how a decision gets made. Removing you is not a purchasing decision, it is a change management project involving people who did not buy you and will resist.

Accountability. An auditor, a regulator, or one of their own customers has been told that this is how the work gets done. Now removing you requires explaining the change to a third party. This is the strongest form and the slowest to build, and it is the commercial payoff of the trust work in Lesson 15.

Most early products have only the first. The work of the second year is climbing that list.

What to build for retention specifically

Time to first value, measured in days. The single largest determinant of whether an account is alive at month twelve is what happened in the first two weeks. If a customer has not received something useful within days of signing, the internal champion who bought you begins losing the argument they made to buy you.

Onboarding that connects their real data. Sandboxes demo well and retain badly. The account that has connected a live source, mapped their fields and corrected their first real output has crossed a threshold that no amount of guided tour replicates.

A second user. Single-user accounts are fragile in a specific way: they churn when that person changes role, goes on leave, or has a difficult quarter. The account did not decide to leave, the person just stopped. Getting a second and third person inside an account is worth more to retention than almost any feature, and it should be an explicit goal of onboarding rather than something you hope happens.

A moment of measurable proof. A specific point where the customer sees a number: this took four hours and now takes twenty minutes, this caught fourteen errors last month. Champions need ammunition for the internal conversation you are not in the room for, and they need it before renewal season, not during it.

The churn you should want

Not all churn is a problem, and treating it as uniformly bad produces bad decisions.

Customers outside your wedge who leave are confirming that the wedge is correct. If you sold to somebody because they had budget rather than because they had the problem, their departure is information rather than failure, and chasing them back with features is how a focused product becomes an unfocused one.

So segment churn before reacting to it. Split by segment, by acquisition channel, by whether they were in the core use case, and by month of tenure. Aggregate churn is an average of unrelated stories, and the average conceals both the thing you should fix urgently and the thing you should be pleased about.

The account that taught me this had wonderful engagement numbers and no dependency. They enjoyed the product. Nothing in their organization would have changed if it vanished. That is a pleasant relationship and it is not a business, and the distinction is worth more than any dashboard.

The customers who renew are the ones who would have to change how they work in order to leave.

Tomorrow, the last one: the roadmap with things crossed out.

The referral log is a column in a spreadsheet fed by a single optional field on the signup form: how did you hear about us. Most people skip it. The ones who answer write two or three words.

Over one quarter, the answer that appeared most often was some version of I asked an assistant and you came up.

Not a search. Not a colleague. Not a post. Somebody described their problem to a general purpose model, and our name was in the reply.

I could not have told you why. That is the uncomfortable part, and it is why this deserves its own lesson rather than a paragraph in a marketing plan.

The channel that changed underneath everyone

The forecast that traditional search volume would fall materially as assistants absorbed informational queries has been circulating since 2024, and the direction has held. Informational queries in particular, the how do I and what is the best kind, increasingly resolve inside an answer rather than in a list of links.

The structural consequence is a change in what visibility means. Ranking third in a list gives you a chance at a click. Being cited inside an answer gives you the attribution without the click: the user reads your claim, associates it with your name, and never visits your site.

Which means your analytics will lie to you for a while. Traffic can be flat or falling while pipeline improves, because the mechanism that produced the pipeline is invisible to a tool that counts visits. Founders who manage marketing by traffic will cut the thing that is working.

What gets cited

Five properties, and they are not the properties that historically ranked.

Specific, attributable claims. A sentence containing a number, a date and a source is quotable. A paragraph of qualified generality is not. The unit of citation is roughly a sentence to a short paragraph, which means writing that buries its point in the eighth line is structurally disadvantaged.

Original data. This is the strongest and the most underused. You operate a product. You see things nobody else sees: how long a task actually takes, what proportion of a workflow is exceptions, what a category of user actually costs to serve. Nobody else can publish that. Anonymize it, aggregate it, put a date on it, and publish it.

Direct answers, structured to stand alone. A section that answers one question completely, under a heading that states the question, is far more likely to be lifted than the same content woven through a narrative.

Comparison content. Queries of the form X versus Y, or alternatives to X, sit at the highest-intent moment in a buying process and are heavily represented in assistant queries. Honest, specific, genuinely useful comparisons, including the cases where you are not the right answer, get cited precisely because they are not marketing.

Consistent entity definition. Who you are and what you do, phrased consistently everywhere: your own site, your documentation, third-party listings, interviews. Models assemble an understanding of an entity from many sources. Inconsistency across those sources produces a fuzzy answer, and a fuzzy answer does not get named.

The asymmetry that is open right now

By early 2026 most large enterprise marketing organizations had an initiative for this. Most small and mid-market teams had not started at all.

If you sell into that second group, or compete with companies inside it, there is a window here of a kind that does not come along often. The work is not expensive, it is not technically difficult, and the competitive set has largely not begun. Windows like that close in eighteen to twenty-four months, and they close from the top down.

The one thing that compounds

If you do one thing from this lesson, do this: publish a number nobody else has.

Original research creates a citation network. A statistic gets quoted by a journalist, referenced in somebody’s newsletter, cited in a competitor’s blog post as background, and picked up by assistants answering adjacent questions. Each of those references strengthens the association between your domain and the topic, which lifts everything else you publish.

You are sitting on the raw material. The instinct is to treat operational data as confidential by default, and the genuinely sensitive parts are. The aggregate patterns usually are not, and they are the most valuable marketing asset most early companies own and never use.

What to stop doing

Three things, and stopping them frees the budget for the above.

Stop publishing on volume. Lesson 12 covers why. Five undifferentiated pieces a week is a cost with no compounding return, and it teaches an audience to ignore your name.

Stop answering questions the models already answer well. A general explainer on a well-covered topic will not be cited, because there are four hundred of them and none has anything the others lack.

Stop gating everything. A resource behind a form cannot be read, cannot be cited, and cannot contribute to how you are described. Gate the thing that requires a conversation. Publish the thing that establishes what you know.

Three ways this goes wrong

You measure visits instead of mentions. The right instrument is how often you appear in answers to the questions your buyers actually ask. Tools exist for this at prices a small company can afford, and in the absence of one you can do it manually: write down twenty real buyer questions, ask them across the major assistants once a month, and record whether you appear. It is an hour a month and it is the only number that reflects this channel.

You block the crawlers reflexively. There is a genuine debate about whether to allow model training crawlers, and it deserves a considered position. What you should not do is block everything by default without distinguishing training access from retrieval access, and then wonder why you are never cited.

You write for the machine and forget the person. Content assembled to be quotable, containing nothing a human would want, gets cited once and converts nobody. The citation is the introduction. What arrives afterward is a person deciding whether you are serious.

Publish the thing a model would want to cite, not the thing a search engine would want to rank.

Tomorrow: the renewal report, and the only kind of customer worth counting.

A term sheet is about three pages and almost all of it is non-binding. Founders read the valuation first, usually twice. The parts that determine what the next five years feel like are further down, in shorter paragraphs, written in language that does not draw attention to itself.

Before any of that, though, there is a question that comes earlier and gets asked less: should this document exist at all?

What raising is actually for

Money buys time. That is the entire product. It converts a runway of nine months into a runway of thirty, and it does so today rather than after you have earned it.

It also sells a say. A board seat, protective provisions that require consent for a defined list of decisions, and, less formally but more powerfully, an expectation about what shape the outcome should take. Venture capital is not neutral capital. It is capital with a required distribution of results, and a company that would be a very good business at fifteen million in revenue is a disappointment inside a portfolio that needs a small number of enormous outcomes.

So the question is not can I raise. In a market where AI-labeled seed companies have been carrying valuation premiums over comparable non-AI peers, quite a lot of people can raise. The question is what am I short of.

If you are short of time, and you can see specifically what you would do with more of it, raise. If you are short of customers, money rarely produces them and frequently disguises their absence for another eighteen months, which is the most expensive form of not knowing.

What each stage requires now

The labels have not changed and what sits behind them has.

Pre-seed. Evidence that this is real. Customer conversations you can quote, a waitlist, design partners, ideally somebody who has paid you something. The bar has risen. The venture market has been sharply K-shaped, with very large sums concentrating into late-stage rounds while the earliest stage became harder rather than easier.

Seed. Design partners and evidence that money changes hands. Recent AI seed rounds have commonly landed in the region of three to four million dollars at mid-teens pre-money valuations, with wide variance by geography and a visible premium for the category. Expect this to fund eighteen to thirty months, and see Lesson 10 about why twelve is not a plan.

Series A. Repeatability. The commonly cited range is one to three million in annual recurring revenue with a demonstrable acquisition motion, not a collection of relationships. Median time from seed to A has stretched toward twenty months.

Series B. Scale, typically five to twenty million in recurring revenue, growth around one hundred percent year on year, and unit economics that survive inspection.

What is new is the diligence layer. Alongside acquisition cost, lifetime value and churn, investors in this category now expect compute economics, revenue per employee, burn multiple, pilot conversion rate and usage depth. That last one deserves emphasis: they want to know whether customers are embedded in a daily workflow or running an experiment, because AI-native retention has generally been running below classic software norms and everybody knows it.

Three questions before you decide

Are you default alive? The calculation from Lesson 10. If current growth and current costs continue with no further funding, do you reach profitability before the money runs out? A founder who knows the answer is negotiating. A founder who does not is auditioning, and everyone in the room can tell.

Is the bottleneck money? Write down what is actually stopping you. Then, for each item, ask whether a bank balance removes it. Engineering capacity, yes, with a lag. A sales motion that has not been proven once, no. Trust that requires elapsed time, as in Lesson 15, no. Money accelerates things that already work. It does not discover things that do not.

What does it commit you to? A priced round with institutional investors is a commitment to pursue an outcome of a particular size within a particular period. That is fine if it is what you want. It is a poor fit if what you actually want is a durable, profitable business you control, and the time to notice the mismatch is before the wire, not at the third board meeting.

The case for not raising

This gets less attention than it deserves, so let me put it plainly. An LLC generating two million dollars of profit annually, owned by the people who built it, is an excellent outcome. It funds lives. It is not a failure mode of a venture company, it is a different company.

What has changed is that this path is far more accessible than it was. Small teams can now build and operate products that would have required substantial headcount three years ago. The bootstrapped, cash-generating software company has become more viable at exactly the moment the venture route became more selective at the early stage.

This is also the moment the entity decision from Lesson 1 either pays off or costs you. A company structured for distributions, deliberately, by people who wanted distributions, is in a good position. A company structured for venture that never raises is carrying overhead for an option it did not exercise.

Reading the document itself

If you do get one, the ranking of what matters is almost the reverse of what founders negotiate.

• Liquidation preference. One times, non-participating, is the standard. Multiples or participation mean that in a modest outcome the investors take most of it and the founders take very little. This clause determines what happens in the likeliest scenarios, not the best one.
• Board composition. Who sits, who appoints, what the independent seat requires. This decides who can remove you.
• Protective provisions. The list of decisions requiring investor consent. Read every line and picture yourself needing consent for it during a bad week.
• Option pool. Size and, critically, whether it is created pre-money. Lesson 4 has the arithmetic. This is worth more real money than a valuation adjustment of the same apparent size.
• Valuation. Genuinely matters least of the five. A higher valuation with a participating preference and a large pre-money pool is worse than a lower one on clean terms, and founders trade the second for the first constantly because only one of them is a number you can say out loud.

Also note which parts bind you immediately. Most of the sheet is non-binding, but exclusivity and confidentiality usually are, and signing a no-shop means the process is over whether or not the deal closes.

Raising money buys time and sells a say. Be clear about which one you are short of.

Monday: the referral log, and why you now optimize to be quoted rather than found.

I wrote the job description at one in the morning at the end of a week in which everything had gone slightly wrong at once. It was a good job description. It was specific, it was honest about the stage, and it described a person who would have solved every problem I had experienced in the previous five days.

I saved it as a draft and did not post it.

Three weeks later I read it again, in a normal week, and it described three different jobs held together by exhaustion. Two of those jobs did not exist. The third one did, and it was not the one I had emphasized.

The bad reason, and the good one

The bad reason to hire is that you are tired. Tiredness is real, it deserves to be taken seriously, and it is not a hiring signal, because it is neither durable nor specific. It tells you that last week was hard. It does not tell you which work will still be there in six months.

The good reason is that a particular, repeatable piece of work has existed roughly unchanged for a full quarter, you can describe what somebody would do with it in their first ninety days, and doing so takes a founder off the critical path.

Those are three separate tests and it is worth applying them individually.

Durability. Has this job existed, in recognizable form, for three months? A bottleneck that is two weeks old is frequently a symptom of something else, and hiring against it institutionalizes the symptom.

Specificity. Can you write what they do in week one, month one and month three, and state how you would know by month three whether it was working? If you cannot, you are not hiring for a job. You are hiring for relief, and relief is not a role.

Removal. Does this hire take a founder out of a critical path, or does it add a person who needs a founder?

The third test is the one people fail, and it fails quietly. Every early hire consumes founder time before they return any, typically for two to four months. That is a genuine investment with a genuine payback period, and it is worth modeling as one. Two hires made in the same month can consume more founder capacity than they release for an entire quarter, which is exactly the quarter you were hoping to get back.

The benchmark that replaced headcount

Headcount used to be a credibility signal. It is now closer to the opposite, and the change happened quickly.

The extremes are genuinely striking. Companies in this category have reported annual revenue in the billions with headcounts measured in dozens, producing revenue per employee figures in the tens of millions of dollars, numbers that had no precedent in software before 2024. Nobody should plan to be an outlier. What matters is that the outliers reset the reference point, and investors now routinely ask for revenue per employee alongside growth and burn multiple.

The practical consequence for a founder is a reversal of an old instinct. Announcing that you are forty people used to say we are real. It now invites the question of why it takes forty, and if the honest answer is that twelve could not have done it, that is a fine answer. If the honest answer is that you hired because you had money, that will surface in the burn multiple from Lesson 10.

The order that usually works

The first hire is rarely a generalist, despite the persistent belief that early companies need someone who can do a bit of everything. In practice a generalist at a five-person company becomes a second version of the founders, and you did not need a second version of the founders.

The first hire is usually whoever owns the thing that is currently breaking and that no founder wants to own permanently.

Two roles come up repeatedly at this stage and both are good bets. The first is somebody who sits with customers and makes the product work in their environment: integrations, data mapping, the specific way this customer’s systems are wrong. This removes founders from implementation, which is usually where founder time is disappearing, and it feeds directly into the integration moat from Lesson 14.

The second is somebody who owns evaluation and data quality: the golden set, the scoring, the incident analysis. It is unglamorous, it is the thing founders keep deferring, and it is the difference between a product that improves and one that drifts.

The hires that are usually premature at this stage are a marketing generalist with no distribution thesis to execute, a junior engineer hired to help rather than to own something, and any operations leadership role before there are operations to lead.

Where they sit, and what that costs you

If your founders are in one country, your entity is in another, and your first hire is in a third, you have a set of obligations that nobody warns you about until you have already created them.

Classification is a real risk, not a formality. Engaging somebody as a long-term full-time contractor, doing core work, under your direction, using your systems, with no other clients, is the exact fact pattern that authorities in many jurisdictions treat as employment regardless of what the contract says. The consequences are back-dated social contributions, penalties and sometimes employment rights you did not know you had granted. Getting this wrong is expensive and it is entirely avoidable.

An employer of record buys speed at a price. A third party employs the person locally and invoices you. It solves compliance, payroll and local benefits without you registering an entity in their country. It costs a monthly fee per person and you give up some control over terms. For your first hire in a new country it is almost always the right first move.

Equity does not travel well. This is the one founders get most wrong, out of genuine goodwill. Option treatment varies enormously by country. In some jurisdictions the taxable event occurs at exercise, at the value on that date, with no liquidity available to pay it. A grant that is a gift in one country can be a liability in another, and the person receiving it will not find out until it is too late to restructure.

Ask before you grant. A thirty-minute conversation with somebody who knows the local treatment, per country, before the offer goes out. It is a small cost and it prevents the specific situation where a loyal employee ends up worse off for having been given something.

Hire against a bottleneck that has survived a quarter, never against a week that felt hard.

Tomorrow: the term sheet, and the difference between buying time and selling a say.

It arrived as a spreadsheet attachment with a two-week deadline and a cheerful covering note. One hundred and eighty questions across nine tabs. It came from the first customer who was actually going to matter, the one whose name would have changed every subsequent conversation, and it arrived four days after they said they wanted to move forward.

We could answer about sixty of the questions honestly. Another forty we could answer with work. The remainder asked for things that take months of elapsed time and cannot be produced by working harder.

That is the lesson, and it is the whole lesson. Some things you can build under pressure. Trust is not one of them, because trust is largely made of time you have already spent.

Trust has a lead time

Take the most commonly requested attestation. A Type I report assesses whether your controls are appropriately designed at a single point in time. Preparation, remediation and the audit itself typically consume two to three months, and it is achievable from a standing start if you commit.

A Type II report assesses whether those controls actually operated over a period, and the period is the point. It requires an observation window, commonly three to twelve months, during which evidence accumulates. There is no version of this you can accelerate with money or urgency. If a buyer requires Type II and you begin the day they ask, you are a minimum of six months from an answer, and their procurement cycle is not going to wait.

This is why the certification belongs on the roadmap during the quarter when you have no customers asking for it. It is the least satisfying work available and it is pure elapsed time, which makes starting early the only lever that exists.

What the hundred and eighty questions are actually asking

Behind the spreadsheet there are about six real questions, and every tab is a restatement of one of them.

• Where does our data physically go, and through whose hands?
• Who inside your company can see it, and how do you know?
• Is it used to improve anything, including anybody’s model?
• What happens, specifically, if you are breached?
• What happens to our data if you cease to exist?
• Who is personally accountable for these answers?

Answer those six well and most of the spreadsheet resolves. The reason founders find the exercise so painful is not the volume. It is that the questions require you to know your own data flows precisely, and a company that has been shipping quickly for a year frequently does not.

One item deserves separate attention because it is new and it catches people. Your model provider is now a subprocessor. That means they appear on a list your customer’s legal team will read, alongside your hosting provider and your error monitoring service. It means when you change providers, or add a second one for routing as described in Lesson 7, you may have a contractual notification obligation. Founders who treat model selection as a purely technical decision discover this at renewal.

The three documents you need before the deal, not during it

A data processing agreement with a current subprocessor list. Templates exist and are fine as a starting point. What is not fine is a subprocessor list assembled from memory in an afternoon. Keep it accurate as you add services, because you will be asked to attest to it.

A one-page security overview. Written by you, honest about what exists and what does not. Encryption in transit and at rest, access control, logging, where data resides, who has production access, what your review process is. One page, dated. This document alone will short-circuit a surprising proportion of the spreadsheet, because a reviewer who can see you have thought about it clearly asks fewer follow-ups.

An incident response commitment with a number in it. Notification within a stated number of hours, to a stated contact, with a stated escalation path. The commitment matters more than the sophistication of the plan behind it.

Underneath all three sits the actual prerequisite: a diagram of where data enters, where it rests, where it is processed, where it leaves, and how long each copy persists. If you cannot draw it, you cannot answer honestly, and answering dishonestly is a much worse day later.

The questions that did not exist three years ago

Modern questionnaires now carry a section that is specific to this category, and it is worth preparing real answers rather than reassuring ones.

• Is our data used to train models? The answer needs to be a contractual commitment that flows through to your provider terms, not a setting somebody toggled. Buyers increasingly ask you to evidence it.
• Where is inference performed? A geographic question with regulatory consequences. Know the answer for every provider and every routing path, including the cheap tier you added last month.
• What is retained at the provider, and for how long? Including any abuse monitoring retention, which is frequently longer than teams assume.
• Does a human ever review the content? Under what circumstances and with what controls.
• How do we learn when the model changes? This connects directly to Lesson 13. A buyer in a regulated function needs to know that the thing they validated is the thing that is running.
• How is the system classified under applicable AI regulation? European obligations in particular now impose documentation and transparency requirements that vary with the risk category of the use case. Treat this as an architecture question rather than a legal one, because the answer determines what you have to log and that is not something to retrofit.

Saying no honestly is a stronger position than founders expect

The instinct when the spreadsheet arrives is to make every answer as green as possible. It is the wrong instinct, and reviewers are extremely good at detecting it.

The position that works is honest maturity. We do not hold a Type II report. Our observation period began in March and completes in September. Here is our current control set, here is our independent penetration test from last quarter, and here is what we are willing to commit to contractually in the interim.

Buyers accept that far more often than founders anticipate, because every security reviewer has dealt with small vendors before and what they are assessing is partly whether you are the kind of company that tells them things. The answer they will not forgive is the one that turns out to have been optimistic, discovered during an incident, when the conversation is no longer about procurement.

We lost that first deal. Not because of the answers, but because the elapsed time we needed did not fit inside their quarter. The work we did to answer the sixty questions properly meant the next one, five months later, took nine days.

Trust has a lead time. Start it before the deal that needs it.

Tomorrow: the job description you wrote and did not post.

Print the architecture diagram. Take a pen. Cross out the box in the middle, the one with the model provider’s name on it, and everything that connects directly to it.

Now look at what is left standing on the page.

That is the exercise, and it takes about four minutes. The first time we did it, the remaining diagram was noticeably thin, and there was a silence in the room that told me everybody had reached the same conclusion at the same speed.

Whatever survives that pen is the company. Whatever falls over was rented, and rented on terms set by somebody else.

What survives

Six things, in rough order of how hard they are to reproduce.

The data you accumulated by operating. Not licensed data, which your competitor can license too. The record of what your product suggested, what the user accepted, what they corrected it to, and what turned out to be right three weeks later. This exists only because you ran, it is impossible to buy, and it is the reason the same architecture in your hands and a competitor’s hands produce different products after eighteen months.

The integrations. Reaching into the systems where work already lives, reading real state, writing back correctly, handling the version of that system from four years ago that your customer still runs. It is slow, tedious, unrewarding work. It is a moat for exactly those reasons.

The evaluation harness and the golden set. This one surprises people, and it should not. That spreadsheet from yesterday encodes months of accumulated domain judgment about what a correct answer looks like in your specific field, contributed by practitioners, refined by incidents. A competitor with unlimited engineering cannot generate it. They have to earn it the same way you did, and it takes the same amount of time.

The workflow state. Approvals, audit trails, who saw what and when, what happens when the approver is away. This is the difference between a capability and something a business can actually operate, and it is the substance of what makes a product hard to remove.

The regulatory position. Certifications you hold, agreements you have signed, jurisdictions you can serve. These take months of elapsed time that cannot be compressed with money or effort. Tomorrow’s subject.

Cost engineering. A twenty point gross margin advantage over a competitor selling something similar is a strategic asset, not a finance detail. It lets you price lower, spend more on acquisition, or survive a downturn that removes them. Routing, caching and context discipline are not housekeeping. Compounded, they are a moat.

What does not survive

It is worth being blunt about the things founders describe as differentiation which are not.

Prompts. A prompt is copyable in one screenshot and can be obsoleted by one model update. Prompt engineering is a skill, and skills are not moats. If your defensibility discussion involves the phrase our prompts, there is no defensibility discussion.

Feature sets. Parity now takes weeks rather than quarters. A feature list is a snapshot of who shipped most recently.

Being early. Being early is a head start. Head starts are valuable and they expire. The question is what you converted the head start into while you had it, and for a lot of companies the honest answer is more features.

Your choice of model. Whatever you picked, your competitor can pick it too, this afternoon.

Design for portability, deliberately

The practical consequence is an abstraction layer between your application and whichever provider serves your inference. Not for architectural elegance. For three concrete reasons: you can move if pricing changes, you can route between tiers for margin as described in Lesson 7, and you can keep operating if a provider has an incident during your customer’s business hours.

There is a real cost and it should be stated rather than glossed. An abstraction that reduces every provider to a common denominator throws away the distinctive capabilities that made you choose one in the first place. Providers differentiate, and the differentiated parts are frequently the useful parts.

The rule I have settled on is to abstract the interface but not the capability. Standardize how you call, log, retry and measure, so that swapping is an engineering task rather than an archaeology project. Then, where a specific provider capability genuinely gives your product something, use it deliberately and write down what you would lose and what the fallback is. A dependency you have chosen and documented is a decision. A dependency you drifted into is a liability that surfaces during a pricing negotiation you did not expect to have.

The uncomfortable version of the exercise

Sometimes you cross out the box and very little remains. At month six that is completely normal and not a cause for alarm. You have not had time to accumulate anything yet.

At month thirty it is the most important fact about your company, and it will not be fixed by shipping faster.

The move is to treat the moat as a deliverable rather than a hope. Pick the two items from the surviving list that are most achievable in your situation, put them on the roadmap with dates and owners, and protect that work from the customer request that arrives on Thursday. Data capture is usually the cheapest and highest return, because it costs almost nothing to log and cannot be reconstructed retrospectively. Integrations are next, because they are pure elapsed time and the earlier you start the further ahead you are.

Nobody will ask you for this work. No customer will thank you for it. It is the difference between a company and a very good implementation.

Ask what you would have to rebuild if you switched model providers on Monday. Whatever is left is the company.

Tomorrow: the security questionnaire, and why trust has a lead time.

The golden set is a spreadsheet with about two hundred rows. Each row has an input taken from real usage, the output a competent human produced for it, and a short note on why that output is right. It is the least impressive artifact this company has ever produced. Nobody has ever asked to see it in a meeting.

It is also the only reason we found out, on a Tuesday in the middle of an otherwise ordinary month, that the product had been getting worse for eleven days.

Nobody had deployed anything. Nothing had broken. The model underneath had been updated, quality on one category of task had moved, and every dashboard we had was green because every dashboard we had measured uptime, latency and error rates. All three were excellent. The product was worse and the instrumentation had no opinion about it.

A problem with no equivalent in ordinary software

Conventional software is deterministic. The same input produces the same output, so a regression is a failing test and a failing test is a red build. The whole discipline of continuous integration rests on that property.

An AI product does not have it. The same input produces different outputs. Worse is not a boolean, it is a movement in a distribution, and you cannot detect a movement in a distribution without a reference point.

There is a second difference which is stranger and which founders reliably underestimate. Your product can change without you changing it. The capability you built on is maintained by somebody else, on their schedule, for their reasons. A model update can improve nine things and degrade the tenth, and the tenth might be the one your customers actually bought.

In ordinary software, the ground does not move. Here it does, and you need an instrument that notices.

What a golden set actually is

One hundred to three hundred real cases, drawn from real usage, each with an output that somebody competent has agreed is correct.

Four things make the difference between a useful one and a decorative one.

It is built by the person who does the job, not by an engineer. The engineer knows what the system does. The practitioner knows what right looks like, and those are different pieces of knowledge. If you have design partners from Lesson 6, this is one of the most valuable things to ask them for, and it is a reasonable thing to pay for.

It contains the hard cases deliberately. A set made of representative examples tells you about the average, and the average was never the problem. Include the ambiguous inputs, the malformed ones, the ones where two answers are defensible, and the ones where the correct behavior is to refuse or escalate. That last category is the one most sets omit and the one that matters most for an accountable product.

It is versioned like a product asset. Not a file in a test directory. It has an owner, it grows when incidents reveal a gap, and every entry records who decided and when.

It is small enough to run constantly. Two hundred cases you run on every change beats two thousand you run quarterly. The value is in the frequency.

Three gates, on every change

Once the set exists, it becomes a gate, and it should sit in front of three questions rather than one.

Quality. Score the change against the golden set. Block on any regression beyond an agreed threshold. Not a warning in a log, a block.

Cost. Compute cost per query for the new path and compare it against the current one before merging. A feature that improves quality by two percent and raises cost per query by four hundred percent is a decision somebody should make consciously. Without this gate, that decision gets made by an engineer at eleven at night and discovered by you in an invoice.

Latency. The same discipline. A change that adds two seconds is a product change even if nobody wrote a product ticket.

The critical scope point: these gates run on changes to prompts, retrieval configuration and model selection, not only on changes to application code. A prompt is code. It is the most frequently edited and least reviewed code in most AI companies, and it is routinely modified directly in production environments by people who would never do the same to a function.

Scoring without pretending

Exact matching works for extraction and classification. It does not work for anything generative, and pretending otherwise produces an evaluation that punishes correct answers for being phrased differently.

The practical approach is rubric scoring with a model acting as judge: define what a good answer contains, have a model grade against that rubric, aggregate. It is fast, it is cheap, and it works well enough to be genuinely useful.

It is also biased in ways that are easy to forget. Models grading models tend to reward fluency, length and confidence, which are three properties of exactly the output described in Lesson 12. So two safeguards are not optional. Sample a fixed percentage for human review every cycle and budget the hours properly. And track the rate at which the humans disagree with the judge. That disagreement rate is your instrument for whether your instrument still works, and when it drifts you have an evaluation problem rather than a product problem.

Pin your versions

Two habits close the loop on the eleven day problem.

Pin explicit model versions rather than accepting whatever the latest alias resolves to. Then, when a new version appears, run the golden set against it, look at cost and latency alongside quality, and adopt it as a deliberate change with a date attached.

And log the model version, prompt version and retrieval configuration with every single request. When a customer says it used to do this correctly, that logging is the difference between a two-hour investigation and a fortnight of theories.

Building this before the demo feels wrong. The demo is what gets you the meeting. But the demo is a claim, and the harness is the only thing that lets you keep making the claim after the fourth model update, the second retrieval rewrite and the day you route half your traffic to a cheaper tier to protect your margin.

If you cannot detect a regression, you do not have a product. You have a demo that has not broken yet.

Tomorrow: the architecture diagram, and the question of what you would have to rebuild on Monday.

The churn email was four lines long and entirely polite. They were not renewing. The team had enjoyed working with us. And then the sentence that took a while to stop thinking about: the output was fine, but the team had started pasting things into a general assistant instead because it was faster.

Not the output was wrong. Not it was too expensive. It was fine, and fine was available elsewhere at no cost.

That is the actual mechanism of slop, and it is not an aesthetic complaint. Slop is a commercial condition.

A definition that is actually useful

Slop is not bad output. Bad output is easy to detect and easy to fix, and customers will tell you about it loudly.

Slop is output that is fluent, plausible, competently structured and completely substitutable. It reads well. It is not wrong. It could have been produced by anybody with access to a general purpose model and ten minutes.

The distinguishing property is not quality. It is substitutability. That is why slop is a distribution problem: it does not damage your reputation, it damages your reason to exist. Customers do not leave angry. They leave the way that email left, politely, having found the same thing on a shorter path.

Three places it lives

In the product. The dangerous property here is that product slop does not hurt acquisition at all. Acquisition is driven by the promise, and the promise demos beautifully. Slop hurts retention, exclusively and on a delay, which means your dashboard looks healthy for two quarters and then does not. If your churn is concentrated at the four to six month mark among engaged users, this is the first thing to check.

In the codebase. Yesterday’s subject. Code that is syntactically clean, passes linting, compiles, and encodes no judgment about the system it lives in. It is the same failure in a different medium: plausible, fluent, undifferentiated, and expensive later.

In the marketing. The most common and the least examined. Content production used to be a genuine moat because it was expensive: you needed writers, editors, subject knowledge and time. All of that collapsed. Which means volume is no longer an advantage, because your competitor has the same collapse available to them.

Publishing a great deal of competent, undifferentiated content in 2026 is paying for noise. Worse, it trains your audience that your name is attached to things not worth reading, which is a hard association to undo.

The substitution test

There is one exercise I recommend to everyone and almost nobody wants to run.

Take ten real tasks from real customer usage. Have somebody outside the product team complete them twice: once with your product, once with a general purpose assistant and a well-written prompt. Then show both sets of results to a customer without telling them which is which.

You are not looking for a win. You are looking for whether they can tell. If they cannot reliably distinguish the two, your differentiation lives entirely in convenience and interface, and you should read Lesson 5 again before spending another quarter on features.

Most teams avoid this test, and the avoidance is itself informative. It is a cheap experiment with a high information yield, which is exactly the profile of an experiment people skip when they suspect the answer.

What the opposite looks like

Four properties, and they are all consequences of decisions rather than of model quality.

• It is specific to this customer. Their data, their history, their naming conventions, the constraint they mentioned in month two. A general model cannot produce this because it does not have the inputs. This is the data asset from Lesson 5 doing its job.
• It knows what it does not know. Output that flags uncertainty, declines to guess, or routes to review when the confidence is low. This is genuinely difficult to build, it is what an accountable product does, and it is the property customers cite most often when explaining why they trust one tool over another.
• It is short. Slop is verbose because verbosity is free and length signals effort. Concision requires a decision about what matters, and a decision about what matters requires knowing the domain. Length is the most reliable surface indicator of undifferentiated output.
• It encodes an opinion. Somewhere in the product there should be a judgment you made about how this work should be done, which a general tool would not make because it has no stake in the outcome. That opinion will lose you some customers. It is also the reason the others chose you.

Three ways this goes wrong

You respond to slop by adding features. The instinct when retention softens is to ship more. If the underlying problem is substitutability, more features produce a larger substitutable product. The fix is depth in one place, not breadth across five.

You measure satisfaction instead of substitution. Satisfaction scores stay high right up until the churn email, because customers are satisfied. They are just also indifferent, and no standard survey question distinguishes those two states. Ask instead what they would do if you disappeared on Monday. The answers cluster into we would have a serious problem and we would manage, and only one of those is a business.

You let volume stand in for differentiation in your marketing. Publishing five undifferentiated pieces a week costs you time, budget and reputation, and returns nothing that compounds. One piece a month containing something only you know, because you operate the product and see the data, is worth more than all five, and it is the thing that gets cited rather than skimmed.

We won that customer back eventually, though not with the same product. What changed was that the output started carrying information from their own history that a general tool had no way to reach. It was less impressive and considerably harder to leave.

If a model can produce your output, it will produce your competitor’s too. Sell the part it cannot.

Monday: the golden set, and how you find out your product got worse.

The pull request was fourteen hundred lines across nine files. The description said add user flow. It was approved four minutes after it was opened, by somebody who was in a meeting at the time, and it went to production that afternoon.

Nothing bad happened. That is the important part. Nothing bad happened for about eleven weeks.

I want to be careful here, because there is a lot of moralizing about this subject and most of it is written by people who are not shipping anything. The productivity gains are real. Teams report forty to sixty percent improvements on bounded tasks and I believe them, because I have seen it. The problem is not the tool. It is that a tool designed for exploration keeps getting promoted into a role it was never designed for, and the promotion happens silently.

What the data actually says

The most careful measurement available comes from an analysis of two hundred and eleven million lines of code changed between 2020 and 2024 across repositories at large technology companies. Two findings matter.

Copy-pasted code rose from 8.3 percent of changed lines to 12.3 percent, a relative increase of roughly half. Over the same period, refactored lines fell from around twenty-five percent to under ten percent. In 2024, for the first time on record, copy-pasted code exceeded refactored code.

That inversion is the whole story in one statistic. Refactoring is how a codebase stays comprehensible. Duplication is how it stops being comprehensible. The tools made it cheaper to add and no cheaper to consolidate, so the ratio moved, and it moved in the direction that compounds.

A separate study of around eight million pull requests found technical debt rising by thirty to forty percent after teams adopted AI coding tools. And in a detail I find quietly telling, the researcher who coined the term vibe coding in early 2025 had, by early 2026, publicly described it as past its moment and shifted to advocating a model with substantially more human oversight in the loop. The phrase did not survive its first year before its inventor moved on.

Where the line goes

The useful framing is not whether to use these tools. It is which code is allowed to be produced this way.

Generate freely. Interface components, internal dashboards, one-off scripts, data migrations you will inspect anyway, test fixtures, prototypes, anything you intend to throw away, anything with no access to production data. This is the majority of code by volume and the speed gain here is close to free.

Never without dedicated review and automated analysis. Authentication. Authorization, which is a separate and more frequently broken thing. Payment handling. Anything touching personal data. Anything that writes to production. Anything that decides what a user is allowed to see.

The failure modes in that second category are boringly consistent. Across incidents reported through 2025 and into 2026, the same handful of causes recur: databases left open by default configuration, row-level security never enabled, keys hardcoded into code that reaches the client, backend services exposed without authentication. None of these are exotic. All of them are the kind of thing that a generated solution produces because it satisfies the request as stated and nobody stated the rest.

The ninety-day reckoning

There is a recognizable arc and it runs on roughly a quarterly clock.

Weeks one to four, velocity is extraordinary and everybody is delighted. Weeks four to ten, small inconsistencies accumulate: three different ways of handling errors, two competing patterns for the same operation, functions that do four things because it was easier to extend than to separate. Around week ten to twelve, the first incidents arrive, and they are hard to diagnose because nobody wrote the code and the person debugging it is reading it for the first time under pressure.

By day ninety, teams commonly report spending twenty to thirty percent of sprint capacity on defects traceable to generated code. The velocity gain from month one is gone. Then it goes negative, because every subsequent change is harder in a codebase nobody trusts.

This is now a market. Rescue engineering, the business of taking a product that was built quickly and rebuilding it into something maintainable, is a recognized specialty with recognized pricing, commonly quoted between fifty thousand and five hundred thousand dollars depending on how long the product ran before somebody looked underneath it. Of the several thousand startups that shipped production applications using these tools through 2025, a large majority reportedly needed some form of partial rebuild or rescue work within the following year.

The cost is not the rebuild. The cost is the six months you spend doing it instead of building.

The protocol that actually works

Five rules, and none of them require slowing down much.

• Somebody must be able to explain it. This is the only rule that really matters. If nobody on the team can explain how authentication works without opening a chat window, you do not have authentication. You have an arrangement that has not yet been tested.
• Cap diff size on anything sensitive. A fourteen hundred line change is not reviewable and everybody knows it, which is why it gets approved rather than read. Small changes get read.
• Static analysis on every path that handles credentials, permissions or personal data. Automated, in the pipeline, blocking. This costs nothing per run and catches the recurring failures listed above.
• Write the tests by a different route than the code. Generated code validated by generated tests derived from the same description will agree with itself confidently. Specify the tests from the requirement, not from the implementation.
• Keep your junior engineers and give them maintenance work. This one is strategic rather than tactical. The people who will be able to maintain generated systems in two years are the people who spend this year reading and modifying code they did not write. That is exactly the work that is being automated away from them, and teams that eliminate it are removing the pipeline for the skill they will most need.

We did eventually go back and read the fourteen hundred line change. It was mostly fine. It also contained a permission check that ran on the client and not on the server, which meant the check was a suggestion. Finding it took an afternoon. Finding it after somebody else had would have taken considerably longer and involved a lawyer.

You can ship code you do not understand. You cannot run a company you do not understand.

Tomorrow: the churn email, and the three kinds of slop.

The runway model is one tab in one spreadsheet and there is exactly one cell in it that anybody actually looks at. Everything else exists to produce that cell. It contains a month and a year, and once you have seen it you cannot unsee it.

For a long time I treated that cell as the deadline. It is not the deadline. It is roughly six to nine months after the deadline, and confusing the two is how founders end up negotiating from a position where the only honest answer to how much runway do you have is a number that makes the terms worse.

The real deadline is earlier than the cell

Raising money takes time. Building a list, first meetings, partner meetings, diligence, documents, close. Three months is fast. Six months is normal. Longer is common and not a sign of failure.

You also cannot raise well with two months left. Investors ask, you answer, and the conversation changes shape immediately. Not because anyone is cruel, but because a company that must close in six weeks has a different set of options than one that could walk away, and everybody in the room understands that.

So the working deadline is the money-out month minus the fundraising duration minus a buffer. If your cell says November and raising takes five months, your real deadline is around April, with the assumption that you will not be building product in April. Founders consistently discover this in month three of a raise.

The twenty-month problem

There is a specific timing assumption baked into a lot of seed-stage plans and it has quietly stopped being true.

The median gap between closing a seed round and closing a Series A has stretched considerably, on recent measures to around twenty months. That is a substantial change from the twelve to fifteen month planning assumption most founders inherited from earlier cohorts, and it is not a temporary market condition so much as a rise in the bar. Series A now expects repeatability, typically somewhere in the range of one to three million in annual recurring revenue with evidence that acquisition can be repeated rather than recounted.

The arithmetic follows. If you raise a seed and plan twelve months of runway to reach a Series A that on average arrives at twenty, you have planned a crunch and scheduled it for a moment when you will also be trying to sell. Plan for twenty-four to thirty months, which usually means either raising more or spending less, and spending less is the option you control.

Two clocks, running at different speeds

Here is the modeling error I see most often, and I made it myself: one burn number.

An AI company has two kinds of burn and they behave nothing alike.

Headcount burn. Salaries, contractors, the tools people need. You control it completely. It moves in steps, because hires are discrete events. It is sticky in the downward direction, both practically and morally. It is almost perfectly forecastable, which is why finance people love it.

Compute burn. Inference and everything metered per request. Your customers control it. It moves continuously, it is only partly forecastable, and its defining property is that it rises when things go well.

Blend those into one line and you get a number that is wrong in both directions. It understates your risk in a good month and overstates it in a quiet one.

The scenario worth modeling explicitly is the uncomfortable one. Growth accelerates. Usage deepens. Compute burn rises immediately, because inference is consumed the moment the work happens. Revenue lags, because you invoice monthly or quarterly and business customers pay on their own schedule, which is thirty to sixty days after that. For a period of weeks, sometimes months, your runway is getting shorter precisely because you are winning. Nobody who learned software finance in the subscription era expects that shape, and it has caught out companies whose only mistake was growing quickly.

The number investors will ask for

Growth rate on its own has stopped being a sufficient answer, because anybody can buy growth. The question now is what the growth cost.

Burn multiple is net cash burned divided by net new annual recurring revenue over the same period. If you burned two million and added two million of net new recurring revenue, your burn multiple is one. Below one is excellent and rare. One to one and a half is a good business. Above two needs an explanation, and above three needs a plan rather than an explanation.

It is a better question than growth because it is difficult to flatter. It captures pricing, retention, sales efficiency and cost of goods in a single ratio, and it penalizes exactly the behaviors that look like traction and are not.

Calculate it quarterly. Show it before you are asked, because a founder who volunteers their burn multiple is telling the room something about themselves independent of the number.

The question almost nobody calculates

If you never raise another round, and your current growth rate and current cost trajectory continue, do you reach profitability before the money runs out?

That is the whole question. It has a yes or no answer and it takes an hour to compute properly. In my experience most founders have never done it, and a meaningful number of them assume the answer is no when it is actually yes with two decisions changed.

What makes it valuable is not the answer. It is what it does to the conversation. A founder who knows they can survive without raising is negotiating. A founder who does not know is hoping. Investors can tell the difference within about ten minutes, and it is the single largest determinant of terms that founders treat as unchangeable.

Three ways this goes wrong

You model revenue as booked rather than collected. Signed is not invoiced, invoiced is not paid, and the gap between them is where small companies die with healthy-looking pipelines. Model cash, on the date it arrives, with realistic terms.

You cut compute instead of headcount, or headcount instead of compute, without checking which is which. Under pressure teams reach for the lever that is easiest emotionally rather than the one that is largest. Compute burn is frequently reducible by thirty percent or more through routing and context discipline, without anyone losing a job. That work should be done before any conversation about people, and it usually is not.

You update the model quarterly. Cost per query moves weekly, prices move, and one shipped feature can change your unit economics overnight. A runway model refreshed four times a year is a historical document. Monthly is the minimum, and the person who maintains it should be a founder, not somebody a founder asks.

Headcount burn you control. Compute burn your customers control. Model them separately.

Tomorrow: the pull request nobody reviewed, and the ninety-day reckoning that follows it.