Field-first · works at one bar of signal

Closing the deal in the driveway

A proof of concept for the moment a sale is actually won — right after a showing, when a buyer says “yes” at the curb — and a single offline-capable app that carries the agent from that moment all the way to an open escrow file.

The decisive moment in a home sale isn’t at a desk. It’s in the driveway, with buyers about to leave and a competing offer landing by five o’clock. Office-bound e-sign tools assume a laptop and Wi-Fi; in a dead zone, rebuilding an offer from half-cached templates bleeds fifteen to twenty minutes and the momentum that closes deals. KeySign owns that moment. It carries the buyer, financing, and verified funds forward with no re-keying, drafts a competitive, fully-disclosed offer, verifies identity, takes signatures on glass, and submits — then keeps going, opening escrow and putting the contingency clock on screen. Everything runs locally and syncs when signal returns, so a dead zone is a state, never an error.

Fully interactive — run the whole flow: Field Home → Smart Offer Builder (escalation clause, live strength meter) → the disclosure package → Pre-flight Guard → identity (KBA + OTP) → drawable signing → submit → an open escrow file. Toggle signal to watch the queue flush on reconnect, and switch this page’s theme to see the prototype follow in real time.

The desk, and the driveway

The problem was never the signature. It’s where the decision happens — and the fact that every existing tool assumes the one place the agent isn’t: a desk, on Wi-Fi, after the buyers have gone home and cooled off.

A competitive market is won in the ninety seconds after “we love it.” KeySign sits in that moment and runs one loop on the whole transaction: carry forward → draft & disclose → verify & sign → submit → open escrow. It reuses the CRM data already on the phone, drafts a compliant offer with one competitive decision left to make, and works entirely offline — so the agent acts while the buyers are still standing there, not from the office two hours later when the competing offer has already been accepted.

The desk · what office-bound tools assume

Minutes to a signed, disclosed offer 15–20

Drive back, find Wi-Fi, rebuild the offer from half-cached templates, chase initials, hope the disclosures are complete. By the time it’s ready, the moment — and often the deal — has passed.

The driveway · what KeySign does

Minutes, in hand, at one bar ~3
Carried, not re-keyed Offline-first Fully disclosed

One device the agent already holds. The decision is made where it’s actually made — at the curb, now — with compliance handled and the “why” always one tap away.

The same offer, two ways. KeySign doesn’t speed up the paperwork — it moves the whole transaction to the moment that decides it.

02 · Discover

The unmet need was a moment, not a feature

Field research with agents kept returning to the same scene: the deal is won at the property, but every tool they own is built for the office.

Shadowing agents through showings surfaced a consistent failure point. The instant buyers commit is fragile and time-boxed — competing offers, expiring momentum, a seller deciding by end of day. Yet to act, the agent had to physically leave: drive to signal, open a laptop, stitch together a CRM record, a templating tool, a disclosure library, and an e-sign product that each assumed a connection. The gap between “they said yes” and “the offer is in” was where deals quietly died.

At the property

Buyers commit right after the walk-through. The agent has minutes, a phone, and often one bar of signal — and a competing offer due by 5 PM.

Back at the desk

Reconstructing the offer from scratch on a laptop costs 15–20 minutes and a half-dozen disconnected tools — long enough for momentum, and the deal, to cool.

The opening

Nobody owned the driveway moment end-to-end. That whitespace — offer, disclosure, identity, signature, escrow, offline — is the product.

03 · Define

One job, three layers

Translating the field insight into a single job-to-be-done: “When a buyer commits at a showing, help me lock in a competitive, compliant offer before the moment — or a competing offer — passes.”

The root causes weren’t laziness or bad tooling in isolation — they were structural: the work was split across disconnected products, all of which assumed connectivity and a desk, and none of which treated compliance as part of speed. KeySign’s definition collapses them into one offline-first surface where doing it fast and doing it right are the same motion.

Functional

Build, disclose, sign, and submit a competitive offer in minutes, in hand, offline.

Emotional

Feel confident and in control at the curb — never exposed by a missed disclosure or a dead zone.

Business

Win more competitive offers and open escrow faster, with a clean, auditable compliance trail.

The principles that fell out of Define

Carry context, never re-key One decision per screen Offline is a state, not an error Compliance is part of speed Every action is inspectable
04 · Explore

Three ways to own the moment — only one held

Before committing to a field-first app, the work explored the obvious alternatives and scored each against the driveway job. Two quietly re-introduced the exact thing the research said was the problem.

A back-office coordinator dashboard re-introduced the desk. An SMS remote-sign link handed the decisive moment to the buyer’s own device and signal, where momentum dies. Only a field-first offline app acted in the moment, in hand, at one bar — so it became KeySign, with the dashboard and remote link folded in later as supporting surfaces, not the core.

Screen 1 · A home screen that starts mid-stride

The agent doesn’t start from a blank form. Field Home opens with the buyer, financing, and verified funds already carried from the CRM — and names the pressure out loud.

Why this is the best choice: the first screen sets whether the agent feels ahead of the moment or behind it. Leading with carried context — zero re-entry — and surfacing the competing-offer deadline turns the home screen into a running start. The benefit: one tap to build, with the stakes and the data already in place.

9:41

Showing · 1442 Pine St

Start an offer

Buyers
Marco & Lena Ruiz
Financing
Conventional · 20% down
Funds verified
$240,000
Two competing offers expected by 5 PM today.

A specimen of Field Home — in the live prototype the chips open the carried record and the build button launches the offer flow.

Screen 2 · One competitive decision, everything else drafted

The builder reduces a competitive offer to the single call that actually requires judgment — the escalation — and drafts the rest, scoring strength live as the agent moves.

A completeness ring anchors the running state; the price field formats money as you type; the C.A.R.-style escalation clause sets a dynamic cap; and a 0–100 strength meter reacts to the escalation, the gap to asking, and contingencies. Buyer-broker compensation is handled inline (RPA ¶3G + SPBB), reflecting the post-Sitzer/Burnett rules. The benefit: a genuinely competitive, compliant offer with one real decision left to make.

Smart offer
90% · one competitive call left

Offer price

$1,285,000
Escalation clause · C.A.R. SMCO
Beat competing offers by $5,000 up to $1,330,000
Offer strength 86 · Very strong

A specimen of the builder — in the prototype the ring climbs to 100%, the price formats live, and the strength meter reacts as terms change.

Screen 3 · Compliance assembled, not bolted on

The full statewide disclosure set is built alongside the offer — so “fast” and “fully disclosed” are the same action, and the one item that needs a human is impossible to miss.

KeySign assembles the RPA with 2026 FinCEN language, Agency/BRBC, the buyer inspection advisory, proof of funds, the SPQ, the wildfire UOA, and buyer-broker comp (SPBB) — and flags the lead-paint FLD as needs you. Why this is the best choice: leaving compliance to the end is where deals get redone; folding it into the flow, with a single clear flag, keeps speed and correctness on the same path.

Disclosure package
7 / 8
RPA + 2026 FinCEN
Ready
Agency / BRBC · BIA
Ready
Proof of funds · SPQ
Ready
Lead-paint FLD
Needs you · page 6
Wildfire UOA · SPBB
Ready

A specimen of the package — the flagged item routes straight to the page that needs initials.

Screen 4 · Catch the redo before the pen

A guard runs before signatures and states the one blocker plainly — because the most expensive error is the one discovered after four people have signed.

The missing page-6 lead-paint initials would force every buyer to re-sign if they slipped through. Pre-flight names it in plain language and offers two stacked, full-width choices: “Queue it & fix now,” which resolves the flag and flips the package to 8/8, or a manual review. The benefit: the system spends a moment of friction now to save a full re-signing later.

One thing before the pen

Page-6 lead-paint initials are missing. Without them, the buyers would have to redo the entire signing after the fact.

A specimen of the guard — “Queue it” resolves the flag and returns the package to complete.

Screen 5 · Identity is what makes a fast signature hold up

A driveway signature is only worth anything if it’s defensible. KeySign verifies each buyer with knowledge-based authentication and an SMS one-time code before the pen touches glass.

Why this earns its own screen instead of a buried modal: identity is the legal backbone of the whole transaction, and treating it as a first-class step — big, auto-advancing OTP boxes sized for thumbs, one buyer at a time — signals that this is real, not a formality. Marco verifies, then Lena unlocks. The benefit: speed at the curb that still stands up in escrow.

Verify identity

Marco Ruiz · code sent to ···5521

4
9
2
·
·
·
Knowledge check passed — 3 of 3
Marco verified Lena · next

A specimen of identity — in the prototype the six boxes auto-fill and unlock the second buyer.

Screen 6 · A signature surface built for a car hood

Signing is the screen, not a step crammed under other controls. A wide drawable canvas, one mark at a time, with progress made explicit across all four required marks.

The real prototype uses a DPR-scaled canvas that takes pointer and touch input, so the signature is crisp whether it’s drawn on a phone balanced on a car hood or a tablet on the hood of a truck. Four marks — each buyer’s signature plus the page-6 initials — advance one at a time with a clear active state. The benefit: nothing competes with the one thing the person is doing.

Sign here
Mark 1 of 4

Marco — buyer signature

A specimen of signing — the live canvas captures a real drawn signature for each of the four marks.

Screen 7 · Submit — and offline is just a state

The signed packet goes to everyone who needs it at once. The same screen handles a live send and a dead zone identically — online delivers, offline queues — so signal is never a wall.

A sealed packet — nine documents, four signatures, SHA-256 — routes to the listing agent, the escrow officer, and the buyers’ deal room. Why this is the best choice: framing offline as Queued rather than an error means the agent submits with total confidence at one bar, knowing it flushes the instant signal returns. The benefit: the moment is never blocked by the network.

Send the packet

Signed packet

9 documents · 4 signatures · SHA-256 sealed

Listing agent
Queued
Escrow officer
Queued
Buyers’ deal room
Auto

A specimen of submit — online the routes read “Delivered”; offline they hold as “Queued” and flush on reconnect.

Screen 8 · The deal doesn’t end at the signature

Most tools stop at “submitted.” KeySign carries the momentum forward into an open escrow file — the single thing that turns a signed offer into a closing deal.

Once accepted, the screen shows the accepted price and escrow number, fraud-safe earnest-money wiring, the contingency deadlines on a visible clock, and a parties hub for the buyers, listing agent, escrow officer, and lender. Why this matters: the driveway moment only pays off if the deal actually closes, and putting the clock and the parties on screen keeps the whole transaction moving. The benefit: driveway-to-close, in one place.

Accepted Escrow open
Accepted
$1,312,000
Escrow #
SC-4471

Contingency clock

17
Inspection
days
21
Appraisal
days
30
Loan
days
MR
LA
EO
LN
4 parties

A specimen of the escrow file — the contingency dates count down and each party links to its role.

Screen 9 · Trust is a screen, not fine print

Everything that makes the signature legally sound — ESIGN/UETA consent, verified identity, a tamper-evident seal — is shown plainly and backed by a full, inspectable audit trail.

A SHA-256 hash seals the packet against tampering; the timeline records every material event from draft to submission. Why this is the best choice: in a transaction this consequential, trust can’t be implied — making the audit legible, in the same calm language as the rest of the app, is what lets an agent stand behind a signature taken in a driveway.

ESIGN / UETA Identity verified SHA-256 sealed

Audit trail

Offer drafted
9:41 · on device
Disclosures completed
9:43 · 8 of 8
Identity verified ×2
9:44 · KBA + OTP
Signed — 4 marks
9:45 · packet sealed
Submitted
9:46 · 3 recipients

A specimen of the trust model — every row in the live prototype expands to its underlying record.

Screen 10 · A dead zone is a state, never a wall

Offline isn’t a degraded mode bolted on at the end — it’s the assumption the whole app is built on. Work continues at zero bars and reconciles itself the moment signal returns.

Toggle the signal and the prototype keeps working: drafting, disclosing, identity, signing, and submit all queue locally, then auto-flush on reconnect with a clear running count. Why this is the best choice: the driveway is, by definition, where signal is worst — designing offline-first instead of online-with-a-fallback is what makes the core promise believable. The benefit: the agent never has to think about the network.

Offline — 0 bars
3 queued
Offer packet
Queued
Escrow notice
Queued
Reconnected — syncing
Flushing
Nothing is lost.Every queued item flushes automatically the instant a single bar returns.

A specimen of resilience — flip the signal toggle in the prototype to watch the queue build and flush.

Screen 11 · Onboarding that tells the truth about access

The first run sets jurisdiction and signing mode, and is honest about what stays on the device versus what leaves it — earning trust before asking for a signature.

Three calm steps with progress dots: pick the jurisdiction (California / Santa Clara, which drives the disclosure set), see a plain truth-in-access list of what’s processed locally, and choose a signing mode. Why this is the best choice: a tool that handles money and legal identity has to lead with candor — saying exactly what it does with data is the foundation the rest of the trust model stands on.

Jurisdiction
California · Santa Clara County

What stays on this device

Buyer & funds data — processed on device
Signatures — sealed locally, then sent
Submitted packet — leaves the device only on submit

A specimen of onboarding — the jurisdiction choice configures the exact disclosure set used in Screen 3.

Unlocking a high-value moment the industry overlooked

The proof of concept demonstrates that the entire driveway-to-close transaction — competitive offer, full statewide disclosure, verified identity, defensible signatures, submission, and an open escrow file — can happen in one field-first app, in minutes, at one bar of signal. It proves speed and compliance aren’t a trade-off when they’re designed as the same motion, and that the decisive moment of a sale can be owned end-to-end instead of abandoned to a drive back to the office.

Run the full prototype

Explore more work

More explorations from the AI Product Design Lab — each a different facet of making AI products people can direct, verify, supervise, and trust.

steer exploration cover
Steer — intent before generation

Turn an under-specified prompt into a negotiated brief: the model surfaces what it inferred and flags ambiguity before it commits.

View exploration
ground exploration cover
Ground — verify what AI claims

Every claim traceable to a source with confidence and freshness; unsupported claims flagged; source conflicts shown, not smoothed over.

View exploration
recall exploration cover
Recall — legible AI memory

A memory layer you can see, attribute, edit, scope, and revoke — personalization as a negotiated, inspectable thing, not a black box.

View exploration