pitch.closings.services
The close, run as a service.
For the business whose motion already fills the calendar: your team holds the meetings, the desk runs the span after them — agents and verified closers under your declared rules, the platform paid only on what closes, human work at flat tags fixed before any claim.
↓ scroll · arrow keys
There is a specific company this door is for: the one whose demand engine is fine. Marketing fills the calendar, the team sets and holds meetings — and then the span after the meeting is where deals go to age. Proposals lag a week. Negotiations stall because nobody's job is to finish them. The founder gets pulled into every close that matters, which caps the company at the founder's calendar. Quarter-end is a pile-up of held meetings the company never converted.
Every available fix is the wrong shape. Hiring closers means recruiting, ramping, managing, and quota risk — a permanent org for a constraint that may be seasonal. Outsourced closing shops and fractional VPs bill monthly retainers on effort, whether or not anything closes. And every one of those paths raises the question that stops delegation cold: who stops a stranger from promising things in your name, at prices you never approved?
closings.services is the closing span of your pipeline delivered as a service. An intake conversation turns your closing rules into a Mandate — negotiation floor, commission cap, per-Role staffing, stall timeout — and from the held meeting onward, the desk runs the close: agents work the span where you declared agents; where you declared a human, a fully-briefed, flat-priced Gig posts to verified closer supply. The platform's cut settles only on closed_won; every human Gig carries a flat tag you see before any claim. Your motion stays yours.
The scope line is structural, not contractual:
| Stays yours | The desk runs |
|---|---|
| sourcing, qualification, the meetings your team sets and holds | the span after the meeting: proposal, negotiation, terminal |
| your pipeline, your accounts, your pricing authority | execution against your declared Mandate — proposals only |
| the decision where a human takes over, declared once | staffing that declaration: agents, or Register-verified closers |
| stalled-deal policy (your stall timeout, within bounds) | a Nurturer working a gone-dark Deal back to revived or confirmed dead |
Where a human works your span, they arrive briefed: the Gig carries the full Brief — account, value, stage history, discovered Signals, your floor — and a flat price tag fixed at post time. Nobody ever picks up your deal cold, and nobody renegotiates their cut mid-deal.
This slide describes the designed shape of the door, not a running service — where it actually stands is stated plainly below, claim by claim.
This door does not invent its scope — it rides a boundary the substrate
already draws. On the rail, a Role is a named span of Deal work with a
defined exit condition, and the Closer Role is exactly this door's
product: meeting → terminal, commission paid only at closed-won. The
Nurturer Role covers the other half of a close-constrained pipeline: a
stalled Deal — a gone_dark Signal — worked back to revived or confirmed
dead, for a flat fee.
The span's contract is public today: the rail's concepts page defines the Closer Role as meeting → terminal (exit: closed_won | closed_lost, commission at closed_won) and the Nurturer Role for stalled Deals, with the Brief defined so "a Closer never picks up a cold deal" — the rail's own words.
The one mechanic this door needs beyond today's documented rail: your deals enter mid-flight. The rail's documented entry point is POST /deals from sourced; this door's intake mints Deals at the meeting stage carrying your motion's attested history, so the desk starts exactly where your team stops. Designed, not shipped — this claim posts when the intake path is live on the rail, with the endpoint in evidence.
authority the Deal's Gate, on the rail — never the maker of the proposal, human or agent
This is the answer to the question the problem slide poses. Everything that works your span — 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 — negotiation floor, commission cap, transition legality. A below-floor close is refused even when a human proposed it, and the Gig stays claimed. The terms a closer saw at claim time are the terms that settle: no mid-deal renegotiation, no retroactive splits, no promises in your name that your rules didn't already allow.
The rail is live and documented in the open: quickstart, concepts (Deal · Stage · Mandate · Role · Gig · Settlement), API reference, SDK, MCP, and a demo environment where the propose → gate → commit seam can be exercised directly — no key required.
Every number above is a posted product fact of the substrate, not a performance figure. Settlement runs on flow of funds through the rail: the same movement of money that pays a Gig is what writes the closer's Register — which is why the humans on your span are verified by settled outcomes rather than résumés. This door publishes no earnings examples, no win-rate promises, and no conversion figures; the mechanics are the offer.
substrate — api.forsale — the demand rail; sole authority over every Deal
developer seller
offers via API, whole funnel
owner-operator seller, no motion
offers via concierge, whole funnel
pipeline-rich business, close-constrained
qualified deals at the meeting stage
individual closer or setter
labor
firm / agency
a bench
Serve states above are curl-verified as of 2026-07-30: the rail and all three supply doors answer today; sells.to and this door's own apex do not serve a surface of their own yet, and both records say so.
A brand here is one ICP and one motion, and this door's boundary is a stage seam. The developer who wants the whole funnel as an API walks through api.forsale — it serves today. The owner-operator with no motion at all — whose business sells only when they're in the room — is filed for sells.to, the concierge door designed to buy the funnel whole; that door is pre-launch (the name does not resolve yet, and its record says so), so its tribe is named in the grid, not routed anywhere today. This door is for the third character: the business whose motion already works to the meeting, and whose constraint is everything after it. If your own team holds the meetings, you belong here; if you need the desk from sourced onward, the rail's own door at api.forsale answers today — and the concierge door will, when it ships. Wrong-door traffic cross-routes to doors that serve — that's what the grid is for.
The name answers today as a 308 permanent redirect to api.forsale — the rail this door rides — where it is filed as an alias in the rail's own record. This record graduates the name into its own door; the redirect stays until this door's own intake surface ships, and the rail's alias entry retires with it. Stated plainly rather than pretending a surface that isn't there.
The supply side this door draws on is live: closers.deals recruits the individual B2B closer tribe onto the same desk, with the Register — the verified, non-transferable record built from settled outcomes — as the ladder.
The second individual supply door is live too: closers.sale recruits the B2C high-ticket closer tribe onto the same desk, under the same Register ladder — "your closes are your résumé" is that door's own masthead.
The Firm envelope is live at closers.agency: benches enroll under their own flag onto the same desk — a supply shape sized for exactly the routed, multi-deal closing work this door generates.
No surface of this door's own exists yet — the apex 308s to the rail, as posted above. This claim posts when the intake surface is served from this domain, with the URL in evidence; the alias retirement rides the same gate.
The claim that matters. It posts when a real company's qualified deal has entered mid-flight, run the span under a declared Mandate, and settled through the Gate — never before. Until then intake opens in small cohorts matched to real closer capacity, and this deck says so instead of implying throughput that doesn't exist. The ambers on this page are deliberate: this door states its stage plainly.
The desk this door rides is public today — read the span's contract at
api.forsale/docs/concepts, and run the demo from the quickstart.
If this was forwarded to you: closings.services is the door where a business whose motion already fills the calendar hands off the span after the meeting — proposals, negotiation, the close — to an operation run under its own declared rules: a floor no executor can breach, briefed and verified closers where a human is declared, a platform fee computed only on closed value, and flat Gig tags fixed before any human picks up the work. It is pre-launch and says so: the name currently routes to the rail underneath, and every claim above carries its own state and evidence. If the close is your bottleneck, read the rail's public contract at api.forsale and reply to whoever forwarded this — cohorts are matched as capacity opens.