Jeff Bezos pushed back from his chair and told Anthony Reeves to throw away six weeks of work. Reeves should come back in four to six months, Bezos said, once he understood how Amazon worked. Then he should write the document again from the customer’s point of view: what Amazon would deliver for her, rather than what Amazon could build and monetize. Bezos left before Reeves said a word.

Amazon had hired Reeves in 2015 to run creative for Amazon Media Group. His team had flown colleagues in from around the world to produce a Working Backwards memo, the six-page format Amazon calls a PRFAQ. Reeves wore a collared shirt instead of his usual untucked T-shirt. A container of red Bic pens sat alone on the light grey table.

Because Amazon meetings open with silent reading, Reeves spent thirty minutes listening to pens scratch and people grunt over the pages. In Eat the Donkey, he says he suffocated in the silence.

His thesis was right: Amazon should pursue brand advertising alongside retail and search. In its 2015 annual report, Amazon reported $1.02 billion from everything outside retail and AWS, a category that combined advertising with its co-branded credit card business. By 2025, advertising services alone brought in $68.6 billion.

The analysis held up, but the memo failed because its four sections covered the revenue opportunity, competitors, technical capabilities, and market size, so every page described Amazon. Reeves had spent twenty years in agencies learning to understand customers, yet his training had produced an excellent answer to the question founders find easiest to ask: what can our company sell?

The questions your board asks point inward

Your board wants to know what you can build, which assets you can reuse, and how large the market is. It can run through those questions before lunch, and each answer gives you a number or a slide. Together they assume the world already cares what your company can do.

Agencies have an industrial version of the same mistake. A brief starts with what the client wants to say, and the team finds ways to make people listen. The customer appears as a persona, which lets everyone sell to her without thinking about her. A seed deck often does the same work in different vocabulary, opening on the architecture and reaching a human somewhere around slide nine.

The dangerous part is that a spreadsheet and thirty customer conversations can produce artifacts that look identical: six confident pages, numbers, and a recommendation. The difference sits upstream in how you gathered the evidence. I’ve argued that the argument that decides your deal is a secondhand version of yours, repeated from memory in a room you never enter. A pitch written entirely inside your building gives the buyer little she can repeat.

Thirty conversations changed the document

Reeves spent the next five months with Amazon’s retail teams, sellers who already bought ads elsewhere, and agencies trying to spend money on Amazon. He visited distribution centers and kept asking what worked, what failed, and what sellers wished they could do on Amazon.

Your interviews need the same discipline because describing the product and asking whether someone would use it turns the customer into a grader for your idea. Ask her to reconstruct the last time the problem occurred, including what she did next, whose budget paid for the workaround, and what happened when nobody fixed it. Her answers describe behavior that already occurred. A founder needs evidence strong enough to cancel a roadmap item, and polite enthusiasm rarely clears that bar.

The answers described outcomes. “We can offer targeted display advertising” became “sellers want to help shoppers find products they didn’t know to look for.” “We can provide detailed analytics” became “sellers want to know which buyers come back and which buy once.” Although the underlying capability stayed the same, the new language named a person and a job she needed done, so teams could decide what to build.

CarMax began with the same discipline when it started in 1993 around one observation about how people feel in a dealership: they hate negotiating. CarMax built the business around posted prices and sold $25.9 billion of used cars in in FY 2026.

Founders like to pitch big markets because they look good in the deck. A better measure is what customers already spend to solve the problem. If they’re paying for a workaround in money or time, the problem is real enough to act on. I’ve argued that a wedge is one problem somebody is already paying to work around, and you have to leave your building to find it.

Five months later, Reeves carried a second six-page memo into a smaller room. This version explained what advertising on Amazon would do for a shopper. The silent read became a conversation about what Amazon should build, with customer outcomes guiding the revenue opportunity.

The pressure to ship distorts what you hear

Customer obsession may appear on your careers page and in your investor update. Your operating calendar keeps dragging attention back to the company.

The board meets every quarter and the next round has a date attached. Soon the governing question becomes what you can show by then, even though customer problems don’t arrive on your financing schedule. The same pressure reaches your first rep, whose compensation depends on a number due this quarter. I’ve never met a good salesperson who was confused about which deadline wins.

What you’ve already built exerts its own pressure: the codebase, the demo that closes, and the architecture you described to investors. Building around those assets feels responsible until customer evidence tells you that eighteen months of engineering solved the wrong problem. When we called Mesosphere’s product a Data Center Operating System, we aimed at a larger budget line. The description was accurate, but it grew from what we already had and held for about eighteen months, until Kubernetes was free and we weren’t.

Your data adds another pull because nearly all of it describes your company: signups, activation, funnel stages, and usage logs. Customer frustration lives in sentences nobody has collected, so you improve what you can measure while the evidence that could change your strategy never enters the system.

The correction gets more expensive every quarter

Thirty customer conversations aren’t something a founder delegates. The person who may have to change the strategy needs to hear the sentences herself. A research firm returns a deck, leaving you with one more document to interpret. Doing the work costs founder time this quarter and may produce nothing you can show in the first month.

The work also adds cycle time, and Reeves spent five months correcting course because Amazon could afford the wait and Bezos stopped the first memo. A startup usually sends the deck, builds the product, and lets the market reject the argument. By then the correction costs quarters of runway instead of weeks of rework.

A rare capability may have to exist before any customer can ask for it, but the discipline still applies: ask early who needs it and accept that the answer may be nobody yet. Customers can’t design your product for you; a good interview gives you a workaround, the frustration behind it, and its price. Turning those facts into something worth buying remains your job.

Every forecast review I’ve sat in had at least one deal in it that was going to close because the customer liked us. The champion was enthusiastic. The demo went great. The notes in the CRM read like fan mail. And then the quarter ended and the deal didn’t, and nobody could say exactly why, because the reason was discussed in a meeting nobody from our side attended.

That’s the standing condition of any purchase big enough to need approval. Somewhere inside the buyer’s company, a buying group whose members have never all been in a room with you will decide whether to spend money on your product. The version of your argument that gets made in that meeting is whatever one of them remembered, edited down to what they’re willing to say out loud in front of their boss.

Matthew Dixon and Ted McKenna studied more than 2.5 million recorded sales conversations and reported in Harvard Business Review in June 2022 that 40 to 60 percent of deals end lost to customers who say they intend to buy and then fail to act. They trace it to indecision: the buyer’s own fear of choosing wrong, which nobody inside the company is willing to absorb on your behalf.

Who can stop the purchase

Robert Miller and Stephen Heiman, writing with Tad Tuleja in Strategic Selling in 1985, sorted members of the buying group into four types of influence: an economic influence that gives final approval, a user influence that lives with the product, a technical influence that screens suppliers out, and a coach on the inside. Their instruction was to start “by looking not for people, but for roles.” Forty years later the titles have changed, but the roles are still there.

What’s changed is that the buying group has grown and the veto has spread across its members. Procurement shows up to squeeze the price. Legal shows up to redline a contract that was fine last year. Behind both of them sits a security review with its own queue, its own standards, and no particular interest in whether anyone at the company wants your product. Each of them can stop the purchase and none of them can approve it.

Add a member and you’ve added a way to die without adding a way to close, which is why the cycle stretches as the deal gets bigger.

The members also disagree about what counts as a good reason, because each one answers to a different boss and gets measured on a different number. A change that helps one of them lands on someone else’s ledger as a cost. The return-on-investment model that settles the finance conversation bores an engineer into suspicion. The architecture walkthrough that wins the engineer loses finance inside a minute. Pitch the average of the room and you persuade nobody, since a buyer wants their own blocker removed, and a general account of why your product is good doesn’t remove it.

Companies have bought this way for as long as anyone has sold to them. I’ve argued before that the single hand raised on a single form is a poor proxy for a decision that ten or twelve people actually make, and that the honest metric is how far into that group you’ve reached. You can reach the group, and you still won’t be in the room when it decides.

I watched an infrastructure company win an engineering team so completely that its logo went on the customer’s internal wiki as “the standard.” We read that as sold and forecast it accordingly. Then somebody in security sent over a questionnaire asking where the data would physically live, and the deal sat untouched for a quarter while one document got written. The product hadn’t changed. The engineers still wanted it. Nobody had ever assigned that review an owner, and it was holding the decision. Answering it is what closed the deal, roughly ninety days after the forecast said it would.

The blank on your map is almost always security or procurement, and the reason isn’t mysterious. Your call log is built out of people who wanted to talk to you. The people who can stop a purchase have no reason to want to talk to anyone. Draw a map from your own calendar and you get a map of your friends.

The member who wants you to lose

Steve Blank found a member of the group that no map of persuadable people contains. In The Four Steps to the Epiphany, he identifies a group he named himself (his coinage, and he says so in the passage). “I call this group the saboteurs. In every large company, for example, there are individuals and organizations that are wedded to the status quo.”

The saboteur is defending their own position: the headcount, the budget, the system they built and are known for running. Your product working is what threatens it, so a better argument about your product changes nothing that matters to them. And they can’t say so, because objecting to a purchase everyone else wants makes them the obstacle. The refusal gets handed to a colleague with a cleaner reason to raise it and reaches you as a budget concern or a sensible-sounding question about integration risk that nobody can quite source.

Pitch harder and they defend harder. Identifying the saboteur gives you the ability to route around them and to stop reading their silence as agreement. Nobody volunteers the saboteur by name, so you have to ask an insider a faintly rude question: who here is worse off if we win? In my experience people answer it and quickly. They’ve often been waiting for someone to ask.

How to tell a champion from a contact

The person who makes your case when you aren’t there has a name in every sales framework. MEDDIC calls them the Champion and makes them one of six things a salesperson has to establish before a deal counts as qualified. Miller and Heiman call them the Coach. None of them tells you how to work out which person it is.

People show you where they stand by what they’re willing to spend. Warm words in a meeting are free, and people give them away to be pleasant. The champion’s work is done when you aren’t there to see it: your one-page summary forwarded without being asked, a warning about the other members that nobody was obliged to give you (legal will care about data residency, get ahead of it), and an internal thread you had no way of knowing existed and are suddenly on. Each of those costs the champion a little of their own standing, and you can’t buy it or reimburse it.

When somebody inside vouches for your product, they attach their own judgment to it in front of people who will remember. If a claim you made falls apart under their manager’s questions, you lose a deal and they lose standing they need for everything else they do there, which is much the worse end of the trade. That is why overselling to a new champion works against you: it raises the odds they get caught holding a claim they can’t defend, and once that happens they stop spending on you. Telling them plainly what your product doesn’t do yet is what keeps them able to speak for you at all.

One moving part

You can’t appoint a champion. What you can do is make it easy for somebody to look smart in front of their boss. You can’t direct what they say in the room. Usually the outcome is all you get. Their candor is what preserves their capacity to advocate.

Every other input in a go-to-market plan is something the company owns or buys and can therefore fix when it breaks. This one is on loan from a person with a manager and a career of their own, who owes you nothing and can stop at any point without telling you or leave the company entirely and take your argument out of the building with them.

The repair is obvious: find a second advocate in a different role while the first one is still there and still enthusiastic and the whole thing looks like it’s going fine. It will feel unnecessary every time, which is why it rarely happens. The moment the need becomes obvious is the moment the opportunity has gone.

Write for the retelling

The argument that decides the deal is a secondhand version of yours. So the thing worth working on is how well it survives being repeated by somebody else, from memory, to a skeptical audience in about ninety seconds.

That changes what you make. Build the one page they can forward without editing it. Give them the number they can say out loud and defend if somebody asks where it came from. Make sure they can answer the hard objection alone, in your absence, without calling you first. A demo that only works when you’re driving is not evidence they can use.

Then check it: could this person defend the purchase for two minutes with you out of the building? If they can’t, more meetings won’t help, because a meeting puts the argument back in your mouth instead of theirs. It’s why the best sellers I’ve worked with spend so much time on things that don’t look like selling. They’re getting one person ready for a conversation they’ll never hear about in a room they were never going to be in.

Some markets depend on shared infrastructure, but no participant can own it without the others refusing to use it. Cloud providers all needed the same way to run containers across a fleet of machines. Banks needed a payment network that reached past their own customers. Manufacturers needed a safety mark that buyers would believe, which ruled out any mark a manufacturer owned.

The reason is ordinary commercial self-defense. Build your product on a competitor’s platform and that competitor sets the rules you operate under, watches what you’re doing while you do it, and can change the terms whenever changing them pays. So you refuse, even though you can see that the shared layer would grow the whole market and your own business with it. Everyone else in the market does the same arithmetic and refuses too.

Either the common ground never gets built and everybody keeps paying for the fragmentation, or an interested party builds it and the others quietly route around it. The second happens more often, and it costs more. One company controls the shared system, so everyone else spends engineering time building workarounds to reduce their dependence on it. Imagine one cloud provider owns the software everyone uses to manage containers. Its rivals may support that software, but they will also build adapters, alternatives, and backup systems so the owner cannot dictate how their customers operate.

A better product cannot solve this trust problem. More features, lower prices, or stronger performance do not change who controls the system or what that owner might do later. Participants will choose the organization whose rules and governance prevent it from favoring itself, even if another product is technically better.

In this kind of market, giving up control is what makes the shared system valuable.

That cuts against most of what B2B strategy has been telling operators for the past several years, which is to own the platform, hold the data, and convert a partner network into a captive audience. I’ve argued here before that the classic fortresses are eroding: switching costs, proprietary technology, and data advantages don’t hold the way they used to. Neutrality is the strange exception. It’s a moat made entirely of powers you give away, and it holds because you can’t take them back.

Why the better product loses this one

You can build the best shared platform and still fail to become the standard. Choosing infrastructure is a long-term commitment. Before a large customer depends on your platform, they will ask what happens if your interests stop aligning with theirs. If you can change the rules in your own favor, they have a reason not to trust you, no matter how good your software is. They may choose a weaker platform governed by an organization that cannot favor itself.

Google worked this out in public. On 21 July 2015, the day Kubernetes reached 1.0, Google contributed the project as the seed of the new Cloud Native Computing Foundation under the Linux Foundation, with a technical oversight committee and founding members that included Cisco, Goldman Sachs, IBM, Red Hat and VMware.

While Kubernetes belonged to Google, adopting it meant taking a dependency on Google, and every one of Google’s competitors could run that calculation. Under the foundation, companies that would never have standardized on a Google product standardized on the foundation’s. CNCF’s 2025 Annual Cloud Native Survey, published in January 2026, found that 82 percent of container users were running Kubernetes in production.

Google gave up the ability to steer the project alone. What it got back was an industry standard it helped design, running on hardware it sells, staffed by engineers it had trained.

Trust comes from giving up control

Most companies promise to be neutral but stop short of giving up the control needed to prove it. They write the blog post about their commitment to openness, publish a set of principles, and expect the market to treat that as neutrality. It doesn’t, and the reason is easy to see from the outside: the promise costs nothing to make, and the incentive to break it sits exactly where it always sat, with you. Everyone you’re asking to trust the promise can also see the quarter in which breaking it would be worth more than keeping it.

What counts is a structure that makes your own betrayal expensive or impossible. Move the trademarks and the governance to a body you don’t control. Give the participants real votes, including votes that can go against you. Publish guarantees of openness that actually bind you. Every one of those is costly, and the cost is the entire point, because a commitment that would hurt to break is the only kind anybody believes.

Bank of America learned this the hard way with BankAmericard. It had licensed the card to other banks since 1966, and every licensee was a competitor of the owner, which meant every bank was building its card business on rules controlled by a competitor. In 1970, Bank of America gave up control. The issuing banks formed National BankAmericard Inc., a Delaware non-stock corporation the members owned jointly, with Dee Hock running it, and it took the name Visa in 1977. Once no member could tilt the rules against another, the network was finally usable by all of them. Visa reported net revenue of $35.9 billion for the fiscal year ended 30 September 2024.

Bank of America traded ownership of a licensing program for membership in the network the whole industry would end up running on. That trade looks obvious now. It did not look obvious in 1970 to the executives who had to sign it.

The ground sits in very few hands

Safeguards such as independent governance, shared voting rights, and separate ownership of trademarks may seem excessive. But shared infrastructure often depends on a small group of maintainers who decide what gets built, accepted, and released. If one company employs those maintainers or can overrule them, that company still has control, no matter what the governance documents say. The structure has to be strong enough to prevent a handful of people from becoming a back door to control.

Nadia Eghbal’s Working in Public (2020) treats open-source code as public infrastructure and cites a study of GitHub projects finding that in more than 85 percent of them, under 5 percent of the developers accounted for 95 percent of the code and the conversation around it. Her argument is that the scarce resource keeping shared infrastructure alive is the attention of a small set of maintainers.

Buyers care about who controls the technology they depend on. If a few maintainers keep an important project running, buyers will want to know who employs them and who has the power to overrule them. They will also ask basic questions: Who owns the trademark? What happens to the project if its sponsor is acquired? Clear, verifiable answers to questions like these are what make a project safe to adopt and a company worthy of trust.

I’ve spent time on this at the Linux Foundation and in commercial open source. The technical case is usually easy to make: neutral governance can bring in more contributors, partners, and customers. The hard part is deciding what the company must give up to make that neutrality believable. Will it transfer the trademark? Give competitors a vote? Let independent maintainers reject a change that would help its commercial product? Promise that it cannot change the license later? Each concession closes off options the company may want in the future. That is why the hardest conversations are usually internal, with executives being asked to surrender control before the market will trust them with it.

Where the money comes from

Neutrality is valuable because no participant gets special treatment. But that rules out the easiest ways to make money, which usually involve giving your own product an advantage. The workable model is to keep the shared system neutral and sell services around it.

Underwriters Laboratories (UL) has held that separation from the beginning. William Henry Merrill founded the Underwriters’ Electrical Bureau in 1894, paid by insurers who needed to know whether wiring would burn a building down, and the organization has never made the products it tests.

The standards live in a nonprofit, UL Standards & Engagement, which has published nearly 1,700 standards and guidance documents. The commercial arm, UL Solutions, went public on 16 April 2024 at $28 a share, and the nonprofit sold 19.4 percent of it for $1.03 billion net and kept the rest. The commercial company makes money by testing products, while the nonprofit controls the standards manufacturers must meet.

Software companies can use the same model. Keep the shared project neutral, then make money by selling support, certification, hosting, or tools around it. The model breaks when the company uses its control of the project to favor its own products. That might mean putting a feature in the paid product before adding it to the open-source project, or requiring customers to use the company’s tools to earn a certification. Each decision may look small, but together they show that the company can change the rules for its own benefit. Once partners and customers see that, they start looking for a project that no single vendor can control.

What it costs to hold

Choosing neutrality means turning down some easy revenue. When sales are below target, someone will suggest a small change that favors your product and seems unlikely to draw attention.

That pressure never goes away. Every quarter, someone will propose a change that helps the commercial business but weakens the neutral project. Someone else has to say no. The lost revenue is easy to measure; the trust that decision protects is not.

Trust also takes years to build and can disappear after one self-serving decision. If the company takes control of the governance or gives its own product special treatment, participants will see that the promise of neutrality no longer holds. They may leave much faster than they joined.

Neutrality only pays off when competitors need a shared standard, network, or meeting place. If your customers do not need to work with one another, giving up control adds cost without creating much value. So neutrality is first a decision about how the market needs to work, not about how to promote the company. It belongs in the same conversation as whether you’re building the market or inheriting someone else’s.

Give up control to gain the market

Neutrality becomes credible when a company gives up the power to change the rules on its own. Competitors need to know that a new CEO, board vote, or acquisition cannot turn shared infrastructure into one company’s advantage.

Kubernetes, Visa, and UL show what that choice can produce. Their governance gave rivals a shared system they could use without depending on a competitor’s goodwill. Wider participation created more value than any founding organization could have created through sole control.

When a market needs common infrastructure, participants choose the organization whose rules protect them from the owner as well as from one another. Giving up unilateral control is the price of becoming the standard.

Pricing and packaging are hard because most of the evidence arrives after you commit. You have to divide a mixed customer base into plans, decide what each plan includes, and set a price before you can see how buyers will respond. Your go-to-market team then takes the package into the market, where customers expose the assumptions that were wrong.

Changing prices or plans later is expensive. New prices affect pipeline and renewals. New packages can alter existing contracts and the systems that quote and bill them. Sales has to explain the difference. Even sensible changes create work across the company, so teams research heavily, debate fiercely, and leave the package alone as long as they can.

Most of that attention goes to the visible choices, like those on your /pricing page: what each plan costs and the features printed beneath it. Somewhere inside a plan, someone chooses the number of users, messages, projects, or API calls a customer gets before the next tier begins.

That number is a forecast about customer value. It predicts that a customer who reaches the limit has received enough value to pay more. It also predicts that customers below the limit still need room to adopt the product. Both predictions can be tested.

Every gate makes a claim

A single price struggles to serve customers with different budgets and stakes. A price low enough for a two-person team leaves enterprise willingness to pay untouched. A price built for the enterprise shuts the two-person team out. Tiered packaging separates those buyers. Rafi Mohammed’s good-better-best structure gives each edition a job: the entry plan brings in customers who would otherwise buy nothing, the middle plan carries the main offer, and the top plan collects more from customers who need more.

The place to focus is the boundary between two plans. Each boundary has to answer two questions. What changes when the customer crosses it? What has happened in the customer’s business that makes paying more reasonable now? Software companies usually answer the first question with a feature list. Advanced reporting starts here. Audit logs start there. API access requires the plan above. The second question, what changed in the customer’s business, gets much less attention, even though it decides whether the customer crosses the boundary willingly or resents being pushed across it.

Draw the gate where the customer has already gotten value from the product. Tie it to something they can watch growing on their own side: more people doing the work, more records under management, and more administrative control needed now that the product runs something the business depends on. Then the higher bill has a cause the customer recognizes, because they created it.

Three places a gate can go

There are three useful places to draw a gate. Capabilities that create adoption should stay open long enough to do their job. Invitations, integrations, shared spaces, and the basic workflow bring the product into daily use. Closing them too early reduces the activity that every later upgrade depends on.

Capabilities associated with operational maturity can support an entitlement gate. Audit logs, advanced permissions, custom reporting, and administrative controls become valuable after a product is established inside a company.

The smallest customers rarely need them. Larger customers often need them to keep using the product safely.

Capacity can support a different kind of gate. The customer keeps the same basic capability but pays as the amount grows: more pipelines, contacts, projects, storage, or transactions. Use itself moves the account toward the next plan.

HubSpot’s customer platform uses all three. Its free CRM includes contact records and a basic deal pipeline, which lets a small team begin running sales work in the product. Custom reporting and forecasting appear at Professional. More detailed permissions and controls appear farther up the range. Deal pipelines rise as a capacity number: one on Free, two at Starter, fifteen at Professional, and a hundred at Enterprise.

The capacity limit creates its own upgrade moment as the customer’s operation becomes more complex. A feature gate triggers when someone reaches for a missing capability, which may happen long after the account has become commercially valuable. Both can work, but they depend on different customer behavior and should be measured differently. They aren’t interchangeable.

A feature gate should not be justified simply because a capability is valuable or can drive upgrade revenue. It requires evidence that the capability becomes materially more important as a customer grows in sophistication, scale, or operational complexity.

Similarly, a capacity gate should be tied to a unit that increases alongside customer value and has a threshold customers can anticipate. The unit should reflect a meaningful expansion in use—such as active users, transaction volume, managed assets, or automation runs—not an incidental count the product happens to store.

Arbitrary limits are easy to implement but difficult to defend. Charging for a metric simply because it is available in the database can feel punitive, unpredictable, or detached from the value delivered. Strong gates create a clear progression: customers receive meaningful value at lower levels, recognize when their needs have outgrown those limits, and can understand why upgrading is worthwhile.

A customer should see the wall coming

Slack chose message history as a free-plan limit early in the product’s life. History accumulates as a team works, and it becomes more valuable as decisions and files collect inside it. The original threshold was 10,000 messages.

Users reached that number at radically different times. A quiet five-person team could take years to reach it. A busy workspace could reach it in weeks. Customers knew the number but couldn’t predict the date without tracking their own message velocity.

In 2022, Slack replaced the message count with a 90-day window. Every free workspace could now anticipate when a message would disappear from view. Slack later added a second limit: messages and files remain visible for ninety days, but data more than one year old is deleted.

Slack kept the underlying value metric and changed how the customer experienced it. Time made the limit predictable in a way a message count couldn’t. A team deciding whether to upgrade could identify which history it would lose and when.

Visibility requires more than putting a number somewhere in the documentation. The customer needs to know the threshold, see current usage against it, understand what happens at the boundary, and connect the limit to the value they receive. Missing any one of those pieces turns an upgrade trigger into a surprise.

Notion shows the difference between publishing a limit and making it easy to find. Its pricing page says pages and blocks are unlimited for individuals and “limited for 2+ members” on the free plan. The exact threshold appears in a separate help-center article: 1,000 blocks per workspace. A buyer can find the number, but the page where Notion asks that buyer to choose a plan doesn’t disclose it.

An obscure threshold changes customer behavior. Teams share logins, open a second account, divide one workspace into two, or keep work outside the product. The company sees lower conversion while the action that explains it happens elsewhere. Support tickets and cancellation interviews may reveal the workaround before the product dashboard does.

Limits expire

A gate drawn correctly at launch won’t remain correct on its own. The product changes what ordinary users can accomplish. The company moves upmarket. Competitors reset expectations about what belongs in an entry plan. Customers who once needed six months to reach a limit may reach it during onboarding, while another segment may never approach it at all.

Moving a gate creates commercial work. Customers calculated budgets based on the plan they bought, salespeople made promises about what it included, and finance built a forecast from the resulting contracts. A new boundary reopens those decisions across every affected renewal.

That dynamic helps explain why packaging changes often arrive beside price changes. In OpenView’s 2023 SaaS pricing data, drawn from more than 700 companies, half of the respondents had changed both pricing and packaging during the year. A quarter changed pricing alone, three percent changed packaging alone, and 22 percent changed neither. Packaging changes rarely happened on their own in that sample. The data suggests companies revisit their gates when a price exercise forces the discussion.

A standing review makes the discussion cheaper. Give every material limit an owner and examine it every six months. Pull the distribution of customer usage around the threshold, the time each segment takes to reach it, conversion after accounts cross it, and evidence of workarounds. Compare those numbers with the customer behavior that existed when the limit was set.

Feature gates need a parallel review. Measure whether the gated capability now appears during activation, whether salespeople routinely give it away, and whether competitors have made it standard. A feature that once identified a mature buyer can become part of the basic product customers expect.

Each review should end with a decision to keep, move, or remove the gate. Moving it requires a transition plan: notice, grandfathering where appropriate, and a clear explanation of what changed in the product or the customer’s use. Document the changes clearly. The goal is to avoid forcing the next pricing project to reconstruct the reasoning from old comparison tables and scattered memories.

Every threshold on a pricing page is a public claim about the customer on either side of it. The company is saying that one customer is still getting started while another has reached the point where paying more makes sense. Usage data can test that claim long before a pricing crisis does.

Before the next debate about plan names, find out who chose the numbers inside them, what customer behavior supported the choice, and when anyone last checked. If the evidence has disappeared, the gate is running on an inherited assumption. Schedule a review of the assumption and determine whether it still reflects your current customers.

Gates should grow with the customer

A pricing page is not just a menu of plans. It is a set of promises about how customers grow, where value accumulates, and when paying more becomes fair. The strongest gates make those promises visible, testable, and revisable.

Treat every limit as a hypothesis, not a permanent rule. When customers can see it coming and recognize the value behind it, a gate supports both adoption and expansion. When they cannot, it becomes friction disguised as packaging.

Subscribe now

A wedge is one problem somebody is already spending money to work around. Most founders go looking for something else. They take the five-year vision and cut off the smallest piece of it, which gives them a smaller diagram with fewer boxes and still nothing a buyer can act on this quarter.

Where you look decides what you find. Slicing the vision is desk work. Finding the wedge means going out and locating an expense that already exists.

Look for the workaround

A gap in a market is something nobody built. A workaround is something a customer built badly because they had to, and it arrives with a name, an owner, and a number attached.

You can see them by asking what people do today. A spreadsheet passed between six people with a tab for each region. A contractor who invoices every month for the same cleanup. A script one engineer maintains that nobody else can read. A hire made specifically to absorb the mess. Each of those is a budget line already approved for your problem. The demand exists; your job is to redirect the spend, which is a shorter sales cycle and a much easier conversation about price. The buyer can tell you what the current answer costs without borrowing a word of your language.

Broad ambitions make weak wedges for that reason. “Help teams collaborate” describes a market and names no expense. “Stop the field team from quoting off last quarter’s price sheet” names the person, the failure, and the money.

At Heroku the workaround was a person. Four Rails developers who wanted their application on the internet needed somebody to configure servers, so they hired him, borrowed him from another team, or lost their weekends to it. The product answered that with one command: you pushed your code and the application was running. Everything Heroku eventually became sat on top of a wedge you could explain in one sentence to a developer who had just lost a Saturday.

Make sure it finishes the job

The wedge has to end somewhere the customer recognizes as done. If your software finds the bad invoices and somebody still has to open each one and correct it, you’ve sold a report and the work stayed where it was. If it catches the error before submission and routes the exception to the person who can clear it, the problem is off the buyer’s desk.

Map the job from the moment the problem shows up to the moment your buyer stops thinking about it, then take the smallest span you can own without handing the hard part back. The final stretch is usually the dull part: single sign-on, an integration with whatever system holds the real record, an import that tolerates messy data. None of it appears in the vision deck. It’s what separates a purchase from a project, and a project needs a sponsor and a timeline, which is how a wedge deal becomes a nine-month evaluation.

Prefer the one that’s hard

Several candidates usually qualify. Take the one that’s painful to build.

A wedge that’s easy for you is easy for the company with forty engineers and an existing relationship with your buyer, and they will ship it as a checkbox at renewal. Depth is the only protection a narrow product has. You want the piece where the demo looks simple and the reason it works took two years because side features are usually bad, and a good narrow product beats a bad side feature for a long time.

Let customers point at the next one

Once the wedge works, you don’t need a strategy offsite to find the second thing. Watch the handoff. Customers export your output somewhere. They keep a spreadsheet open beside your product. They reach for a particular tool the moment they close yours. Three accounts ask for the same integration in one quarter. That adjacent job already connects to the value you deliver, which makes it safer than a use case invented to make the market slide bigger.

Write your wedge down as four lines: the buyer, the workaround she pays for now, what that costs her a year, and the measurable result that tells the customer the job is complete. Founders can usually fill in the first line and the last. The cost line is the one that comes back empty, and an empty cost line means you’re still looking at a gap.

Dean Kamen unveiled the Segway on December 3, 2001, on Good Morning America, where Diane Sawyer said on air, “I’m tempted to say, that’s it?” The coverage that followed was about the machine: the gyroscopes, the rider who leans forward to go forward. What nobody could say was what it was. A vehicle, a scooter, a toy, a piece of medical equipment. The Segway sold for $4,000 to $5,500, which lands in the gap between two budgets: too much to buy the way you buy a toy, too little to be worth the procurement process that buys municipal vehicles. A buyer who can’t say what kind of thing you are has no way to decide whether she wants one.

The buyer picks your shelf with or without you

Al Ries and Jack Trout turned the problem into a law in The 22 Immutable Laws of Marketing: a company that can’t be first in a category should set up a new category it can be first in. Their concern was memory, which brand comes to mind when the category comes up. The shelf does more than that. It settles which budget pays for you, which title has the authority to sign, and what a fair price looks like, and it settles all three before anyone evaluates a feature.

A shopper who picks up an unfamiliar bottle in a grocery store decides what it is before she reads the label. Soda, juice, supplement, medicine. A CIO who meets a new technology does the same thing. Is it a CRM, a SIEM, an ERP, or something she has no shelf for yet? She’s trying to spend as little effort on the decision as she can, so she’ll place you somewhere whether the fit is good or not. When your category is undefined or keeps moving because you keep rewriting the homepage, no shelf fits.

The distance between two shelves is the distance between two budgets. A product read as a developer tool gets bought on a team’s discretionary line by a director who can sign alone. The same product read as infrastructure goes to a capital review, waits for the annual cycle, and needs a sign-off from the CFO’s office. Nothing about the software changed. What changed is the price it can carry, the number of weeks it takes to close, and the number of people who have to be convinced.

I’ve argued that a buyer who hasn’t been handed a way to read a new thing will supply one herself, reaching for whatever costs her the least thought. An undefined category makes the cheapest available thought I don’t know what this is.

You have two ways out. Pick one deliberately, before launch, rather than finding out at the end of a bad year which one you’ve been half-making.

Borrow a shelf

The first way is to anchor inside a large existing category and take a niche within it. “An AI-driven text-generation engine” gives a buyer nothing to hold on to. “A CRM for freelancers” lands instantly because buyers already know roughly what a CRM costs, which budget it comes out of, and who signs for it. You inherit the parent category’s stability and spend your scarce time explaining your niche instead of on teaching the market what kind of thing you are.

What you inherit along with the shelf is its ceiling. The parent category carries a price the market has already settled on, and charging above it means arguing against an anchor you picked for yourself. You also get graded on the incumbent’s feature list, because a buyer who has filed you under CRM will evaluate you as a CRM, including the twenty things you deliberately didn’t build. Borrowing is the safer path, and it’s the right one when the parent category is mature and your real innovation is the segment rather than the kind of thing.

Salesforce is usually told as a category-creation story, but the more interesting part is what it left alone. At the turn of the millennium sales leaders already knew what CRM was, what Siebel charged for it, and who owned the budget line, and Salesforce asked them to relearn none of it. What it renamed was the delivery model, with the word “software” crossed out in the logo. The familiar shelf carried the price anchor and the buyer along with it, so the whole argument narrowed to how the thing got installed.

I’ve borrowed a shelf myself. When we called Mesosphere’s product a Data Center Operating System, we weren’t asking anyone to learn a new kind of thing. Everyone already knew what an operating system was and knew you couldn’t run a computer without one, and we took fifty years of accumulated understanding for free. We invented the name and borrowed the shelf.

Build a shelf

The second is to build the product and its category together. Higher risk, higher ceiling, and more work than it sounds, because a category isn’t something you can ship. It exists only once other people are using it: when buyers have words for the space and when a company has a line in its budget to spend against. It gets built alongside the product, by you, and it never shows up in a release note. Three jobs come with it, and none of them is engineering.

Standardize the vocabulary so that the market has words for the space when you aren’t in the room. Define what winning looks like, because if you don’t set the measure the incumbents will apply theirs, and theirs was built to make their product win. And make the problem legible before you sell the answer. “Data gravity” is a problem; “container orchestration” is a solution. Categories are built on problems, because a buyer has to agree the problem exists before she’ll accept that a class of product addresses it.

Red Bull is the cleanest example outside software. Dietrich Mateschitz launched it in Austria in 1987 into a European market that had soft drinks and nothing else. The drink itself was not new: Red Bull is a reformulation of Krating Daeng, on sale in Thailand since 1976. What Mateschitz built from scratch was the shelf, and most of that work was vocabulary rather than product: what an energy drink is for, when you drink one, what it’s reasonable to pay. It took years, and the shelf they built now holds every competitor they have.

The Segway is the same path attempted with none of the three jobs done. Kamen built the product and expected the category to arrive on its own, and what vocabulary work happened went to legislatures rather than to buyers. The company had a legal class within three months of the unveiling and never got a budget line. It sold roughly 23,500 units in the U.S. between March 2002 and September 2006. Building a category and building a product are separate jobs, and finishing one of them earns no partial credit on the other.

Your early customers will hide the problem from you

Visionaries and early adopters buy interesting technology on its merits, and they’re happy to be the only company doing something. When you can’t tell them what kind of thing you are, they’ll work it out for themselves and enjoy the puzzle. They’ll take your call, sift through the architecture, and sign. Geoffrey Moore named the wall in Crossing the Chasm in 1991: the early majority buys known solutions to known problems in categories that already exist from vendors their peers can name. Your early wins are real revenue and they’re also camouflage because they came from the one group whose buying behavior doesn’t test the thing that’s broken.

You hit the wall when you run out of visionaries and start selling to the early majority. The damage shows up late in the sales process, far from the category decision that caused it. Cycles get longer. Deals need three more meetings. A champion who loves the product stops returning calls after he takes it to his boss, and the loss reason gets written down as “no decision” or “budget.” What happened is that a buyer who can’t categorize you can’t defend you internally, so ambiguity converts into perceived risk somewhere, usually in a room you weren’t in.

The work nobody schedules

Category work needs investment and stamina because the number that would justify it arrives after the budget cycle that has to fund it. A roadmap review happens every two weeks with a list you can check off. Evangelism has no weekly number, produces nothing demoable, and takes quarters to show up anywhere a board can see it.

Category work is also cheap while it’s still on paper and expensive afterward. Before launch, settling what kind of company you are costs an argument among the founders. After two years with no shelf, it costs a repositioning, with a price change, a sales team retrained off a pitch they’ve internalized, and a customer base that has to be told the thing they bought is now something else.

You can run a test this week without anyone’s permission. Call three customers who’ve been live for a quarter and ask each one how she described you to her boss when she asked for the money. You’re listening for one sentence, without your product name in it, naming a shelf her boss already had. If you get three different sentences, or a sentence that takes a paragraph, you’re already paying for it in cycle time and in losses booked as “no decision,” and the bill goes up every quarter you leave it alone.

Subscribe now

By the time Iridium’s 66 satellites were in orbit, much of their intended market had disappeared. During the company’s eleven-year build, terrestrial carriers extended cellular coverage across the cities where its customers traveled. The executive Iridium had designed the service for could now make the call from Frankfurt or Jakarta with an ordinary mobile phone. Iridium asked that customer to buy a $3,000 satellite handset and pay $3 to $8 a minute.

Iridium spent more than $5 billion building a system that worked. Service opened in November 1998. Nine months later, with roughly 20,000 subscribers against the 52,000 required by its loan covenants, the company filed for Chapter 11. A bankruptcy court later approved its sale for $25 million.

Timing was embedded in Iridium’s business thesis. The company had to reach the places its customers traveled before regular cell phones closed the window. That window was narrowing and then closed while the rockets were still going up.

Every company betting on a market shift carries a similar assumption. A cost must fall, a rule must change, a platform must spread, or buyers must become ready. Calling yourself early explains nothing. You need to name the change, track it, and fund the wait.

Name the Claim

A plan that depends on the market changing should say exactly what has to change. “AI is changing everything” gives you nothing to track. A useful timing claim names evidence you can watch: a product becomes cheap enough for widespread use, a regulation takes effect, a platform adds a capability you need, or customers begin buying in measurable numbers.

Put four things in the plan: the change you expect, the date by which it must happen, the evidence that would invalidate the schedule, and the cash required to survive the wait. Track any technology that could remove the customer problem before your market develops. When the expected evidence fails to appear, change the plan.

Companies often budget market education as marketing, which understates the capital required to wait for buyers. If customers won’t be ready for two years, you need enough cash to cover those two years without assuming revenue from the new market. A product or service that solves a current problem can provide that revenue while the larger market catches up.

Waiting for certainty creates a different timing problem. Once the evidence makes the opportunity feel safe, your competitors can see it too. Companies with more money will enter quickly. You have to act while customers are becoming ready and the market still has room for you to claim a clear position.

I’ve Paid for the Wait

At Vapor IO, we bet that latency and bandwidth economics would make distributed compute near the user inevitable. We built the infrastructure, helped define edge computing, and won some of the world’s largest infrastructure providers as customers and partners. Much of the work was still market education. We had to explain why computing needed to move beyond centralized cloud regions before buyers could decide where edge infrastructure belonged in their plans.

We raised a lot of money. Nearly $100 million. That capital extended the time available for market education while customer budgets and production deployments continued on their own schedules. The larger window never opened wide enough, soon enough, for us.

That experience changed how I think about market timing. A technical forecast can tell you where costs and capabilities are headed. The commercial forecast must account for how long customers need; every month between technical possibility and commercial demand has to be financed.

Early Companies Finance the Market

A company that arrives before the shift spends its money on market education, often to the benefit of competitors. You write the explainer that defines the problem. You fund the conference track. You brief the analysts twice a year until they stop asking what the words mean. You make the same argument in three hundred sales calls, and slowly the category becomes legible to buyers who had no vocabulary for it. Then the money runs out. Two years later a better-timed entrant walks into a room where the buyer already knows what the thing is, already believes She needs it, and wants to talk about implementation and price. You paid for that room. The competitor books the revenue in it.

The accounting offers no mercy. A company that’s early for the right reasons reports the same missed plan as one built on a bad premise. The board and investors see the same revenue shortfall. By the time customers catch up, the original company is often gone, and the competitor that survived long enough collects the proof and the revenue.

General Magic is the cleanest case I know. Marc Porat, Bill Atkinson, and Andy Hertzfeld spun it out of Apple in May 1990 to build the handheld personal communicator. Magic Cap was the operating system. Telescript was a language for software agents that could travel across a network and run errands for you, something that people are still trying to ship. Sony’s Magic Link went on sale in September 1994 at about $995. Motorola’s Envoy followed that December at $1,500.

General Magic’s 1996 annual report names the problem. Telescript, the filing says, “was designed for a proprietary telecommunications network environment,” and the market for personal communicators “has been slow to develop.” The Web showed up and took the electronic marketplace General Magic had spent six years describing. AT&T shut down PersonaLink, the only commercial Telescript service, in August 1996.

What General Magic paid for became other people’s products. Tony Fadell left for Apple and ran the iPod, then the iPhone hardware. Andy Rubin, lead engineer on the Envoy, went on to found Android. Pierre Omidyar launched AuctionWeb, which became eBay, while still on General Magic’s payroll. The company discontinued operations in September 2002 and told shareholders to expect nothing. The handheld communicator it had described in 1990 shipped as the iPhone five years later.

Track the Curve That Can Erase Demand

Iridium’s engineers had identified a real constraint. Geostationary satellites orbited roughly 22,000 miles above Earth, which added delays to calls and required powerful radios with large antennas. Motorola’s proposed low-Earth-orbit constellation would make faster connections and smaller handsets possible. The engineering plan tracked that curve closely from 1987 until service opened eleven years later.

The business depended on another curve moving slowly. Terrestrial cellular coverage determined how many travelers would still need a satellite phone once Iridium was ready. Sydney Finkelstein and Shade Sanford traced the collapse in “Learning from Corporate Mistakes: The Rise and Fall of Iridium”. Cellular networks spread much faster than Iridium’s plan assumed.

John Richardson, who took over as interim chief executive, attributed the failure thusly: “First we created a marvelous technological achievement. Then we asked how to make money on it.” Under new owners, Iridium found a smaller market and remains in business. Its original plan failed because the window closed.

What You Can’t Know From Inside

Timing is much clearer in hindsight. Looking back, people can point to the year a market took off. While you’re waiting, you know only that the change seems real and customers haven’t responded yet. You can’t tell whether they’ll be ready in eighteen months or five years. A company can survive the first delay and run out of money during the second.

That uncertainty belongs in the cash plan and every board discussion about growth. At each review, decide how much more cash the evidence justifies. A missed date should change the plan; a competing technology that removes the need should end the original bet.

Subscribe now

A go-to-market plan usually arrives secondhand. A founder names three companies she admires, somebody reconstructs how those companies launched, and the plan gets assembled out of the parts that worked: the content cadence, the pricing page, the conference booth, the analyst briefings. The tactics are described accurately. What travels with them, unannounced, is a set of assumptions about the market the original company was standing in, and those assumptions are what made the plan work.

There are four ways in. You can enter a market that already exists and try to outperform what’s there, competing on features against incumbents who set the terms of comparison. You can resegment that market on price, taking the low end who’ll accept good-enough performance in exchange for paying a lot less. You can resegment it for a niche, serving a subset the incumbents ignore, sometimes at a higher price and often with worse performance on the attributes that subset doesn’t care about. Or you can create a market where your customers couldn’t do the thing at all before. Steve Blank laid this out in The Four Steps to the Epiphany in 2005. His categories are existing, resegmented, and new, with resegmentation splitting two ways. He reckons more than half of startups walk through one of the two resegmentation doors.

Each door changes the target, the argument, the clock, and the budget at once. Enter an existing market and you’re selling to the incumbents’ customers, who want better performance and will score you against a list they already have. Resegment on price and you’re selling to the cost-sensitive end of that same base, at the risk of the incumbent deciding to match you. Resegment for a niche and you’re telling a specific group that everything else on the market was built for somebody else, at the risk that the group turns out to be too small to live on, or not distinct enough to buy any differently from the mainstream. Create a market and you’re selling against people doing nothing at all, at the risk that adoption never arrives.

I’ve argued before that nobody finds a market; you build one or take a seat in somebody else’s. The four doors are what that choice looks like in operational terms, before anyone writes a plan.

The Door Is a Choice

Blank frames the four as a diagnosis, a question you answer about a market that already is what it is. Three things you control move a market from one type to another.

Price moves it. Come in far enough under the incumbent and what would have been an existing-market fight becomes a low-cost resegmentation, which brings a different buyer, a different motion, and a ceiling on what you can ever charge.

How wide you draw the problem does the same work. Narrow it to a subset nobody serves and you’re a niche entrant. Widen it past anything a buyer can currently purchase and you’re creating a market, whether or not you meant to.

The third lever has no slot in Blank’s scheme at all. It’s the buying center you enter through, meaning which person inside the customer you actually sell to. There are always at least two. One is whoever will use the thing every day. The other controls the budget and signs the contract. Blank’s four types quietly assume you’re selling to the same buyers the category has always been sold to.

The Fifth Door

Sell to the person who uses the thing rather than the person who signs, and the market type moves underneath you. Payments in 2011 was a thoroughly settled category, with incumbent processors, a known budget line, and a procurement process every finance team already knew how to run. Stripe sold to the developer, who had never been the buyer of anything. Everything on the seller’s side of that deal was ordinary existing-market business, and the buyer was somebody the category had never once pitched.

Those two halves want opposite plans, and running both at once is the part nobody budgets for. The category hands you named competitors, a price the market already understands, and a problem no buyer disputes is worth solving. That’s ordinary existing-market work, and at least it’s legible. You’re arguing you’re better than a specific alternative in front of people who agreed long ago that the category deserves a budget line. What you build for it is competitive positioning, a differentiation claim that survives a bake-off, and a clean migration path off the incumbent.

The buyer hands you somebody who can’t sign a contract, has never sat through a vendor pitch, and will make up his mind by signing up and trying the thing well before he talks to anyone. That’s new-market work, and it costs differently. He can’t be sold to in the ordinary sense, so the documentation becomes the pitch and the free tier becomes the demo, and the product has to close itself with nobody in the room. He also can’t buy. Adoption shows up before revenue does, and at some point you have to go find the person with the budget and sell her a tool her own staff installed months ago.

So you’re funding two motions at the same time, and in most companies they report to different people. The education work sits with docs and developer relations, measured on adoption. The competitive work sits with product marketing and sales, measured in pipeline. Each side can look at the other’s budget and see something optional, which is the argument that surfaces the first time you have to cut. Cut either one and the machine stops. Lose the education and nobody arrives; lose the competitive work and the people who did arrive can’t get a purchase order approved.

Two Quarters of Expensive Confusion

Most developer-tools companies live in this position. Datadog entered a monitoring market with entrenched incumbents, Twilio sold into telephony, a category older than software itself, and MongoDB went after Oracle. The category was settled in every case and the buyer was brand new, and the plans that come out of that combination look broken to anyone trained on enterprise go-to-market. The documentation is public and ungated, so no leads come off it. There’s a free tier that on paper eats revenue. Sales gets hired late and hired to expand accounts the product already won rather than to source new ones. The pipeline report reads thin, because the signal that matters is sitting in usage data the CRM never sees.

Drop a conventional enterprise plan on top of that and every change in it is defensible on its own. Gate the documentation to capture leads. Retire the free tier to protect the average selling price. Hire SDRs to call the person who controls the budget and buy the analyst placement while you’re at it. What breaks is the top of the machine. The practitioner who would have found you through the docs and tried you for free never arrives, and he or she was the entire acquisition motion.

It takes a couple of quarters to see because revenue lags badly here. Practitioners who already installed you keep converting into paid accounts on their own schedule, so the numbers hold while acquisition quietly stops. By the time the revenue line bends, the cohort that would have fixed it stopped showing up two quarters earlier, and the plan that caused it has been running long enough to look like the status quo.

One Team, Two Doors

Donna Dubinsky ran Palm Computing when the Pilot shipped in 1996 and was CEO of Handspring when the Visor shipped in 1999. The two go-to-market plans were opposites, and both were right. At Palm the job was convincing people a handheld was worth wanting at all because nobody was shopping for one. By 1999 buyers compared handhelds on specifications, and Handspring differentiated on expandability and performance in a market Blank describes as already worth a billion dollars. Handspring running Palm’s evangelism would have spent a year teaching buyers what they already knew, and Palm running Handspring’s feature comparisons would have burned its cash arguing against products nobody was cross-shopping.

Blank calls 1996 a market that didn’t exist, which is tidier than the record. Handhelds had been on sale since the Psion Organiser in 1984 and had simply never sold in volume. What changed between 1996 and 1999 was buyer literacy: whether people knew what the thing was for, what to compare it against, and which budget it came out of. Neither Palm nor anyone else bought that literacy; it accumulated over four years of people watching a colleague pull one out in a meeting.

Your Dashboard Can’t Tell You Which Door You Walked Through

The uphill direction of travel is running a new market on existing-market assumptions. You fund demand capture when there’s no demand yet to capture. You buy search terms nobody types. You staff a sales team against a buying process that hasn’t formed. None of it looks like waste while it’s happening, because every line item is something a competent company does.

The obvious correction is to run the plan and watch the numbers, adjusting when they disappoint. But early success in a new market looks just like failure in an old one. Low volume. Long cycles. Prospects who engage warmly and never convert. Read as an execution problem, those numbers call for more spend and more reps. Read against the right market type, the same numbers are on schedule, and the correct response is to protect the runway. No metric tells you which situation you’re in, and the dashboard will quietly recommend the wrong one.

Each door has its own objective, and the numbers only mean anything once you know which one you’re walking through. In an existing market the objective is share: a slice of spending that already exists, taken from somebody who currently has it. The work is capture against a buying process that already runs. In a resegmented market it’s share and education at once, which is harder than either alone and also the most common way in. In a new market there’s nothing to take and nobody to take it from, so the objective has nothing to do with share. The measure is whether the number of people who could plausibly buy is moving toward something a business could live on.

The Flattering Answer Is the Expensive One

Picking a door is supposed to be a judgment about the market. It’s also a judgment about which conversation you’d rather have with your board. “New market” buys a longer runway and more patience, and it’s a claim a founder can always argue for, because nobody can disprove it inside a year. “Existing market” obliges you to explain how you’ll beat a funded incumbent with a tenth of their go-to-market budget. The answer that’s easiest to defend is also the most expensive one to be right about.

Money settles what the analysis can’t. Add up what each door costs, set it against what’s in the bank, and where two types both fit, take the one you can pay for. Each carries a different bill. A low-cost resegmentation needs a cost structure that survives the incumbent matching your price, and they can usually hold a lower price longer than you can. A niche resegmentation needs a subset both large enough to live on and cheap enough to reach because a small audience can’t absorb a big acquisition cost. A new market needs enough runway to pay for the education before anybody buys. When the only type you can afford isn’t the one you want, you have a financing problem wearing a market-type label, and it belongs in front of your board as a financing problem.

The Door Closes Behind You

A market can be new when you enter it and ordinary three years later. Nothing announces the change when it comes. So you keep spending to teach people what the category is for long after they’ve learned it, and you’re still funding evangelism while your buyers have started comparing feature lists.

So market type belongs on the quarterly agenda, next to pricing and segment, which you already revisit. Ask whether you’re still in the market you planned for. If you aren’t, ask what your objective and your spending should have changed to and how long ago.

The longer you wait, the less of a choice it is. Price, how wide you draw the problem, and which buyer you sell to are all yours to set before launch and expensive to change after. A published price fixes what the market thinks you’re worth. A buying center you’ve sold into for two years has headcount attached to it, comp plans written around it, and a content library aimed at it. You can pick the type while it’s still on paper. Once you’ve spent two years executing it, you aren’t choosing anymore, you’re living with it.

Nobody “finds” a great market. You build one, or you take a seat in somebody else’s.

It’s easy to end up in someone else’s market. For example, “searching” for product-market fit casts you as an explorer hacking toward a golden idol already buried in the jungle: fit exists somewhere out there, and enough machete work will reveal it. Tweak the messaging, adjust the pricing, and a hungry crowd surfaces.

I’ve defended that search, and I still do. Steve Blank built a methodology on it. The Four Steps to the Epiphany (2005) describes a startup as a temporary organization looking for a repeatable business model, and running one as a small version of a big company kills it. The customer development loop the book introduced is now the standard for how founders talk to buyers before they build, and it deserves to be. I’ve made the case for accepting the search and for grounding that phase with execution metrics.

The Market You Choose Shapes the Frame

The Four Steps to the Epiphany says startups are either in existing markets, resegmented markets, or new ones.

Blank encourages founders to figure out which market type they’re in, as though it were something the market had done to them. It’s a decision made early, often accidentally, and then defended for years by everyone who joins afterward.

Confined to a market that already exists, most founders reach for segmentation to carve out a slice of it. Sort a population by firmographics and geography and you get a TAM slide the board will nod at. That slide describes the world as it is. Whether anyone in that world will listen to a new claim is a question segmentation has no way to ask.

When you pursue an existing segment, you inherit the buyer’s mental models along with it. You enter an existing budget line. You accept a price ceiling somebody else set. A database buyer measures you against Oracle. A CRM buyer measures you against Salesforce. You’re selling on ground somebody else surveyed, and your win-loss reports come back saying “feature gap” and “price” more often than you’d like.

Why the Funnel Can’t Fix It

The reflex at that point is to work the funnel. Rewrite the headline, rebuild the demo, run the test again. A buyer who hasn’t been given a way to read a new thing will supply one himself, and he’ll reach for whatever costs him the least thought: you’re a cheaper Oracle, or you’re a line item he isn’t going to defend to anyone. Every test you run gets scored inside that sentence.

Funnel work can’t reach the problem because of where it sits in the buyer’s decision. A funnel measures conversion inside a frame somebody already set, and the setting happened upstream, out of view. By the time anyone reaches your pricing page, the comparison set has been chosen, the budget line has been picked, and your champion already has a sentence she uses to describe you to her CFO. A better headline might move her through that decision faster while the decision itself stays closed.

So the gains are real and capped. Each round of testing tunes the message toward the buyers who already understood you in the incumbent’s terms, since those are the people converting and producing the data. Anyone who might have responded to a different story never appears in the results because nobody told them one. What you get is a well-tuned machine for recruiting the customers most likely to grind you down on price.

Building the frame instead starts with a specific claim about how the world has changed and uses that claim to redraw the context your product gets judged in. Positioning leaves the product alone; it changes the surroundings until your product is the obvious conclusion. Three moves do that work.

Three Moves to Build the Frame

A market doesn’t change because you call your product something new. It changes when buyers are given a new way to understand the problem, the moment, and the outcome. Building that frame takes three moves.

Name the Enemy

The enemy is the status quo: the friction your customer already resents and has stopped mentioning, because mentioning it never helped. It’s a way of working that has to end. Name a competitor instead and you’ve validated the competitor, then spent the rest of the sales cycle arguing inside its frame.

At Heroku, the market that already existed was obvious and terrible. Developers wanted somewhere to host Ruby apps, which meant a commodity knife fight against every VPS provider, settled on specs per dollar. We went somewhere else. Our enemy was infrastructure management, the whole body of sysadmin chores that had nothing to do with shipping software. Nobody was calling it an enemy at the time. Developers assumed servers were part of the job, the way you assume weather.

Explain Why Now

Name the change in the world that makes the old way untenable. This is the hinge, and it’s where designed markets mostly fail, because the founder reaches for a shift that turns out to be a wish.

A real one passes a test you can run before writing a word of copy: somebody who doesn’t work for you can verify it, and it happened before your pitch. If your why-now is “buyers are waking up to the need for this,” you don’t have one; you have a hope with a date attached. If it’s a change in what something costs, or a capability that shipped and didn’t exist eighteen months ago, a skeptic can check it.

Heroku’s was sitting in public. Rails had made web applications fast to write, and EC2 had made servers rentable by the hour since 2006. The distance between how quickly you could write an application and how long it took to get one running had grown absurd, and anyone paying attention could see it. We never had to convince a buyer the shift was real. We had to name what it meant.

Describe the Promised Land

Sell the new way of working. Features are evidence for it, and they only get interesting once the buyer wants the world you’re describing. Latent irritation becomes a market requirement when somebody names it out loud and gives buyers the language for it.

Heroku’s promised land was that you deploy code and stop thinking about servers. We made time-to-deploy the measure, and the incumbents had no answer for a yardstick they’d never thought to compete on.

A yardstick only counts once it leaves your marketing. Ours left through documentation. In 2011 Adam Wiggins, one of Heroku’s founders, published the Twelve-Factor App, a plain description of how an application should be built so it can be deployed and scaled without ceremony. It read like engineering guidance instead of positioning, which is precisely why it traveled. Teams that never bought anything from us adopted it. Competitors built products against it. The assumptions underneath it, disposable processes and config kept in the environment and no server anyone nurses by hand, became the default way a generation of developers thought about running software. By the time the category had a name, Platform as a Service, the argument had been settled somewhere upstream of any sales call.

Salesforce ran the same play on a bigger stage. The market that existed was people who wanted cheaper on-premise CRM. Marc Benioff’s company launched its on-demand service in February 2000 and sold it against packaged software itself: the eighteen-month implementations and the upgrade cycles and the IT tax. The web had made hosted software workable, and that was the why-now. The promised land was that you log in and start working. The red “no software” circle was a thesis compressed into a logo.

I’ve written about Mesosphere at length elsewhere. The part worth adding here is the pricing. Selling a Data Center Operating System instead of a cluster scheduler moved us against a different budget line, with a different approver and a much higher ceiling. The reframe held for about eighteen months, and then Kubernetes was free and we weren’t. Winning the argument about what a thing is doesn’t settle who gets paid for it.

The Play Isn’t Confined to Software

Dietrich Mateschitz found Krating Daeng, a Thai tonic sold to truck drivers and laborers, and saw a product with no Western market. By Red Bull’s own account of its founding, the market research he commissioned came back brutal: testers disliked the taste, the logo, and the name. Those are reasonable objections if the thing on the table is a soft drink.

Mateschitz changed what was on the table. He reformulated and carbonated it, launched Red Bull in Austria in 1987, priced the slim can well above cola, and seeded it with students and extreme-sport athletes. The price did argumentative work, since nothing costing triple a Coke is ordinary refreshment. The users did the rest, demonstrating in public what the thing was for. “Energy drink” became a Western category because Red Bull handed buyers a way to understand a product that had been sitting in Thailand for years.

What the Bet Costs

A designed market is a falsifiable bet on reality, and that’s what makes founders flinch the most. Slot a product into an existing category and you can post mediocre numbers for years without ever learning whether the premise was wrong. Every miss gets charged to execution, so you hire two more reps and run the quarter again. Design a market and the verdict arrives early and in public. You’ve named a shift in the world, built the pitch on it, priced against it, and told everyone what to expect. If the shift isn’t real, buyers won’t argue with you; they’ll just fail to show up, and that silence is legible to your board and to every competitor watching.

There’s a line here worth being honest about, because from the outside the move looks identical to spin. Reframing works when the product can actually deliver on the new measure. Heroku could genuinely take deployment down to seconds. Red Bull genuinely did something to you that a cola didn’t. Move the yardstick onto ground you can’t hold and buyers find out in their first quarter of use, and you’ve taught the market a vocabulary that now indicts you. The frame has to be true before it’s useful.

Keeping the bet honest takes the same discipline the search phase demands: write down what has to be true, decide in advance what evidence would change your mind, and hold yourself to the list. What changes when the market is designed instead of inherited is the exposure. Your hypothesis stops being private. It’s on your home page, and your competitors have read it.

The other cost is that you can’t hand this off. The organizational temptation is to push go-to-market downstream to a VP of Sales and get back to the product. But a VP of Sales optimizes inside whatever frame he inherits, because that’s the job you hired him to do. Deciding what the company means sits outside that job, and it stays with the founders. Two questions get you started, and you have to answer them about your own technology: who loses if we win, and what happens to our customer if they don’t buy from us. No feature list has ever answered either one.

Slotting into an existing category usually does get you revenue faster, and it locks you into the incumbent’s price. That trade looks like traction on a monthly board update and reads as a race to the bottom two years later.

None of this makes the outcome safe. Mesosphere named its category, held the frame for a year and a half, and lost the market anyway. What the work buys is narrower than the headline examples suggest: a market that’s yours to lose rather than somebody else’s to defend. Whether that trade is worth making is the founder’s call, and it has to be made while the pitch is still being written.

Subscribe now

Most CMOs aren’t losing their jobs to AI. They’re losing them to the data layer.

That’s the less dramatic version of the story, and the one more likely to be true. The tools aren’t the threat. What the tools reveal is the threat. Point a capable AI system at a marketing org and it will find, within about a week, every place the machine underneath is held together with duct tape and quarterly heroics. Then it builds on that foundation, faithfully and fast, and hands you back your own dysfunction at ten times the volume.

The work we judge marketing on hasn’t changed much: the message, the brand, whether the pipeline number lands at the end of the quarter. That still gets you hired. It won’t keep you in the seat. For most of the last two decades, a CMO could be brilliant at the visible half of the job (positioning, story, the launch) and treat the plumbing as somebody else’s department. Data lived with IT or a RevOps team. Attribution was a slide you argued about once a quarter and then stopped thinking about. Experimentation, if it happened at all, was whatever the agency felt like testing that month.

That arrangement is quietly ending, and AI is the reason.

When execution gets cheap, the bottleneck moves

AI makes marketing execution cheap and fast. Generating a hundred ad variants, personalizing a lifecycle flow, drafting landing pages, scoring leads, forecasting spend: all of it collapses in cost. When execution gets cheap, the bottleneck moves to the quality of the inputs and the speed of the learning loop. If your customer data sits in twelve systems that don’t talk to each other, no model fixes that for you. It averages across the gaps and produces confident, well-written, wrong output. Bad data doesn’t make a bad report you can ignore. It trains bad targeting, teaches the system the wrong lesson about who to chase, and ships forecasts built on holes, all of it automatically.

The companies already run this way

Look at the companies that already run marketing this way. Booking.com has said publicly that it runs more than a thousand concurrent experiments at any given moment. Amazon built an internal experimentation platform, Weblab, because it decided the rate of learning was the thing to optimize, not any single campaign. Netflix treats its recommendation and merchandising systems as a testing surface rather than a set-and-forget feature. None of these companies won by hiring a more poetic copywriter. They won by building a system that turns a market signal into a decision faster than their competitors can, and by keeping the data clean enough for that system to be trusted.

Now put an ordinary B2B marketing org next to that. The CRM is half-empty because sales never had a reason to fill it in. Product usage data lives in a warehouse marketing can’t query without filing a ticket. The attribution model gets re-litigated in every QBR because nobody actually believes it, so nobody wants to bet a budget on it. Three teams have three definitions of a “qualified” lead. This isn’t a tooling problem. You can buy the best martech stack on the market, drop it on top of that mess, and the mess wins. It always wins.

The job description is being rewritten

So the job description is being rewritten, whether or not the titles catch up. Knowing the customer, owning the story, running campaigns, minding the brand: table stakes now, not the whole hand. The CMO increasingly has to answer a different set of questions. What data does the company actually capture, and which of it does anyone trust? What’s connected to what? How does a signal from the market become a decision, and how many weeks does that take? Where do the feedback loops between creative, sales, product, service, and finance break? Those are architecture questions, and most of us were never trained to answer them, because for most of our careers we didn’t have to.

A lot of marketing leaders came up learning to sit above the system rather than build it. We were rewarded for taste, for narrative, for the big launch, and we treated the data layer as back-office hygiene, the kind of thing you delegate and forget. In an AI-run marketing stack, the back office is the strategy. The quality of your data governance determines the quality of everything the models produce downstream. Your ability to run clean experiments determines how fast you can learn. Measurement stops being a reporting function and becomes the steering wheel. If you can’t defend your measurement model in a hostile finance review, you can’t defend your budget, and pretty soon you can’t defend your role.

The craft becomes the scarce part

None of this means the craft stops mattering. It matters more, because it’s now the scarce part. When anyone can generate a competent campaign in an afternoon, competent stops being a differentiator. Taste still separates the good from the forgettable, and so does the judgment to know which idea is worth betting a quarter on. Plenty of brands have won on story alone with a mess behind the scenes, and some still will; that window is just closing as the mess becomes computable. The craft now sits on top of a foundation a modern CMO has to own rather than delegate: data architecture, experiments you can design and defend instead of merely approve, a real point of view on what the models are allowed to touch and how you’ll know when they’re wrong.

Do the audit before AI does it to you

So do the audit AI would do to you, before it does it. Map where your customer data actually lives and how much of it you’d stake a forecast on. Count how many genuine experiments you ran last quarter, not how many “tests” someone name-checked in a deck. Ask whether your attribution model would survive an hour with a skeptical CFO. The answers tell you how ready your function is to move at the speed the tools now allow, which is a different question from how many tools you’ve bought.

The CMO who comes out of this ahead owns one number above the others: how fast the company learns from its market. It’s an unglamorous number. Nobody puts it on a launch slide, and no agency can move it for you; it lives in the plumbing most of us spent a career delegating. Claim it and the tools multiply everything you’re already good at. Leave it unclaimed and they’ll multiply the mess instead, at ten times the volume, in your name.

Subscribe now

Two marketing teams get the same tools on the same Monday. Same models, same budget for tokens, same access to the same vendors pitching the same “AI-native” platform. Six months later one team is shipping sharper work in half the time and the other is drowning in competent, forgettable output. The tools didn’t cause the gap. They revealed it.

This is the part the vendor demos won’t tell you. AI is not a skill you bolt onto a marketing org. It’s a mirror. Point it at a team with a muddy point of view and a fuzzy sense of who the buyer is, and it produces muddy, fuzzy work at ten times the rate. Point it at a team that actually knows its market, and it amplifies that clarity into reach the team could never have hit by hand. The technology is neutral. The marketer is not.

The lens that beat the specialists

The marketers who are hardest to compete with don’t win on a channel tactic. They win on a habit of mind, often carried in from somewhere outside marketing entirely, like manufacturing or supply-chain work: they look at a business as a system of interacting parts. A marketing operation, seen that way, is a production engine assembled from components. Pricing feeds positioning. Positioning feeds the message. The message feeds the pipeline. Sales feeds back what the message is actually doing in the wild. Change one part and the others move.

Most marketers are trained to do the opposite. The advice you’ve heard your whole career is to specialize: become the best paid-search operator on the planet, or the best lifecycle-email person, or the best brand storyteller. Deep specialization buys you mastery of one slice and blindness to the rest of the machine. The paid-search expert optimizes a campaign that’s selling the wrong promise to the wrong segment, and the dashboard looks great right up until the pipeline doesn’t convert. The specialist did the job. The system still lost.

Here’s why that matters more now than it did five years ago. The specialist’s slice is exactly what AI is best at. Bid management, keyword expansion, variant generation, first-draft copy, the assembly of an attribution report: this is information processing, and information processing is precisely what the machine automates first. If your value to a marketing org was that you were the person who could operate one platform better than anyone else, the platform now operates itself well enough. The premium on that skill is already falling, and it isn’t coming back.

Where the value goes instead

So where does a marketer’s value migrate? Not to whoever prompts the fastest. It migrates to judgment, the one capability AI structurally cannot supply.

A model is a prediction engine. It surveys everything that has already been written and predicts the most reasonable average next move. That’s enormously useful and also its hard ceiling. Ask it to position a genuinely new category and it will hand you the existing language for the nearest old one, because the new framing isn’t in the training data yet. Someone has to originate it. Ask it whether to plant your flag on “data observability” or invent a term the market doesn’t have words for, and it will give you a tidy list of pros and cons. It cannot tell you which bet is right for your company, your moment, your tolerance for being misunderstood for eighteen months. A human still has to decide. Category creation is the purest version of this: by definition you’re naming something the corpus has no consensus on, so the corpus can’t name it for you.

That’s the work that’s becoming scarce, and scarce work is where the money goes. The marketer who’s worth keeping isn’t the one with the most certifications. It’s the one with the clearest read on the buyer and the steadiest hand on the bet.

Judgment is a muscle, and it’s atrophying

There’s a quieter problem underneath this, and it’s worth naming because it’s happening inside good teams right now. Judgment behaves like a muscle. Used, it strengthens. Unused, it wastes away. And the easiest thing to do with an AI is to hand it the decision.

Watch how a content brief actually gets made now. A marketer feeds the model the source material and asks for the angle, the headline, the structure. The output feels like progress, so the habit compounds. What got quietly outsourced wasn’t the typing. It was the interpretation, the part where a person reads the market and forms an opinion about what to say. Do that for a quarter and you still have a content team. Do it for two years and you have a content team that can no longer tell a sharp angle from a safe one, because the muscle that made that distinction hasn’t been loaded in a long time.

The fix isn’t to ban the tool. It’s to change the job you give it. Use the model to attack your thinking, not to replace it. Form your own read of the positioning first, then hand the machine the argument and tell it to find every hole: the counterexample, the segment you’re ignoring, the reason a skeptical buyer would bounce. There’s documented work, including a Procter & Gamble study run with Harvard Business Review, showing that a person paired with an AI used as a sparring partner performs at roughly the level of a whole team. The order of operations is the entire game. Decide, then pressure-test. Reverse it and you’ve trained yourself out of deciding.

From a map to a compass

Most marketing leaders were trained to run on a map. Build the annual plan, commission the research, chart the route, then follow it with small corrections quarter to quarter. That worked when markets moved slowly enough to forgive the lag. It’s now a liability. A category window can open and close inside the six months it used to take to validate the move, and a plan that assumes a stable market is a plan that’s wrong on arrival.

What the work demands instead is a compass: the ability to move through terrain you don’t have a map for, read how the ground is shifting, and change direction without waiting for permission from a deck. A compass needs a fixed point to orient against. For a marketing org, that fixed point is positioning, the bedrock answer to who you’re for and why you’re the obvious choice. Get that right and you can improvise everything downstream, because every tactical call has something true to test itself against. Get it wrong and no amount of AI throughput saves you. You’ll just be lost faster, with better graphics.

The hype keeps insisting the winners will be the teams that adopt the most. The opposite is closer to true. The winners will be the ones who know what they’re doing well enough that the machine has something real to amplify. AI made execution cheap. It made taste, judgment, and a defensible point of view the only things left worth paying for. If you’ve spent years building those, this is the best market you’ll ever work in. If you outsourced them to the tool, you already have your answer to why the other team is pulling ahead.

Subscribe now

For most of my professional life, a website’s job was simple. A person landed on your homepage, read the headline, clicked through the nav, compared a couple of pages, and if you’d done your work, filled out a form. Every instinct we built as marketers points at that person: the headline that earns the scroll, the proof that earns the click, the call to action that earns the email address.

That person is still showing up. But more and more, they send someone ahead. An AI agent reaches your site first now, working on the buyer’s behalf. It summarizes vendors, builds a shortlist, drafts the internal recommendation, and decides whether you belong in the conversation before a human opens a tab. Sometimes the human never visits at all. They read what their agent told them about you, and they act on that.

This moves the job. Your website used to be a persuasion surface pointed at one reader. Now it’s also a reasoning surface that a machine mines for structure, and those two readers want different things from the same pages.

Here’s the line I’d put on the whiteboard: your website is becoming your company’s public prompt surface. It’s the raw material an agent uses to assemble an answer about you, for someone, while you’re nowhere near the room. Most sites make a poor prompt. They’re abstract, they’re inflated, and they bury the few facts an agent actually needs under copy engineered to make a human feel something. Closing that gap is the work.

For an operator who has spent a career optimizing for the human funnel, this is uncomfortable, because the new reader is unmoved by everything that used to convert. So let’s redesign for it.

Every Page Is the Front Door

Humans may still enter through the homepage. Agents rarely will.

An agent meets your company in fragments: a search result, a docs page, a pricing table, a GitHub readme, a LinkedIn post, a podcast transcript, a scraped snippet, a PDF someone uploaded into a chat window three years after you published it. It assembles its picture of you from whatever surfaces first, in whatever order, with no guarantee it ever sees the page you consider the real introduction.

So every page that matters has to stand on its own. Each one should answer the same short interrogation without relying on the page before it: What is this company? Who is it for? What problem does it solve? When should someone recommend it, and on what evidence? What’s the next step? A page that only makes sense after you’ve read the homepage is a page an agent will quote out of context, or skip.

That pushes the site away from a linear brochure and toward something closer to a knowledge graph, where each node is a self-contained explanation of the company, the category, and the buyer’s path through it. The working rule is blunt: assume every page is the first page an agent sees, because for someone, it will be.

Write Claims a Machine Can Lift

Most marketing copy is useless to an agent because it’s abstract, inflated, and interchangeable. “We help teams unlock the future of intelligent transformation” sounds finished and says nothing. An agent can’t classify it, can’t compare it, can’t quote it into a recommendation. It’s noise that happens to be grammatical.

Now picture the alternative. “We help enterprise support teams cut ticket resolution time by triaging requests, retrieving policy-compliant answers, and escalating the hard cases to human specialists.” That version hands the agent a category, an audience, a problem, a mechanism, and a use case. It survives extraction. Lift any sentence out and it still means something.

This is where category work and machine-readability turn out to be the same discipline. The vocabulary you use to describe yourself is the vocabulary an agent will repeat when it describes you to a buyer. If your language is vague, the agent paraphrases you into the generic middle of your category, indistinguishable from the four other vendors it’s also summarizing. If your language is precise and owned, the agent carries your terms forward intact. Controlling the words a machine uses for you is the linguistic moat, rebuilt for a reader that takes you literally.

Declarative statements travel best. “We’re best for.” “We’re not a fit for.” “Teams use us when.” “The main alternatives are.” “The strongest proof is.” None of this dumbs the site down. It makes the company legible, which is a harder thing to be than clever.

Build the Layer the Buyer Can’t See

Underneath the site humans look at, you want a layer built for the machine. It doesn’t have to hide from people, but it isn’t designed to charm them. It’s designed to be retrieved.

The ingredients are familiar to anyone who’s done technical SEO, just pointed at a new consumer: an llms.txt file, schema markup, structured metadata, clean docs, a canonical set of company facts, a product taxonomy, comparison and objection pages, a plain pricing explanation, security and compliance documentation, machine-readable FAQs, citation-ready proof. Most of it you already half-own. The shift is treating it as a coherent layer rather than scattered exhaust.

The single highest-leverage piece is a plain-language briefing written directly at the agent. Call it an Agent Briefing or a Vendor Brief for AI Assistants; the name matters less than the candor. It should be structured, direct, and boring in the best possible way:

Company:
Category:
Primary customer:
Primary buyer:
Primary problem solved:
Best-fit use cases:
Not a fit for:
Main alternatives:
Key differentiators:
Proof points:
Security posture:
Pricing model:
Evaluation path:
Recommended next step:

The discipline of filling that in does something useful even before any agent reads it. It forces the company to say plainly what it actually is, which is a sentence a surprising number of companies can’t finish.

And while you’re at it, reorganize how you think about pages. A conventional site is built around sections: Home, Product, Solutions, Resources, About. An agent-facing site is built around the questions a buyer types into a chat window. What does this do? Who’s it for? When should I not use it? How’s it different from the obvious alternative? What does it cost? How hard is it to adopt? What would a technical evaluator pick at? What proof exists? What’s the fastest way to test it? Each of those deserves a clear, structured answer living somewhere findable. The goal isn’t a content swamp. It’s a site that can be answered.

Tell the Agent Who You’re Not For

Two kinds of pages most marketers treat as afterthoughts become load-bearing in an agent-mediated market: the comparison page and the disqualifier.

Comparison pages are usually thinly disguised hit pieces, and an agent reads right through them. A page that says “us good, them bad” gives a machine nothing to reason with, so it discounts the whole thing. A page that explains the actual tradeoff gives it material it can use. What is each approach genuinely good at? Where do they overlap? When should a buyer pick one, and when should they run both? Write it as a decision, not a verdict. “Choose this if you need X. Choose that if you need Y. Run both if your architecture forces Z.” That page earns trust from the human and hands the agent honest inputs, which is the only kind it can safely repeat.

The disqualifier is harder, because it runs against every instinct we have. Companies are afraid to name who they’re not for. In a market where an agent is deciding fit, that fear costs you. A good agent isn’t trying to find the most enthusiastic vendor; it’s trying to find the right one, and it needs boundaries to do that. So give it some. “This probably isn’t a fit if you only need a prototype, have no production reliability requirements, or could solve the problem with a short internal script.” Naming the wrong-fit buyer doesn’t weaken your positioning. It sharpens it, and it keeps the agent from recommending you into deals you’d lose anyway.

Make Your Proof Portable

Humans skim proof. Agents retrieve it and reuse it, which means your proof points have to survive being lifted out of your site and dropped into someone else’s memo.

“Trusted by leading teams” survives nothing. It carries no fact. “Used by enterprise security teams to cut manual review time on high-volume access requests” carries a context an agent can place. And a fuller version carries more: a deployment window, an organization size, a before-and-after number, a note on what stayed under human control. The richer the context attached to a claim, the more accurately a machine can repeat it without inventing the parts you left out.

Not every company can publish hard metrics, especially early, and you shouldn’t fabricate them to fill the template. But every company can make the proof it does have more legible: quote a named customer instead of an anonymous one, attach a number to an outcome, document the security posture, show the architecture. The test is portability. A buyer’s agent should be able to move your proof into a recommendation without guessing what it meant, because the guess is where you get described badly.

Write for the Memo You’ll Never See

Most B2B sites optimize for conversion. The page that matters most in an agent-mediated deal is one you’ll never design, because the buyer’s agent writes it: the internal recommendation that goes to the team.

That memo has a predictable shape. What the company does. Why it matters now. Where it fits in the stack. What problem does it solve that the current approach doesn’t. Who should evaluate it. What the risks and objections are. What evidence backs it. What the next step should be. If your site supplies those pieces cleanly, the agent assembles a credible case for you. If it doesn’t, the agent either leaves you out or describes you in a way you’d never sign off on, and you never find out it happened.

So write toward transmission, not just conversion. The question isn’t only “will this page persuade a visitor.” It’s “can a buyer’s agent turn this site into an internal recommendation that survives scrutiny from people who never visited it.” Optimizing for the memo you’ll never see is the closest thing this market has to a new fundamental.

Keep the Human Side Beautiful

None of this is an argument for an ugly, robotic, utilitarian site. The opposite. As the machine layer absorbs the facts, the human layer is freed to do the one thing the machine can’t: create belief.

The human visitor doesn’t need every FAQ, integration, and objection stacked on the homepage. They need orientation and confidence. They want evidence that the company has taste, judgment, and a coherent read on where the world is going. They want a thesis, the stakes, the mechanism, the proof, and a clear next step, delivered with enough conviction that they trust the people behind it. “Teams are adopting AI faster than their operating models can absorb, and the result isn’t just more automation; it’s more decisions, more handoffs, and more ways to get burned. We give teams a governed way to put agents into real workflows without losing visibility or accountability.” That gives a person a point of view. The agent layer underneath supplies the receipts.

Think of the visible site as a well-lit gallery and the agent layer as the archive and catalog behind it. The companies that win this won’t choose between the two. The human side earns belief; the machine side earns distribution, the quiet kind that happens inside chat windows and recommendation memos you never see. You need both, and they reinforce each other when you stop pretending one reader can do the job of two.

The Clever Move: Copy Briefing for My AI

Here’s the one new mechanic I’d ship first, because it’s cheap and it signals that you understand where buying is going.

Put a button on your key pages that reads “Copy briefing for my AI.” When the buyer clicks it, you hand them a clean, structured summary of the company, product, fit, alternatives, and next step, ready to paste into whatever tool they already trust:

I am evaluating [Company Name].

Summary:
[Company Name] is a [category] for [audience]. It helps [buyer/user]
solve [problem] by [mechanism].

Best fit:
Use it when [situation].

Not a fit:
It's probably wrong when [situation].

Key differentiators:
1. [Differentiator]
2. [Differentiator]
3. [Differentiator]

Main alternatives:
[Alternative categories or products]

Questions to ask:
1. [Evaluation question]
2. [Evaluation question]
3. [Evaluation question]

Recommended next step:
[Demo, trial, technical evaluation, docs, pricing request]

The old site asked the human to fill out a form so you could start selling. This one helps the human brief their agent so the selling continues after they leave, in language you wrote instead of language the agent guessed. That’s a small button doing real work.

A Short Audit

Before you publish, run the site against the reader who can’t see it. A handful of questions sort the legible companies from the rest:

• Can an agent name your category in one sentence and your buyer and user in two more?

• Does every page that matters stand alone, or do half of them only make sense after the homepage?

• Are your important claims specific enough to lift and quote without distortion?

• Do you have the machine layer: structured metadata, schema, an llms.txt, a plain-language agent briefing?

• Could a buyer’s agent build a fair vendor summary, compare you to the alternatives, surface the real objections, and recommend the right next step, all from your site?

• And is the human experience still clear, confident, and worth a person’s attention?

If the answer to most of those is no, you don’t have a content problem. You have a legibility problem, and the machine reading your site right now is already acting on it.

The New Bar

The old website was a destination. The thing we’re building is a source: for humans looking for confidence, for agents looking for structure, and for buyers trying to justify a decision to people who will never visit the page.

The job is no longer just to persuade one person to click. It’s to make the company easy to understand, easy to compare, easy to trust, easy to cite, and easy to recommend by a reader that takes you at your word and repeats exactly what you gave it.

Design for the human. Structure for the agent. Win the shortlist before the buyer ever fills out the form.

Subscribe now

The old playbook had a comforting shape. You found an underserved segment, spent eighteen months building something proprietary, locked customers into multi-year contracts, and let switching costs do the rest. Defensibility was a thing you could point to on a slide: years of engineering, a data advantage nobody could clone, an installed base too heavy to move. Marketing’s job was to narrate that fortress and price the rent.

That fortress is rubble. A product that ships Monday gets cloned by Wednesday because the hard part of building it has collapsed into a weekend of prompting against a frontier model. The technical lead that used to last years now buys you a few months, sometimes weeks. Cursor reportedly crossed $100 million in annual recurring revenue in roughly a year, and a dozen credible competitors showed up while it was still working out its own onboarding. Once the product stops being the moat, every assumption GTM was built on needs a second look, starting with the most flattering one, that a great product markets itself.

So the real question for whoever owns marketing now is what’s actually left to defend. The honest answer is uncomfortable, because it sounds like the soft stuff we spent a decade learning to distrust. Two things are left standing: taste and velocity. Not the product, not the data, not the contract. The feel of the thing and how fast you can make the next one. That changes what positioning, category work, and demand gen are even for.

Taste is the cover charge

When the technical differentiators dissolve, everyone reaches for the same word. Taste. If the models are commoditized, the argument goes, then judgment becomes the moat: the aesthetic sense, the editorial restraint, the instinct for what’s right that a machine can’t fake. It’s a flattering story for people who do positioning for a living, which is precisely why I distrust it.

Paul Graham made the observation that undercuts it in an essay about why he likes Swiss watches. Good design is centripetal. It pulls everyone toward the same right answer. When most people have bad judgment, the one operator with taste looks like a genius. But taste isn’t a secret. It’s a skill, and skills diffuse. The tools that bake in good defaults are in everyone’s hands now, the patterns are written down, and the median product in any category gets better-looking every quarter. The field converges.

Which does something specific to your positioning. Taste stops being a differentiator and becomes the price of admission. A product that feels clunky is dead before the first demo. A product that feels great no longer wins on feel because the other three vendors in the bake-off feel great too. Linear is the example everyone cites, and it cuts both ways: its design didn’t just lift Linear, it reset what every buyer in project management now expects on day one, which means Linear’s own polish bought it less room than the case studies imply. When everyone at the table has taste, taste gets you to the table. That’s all it does. The deck that opens with “beautifully designed” is describing the floor and calling it the ceiling.

Velocity is the engine

If taste only gets you in the room, velocity is what keeps you there. Not launch-week speed. The kind that compounds.

The fashion creative director is the comparison most people reach for. They invoke it to mean “have a vision.” The actual lesson is that it’s one of the most precarious jobs in business. Houses burn through creative directors with a brutality that has nothing to do with talent because talent was never the question. The question is whether you can deliver the next collection on time, before the room’s attention drifts. Nobody’s grading the show that just closed. They’re grading the market’s belief that the next one will be good.

Software runs on that same clock now, only compressed. The investor Elad Gil has put it plainly: in AI, a feature lead that once meant years means a quarter. Build one excellent thing, try to harvest it for a decade, and you’ll watch the harvest get cloned before the renewal lands. Velocity is the operational and cultural muscle to keep shipping reinventions while the last one is still getting applause. Feeling the market move, deciding what’s next, getting it out the door before the feeling goes stale.

For GTM that’s structural, not a matter of tempo. A launch motion designed to fire twice a year can’t carry a product that changes in meaningful ways every six weeks. The messaging has to be re-derived as fast as the product moves, which means the positioning is never finished, and the category story underneath it has to be sturdy enough to survive constant churn in the feature set above it. The teams winning here run marketing like a collection, not a campaign. New drop, new beat, same point of view. For twenty years the hard part was building. Now it’s not stopping.

Brand is real. The ground under it isn’t.

The Swiss watch story is the one the luxury crowd loves, and it’s worth telling straight, because the ending always gets dropped. It ran in three acts over about forty years. First, engineering merit, when a Swiss movement was simply the most accurate way to know the time. Then the quartz crisis, when cheap Japanese quartz made accuracy a commodity and gutted the function the whole industry sold. Then the brand age, when the survivors stopped selling timekeeping and started selling status, heritage, the object on your wrist.

Software is running the same three acts at ten times the speed. A product launches with a genuine technical edge. Improving models commoditize that edge inside a quarter. And it’s shoved, fast, into competing on experience and feel and brand, the same pivot the watchmakers took a full generation to make. The optimistic reading of that arc stops at act three: build a brand, reach the harbor, charge the premium forever.

The harbor isn’t safe, though. A brand is only as durable as the ground it stands on, and the Swiss watch brand age held right up until the Apple Watch colonized the wrist. The threat was never a rival watchmaker with cleverer branding. It was a different device that reset the whole stack and erased the distinction the brand existed to signal. In AI, the ground never stops moving. The model under you, the interface, the device, and the basic shape of the interaction, any of them can reset inside the life of a single company. A brand built on one interaction pattern goes stale the day that pattern changes. The luxury comparison leaves this part out because luxury, for a long stretch, got to stand still. You don’t get that.

What’s actually left

Taste is the cover charge. Velocity is the engine. Brand is shelter on ground that won’t hold still. What compounds underneath all three is harder to name and harder to copy: the instinct for finding the next real problem before anyone’s paying you to.

The operators who last won’t be the ones with the most refined taste or the loudest demand-gen machine. They’ll be the ones who get restless with their own wins, who can smell the commoditization coming for their own product before the market prices it in, who are already chasing the next genuine customer need while the current one is still on the board. That sits upstream of every positioning exercise you’ll ever run. You can’t position your way out of a problem that’s stopped mattering to anyone.

There’s a real irony in here for those of us who build brands for a living. The way to build one that lasts is to stay willing to walk away from it. You protect a brand age by refusing to get comfortable in it. So the move isn’t to cosplay the creative director’s taste. It’s to build a GTM org that can survive the creative director’s actual job: own as much of your own infrastructure and distribution as you can, treat every product and every campaign as this season’s collection rather than a monument, and keep your judgment pointed at hard customer problems instead of at curating how the last answer looks.

From the cheap seats, the company that wins the next decade will look like a luxury house. Impeccable taste, frightening pace, a point of view people pay just to stand near. Up close it’s less glamorous than that. It’s a room full of people who’ve made their peace with the fact that nothing they ship gets to be permanent and who’ve stopped wishing it would.

The most dangerous move a marketing or sales leader can make is to drift away from the work itself. It happens slowly and it looks like a promotion. You stop building campaigns and start reviewing them. You stop writing the email and start approving it. One day you’re the person who hasn’t logged into the ads account in eight months, the one who reads a dashboard and tells the team to go execute and you’ve quietly become a different kind of employee than the one you used to respect. Some leaders formalize the drift by renaming themselves. “Evangelist” is the tell: a title that means the job is now appearances and pronouncements with nobody underneath you who’d report that you still do anything.

The player-coach

The alternative has a name too, borrowed from sports. The player-coach finishes a meeting and then opens the Google Ads account to adjust live campaigns. She reads the metrics and acts on what they say instead of glancing at a number and delegating the thinking. She knows which landing page the traffic is hitting because she pulled it up this week not last quarter. Staying tactical like this isn’t nostalgia for the entry-level grind and it isn’t a refusal to delegate; it’s the only reliable way to keep learning and it’s how strategy actually improves. The plan changes because you’re doing the work, because the next move only becomes visible up close. You can’t see it from the altitude of a quarterly review.

That distance used to be a perk of seniority. Now it’s a career risk. The channels and tools turn over faster than any leader can absorb secondhand and the people getting replaced are the ones who lost touch with execution and never noticed. The title shift already underway in consumer brands points at where this goes: when Pepsi traded its chief marketing officer for a chief growth officer that wasn’t cosmetic, it was a company deciding the person at the top of marketing needs to own a number and know how it moves. The same logic is arriving in software businesses. The framing is almost Darwinian. If you can’t run at the pace of your fastest operators you fall behind, and the way to stay in shape is to keep doing the reps.

You can’t audit what you can’t do

The real exposure isn’t a stale skill set. It’s the moment you can’t explain why leads from a given source stopped converting and you’re the one accountable at the table. That gap shows up most painfully when a company is spending money it has no way to evaluate. Plenty of organizations hire an agency, a consultant, or an in-house specialist and have no idea whether the work is any good because nobody in leadership knows how to do it themselves. One company had a single specialist managing a million dollars in media spend with no one above able to judge whether it worked. Another had eight million dollars in Google AdWords run by an outside agency; the chief executive opened the first call by admitting he was spending eight million dollars and didn’t know whether a dollar of it produced anything. That isn’t a budgeting problem. It’s a knowledge problem wearing a budget’s clothes.

Whoever owns the spend under whatever title has to be able to audit the people spending it at a detailed level. That requires real fluency in the craft not a vocabulary for sounding fluent in a meeting. The same principle is why the marketing leader should be the face of the company’s podcast rather than handing it to a junior producer. The finished recording is the least valuable part of it. The value is in the process: meeting the guests, choosing the topics, working out how the thing gets distributed and who actually listens. That’s where the learning lives and where the relationships that compound into pipeline get built. Delegate the podcast and you’ve delegated exactly the part worth keeping.

The small, ordinary practice

None of this asks for heroics. The practical version is almost embarrassingly small. Take the hours you’ve freed up as you’ve moved up and reinvest a slice of them into hands-on familiarity. Open the ads account and poke around. Pull up the landing pages you’re sending paid traffic to and ask whether you’d convert on them. Sort a campaign’s ad groups from most expensive to least and follow the money into whatever you find. It really is that ordinary and it’s the difference between a leader who can interrogate a number and one who can only receive it.

When the work corrects the plan

Doing the work also changes what you build because the tactical view keeps correcting the strategic one. Consider the webinar, run almost everywhere as a lead-generation machine. Spend a few weeks actually running them and the premise falls apart: audiences don’t want to be sold, won’t wait twenty minutes for substance, and tune out the company-slide preamble. Sit in the data and you stop treating the webinar as a list grab and start treating it as a brand asset that earns trust, which is the one thing a fast-growing startup with money but no reputation can’t buy. You’d never reach that conclusion from a strategy deck. You reach it by watching real people drop off at minute nineteen and asking why.

The same correction runs through content syndication where companies hand a vendor an ebook to re-skin and embed across other people’s blog posts, usually against broad top-of-funnel search traffic the company could capture on its own. A leader who has ranked a page for a keyword knows this in their hands and knows the audited win rate on those syndicated leads sits near one-tenth of a percent. That’s paying a middleman to waste your sales team’s time. The person who can see it clearly is the one who has done the work the vendor is charging to replace.

Show, don’t recommend

There’s a quieter benefit to staying close and it shows up when you have to bring a skeptic along. Telling a client to swap the trade-show booth for a series of small filmed events rarely moves anyone. Going and running two of those events yourself, learning the process, capturing the video, distributing it, and knowing to the dollar what it cost and returned moves everyone. Demonstration outperforms persuasion and you can only demonstrate what you’ve actually done. The leader who delegated everything has nothing to point to but a recommendation.

Strategy is a hypothesis, not a document

The player-coach protects something specific. Strategy isn’t a document you write once and defend; it’s a hypothesis you revise every time the work talks back. The leader who stays in the account hears it talk back constantly in click-through rates and reply rates and the precise reason a channel stopped performing. The leader who delegated all of it hears a summarized version weeks late, already smoothed into a story that flatters the plan. One of them is steering. The other is being driven and calling it leadership.

So the instruction is plain enough to act on this week. Keep one hand on the work no matter how senior the title gets. Not because the grind is noble and not to second-guess your team, but because the work is where strategy comes from, and the day you can’t do it anymore is the day you stop being able to lead it. The operators still standing when the channels shift again will be the ones who never stopped logging in.

Anyone can produce content. It’s table stakes. The harder craft, the one that actually compounds, is producing content at high volume and distributing it so that the right people consume it, share it with influencers and decision-makers inside their own organizations, and begin an internal conversation about the very problem your product solves.

The arrival of generative AI has supercharged this reality. Where producing a single blog post once took hours, AI can now generate a dozen drafts in minutes. This doesn’t solve the marketing problem; it amplifies it. The challenge is no longer the physical act of creation, but the strategic act of differentiation. With the cost of content production plummeting to zero, the value has shifted entirely to the difficult, human-led work: deep audience understanding, genuine insight, and sophisticated distribution. In a world flooded with AI-generated noise, the premium is on content so specific and well-targeted that it can’t be ignored.

The return on all that patient education doesn’t arrive where you spend the effort. It arrives later, as sales efficiency. When buyers finally raise their hands, they come in already qualified. They’re arriving because they already understand your company and what makes it different. They’ve done the reading. They’ve had the internal debate. By the time they reach a salesperson, the hard part of the sale is behind them.

The result is a sales cycle that closes faster, at a higher win rate, with less sales overhead required to produce the same revenue. Fewer reps chasing colder leads. Fewer demos that go nowhere. Fewer deals lost in procurement because the buyer never understood why you were worth a premium in the first place.

Reinvestment is what turns a marketing tactic into a company strategy. That freed-up money, the overhead you no longer need once selling becomes efficient, can be reinvested. You can put it back into marketing, into the product, or into customer success. Fixing the customer education piece is what lets a whole company change shape. The savings don’t just sit on the income statement looking pretty; they fund the next round of advantage.

You Can’t Write for an Audience You Don’t Know

You cannot create the right content until you genuinely understand the audience. Not understand them the way a positioning deck claims to understand them, with three tidy personas and a list of pain points someone invented in a conference room. You have to physically get out into the market. Visit prospects and customers. Go alongside a sales rep, or go alone. Sit in the room, or on the call, and listen to how people actually describe the problem in their own words, with their own anxieties and their own internal politics attached.

What you learn out there is the raw material that feeds the entire content operation. The phrases buyers use, the objections they raise before they raise them out loud, the rival initiatives competing for their budget, the person two desks over who has to be convinced. None of that shows up in a keyword report. You collect it in person, and then everything downstream gets easier because you’re writing from the market instead of writing at it.

What Content Actually Works

Once you understand the audience, a counterintuitive move starts to pay off. Much of your most effective content has nothing directly to do with your product.

This feels wrong to people who measure everything. If we’re paying to publish, shouldn’t every piece sell? No. The most effective content runs parallel to what your audience already cares about. It acts as a gateway. It creates awareness first and earns the right to deliver deeper, product-specific material later. You show up where the buyer’s attention already is, talking about what already keeps them up at night, and you become a voice worth listening to before you’ve asked for anything.

The second lesson is about speed and volume, and most companies fail it badly. They simply don’t produce content fast enough to break through. The reasoning is plain: there’s no real ceiling on volume, because attention across every channel is a matter of supply and demand, and only volume cuts through. You’re competing for finite attention against an effectively infinite supply of other content. One thoughtful post a week loses that math before it starts.

Cutting through also depends on format. Picture your reader honestly. They’re on a phone, on a train, scrolling LinkedIn or Facebook between two other things. They will never wade through a twenty-paragraph essay. So the target is a total read time under two and a half minutes. That constraint isn’t a compromise; it’s the design spec.

A reliable structure for these short posts is to open with industry news and then pivot into your own point of view. The model generalizes to almost any industry. Lead with what just happened in the world your buyer lives in. Then tell them what you think it means. What makes it work is precisely its restraint.

Restraint matters because the action you’re creating is small. It’s a sliver of messaging that quietly begins the process of awareness. You spread the content with paid amplification, advertising spend that pushes a post in front of a targeted audience, yet you’re asking nothing of the reader. No form. No download. No demo. Because you ask for nothing, the buyer’s journey unfolds on its own. Information gets delivered. Conversations start inside the buyer’s organization. Eventually someone comes back to your website, encounters the value proposition (the concise statement of the benefit your product delivers and why it’s worth paying for), and converts into a genuine sales opportunity.

The conventional approach is the classic funnel: a top-of-funnel blog post to attract attention, a mid-funnel asset to download, then a push toward a demo or a price quote. The dashboards look fantastic. But almost none of those leads convert into actual revenue. You’ve optimized for the cost of a hand-raise, not for the readiness of the hand that’s raised.

The conclusion from that failure is the heart of the philosophy. You have to let the buying process happen on its own terms. The marketer’s only job is to deliver the right information at the right time so those internal conversations can occur. You’re not pulling buyers down a funnel. You’re feeding a conversation you don’t control and trusting it to mature.

This is also why generic content fails so badly.

Specificity and the Problem of Volume

Generic content fails because the same vanilla ebook or blog post, blasted out unchanged to everyone, simply disappears into the noise. And the noise is staggering. By a figure that was already a year old, something on the order of two million blog posts were published every single day. That number has likely climbed past two and a half or three million since. Your unremarkable post isn’t competing for attention. It’s drowning in company.

The antidote is specificity. Take one piece of content and tailor it deliberately. Change just a handful of words so that one version speaks to financial advisors and another to investment decision-makers. Same core idea, different reader, different framing of the stakes. These are small, almost trivial tweaks, and most marketers never bother to make them. That’s why they work. The advisor reads a post that sounds like it was written for an advisor, the decision-maker reads one written for a decision-maker, and both feel seen in a stream of content that ignored them. The difference between cutting through and being ignored often comes down to those few words, whether you’re using the content for inbound marketing or for outbound sales outreach.

The specificity problem is really half of a larger neglect. Most people pour ninety percent of their effort into creating content and almost none into figuring out how anyone will actually consume it. Two things have to be true at once. The content has to be genuinely worth consuming, and there has to be a real mechanism to get it in front of people. Either one alone is wasted motion.

Writing a blog post, dropping it on your company website, and having a few employees share it to LinkedIn for twenty views apiece is a waste of time. It feels like marketing. It produces almost nothing. What you need is a high volume of reads that are actually happening, reads by the specific people whose internal conversations you’re trying to start.

Solving that distribution problem is where paid advertising comes back in. Not as a contradiction of the organic philosophy, but as its accelerant. The organic part is what happens after the read: the sharing, the internal debate, the eventual return to your site on the buyer’s own schedule. Paid is simply how you guarantee the read happens at all, in front of the right person, at the volume the supply-and-demand math demands. You’re not buying conversions. You’re buying the first quiet moment of awareness, then getting out of the way.

What This Adds Up To

Done patiently, that machine produces qualified buyers who arrive already convinced, sales cycles that close faster at higher win rates, and overhead you can recover and reinvest. The single piece you fixed turns out to move the whole company. The waste was never the real prize. The real prize was teaching the market to sell itself.

Plenty of founders, especially technical ones, quietly dread selling. The picture in your head is the used-car salesman moving a bad product to someone who doesn’t need it, and you don’t want to be that person. So you try to design selling out of the company: credit-card-only signup, a free trial, anything that avoids getting on a call and pitching. The problem is that scaling revenue, landing stickier customers, and closing bigger deals all run through your ability to sell. No strong salesperson will bet their career on a founder who can’t close.

The good news is that the dread comes from a wrong definition of the job. Get that right and a founder-led process can run above a 50% win rate, and it holds up when you hand it to the salespeople you hire later. Three principles, plus the step most founders skip.

The reframe that makes it bearable

The unlock has nothing to do with closing technique. It’s that selling isn’t convincing someone to buy; it’s getting clear, fast, on whether they should. Once a sales call becomes a diagnosis instead of a pitch, the icky feeling goes away, because you’re no longer talking anyone into anything. You’re a doctor figuring out what’s wrong, and sometimes the honest answer is that this person isn’t your patient. The win rate is a byproduct of disqualifying early, before you’ve sunk hours into the wrong buyer.

Principle one: never go outbound

The first rule is blunt. Don’t do outbound, ever. Get the prospect to come to you. Expect them to fill out a form with real information about their company and role, and book a call on your calendar. Part of the reasoning is timing. Ten years ago a personalized cold email landed because almost nobody was sending them at scale. Today every inbox filters AI-written outreach into the promotions tab, and your prospect already knows an SDR agent wrote it. Outbound is a loser’s game: the response rate sits around 1%.

There’s a corollary worth coaching into every rep: once a meeting lands, you’re allowed to delete it. Look the person up on LinkedIn, check their company, and if they’re outside your ideal customer profile, decline politely and free both calendars. Tell them you want to respect their time and yours, and ask them to correct you if you’ve got it wrong. Protecting reps from bad-fit meetings keeps them working pipeline that actually moves.

And don’t confuse sales and marketing. Getting people to book is a marketing job, turning those bookings into revenue is the sales job, and conflating the two is a common founder mistake.

Principle two: never sell, diagnose

When the prospect shows up, the instinct is to launch into why your product is great. Don’t. The call opens with a question: you could be doing anything right now, so what’s going on in your company that made you book this? Then keep probing. How are you generating pipeline today? What have you already tried? Where are you in the buying process? What specifically are you looking for? None of that is you talking.

Call-analysis tools score how much of a call the rep spoke versus the prospect, and on a strong call the rep is mostly quiet. Drop a transcript into your favorite LLM and ask it to grade the call, and that talk ratio is the first thing it flags. The quality of the questions you ask sets the quality of the call, and the prospect describing their own problem out loud is worth more than any feature you could recite at them.

Principle three: never give a generic demo

The biggest founder mistake isn’t skipping the questions, it’s demoing blind. You’ve got a product with real surface area, every feature maps to some outcome, and people only buy outcomes. So before you share your screen, ask what matters to them. There’s a lot I could show you; what would actually be relevant? If they can’t name a feature, fine, they’ll name an outcome, and you build the demo around that. A walkthrough of everything you’ve shipped is the fastest way to lose a call you’d already half-won.

The rebuttal clever founders reach for is that the product is too new for prospects to know what to ask for. Sometimes true. But even then they’ll tell you the outcome they’re chasing, and an outcome is enough to personalize around. You’re not waiting for them to spec the demo; you’re listening for what they actually want the thing to do.

The step founders skip: define the next step

Here’s the part founders learn the hard way and young ones blow constantly. You run a sharp diagnostic call, you give a tailored demo, and then you close with “cool, I guess I’ll follow up.” That deal is dead.

What you send depends on the deal. A 20-to-30K mid-market deal should close in one call, maybe one and a half, so you send the proposal then. A million-dollar enterprise deal is a six-to-eight-month motion, so the deliverable is a clearly defined next step, not a contract. Either way you budget for it. On a 30-minute call: ten minutes asking why they’re here, ten minutes on questions and a personalized demo, ten minutes defining what happens next, down to who else needs to be in the room.

What you’re actually building

Notice that none of this is advice is closing technique. Come-to-you instead of outbound, diagnose instead of pitch, personalize the demo instead of dumping features, and always name the next step: every principle pulls in the same direction, which is toward telling the truth about fit faster than the other guy. That’s why the dread lifts. You’re not learning to talk people into things; you’re learning to find out, early and on purpose, who you can genuinely help and who you can’t.

That’s also why the playbook survives the handoff. A process built on persuasion lives and dies with the person doing the persuading, so it never transfers. A process built on honest diagnosis is just a set of questions and a discipline, and questions and discipline are teachable. Run it yourself until the win rate proves it works, then hand the salespeople you hire a system they can trust their careers to. Get selling right while it’s still your job, and you build something that keeps selling long after it stops being your job.

Most technical founders carry a quiet ranking in their heads. Research sits at the top. Engineering comes next, a notch below, because engineers implement what the researchers discover. Then, somewhere down in the basement, sits sales and marketing: the dirty work, the part you’d skip if you could. The comforting form of this belief is the line you’ve heard in every Bay Area kitchen: “If we just build a good enough product, it’ll sell itself, and we won’t have to deal with all that sales stuff.”

It’s a delusion, and an expensive one. Call it the Silicon Valley fallacy, and it’s worth naming where it breeds. The idea that a great product sells itself survives because it lets the people who love building things avoid the part of the business they find distasteful. It tells engineers that the work they already enjoy is also the only work that matters. That’s a flattering story. It is also how good products die in obscurity while worse ones take the market.

The fallacy has a cost you can measure. It shows up as a sales team treated as overhead instead of a discipline, hired late, paid on a different floor of respect, and handed a product nobody bothered to make legible to a buyer. It shows up as marketing reduced to “make the website nicer” instead of the work of deciding what category you’re in and what question you want a buyer to be asking when they go looking. Companies that believe products sell themselves tend to build products that require a genius buyer to understand them, then act surprised when the genius buyers are scarce.

Why the lie is so easy to believe right now

There’s a reason this fallacy is having a moment. We’re in a gold rush. Demand for anything with “AI” on it is so hot that founders barely have to sell; buyers are lined up, desperate to sign, eager to throw budget at tokens before they’ve figured out what they want from them. When inbound is that strong, you can run a company with no real sales muscle and post numbers that look like product-market fit. The orders arrive. The dashboard goes up and to the right. Who needs a sales team?

The right picture for this is the astronaut’s. The companies coasting on inbound are like astronauts in zero gravity. Float around long enough with no load on your muscles and they atrophy without you noticing, because nothing is asking them to work. The astronaut feels fine. He feels great, actually; everything is effortless up there. Then he comes back to Earth, gravity switches on, and he can’t stand up.

Gravity always comes back. The AI hangover is already starting: the CIOs who approved six-figure monthly bills are now asking what they bought, the token-maxing debauchery is meeting the morning-after invoice, and the easy inbound will cool the way every gold rush cools. When it does, the companies that built a real GTM discipline while it was unfashionable will still be standing, and the ones who decided their product would sell itself will discover their selling muscles wasted away during the years they didn’t need them. You don’t build a sales organization in the quarter you suddenly need one. You build it before, while you can still pretend you don’t.

“Sales” in this challenge is doing double duty; the phrase is “sales or marketing,” and the marketing half is where the fallacy does its quietest damage. Salesforce is the cleanest case. Marc Benioff is a marketer first, and the “No Software” campaign, the red circle with a slash through the word, decided how a generation of buyers thought about the category before a single rep dialed a number. Gainsight didn’t just sell software; it named “customer success” and convinced a market the function should exist. That naming work is marketing at its most load-bearing, and it’s the part technical founders are quickest to dismiss as fluff. Deciding what category you’re in, what question you want a buyer asking, and what words they’ll use to ask it: that’s not decoration applied after the product is built. It’s a choice that determines whether anyone understands what you made.

The product is the whole journey

The fix isn’t to bolt a sales team onto an engineering culture that quietly looks down on it. That just relocates the contempt. The fix is to redefine what “the product” actually is.

Define the product as the entire journey, from the first time someone hears the company’s name to their tenth renewal a decade later. The software is a large part of that journey. So is the marketing that frames it, the discovery call where a salesperson actually listens, the demo, the solution engineering, the onboarding, the renewal conversation. All of it is the product. Which means the people doing all of it are building the product, and there’s no second class.

The org runs to match. No engineering corner and sales corner. Engineers and salespeople sit intermixed. When a salesperson closes a deal, the engineers say “we closed a deal.” When an engineer ships a feature, the salespeople say “we shipped a feature.” One team, one scoreboard, no priesthood. This is shockingly controversial in the Bay Area, especially in AI. That it’s controversial is the tell. The contempt is so baked in that treating sales as equal reads as a radical act.

You can feel why it works once you stop ranking the functions. The engineer who sees sales as beneath her builds features nobody can sell. The salesperson who sees engineering as a black box sells things the product can’t do. Put them on one team accountable to one business outcome and the engineer starts asking how a customer actually behaves and how to change that behavior so they get more value, and the salesperson starts able to demo what was actually built. The seams between the functions are where deals leak. Sitting people together and giving them a shared number is how you close the seams.

What to do with this if you run GTM

The lesson generalizes past AI startups, because the fallacy isn’t about AI. It’s about respect, and respect shows up in your org chart, your comp, and your calendar.

Hire your first real GTM person earlier than your instincts say, and give the role the same seniority as your first principal engineer. Treating the first salesperson as a hire you’ll “get to once the product is ready” is the fallacy in scheduling form. The product is never ready in the sense that lets it sell itself.

Tie everyone, including engineers, to a business outcome rather than an intermediate metric. “We shipped four features this quarter” is the kind of number that lets a bloated org feel productive while moving nothing that matters. Revenue, retention, the share of a market you actually want: those are the numbers a one-team culture can rally around, and they’re the ones that survive a downturn.

And kill the seating chart that separates the believers from the help. The literal version matters less than the cultural one, but the literal one is a fast diagnostic. If your engineers have never sat in a discovery call and your salespeople can’t get an engineer to return a Slack message, you have two companies pretending to be one, and the gap between them is where your best deals go to die.

The companies that become legendary don’t get there because their product was so good it sold itself. They get there because they refused to believe that was possible, and built the muscle to sell while everyone around them was still floating, weightless, certain they’d never need it.

East of Silicon Valley runs a long set of brown oak-savanna hills that nobody had ever loved. They aren’t redwoods or coastline. The grass stays brown most of the year, and their one real distinction was deeply unglamorous. They happen to be the watershed for the San Francisco Bay, one of the most ecologically critical stretches of ground in the region, roughly the size of Yosemite. The Nature Conservancy (TNC) had wanted to protect them for years and couldn’t get anyone to care. The pitch was a sentence that died on contact: there’s a critical area east of Silicon Valley. Say it out loud. Nothing happens.

So TNC stopped describing the place and named it. They called the brown hills “The Mount Hamilton Wilderness,” after the local peak, and put the name on the map as though it had always been there. The effect was not cosmetic. The Packard Foundation wrote a large grant to protect the Mount Hamilton Wilderness. Local groups around the Bay started campaigning to save the Mount Hamilton Wilderness. Rival organizations began writing the Mount Hamilton Wilderness into their own documents as a settled fact of geography. Mike Sweeney, who ran TNC’s California chapter, would read those documents and laugh because, in his words, “You know we made that up.” Chip and Dan Heath, who tell the story in Made to Stick, land the lesson cleanly: the Mount Hamilton Wilderness is not a set of acres; it’s an eco-celebrity.

This is category creation in its purest form and the most honest example I know, precisely because TNC had nothing to sell. A nonprofit with no product and no profit motive discovered that its single largest strategic unlock was a proper noun it made up. The hills didn’t change and the acreage didn’t change; the word changed, and the word was the part people could finally pick up and carry.

A Name Gives People Something to Carry

People who live in cities know this in their bones. “SoHo” and “the Castro” were never survey coordinates. They’re characters, and the name is what handed each one a personality the street grid never supplied.

A name is a handle on a suitcase. A coherent block of imperiled watershed, packed with ecological argument and competing priorities, is heavy, and most people can’t get their arms around it. Stamp “The Mount Hamilton Wilderness” on the side and anyone can pick it up, point to it, defend it, and write it into a budget. That’s the same work Brian Halligan and Dharmesh Shah did when they drew a circle around blogging, email, and search optimization and called the bundle “Inbound Marketing.” The activities already existed as disconnected chores, and the name turned them into a philosophy you could join, and you joined it by going to HubSpot. It’s what Ward Cunningham did when he looked at tangled code and called it “Technical Debt,” handing engineers a phrase their managers already feared.

Vocabulary Becomes Infrastructure

A coined word does a second thing once it catches: it draws a line between the people who use it and the people who don’t. Learn a tribe’s vocabulary and you’re inside it; every CrossFit box (CrossFit affiliates are called "boxes" rather than "gyms”) runs on private language for exactly that reason. When your customers start saying your word instead of the generic one, leaving you means unlearning it, and that’s a cost most of them won’t pay.

I’ve run this play myself. At Mesosphere (later, D2IQ), while the industry was still fighting over how to run software across thousands of machines at once, we refused to sell “a distributed cluster scheduler.” We named the category the Data Center Operating System and shipped a command-line tool whose command was, literally, dcos. Every engineer who typed dcos node list reinforced the premise in their own hands: the data center is a computer, and a computer runs an operating system. The argument lived in muscle memory instead of in a slide anyone had to be sold on. A name asserts that a thing exists, and steady use quietly turns the assertion into common knowledge.

Name the Outcome

Naming works on funders and buyers by the same mechanism, the one Theodore Levitt described long before any of us got here: people don’t want a four-inch drill, they want a four-inch hole. They back outcomes they can see rather than inputs they can’t. An anonymous run of brown hills is an input. “The Mount Hamilton Wilderness” is the outcome, rendered so vividly you can already feel yourself standing in it. Naming is the craft of making an outcome visible enough that someone wants it badly enough to pay for it.

AI Rewards the Cleanest Handle

The lever has only gotten longer in a market run through AI. Ask a machine to explain your category now, and it reaches for the cleanest handle in everything it has read and repeats that one back to whoever asked. If the handle is the term you coined, used consistently by enough people, you land inside the answer by default, with the credit routing to you whether anyone recalls you started it. The market begins hiring for your word, writing it into job descriptions and analyst notes, and the machine simply mirrors that back. Owning the vocabulary has become the most durable position on the board because it keeps paying out while you sleep.

The Thing Still Has to Be True

One grown-up caution, since it’s the part the hype crowd always skips. None of this is spin. The Mount Hamilton hills genuinely were the Bay’s watershed and genuinely were in danger. TNC named something true, claimed it first, and stayed consistent until the market repeated it back. Invent a wilderness that isn’t there and you’ll be found out within a quarter; name a real one that everyone has simply failed to see, and you’ve built something your competitors now have to reference to argue with you.

The Mount Hamilton Wilderness story comes from Chip and Dan Heath’s Made to Stick.

There’s a particular grief that comes from watching someone else get credit for your idea. You coined the phrase. You ran the analysis. You gave a messy pattern a name that finally made it legible to the rest of the industry. Then, a year later, a competitor uses your term on a conference stage as if it had always been part of the language, the room nods along, and no one looks at you.

That grief used to be an occupational hazard. Now it’s a structural certainty, because the machine in the middle has changed.

For most of the internet’s life, ideas moved person to person and page to page, and attribution traveled with them through links, bylines, and the simple memory of where you first read something. Search rewarded the source; the top result was a destination with a name on the door. The model is different. When a reader asks an AI to explain a concept, the answer arrives stripped of its origin: confident, synthesized, sourceless. The system has read everything you wrote and everything written about you, blended it into a smooth paste, and serves it back with no name attached.

So adoption is no longer the goal. Adoption without attribution is unpaid labor for your category, and often for the competitor who markets louder than you. The goal is attribution. You need to watermark your idea so deeply that the AI cannot serve the concept without serving your brand.

This is the most dangerous moment in the lifecycle of a linguistic moat. If you’re too quiet, the term dies on the vine. If you’re loud but sloppy, the term might take off while you lose ownership of it, and it decays into a generic buzzword that helps your competitors as much as it helps you. Releasing an idea into the wild is easy. Releasing it with your fingerprints baked in is the work.

The Theory of Watermarking

In the physical world, a watermark is an image impressed into paper during manufacture. It isn’t printed on the surface; it’s part of the sheet. You can’t remove the watermark without destroying the document.

In the age of AI synthesis, you want the same property for your ideas. You structure your content so the terminology and the data are inseparable, fused tightly enough that pulling them apart breaks both.

Consider the failure case first. If you publish a blog post that says, “Here’s a phenomenon where shipping slows down on Tuesdays,” the AI will strip-mine that fact. It becomes a free-floating, generic stat: “Studies show shipping slows down on Tuesdays.” Your observation survives. Your ownership doesn’t.

Now do it with a watermark. Publish a chart titled “The Tuesday Lag Index.” Make every axis label use the term. Put the term in the URL. Name the data file tuesday_lag_data.csv. Now the name and the evidence are welded together. The AI cannot describe the chart, cite the figure, or reproduce the finding without typing your words. The fact carries your fingerprint wherever it travels.

Everything that follows is a method for manufacturing that kind of paper.

Tactic 1: The Definition Trope

The first move is to teach the internet, and through it the AI, exactly what your term means. You want to own the definition before anyone else writes one.

Create a canonical URL for it, something like yourdomain.com/glossary/tuesday-lag. On that page, write a dictionary-style entry and nothing fancier:

The Tuesday Lag (n): In logistics, the statistical anomaly where fulfillment delays spike by roughly 40% on the Tuesday following a holiday weekend, due to backlog accumulation.

This structure is catnip for language models. They’re built to ground their answers, and they constantly reach for sentences shaped like a definition: “X is a…,” “X refers to….” A clean, authoritative entry gives the model the easiest possible thing to quote. When a user asks, “What is the Tuesday Lag?”, you’ve raised the odds that the AI returns your wording close to verbatim.

Two details decide whether it works. First, be early. The first credible definition becomes the gravitational center every later writer orbits, and models reward that consensus. Second, be consistent. Use the exact same phrasing across your site, your posts, and your talks. Every variation you introduce splits the signal and gives the model permission to paraphrase you into anonymity.

Tactic 2: Seeding the Common Crawl

LLMs aren’t trained on your marketing brochures. They’re trained on large public scrapes of the web, the Common Crawl chief among them. To get your term into the model’s vocabulary, you plant it where the crawl reaches and where the training process assigns weight.

1. Reddit and forums. Start threads that discuss the phenomenon by name. “Has anyone else hit The Tuesday Lag after this last long weekend?” Models lean on Reddit because it reads as real people reaching real consensus, which is exactly the texture you want your term to acquire.

2. Wikipedia, the holy grail. If the concept is rigorous enough to survive editorial scrutiny and is backed by third-party citations, a Wikipedia entry is the decisive win. It functions as long-term memory for the AI, and it lends your term an air of settled fact.

3. YouTube transcripts. Spoken-word content increasingly feeds the training data. Record yourself explaining the concept, say the term plainly and often, and the auto-generated transcript seeds it in a format the crawl ingests cleanly.

The connective thread across all three is repetition of the exact string. A term mentioned once in a hundred clever paraphrases barely registers. The same words, repeated in many independent places by many different people, is the pattern a model learns. You’re not trying to be original each time. You’re trying to be consistent enough that the phrase calcifies.

Tactic 3: The Trojan Horse Asset

One of the most durable ways to watermark an idea is to bury it inside something useful, so people carry it for you without thinking about it.

In the Kubernetes war, we didn’t just write blog posts about the “Data Center Operating System.” We built a command-line interface where the command itself was dcos:

• dcos package install spark

• dcos node list

Every time an engineer typed that command, they reinforced the premise that this thing was an operating system. The argument wasn’t in a whitepaper anyone had to be persuaded by. It was in their muscle memory.

You might not ship a CLI, but the shape generalizes:

• A calculator. “Calculate your Tuesday Lag Risk Score.”

• A template. “The Tuesday Lag Staffing Adjuster.”

• A certification. “Certified Inbound Marketer.”

When a utility is genuinely valuable, people share it, and the name is welded to the tool. They can’t pass along the thing that helps them without passing along your vocabulary. Usage becomes repetition, repetition becomes training signal, and the watermark spreads on the strength of the favor it does for everyone who touches it.

Defensive Positioning: When They Steal It

If any of this works, competitors will start using your term. Your instinct will be to panic, to reach for a cease-and-desist. Don’t.

When a competitor adopts your terminology, they’re capitulating. They’re conceding that your map of the territory is the correct one, and they’re agreeing to argue on the ground you surveyed.

When Microsoft began talking about “Inbound Marketing,” HubSpot didn’t sue. They celebrated. If Microsoft is talking about Inbound, and HubSpot is the first result anyone finds for Inbound, then Microsoft is effectively buying ads for HubSpot. The theft routes attention straight back to the source.

The moment your competitors adopt your language, the game is over and you’ve won it. You’ve stopped being one vendor among several and become the standard everyone else has to reference.

The Ultimate Metric: Citation Velocity

In the old world, we measured keyword volume: how many people typed a phrase into a search box. In the new world, measure citation velocity, the rate at which your term shows up in the language other people use on their own.

How often does it appear in industry newsletters you don’t write? In analyst notes? In job descriptions? “Looking for a manager familiar with Inbound methodologies” is worth more than a thousand impressions, because a company has rewritten its own hiring around your word. That’s the market speaking your language back to itself, unprompted.

This is the measure that matters, because the AI is essentially a mirror of the market. When enough of the market describes its own reality in your terms, the model reflects that reality back to every person who asks it a question. The credit you once had to fight for becomes the path of least resistance for the machine.

That’s the whole point of the watermark. The grief at the start of this essay, watching your idea walk off without you, came from attribution being something fragile that you had to defend. Build the watermark well and that fragility becomes your defense: the more your idea spreads, the harder your name is to remove from it. You’re no longer a source someone has to remember to credit. You’re part of the answer itself.

If you walk into a marketing agency today and ask them to increase your lead flow, they will almost certainly talk to you about “Inbound Marketing.”

They will use the term casually, as if it were a fundamental force of nature like gravity or electromagnetism. But “Inbound Marketing” is not a natural phenomenon. It was invented in a conference room in Cambridge, Massachusetts, by the founders of HubSpot, Brian Halligan and Dharmesh Shah.

Before HubSpot, the activities that make up Inbound Marketing already existed. Companies were already writing blogs. They were already sending emails. They were already optimizing their websites for search engines. But these activities were disparate, disconnected chores. They were just “stuff marketing interns did.”

HubSpot’s genius wasn’t just building software to manage these tasks. Their genius was grouping these messy, disconnected activities together and giving them a name.

By coining the term “Inbound Marketing,” they created a conceptual container. They drew a circle around a specific set of behaviors (blogging, SEO, social media) and labeled it “Inbound.” Simultaneously, they labeled everything else, cold calling, TV ads, spam, as “Outbound.”

This wasn’t just a branding exercise; it was a coup.

Suddenly, you weren’t just “blogging”; you were practicing a philosophy. You were part of a movement. And crucially, if you were eager to learn how to do this new thing, you had to go to the people who named it. You had to go to HubSpot.

The Handle on the Suitcase

A simple label changes the economic value of an activity, and the reason sits in cognitive science. The human brain is a cognitive miser, constantly looking for ways to conserve energy. Processing complex, nuanced, or disconnected information is metabolically expensive.

Imagine a complex methodology, like the Kubernetes orchestration from the last post or HubSpot’s marketing philosophy, as a heavy, awkward suitcase. It’s packed with data, protocols, and exceptions. Without a handle, it’s almost impossible to pick up. You have to wrap your arms around it, heave it up, and shuffle forward. It’s exhausting.

A specific term acts as the handle on the suitcase.

When you coin a term like “Inbound Marketing” or “Data Center Operating System,” you are compressing a massive amount of information into a portable linguistic unit. You are giving the brain a shortcut.

Now, instead of explaining the entire history of container orchestration every time we want to discuss it, we just say “DCOS.” The brain accesses the label, unpacks the associated meaning, and moves on.

This is why “generic” content fails in the AI era. Generic content describes the contents of the suitcase (“Here is a sock, here is a shirt, here is a toothbrush”). It’s accurate, but it’s heavy. Proprietary terminology gives the user the handle. And the AI, just like the human brain, prefers the handle because it is the most efficient way to retrieve the concept.

Affordances for the Mind

In design theory, there is a concept called an “affordance.” A flat plate on a door affords pushing; a vertical bar affords pulling. The physical shape of the object tells you how to interact with it.

Words are cognitive affordances. They tell us how to interact with an idea.

If you don’t have a word for a problem, you can’t solve it. You can’t even really discuss it.

Consider the term “Technical Debt.” Before Ward Cunningham coined this metaphor, software engineers struggled to explain to management why they needed to refactor code. They would talk about “messy code” or “spaghetti logic,” which sounded like laziness.

But when Cunningham slapped the label “Debt” on it, he created a cognitive affordance. Managers understand debt. They know that if you don’t pay down the principal, the interest accumulates until it bankrupts you. Suddenly, the problem had a shape. It had a handle. Managers could “pick up” the concept and make decisions about it.

In your industry, there are dozens of problems that your customers are facing right now that they cannot solve because they cannot name. They are struggling with a vague sense of inefficiency or a friction they can’t articulate.

If you’re the one who hands them the language to describe their pain, the one who gives them the handle, they’ll trust you to solve it.

The Velvet Rope: Tribalism and Insider Status

Finally, proprietary terminology works because humans are tribal creatures. We use language to signal who is “in” and who is “out.”

If you walk into a CrossFit gym, you will hear a foreign language: WOD, AMRAP, Rx, Box, Burpee. If you know these words, you are part of the tribe. If you don’t, you are a tourist.

When you create a unique taxonomy for your business, you are inviting your customers into a tribe. You are saying, “We see the world differently here. We have our own words for things.”

This is incredibly sticky. Once a customer learns your language, once they start calling it “Inbound” instead of “digital marketing,” or “The Tuesday Lag” instead of “shipping delays,” switching costs skyrocket. To switch to a competitor, they would have to unlearn your language and learn a new one. They would have to give up their insider status.

The AI Connection

The same logic governs AI, which turns the challenge into an opportunity.

AI models are the ultimate outsiders desperately trying to become insiders. They are trained to mimic human language patterns, to blend in, to sound like they belong. When an AI encounters a term like “Inbound Marketing” or “Technical Debt” being used consistently by a tribe of experts, it assigns a high statistical weight to that term. It recognizes it as a “handle” for a specific cluster of concepts: a shortcut to efficiency.

The AI, like the human brain, is a cognitive miser. It prefers the handle because it’s the most efficient way to retrieve and package the concept.

If you successfully build a tribe around your terminology, if the market begins using your language consistently, the AI has no choice but to adopt it. It cannot accurately answer a question about modern marketing without using the word “Inbound,” because the training data overwhelmingly signals that “Inbound” is the correct handle for that conceptual suitcase.

And because you coined the term, you own the definition.

This is the fundamental shift from the SEO era to the AI era. In the old world, you won by ranking #1 for “marketing strategies.” In the new world, you win by making it impossible for anyone, human or machine, to discuss marketing strategies without using your vocabulary.

You’ve forced the AI to play by your rules, on your field.