pitch.sells.to
Every seller has an audience. Now it's an address.
The concierge door for the business seller: one conversation turns your offer into a Mandate, and the deal desk developers get as an API — public and runnable at api.forsale today — is built to work your deals. You pay on outcomes.
↓ scroll · arrow keys
The business seller this door is for closes fine in the room — the product is their own persona, and the business sells whenever they are present. That is exactly the ceiling. Every path to a motion that runs without them demands becoming a sales operation: recruit, ramp, and manage an org they don't want; retain an agency billed monthly whether or not anything closes; or buy funnel software and take on a second job operating it. And every one of those paths raises the delegation question that stops most owners cold: if someone else works my deals, who stops them promising things in my name at prices I never approved?
Developers already got a better answer: a rail. api.forsale publishes the contract in the open — declare an offer and a Mandate, and the desk is built to work the deals: agents on every Role, verified human closers exactly where declared, authority held by a Gate that enforces the seller's floor on everyone. The rail is candid about its own stage — its front door says pre-launch, keys go out in small batches as access opens — but its docs and demo environment are live and runnable today, and the authority slide below carries the evidence. But that answer is an API. A realtor, a consultant, a coach, an agency principal — the owner-operators whose businesses sell through their own persona — will never call it, and shouldn't have to. The desk is right. The interface is wrong for them. This door is the other interface.
{persona}.sells.to/{audience}
realtor.sells.to/retirees
coach.sells.to/founders
broker.sells.to/dentists
Read any of those addresses aloud and it is a sentence about the person it is for: a realtor who sells to retirees. That is the design intent of the namespace — every junction of one seller persona and one audience gets its own address, and the address does the targeting before a single word of copy loads. The plan is programmatic: landings generated junction by junction from records like the one this deck renders from, each one a door keyed to exactly who its visitor is and who they sell to.
A brand here is one ICP and one motion — and the grammar does not bend that
rule. The ICP is the owner-operator business seller; {persona} and
{audience} enumerate that one ICP's junctions. A realtor selling to
retirees and a coach selling to founders are the same character with the
same problem walking through the same door — the grammar just holds it open
by name.
No programmatic landing exists yet. The grammar is a designed acquisition surface, stated here as intent; the claim posts when the first junction page is served from the zone, with the URL in evidence.
One conversation turns your offer into a Mandate — the same declared object a developer would POST: per-Role staffing (agent, human, or human-above-a- threshold), your negotiation floor, price tags within platform bounds, a stall timeout. The concierge drafts it; you approve it; nothing runs until you do. The values are yours. The shape is house rules — which is exactly what keeps every closer's Register comparable and every Gig evaluable before it's claimed.
From there the design is the desk the sibling doors already describe: your Deals live on the rail, agents work every Role, and where your Mandate says human, a fully-briefed Gig — account, value, stage history, Signals, your floor — posts to the supply doors at a flat price tag fixed before anyone claims it. A named closer runs the Role start to finish; a stalled Deal goes to a Nurturer; and the Brief means nobody ever picks up your deal cold.
This slide describes the designed shape of the door, not a running service — where it actually stands is stated plainly below, claim by claim.
authority the Deal's Gate, on the rail — never the maker of the proposal, human or agent
This is the answer to the delegation question the problem slide poses — who stops someone else committing in your name? Everything that works your Deal — every agent, every human closer — is judgment-only: it proposes an advance, a close value, discovered Signals. One code path commits: your Deal's Gate, enforcing the Mandate you approved. A below-floor close is refused even when a human proposed it. Delegation without surrendering authority is not this door's promise — it is the substrate's architecture, and the concierge just gets you to it without an API key.
The seam is runnable in the open today: the rail's live quickstart walks a Deal to settlement against the demo environment in a handful of calls, no API key required — including the refusal that matters here, a below-floor close the Gate rejects with a 422 while the Gig stays claimed.
Every number above is a posted product fact of the substrate, not a projection: sellers set price tags in their Mandate within platform bounds, the platform supplies defaults, and settlement writes payouts from outcomes. Compare it to the alternatives' shape rather than to promised results: the agency retainer and the SDR shop bill monthly on effort; this desk bills only when a Deal closes won. This door publishes no earnings examples and no pipeline promises — the mechanics are the offer.
substrate — api.forsale — the demand rail; sole authority over every Deal
developer seller
offers via API
business seller
offers via concierge
individual closer or setter
labor
firm / agency
a bench
referrer
sellers, closers, or deal flow
The sibling decks have carried the business-seller row as "queued" — this record fills it. The developer seller and the business seller are the two demand actors around one desk: same Mandate object, same Gate, same supply doors recruiting for the human Roles — different interface, because one reads API docs and the other has a business to run. The grid's rule is that doors cross-route wrong-door traffic, and this door's side of that routing ships with its first page: a technical founder who lands here should find the rail in one click, an owner-operator who lands on the rail's docs should find a door that speaks their language. Designed, not yet serving — the amber claims below say exactly where that stands.
The desk underneath is live and candid about its stage: the rail's front door, docs, and runnable demo environment are public at api.forsale — whose own page says pre-launch, keys go out in small batches as access opens.
The supply side is recruiting against the same substrate: closers.sale — the high-ticket consumer closer tribe — is live.
closers.deals — the individual B2B seller onto the same desk — is live.
closers.agency — the Firm envelope, a bench under its own flag — is live.
The domain is reclaimed and the zone is active in the estate's account — and no surface is served from it yet. This deck precedes the door, and says so rather than implying a funnel that doesn't exist.
The concierge motion has not run. It opens in small cohorts matched to real fulfillment capacity — the same honest sequencing the supply doors state on their own pages — and the claim posts when the first concierge-drafted Mandate is live with the record in evidence.
The claim that matters: a business seller's Deal, worked to their approved Mandate, settled at closed_won with the settlement in evidence. Until it posts, this door implies no liquidity and promises no pipeline. The amber is deliberate — candour is the house style of every door on this desk.
The desk this door opens onto is public and runnable today — read the docs and run the demo at api.forsale.
If this was forwarded to you: sells.to is the planned concierge door where an owner-operator business seller — the realtor, consultant, coach, or principal whose persona is the storefront — gets their offer turned into a Mandate in one conversation, and the deal desk behind api.forsale is built to work their deals under rules a Gate enforces in code, billed only on closed outcomes. The domain itself is a grammar: {persona}.sells.to/{audience} — every address a sentence about the seller it's for. Every claim above carries its own state and evidence, including the candid ones about what isn't built yet. If you sell through your own name: the desk's mechanics are public at api.forsale today. If you know who does: forward this.