The LeverageAI Canon

Someone to Hit
the Ball Back

The venue thinks it sells courts. It sells counterparty liquidity — and the experience economy was always a reciprocity economy.

For operators of venues, marketplaces, and multiplayer products who still describe facilities and sessions while customers buy other humans.

Eight chapters. Three parts. One product truth.

What this book gives you

  • The delete-test both ways: keep the players, lose the software — or the reverse.
  • Named concepts: counterparty liquidity, reciprocal activation, social liquidity (not community).
  • The liquidity flywheel and poker-room rake framing for experience businesses.
  • One rung past Pine & Gilmore: you are simultaneously product and customer.

Scott Farrell · LeverageAI · Sydney, 2026

leverageai.com.au

Part I

The Product You Actually Sell

Chapters 1–3 · Driveway, counterparty liquidity, the delete-test

01
Part I — The Product You Actually Sell

The Driveway Experiment

You can own the court and still not play. The missing product is not asphalt. It is a human who returns the ball.

There is a version of this story that ends with a booking app. Screenshots. A WhatsApp announcement. A customer told, gently or not, that they simply failed to follow the process. That version is how small businesses defend a migration they have already paid for. It is not how strategy works.

Here is the experiment that cuts through the screenshots. Take the sport offline. Put a court on a driveway — or any private rectangle of space where you could, in principle, hit a ball alone. Nets optional. Paddles optional. Perfect surface optional. Ask the only question that matters: do you play?

Most people who love the game still do not. The ball does not come back. There is no one to talk to in the breaks. The infrastructure is present. The product is absent.

“I play it on my own driveway, but the ball wouldn’t come back, and there’s no one to talk to. Otherwise, I’d just play it in my driveway.”

In this chapter

  • Why facility ontology fools operators into defending the wrong asset.
  • The Jobs-to-be-Done move applied to a wet Sunday and a paddle.
  • A North Star sentence that every layer of software must justify itself against.

They think they sell pickleball

Watch the operator’s ledger. Court hire on one line. A few dollars per player on another. Capacity counted in session slots. Staff time to unlock the shed. From that view, the business is obvious: we run organised sessions. Improve the app. Publish the inventory. Prove the announcement was sent. When a regular complains about friction, send screenshots. The customer is wrong about the process; the process is the product.

From the customer’s side the invoice is almost a lie. They are not paying for asphalt. They are not paying for a row in OpenSports. They are paying for a high probability that when they turn up with a paddle, another human will repeatedly return the ball — and that the two hours will contain enough light human texture to feel like a social sport rather than a lonely drill.

This is Jobs-to-be-Done with a net. Theodore Levitt’s old cut still holds: people do not want a quarter-inch drill; they want a quarter-inch hole.1 The club markets the drill — courts, sessions, brand, the sport itself. The job is the hole: someone suitable to hit the ball back, nearby, when the customer feels like hitting it. Name that once and the ontology error becomes hard to unsee.

Railroads thought they were in railroads. Newspapers thought they were in print. Recreational venues think they are in facilities. The discipline is older than AI: strip the current implementation and ask where value is actually created, what is scarce, and what competition is really over. Twenty years ago, organising thirty people by phone list and email may genuinely have been the hard capability. That constraint shaped the self-story: I organise sessions. Then Meetup arrived. Then apps. Then payments. Then agents. Coordination keeps getting cheaper. The self-story does not automatically update.

Strip the stack

Boundary cases are useful because they remove polite ambiguity. Push planning friction toward zero. Imagine waking late on a Sunday, no advance polling, and a simple intent: play soon, within a short drive, social pace. Now walk the stack the industry still worships:

booking app / notification history
→ published session inventory
→ court ID and timeslot
→ N players who actually appear
→ someone hits the ball back

Everything above the last line is candidate machinery. Some of it is load-bearing. Six courts times four players is real physical scarcity — do not pretend inventory is fake. But the polling ritual, the brand loyalty to a booking intermediary, the pride in a migration that still forces the customer to hunt — those are scars of old software, not the product. If a venue provides a court and then says “invite three friends,” it has kept the easy asset and outsourced the hard one. The court is not scarce from the customer’s perspective. Coordinated humans are.

So the North Star for this whole book is deliberately small and brutal. It is not a platform vision. It is not a community manifesto. It is one sentence the customer would recognise as true:

Someone suitable to hit the ball back, nearby, when I feel like hitting it.

Suitability includes pace, friendliness, and the light social grain of a session that is not three strangers staring at their shoes. Nearby includes drive-time and weather and the real geography of a Sunday morning. When I feel like it includes fuzzy intent — not only a firm commitment made last Tuesday because the inventory dropped on a schedule designed for software, not for humans.

We think this is the only sane altitude at which to judge the business. Not because courts do not matter. Because courts without return balls are driveways with better branding. The chapters that follow name the product properly — counterparty liquidity — run the delete-test both ways, and show why “community” is usually the wrong word for what customers actually need when they walk through the gate.

Key takeaways

  • 1.Run the driveway experiment on your own offer: if the counterparty vanished, would anyone still care about your facility?
  • 2.Write the job in lived language, not category language. “Hit the ball back” beats “premium racquet-sport experience.”
  • 3.If your process asks customers to bring the other humans, you are renting the easy asset and calling it a product.
02
Part I — The Product You Actually Sell

Counterparty Liquidity

Not raw headcount. Compatible humans, at a usable time and place, who will actually show up and reciprocate.

Once you admit the product is someone to hit the ball back, you need a word that travels. “Player liquidity” is good for sport. It is not good enough for the general case. Dating apps, poker rooms, multiplayer lobbies, local marketplaces — none of them are selling pickleball, and all of them live or die on the same scarcity.

The general name is counterparty liquidity: a high probability that compatible humans are present to reciprocate when you show up.

In this chapter

  • Why “enough people” is the wrong metric and compatibility is the real one.
  • The actual bundle a venue sells when it is honest.
  • How the same product hides inside poker, dating, and marketplaces.

Not thirty people. Thirty of the right people.

Liquidity language comes from markets for a reason. A market is not “alive” because a spreadsheet says capacity exists. It is alive when you can transact without heroic effort. In recreation the transaction is reciprocal play. That means raw headcount is a vanity metric.

Pool What you actually have
30 players somewhere in the cityAlmost useless
30 within a 15–20 minute driveBetter
…available Sunday morningBetter
…roughly compatible skill and social paceBetter
…who will actually show upA market

That ladder is the difference between a full calendar and a playable morning. Operators often optimise the top rows — city-wide followers, email lists, app downloads — while the product lives at the bottom. Counterparty liquidity is not a marketing audience. It is arrival-time density of people who can complete the loop with you.

A poker room without players is worthless. Beautiful software, perfect tables, zero counterparties: product value zero.

The bundle the P&L refuses to name

If you force honesty, the recreational venue is not selling a sport SKU. It is selling a bundle:

  • 01Counterparty liquidity — enough suitable humans will be there.
  • 02Compatibility — skill band, social tone, show-up reliability.
  • 03Rotation / matching — so you are not locked to the same three faces for two hours.
  • 04Venue — real courts, nets, a place the market can clear.
  • 05Light social coordination — enough structure that strangers can play without a committee meeting.

The sport itself is the protocol everybody agrees to use so the interaction has rules. That is almost funny when you say it out loud. Pickleball, soccer, poker, doubles tennis — different protocols, same economic object underneath: other people’s willingness to enter the loop with you.

Notice what is not in the bundle as the hero asset: the booking UI, the logo, the migration from Meetup to whatever is fashionable this year. Those can help or hurt. They are not the moat. The moat is density of willing counterparties at times people actually want. Empty rooms stay empty for a reason we will formalise in the flywheel chapter. Busy rooms attract more players because the product — other humans — is already on site.

The same product wearing different shirts

Once the term is in your mouth, you see it everywhere. An online poker room is not primarily selling card graphics; it is selling a seat next to suitable opponents without a two-hour wait. A dating product is not primarily selling profiles; it is selling a non-zero chance of a compatible human who will also show up and engage. A two-sided marketplace is not primarily selling listings; it is selling the other side of the trade. A multiplayer title with empty servers is a single-player game with better marketing.

We will port the doctrine properly in the final chapter. Here the point is definitional: any business whose real product is the other people is a counterparty-liquidity business, whether or not the founder can say the words. Most cannot. They say community. They say engagement. They say experience. Those words are not always wrong, but they are soft enough to hide a zero on the only metric that clears the market.

One fence, because sibling work exists for a reason. How you assemble fuzzy demand into a cleared session — continuous intent, graded willingness, demand-first formation — is market microstructure. That is not this book’s job. This book owns what is being sold once you stop lying to yourself. The assembly layer has its own treatment next door. Here we stay on the product: compatible humans who reciprocate.

Key takeaways

  • 1.Define success as compatible arrival-time density, not downloads or city-wide reach.
  • 2.Write the five-part bundle on a whiteboard. Fund the parts that create counterparties.
  • 3.If your category has two sides, ask which side is the scarce counterparty for your customer — and whether you are actually producing it.
03
Part I — The Product You Actually Sell

The Delete-Test

Delete the software and keep the humans: delighted. Keep a perfect app and delete the humans: worth zero.

Definitions are cheap. Diagnostics are expensive — which is why operators avoid them. The delete-test is the cheapest expensive tool we know: two thought experiments, five minutes in a leadership meeting, no consultants required. It does not ask what you wish you sold. It asks what still has value when you remove the parts you are currently proud of.

Run it both ways. One direction flatters the app. The other direction tells the truth.

In this chapter

  • Direction A: software vanishes, players remain.
  • Direction B: software is perfect, players vanish.
  • Why this is terminal-value thinking applied to counterparties, not code.

Direction A — delete the software

Imagine tomorrow morning every booking intermediary disappears. No OpenSports. No Meetup. No polished push notifications. No AI chatbot on the club website. Somehow — paper list, habit, SMS, a human who still has everyone’s number — twenty-eight reasonably compatible, friendly players still arrive every Sunday at ten. Courts are ready. Nets are accessible. The rotation still works. Someone still says “good shot” after a lucky dink.

Does the regular care that the software died?

Of course not. They are delighted. The product they bought is intact.

That answer should make product teams slightly ill. It means the artefact they migrated for, argued about, and sent screenshots to defend was never the terminal value of the business. It was scaffolding. Useful scaffolding, sometimes. Scaffolding you can still improve. But scaffolding.

Direction B — delete the players

Now invert it. Keep the perfect stack. Gorgeous app. Instant booking. Apple-smooth payments. A vision-headset tutorial if you insist. Marketing site that would make a Series B deck blush. The customer turns up and finds:

no players

Product value: zero.

Same court. Same net. Same paddle. Same ball. Same brand. The loop does not close. There is no one on the other side of the protocol. You have built a driveway with a login screen.

Someone friendly hits the ball back. That phrase beats “community,” because community is provider marketing mush. The lived outcome is a return ball and a human who produced it.

The keep / delete matrix

Keep Delete Customer result
28 friendly compatible players, playable format All booking software Delighted
Perfect app, AI concierge, brand The players Product = zero
Court + net + ball only Counterparties Driveway with better signage
Counterparties + light structure Staff key-holder theatre (if access is solved) Often still fine

The last row is a deliberate provocation, not an HR policy. Many sessions still need a human for exceptions, safety, or genuine hosting. The point of the matrix is not “fire everyone.” It is to stop confusing necessary access control with the thing customers buy. If the employee is mostly a biological lock, you have an operations smell. If the employee is manufacturing social energy and match quality, they may be part of the liquidity system. Audit which is which.

Terminal value, different class of answer

Elsewhere we have argued that boards should select AI projects by whether they defend terminal value under cheap cognition — not by near-term workflow ROI. The same altitude question applies here, with a different answer class. When coordination software gets cheap, what still makes the experience business valuable? Not the session row. Not the migration. The scarce, hard-to-fake layer is reciprocal human presence: counterparty liquidity dense enough that the delete-test fails in the software-only direction and passes in the humans-only direction.

You do not need to join a family brand to get that. You do not need twenty-two WhatsApp announcements. You need enough familiar-ish, friendly-ish humans that the game works and the two hours feel socially usable. Chapter 5 will refuse the word “community” for that need. Here it is enough to lock the diagnostic:

If deleting the people zeros the product while deleting the software barely dents it, the people were the product. Fund, measure, and defend accordingly. Everything else is a supporting actor that has been over-billed in the credits.

Later chapters assume this test. Reciprocal activation explains how the other humans create value moment by moment. Social liquidity explains the light texture customers want without a cult of belonging. The flywheel explains why density compounds. The ladder in Part III explains why this product rises in value as machines absorb everything countable around it. But if you only steal one tool from the book, steal this: run the delete-test both ways before you spend another dollar proving the customer used the app wrong.

Key takeaways

  • 1.Formalise both deletes in writing. If leadership disagrees on the answers, you do not yet share a product definition.
  • 2.Budget the moat that survives Direction A: compatible humans and the formats that keep them coming.
  • 3.Treat software as accountable infrastructure. It must earn its keep against the North Star, not against migration sunk cost.
Part II

How Reciprocity Works

Chapters 4–6 · Activation, social liquidity, the flywheel

04
Part II — How Reciprocity Works

Reciprocal Activation

You do not arrive with a full tank of motivation. The other human fills it — moment by moment.

Ask a group of men in their fifties whether they feel like running on a random Tuesday. Many will give you a polite version of no. Ask what happens on Saturday when a ball rolls loose across a soccer pitch with twelve of their lunatic friends on it, and the answer changes before the sentence finishes. They chase. They did not download willpower from an app. The ball moved, another human wanted it, and their body joined a system that did not exist when they were alone in the kitchen.

That is not “engagement.” It is not community spirit in the brochure sense. It is a mechanical property of multiplayer human activity: reciprocal activation.

In this chapter

  • Why motivation is manufactured in play, not stored in advance.
  • The activation loop with two centres of intent.
  • Why independent agency is the ingredient machines struggle to fake.

The ball rolls past

The soccer version is almost comic in its reliability. Training talk turns up the same confession: outside the pitch, running is optional and usually skipped. On the pitch, a ball in motion is an irresistible cue. Twelve old men who would not jog for a podcast will sprint because the ball is there and someone else is also sprinting. The incentive is not abstract health. It is immediate, social, and competitive in the light way that does not need a league table to work.

Pickleball produces the same pattern with a smaller object. Someone hits a ball toward you. You become crazily interested in hitting it back. The motivation did not pre-exist as a complete internal speech about cardio. It was triggered by another person’s action. Your return then becomes their trigger. The session is a chain of mutual activations that neither party could bootstrap alone at the same intensity.

Ball rolls past → twelve old men chase it. The game manufactures motivation reciprocally.

The loop

someone acts (hits / kicks / bluffs / passes)
you are activated
you act
they are activated
repeat until the clock dies

Counterparty liquidity, from Chapter 2, is the stock condition: enough suitable humans are present. Reciprocal activation is the flow: what those humans do to each other’s nervous systems once present. Liquidity without activation is a waiting room. Activation without liquidity is a fantasy about friends who never schedule. The product needs both.

This is why the “crazy motherfuckers” framing is more than comedy. You think you are buying a sport. You are buying contact with other people who want the ball as badly as you do — people too old to pretend it is serious and too alive to treat it as optional. Team-sport marketing talks about belonging. The lived mechanism is simpler: someone else kicks so you chase; someone else hits so you swing.

Independent agency is the point

A defender who actually wants to stop you changes the meaning of your run. A teammate who actually wants the pass changes the meaning of your glance. A pickleball opponent who wants the point changes the meaning of your dink. The other person is not a prop in your workout. They are another centre of intent. Your action matters because it lands in a mind that is not yours and returns as a new problem.

Strip that independence and you can still get heart rate. You can still get reps. You can still get a data summary of your swing path. What you lose is the self-energising social physics that makes two hours feel short. That is why solitary substitutes so often feel like homework even when they are “better training.” They are missing the second brain in the loop.

Design for triggers, not speeches

Operators who understand activation stop trying to pre-motivate customers with content alone. Inspiration videos do not replace a ball in motion. Loyalty emails do not replace a human who shows up wanting a game. The format questions become practical:

  • How many reciprocal triggers per hour does this format create?
  • Does matching put people in loops quickly, or strand them waiting?
  • Are we optimising for spectator polish or for mutual action?

We think this is the deeper product underneath counterparty liquidity. Liquidity gets bodies in the room. Activation is what those bodies do to each other so the room becomes a living system none of them could produce alone. Miss that, and you will keep describing your business as facilities and sessions while customers quietly describe it as “the only place where I actually move because someone else made me.”

Next we separate the light social texture that supports activation from the heavy identity project operators call community. They are not the same product. Confusing them is how you overbuild belonging programmes and underbuild arrival-time humans.

Key takeaways

  • 1.Treat motivation as an emergent property of the loop, not a prerequisite customers must bring fully formed.
  • 2.Count reciprocal triggers. Formats that starve the loop will feel dead even when courts are booked.
  • 3.Protect independent agency in the design. Props and bots can train; they do not replace a second intent.
05
Part II — How Reciprocity Works

Social Liquidity Is Not Community

Belonging is optional. Arrival-time humans with light texture are not.

“Community” is the word operators reach for when the invoice cannot name the human part. It sounds warm. It fits a slide. It implies loyalty, culture, and a Facebook group with a cover photo. It is also, very often, the wrong product specification.

Most adults who turn up to hit a ball are not applying to join a family. They want social liquidity: when they arrive, there are enough friendly humans for the social interaction the activity needs.

In this chapter

  • A hard distinction between community and social liquidity.
  • Why rotation is liquidity engineering, not a nice-to-have.
  • How overbuilding identity programmes misses the arrival-time job.

Two different products

Community Social liquidity
Identity and belonging Arrival-time availability of light social texture
Ongoing relationships Enough friendly humans for this session
Shared culture, rituals, in-group G’day, good shot, what’s your name again
Often slow to build; high commitment Can be produced session by session with density + format
Marketing-friendly Operationally load-bearing

Friendships may form later. Fine. Celebrate them when they do. But the club does not need to manufacture an “ATP family” for the product to work. It needs to maintain social liquidity around the game: familiar-ish, friendly-ish humans so the two hours feel socially pleasant and the ball keeps moving among more than a sealed clique.

You want enough familiar-ish, friendly-ish humans that the game works. That is social liquidity, not community.

Rotation raises liquidity quality

Here is a format fact operators underprice. A session that locks you with the same three people for two hours can still be “full.” It can still clear a booking. It is often lower-quality social liquidity. You get one social micro-climate. If the chemistry is flat, the whole block is flat. If the skill mismatch is awkward, you live in it.

Rotation changes the microstructure. Many lightweight collisions replace a single sealed foursome. You say g’day more often. You learn a few names without being forced into intimacy. You get the social grain of a market, not the intensity of a dinner party. For a large class of adult customers, that is exactly enough — and more attractive than a high-pressure belonging pitch.

Low liquidity quality

Same three people for two hours. One social draw. High variance. Feels like a private lesson you did not ask for if the mix is wrong.

Higher liquidity quality

Many short collisions. Names, laughs, resets. The room feels peopled. Activation has more surfaces to catch on.

This is liquidity engineering, not vibes. Counterparty liquidity asked whether suitable people exist at arrival time. Social liquidity asks whether the format turns those people into usable social texture or wastes them as a static seating chart.

Stop building the wrong cathedral

Community programmes are not evil. Some businesses truly sell belonging — churches, certain clubs, long-horizon teams. Saturday soccer with a season commitment can lean that way on purpose: a forward contract on the same lunatics for eighteen rounds. The error is using community language as a fog machine when the customer is buying a lighter good.

Overbuilding identity creates its own frictions: mandatory chats, performative loyalty, announcements that treat every regular like a staff member. Underbuilding social liquidity creates a colder failure: you arrive, the maths of the booking worked, and the human texture is too thin for the session to feel like the product you paid for. The delete-test from Chapter 3 already hinted at this. Customers can forgive a dead app. They cannot forgive a dead room.

So rewrite the operating goal. Not: make them join our family. Instead: maintain reliable access to player and social liquidity so someone friendly is there to hit the ball back. Measure density, compatibility, show-up rates, and collision quality. Let friendship be an optional surplus, not the SKU you pretend to ship every Tuesday.

A practical test helps. After a session, can a first-timer name two people they exchanged more than three sentences with? If the answer is routinely no, you may still have counterparty liquidity in the thin sense of bodies present, but social liquidity failed. If the answer is yes without anyone being forced into a bonding exercise, the format is doing its job. That is a very different KPI from newsletter open rates or group-chat message volume — both of which can rise while the court feels cold.

We are not anti-friendship. We are anti-category error. Call the light product by its real name, engineer for it, and stop using community language as a polite cover for missing humans. The flywheel in the next chapter depends on this honesty: density compounds when arrival feels good, and arrival feels good when social liquidity is real.

Key takeaways

  • 1.Replace community mush with an arrival-time specification: how many friendly humans, at what compatibility, with what collision pattern?
  • 2.Use rotation and remixing as deliberate liquidity-quality tools.
  • 3.Allow community to emerge; do not require it as the ticket to a decent session.
06
Part II — How Reciprocity Works

The Liquidity Flywheel

Empty rooms stay empty. Busy rooms attract players. The fee is a rake on that fact.

Online poker is honest in a way most recreational venues are not. You cannot book a full table weeks ahead the way you book a tennis court, except at the edges of big tournaments. Players arrive when they have time. The room’s job is to have other players there. When the product works, you sit quickly with suitable counterparties. When it fails, you stare at empty seats. The software can be exquisite. Without liquidity it is a museum of felt.

Poker rooms know what they charge for. They take a rake. You are not paying for the table legs. You are paying for the probability that someone else is there to play.

In this chapter

  • The rake reframe for the few dollars per player.
  • Why density compounds and emptiness is sticky.
  • Spot markets versus season-long forward contracts on humans.

The $5 is not a booking fee

In the flagship story that opened this book, the club’s margin looks like a small per-player contribution on top of court hire — a few dollars a head, enough to make a session worth staffing if thirty people clear, not a fortune if they do not. On a ledger it resembles a booking fee or a service charge. Economically it is closer to a rake on liquidity.

The customer already understands this intuitively. They will pay something modest for the right to walk into a room where the product — other humans — is present. They will not forever pay for the privilege of wrestling a UI so they can discover that the room is thin. Confusing the rake with a software fee is how owners end up defending the app while the actual asset — density — goes unmanaged.

You’re paying the rake for the fact that there are other players here. Poker is upfront about that. Most venues are not.

How the flywheel turns

  1. 1.Density appears — enough compatible players at a time that play works.
  2. 2.Activation fires — reciprocal loops make the session feel alive (Chapter 4).
  3. 3.Social liquidity feels good — light texture without mandatory cult membership (Chapter 5).
  4. 4.Repeat intent rises — people want to return when the product is the other people.
  5. 5.Density deepens — busy rooms attract more players because the counterparty is already there.

The reverse flywheel is just as real. Empty rooms stay empty. Thin sessions teach regulars that the product is unreliable. They poll less. They defect to whatever denser pocket they can find. Marketing then tries to paper over a liquidity hole with acquisition, which is the expensive way to fight physics. Marketplace cold-start dynamics are not a special case of consumer internet; they are the general case of any counterparty business.2

This is why “late registration” language keeps fitting social sport. When a second session still has seats and you jump from the first into the second, you are not consuming inventory like a cinema ticket. You are responding to live liquidity. The room reorganises around who is actually present. Poker does this continuously. Many clubs still behave like a primitive batch auction: publish a slot, hope humans fill it, close the market early, then act surprised when demand was fuzzy and the calendar was rigid.

Two market structures for the same product

Not every sport solves liquidity the same way. Saturday soccer for a season is a different instrument. You commit early. You pay for the year. A dozen other people commit. Grounds are allocated. For eighteen rounds you have purchased something like a forward contract on player liquidity. On match day you do not ask whether enough lunatics will feel like soccer. The market cleared months ago.

Social pickleball, in the spot-market version, clears every session. That is why it feels fragile. It is also why the upside of density is so large when a venue accidentally gets good at it: six courts full, thirty people, rotation humming, the flywheel visible in real time. The operator may still think the win was “we booked the courts well.” The customer experienced reliable counterparties.

Season / team (forward)

High commitment up front. Liquidity pre-assembled. Lower weekly discovery cost. Identity can thicken because the cast is stable.

Session / open play (spot)

Lower commitment per date. Liquidity must re-form often. Higher need for ignition, visibility of fill, and formats that make thin nights less deadly.

Operate like a market maker

Once you accept the flywheel, the job description changes. You are not primarily a court landlord. You are a market maker for recreational intent: detect forming density, ignite sessions that can clear, avoid publishing ghost inventory that trains customers to expect emptiness, and take a rake that is honest about what it purchases.

How continuous intent books and agent-held demand change the assembly layer is a sibling problem — important, but not the claim of this chapter. Here the economic object is enough: liquidity attracts liquidity; emptiness taxes everything downstream; software does not replace density.

Part III lifts the same object into macro language. If machines make booking, coordination, and content abundant, the rake-worthy good was never the transaction. It was the reciprocal human. Pine and Gilmore gave us a ladder for experiences. We need one more rung for the case where you are both product and customer.

Key takeaways

  • 1.Price and describe the fee as access to counterparty liquidity, not as a software convenience charge.
  • 2.Manage the flywheel explicitly: protect density, kill ghost sessions that teach emptiness, measure fill quality.
  • 3.Choose market structure on purpose — spot versus forward — instead of inheriting a calendar because the app template had one.
Part III

The Economy That Emerges

Chapters 7–8 · The ladder extension and cross-domain ports

07
Part III — The Economy That Emerges

One Rung Past Pine & Gilmore

The experience economy was always, for this class of product, a reciprocity economy.

In 1998, B. Joseph Pine II and James H. Gilmore argued in the Harvard Business Review that experiences had become a distinct economic offering — not merely goods wrapped in service theatre. Their progression is now familiar: commodities are fungible, goods tangible, services intangible, experiences memorable. As each lower rung commoditises, value and pricing power move up the ladder. When you stage an experience, you charge for the time customers spend with you.3

That ladder still holds. AI simply commoditises the bottom faster. What it does not do is replace the reciprocal rung Pine and Gilmore did not quite draw.

In this chapter

  • The classic ladder, cited properly.
  • Why reciprocal sessions are not experiences you merely consume.
  • The human reciprocity premium as synthetic cognition gets abundant.

The ladder we inherited

Rung Economic function Nature
CommoditiesExtractFungible
GoodsMakeTangible
ServicesDeliverIntangible
ExperiencesStageMemorable
Reciprocal co-productionMutually activateYou are product and customer

Pine and Gilmore’s birthday-cake progression made the climb intuitive: farm commodities mixed at home, then industrial cake mix, then bakery service, then outsourced party experience. Later work in their line also discusses transformations above experiences. Useful context. Our claim is lateral rather than a quarrel with their stack: some offerings are not experiences a provider stages for a consumer; they are reciprocal systems in which each participant is simultaneously product and customer to the other.

Not all experiences are equal under AI

Netflix is an experience. A themed café is an experience. Talking to a model can be an experience. A ball machine is an experience of a sort. None of those require another autonomous human to want something from you in real time.

Reciprocal human experiences contain a different ingredient:

I act
another autonomous human experiences my action
they react
I experience their reaction
two centres of intent, one living system

That is the loop Chapter 4 named as reciprocal activation, now placed on the economic ladder. The venue can stage conditions. The market maker can assemble density. The machine can clear logistics. The value customers keep paying for is the other mind in the loop.

A ball machine returns the ball better. Who gives a fuck. I nutmegged Dave and he called me a cunt. Now we’re having an experience.

The human reciprocity premium

As synthetic production becomes abundant — text, images, code, analysis, even fluent conversation — the scarcity profile of the economy shifts. Things that were hard because they required cognition get cheaper. Things that were always hard because they required another person’s free choice become more visible as the residual source of value.

Call that the human reciprocity premium. Not because models cannot mimic chat. Because Claude cannot currently give you the core of the pickleball product: another body that wants the point, laughs when you both miss, and forces you to react in physical space. Machines historically priced what is countable, ownable, schedulable, transactional. They modelled court, session, capacity, booking, payment. They shoved the reciprocal loop under a fog word: community. AI can hold more of the fuzzy demand and assemble conditions without being the thing assembled for. That is a healthier North Star than replacing the partner across the net.

We already made food arrive without speaking to anyone astonishingly efficient. We did not make “find enough compatible people for something worthwhile this afternoon” remotely as efficient. That imbalance is the commercial opportunity hiding inside the loneliness statistics: not more content about connection, but better assembly of reciprocal presence. The coordination layer around physical human connection is still prehistoric compared with the consumption stack.

Name the economy correctly

So the shallow version of the experience economy — spend less on stuff, more on concerts and restaurants — is incomplete. The deeper transition, as cognition and coordination get cheaper, is that reciprocal human presence becomes more legible as a scarce source of value. Experiences you consume can be synthesised further. Experiences you co-produce with another free agent cannot be fully synthesised without destroying the product.

That is why the delete-test keeps returning the same answer. That is why the rake is on liquidity. That is why social liquidity beats community mush as an operating target. And that is why AI’s best role in this story is not to be Dave. It is to get Dave and you into the same rectangle of space, then shut up while the ball does the rest.

The last chapter ports the doctrine without adding a new one: poker, dating, marketplaces, multiplayer — anywhere the ball, the match, the trade, or the raid only works if someone hits it back.

Key takeaways

  • 1.Keep Pine & Gilmore’s ladder; add the reciprocal co-production cut for two-sided human products.
  • 2.Price and protect the reciprocity premium as synthetic alternatives multiply around it.
  • 3.Use machines to assemble conditions; refuse products that try to replace the second centre of intent.
08
Part III — The Economy That Emerges

Anywhere the Ball Comes Back

Poker, dating, marketplaces, multiplayer — same doctrine, different protocols.

If the argument only worked for pickleball, it would be a sports-ops pamphlet. It works because the product was never the sport. The sport was a protocol. The product was a counterparty. Change the protocol and the doctrine still travels.

No new thesis here — only ports of Chapters 1 through 7, plus a diagnostic you can run on Monday.

In this chapter

  • Four domains under the same delete-test.
  • A six-check portable diagnostic.
  • The driveway callback that closes the loop.

Four ports

Poker

P&L language says tables, rake percentage, software client. Delete-test says: empty room equals zero, regardless of graphics. The business already speaks liquidity and rake honestly. Recreational venues should steal the honesty, not necessarily the vice.

Dating

P&L language says profiles, swipes, subscriptions. Delete-test says: if suitable counterparties never become real-world reciprocal presence, the product failed even if engagement metrics soared. Social liquidity here is arrival-time willingness to engage as a human, not a larger photo library. Community branding (“join our singles family”) is usually a category error; people want compatible humans who show up, not a new identity cult.

Marketplaces

P&L language says listings, take rate, search ranking. Delete-test says: one empty side zeros the trade. Counterparty liquidity is the other side of the market at usable quality and time. Flywheel dynamics are textbook. The operators who win obsess over density and match quality; the ones who lose obsess over feature parity on the storefront.

Multiplayer

P&L language says content drops, battle passes, engine tech. Delete-test says: beautiful game, empty lobby, product value approaches single-player with worse UX. Reciprocal activation is the raid, the duel, the squad that needs you. Social liquidity is a peopled server, not a lore wiki. The moat is who is online and matched — again, humans.

Domain Thinks it sells Delete-test product
Social sportCourts / sessionsReturn ball + light human texture
PokerTables / softwareSuitable opponents now
DatingProfiles / matchesHumans who reciprocate offline
MarketplaceListings / checkoutThe other side of the trade
MultiplayerContent / clientPeopled lobbies and live opponents

Portable diagnostic

Steal this checklist. Run it on any business that might secretly be a counterparty product:

  1. 1.Ontology: What does the P&L say you sell? What does the delete-test say the customer buys?
  2. 2.Liquidity: At arrival time, is there compatible density — or do you make the customer bring the other side?
  3. 3.Social liquidity: Are you optimising identity/belonging, or lightweight collision quality?
  4. 4.Activation: Does the format manufacture moment-by-moment motivation via other humans’ autonomous actions?
  5. 5.Rake honesty: Is pricing framed as facility or software — or as access to counterparties?
  6. 6.AI boundary: Does intelligence assemble conditions and leave, or try to be the reciprocal partner?

You have a court

We opened on a driveway because it is the purest delete. Keep the surface. Lose the human. Watch the product vanish. Every domain above has a driveway: the empty poker client, the dating app that never becomes a Tuesday night, the marketplace with listings and no buyers, the multiplayer title with a login screen and a silent lobby.

The operators who win the next decade will not be the ones with the prettiest booking flow. They will be the ones who notice where scarcity moved when coordination got cheap. Organisation is no longer the hard thing. Compatible nutters in the same place at roughly the same time is the hard thing. Price it. Format for it. Measure it. Let machines eat the polling. Let the meatbags hit the ball back to each other.

You have a court — and you don’t play — because the ball doesn’t come back.

That sentence is the whole doctrine in one breath. Everything else in this book is commentary: counterparty liquidity as the product name, the delete-test as the proof, reciprocal activation as the mechanism, social liquidity as the texture, the flywheel as the economics, and one rung past Pine and Gilmore as the macro reason the product’s value rises while machines make everything around it abundant. The venue thought it sold courts. It sold someone to hit the ball back. Once you see it, you cannot responsibly unsee it.

Key takeaways

  • 1.Port the delete-test to every two-sided human product you touch this quarter.
  • 2.Run the six-check diagnostic in a real leadership meeting; fund the gaps it exposes.
  • 3.Keep the North Star sentence visible: someone suitable to hit the ball back, nearby, when people feel like hitting it.
REF
Sources & Evidence

References & Sources

The evidence base behind every claim — primary research, industry analysis, and technical specifications

Research Methodology

This ebook draws on primary research from standards bodies, independent research firms, enterprise technology vendors, and consulting firms. Statistics cited throughout have been cross-referenced against primary sources.

Frameworks and interpretive analysis developed by Scott Farrell / LeverageAI are listed separately below — these represent the practitioner lens through which external research is interpreted, and are not cited inline to avoid self-promotional appearance.

Primary Research & Standards Bodies

Theodore Levitt / Harvard Business Review — Marketing Myopia [1]

People want the hole not the drill; define business by customer need not product

https://hbr.org/2004/07/marketing-myopia

B. Joseph Pine II & James H. Gilmore / Harvard Business Review — Welcome to the Experience Economy [3]

Commodities → goods → services → experiences; charge for time spent

https://hbr.org/1998/07/welcome-to-the-experience-economy

World Health Organization — Social connection linked to improved health [4]

About 1 in 6 people worldwide affected by loneliness

https://www.who.int/news/item/30-06-2025-social-connection-linked-to-improved-heath-and-reduced-risk-of-early-death

LeverageAI / Scott Farrell — Practitioner Frameworks

The interpretive frameworks, architectural patterns, and practitioner analysis in this ebook were developed through enterprise AI transformation consulting. The articles below are the underlying thinking behind those frameworks. They are listed here for transparency and further exploration — not cited inline, as this is the author's own analytical voice.

Scott Farrell / LeverageAI — The Terminal Value Doctrine

Select projects by terminal value under cheap cognition

https://leverageai.com.au/the-terminal-value-doctrine-stop-optimising-the-horse/

Scott Farrell / LeverageAI — The Intent Order Book

Binary bookings as lossy compression of intent; assembly layer sibling

https://leverageai.com.au/the-intent-order-book-binary-bookings-are-lossy-compression-of-intent/

Industry Analysis & Vendor Research

Andrew Chen — The Cold Start Problem [2]

Marketplace liquidity and atomic network dynamics

https://www.coldstart.com/

About This Reference List

Compiled July 2026. All URLs verified at time of compilation. Regulatory documents and standards specifications are subject to revision — check primary sources for the most current versions.

Some links to academic papers and vendor research may require free registration. Government and standards body publications are freely accessible.