Private beta · Spring 2026

Every handoff
is a contract.
We made it
invisible  legible.

Handoffs turns the murky transfer of work between teams into a signed, searchable contract - with clear acceptance criteria, named authors, and a ceremony for when it's done.

4.2×
Less ping-pong on acceptance
< 24h
Median time to sign-off
0
"Wait, who owns this?"
HF-2407Live
Search reindex - platform cutover
Data → PlatformDue Fri
§I.1 - New index schema agreed
§I.2 - Backfill plan signed
§II.1 - Shadow traffic ≥ 48h
HF-2401Delivered
Pricing page v3 - staging → prod
Design → GrowthSigned Wed
§I.1 - Hero variant locked
§I.2 - Mobile tested on 3 devices
§II.1 - Analytics events wired
Accepted
HF-2412Counter
Billing export feed
Finance → DataFlagged
§I.1 - SFTP endpoint confirmed
§I.2 - Column mapping · counter proposed
Acceptance criteriaTwo authors, one contractSignoff ceremonyPipeline visibilityAudit trailNo dropped handoffsAcceptance criteriaTwo authors, one contractSignoff ceremonyPipeline visibilityAudit trailNo dropped handoffs

An internal contract
for every handoff.

§ II · MANIFEST
Filed 03 · 2026
§ I

Two-author contracts

Sender writes acceptance criteria. Receiver writes their requirements. Both sign. Both own it.

§ II

Row-level signoff

Each line of the contract is its own decision - agree, counter, or flag. No mystery checkboxes.

§ III

The ceremony

When work ships, it ships with a stamp. A named moment your team can point to and celebrate.

§ IV

Pipeline visibility

Inbound on your desk. Outbound awaiting review. Parked, blocked, delivered - all on one page.

§ V

An audit trail worth keeping

Every counter, every dispute, every comment - timestamped and searchable for the next engineer who asks "why."

§ VI

Templates & shortcuts

Codify the handoffs you run over and over. Design → Eng. Eng → Ops. Data → Everyone.

Three acts.
That's the whole play.

I.

Draft

Pick a template - or start blank. Name the sender, the receiver, the due date. Write your acceptance criteria as plain English.

template: design → eng
II.

Negotiate

The other team accepts, counters line-by-line, or flags. Every thread stays on the row it's about. No separate Slack graveyard.

§I.2 · counter from @mei
III.

Sign off

When criteria are met, both sides stamp the contract. It lands in the archive, linked to the sprint, the PR, and the next handoff downstream.

accepted · stamped friday

Ship the thing.
Then ship the handoff.

Handoffs is in private beta with a handful of founder-led product teams. If your team loses a week a month to "I thought you were doing that," we'd love to talk.