KeySign: writing and signing a real estate offer at the property
The moment a sale is won is the moment a buyer says “yes” at the curb. One offline-capable app carries the agent from there 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. Office-bound e-sign tools assume a laptop and Wi-Fi, and in a dead zone rebuilding an offer costs twenty minutes and the momentum that closes deals. KeySign owns that moment: it drafts a competitive, fully disclosed offer, reads it back in plain language, verifies identity, takes signatures on glass, and delivers. Then it keeps going, through the seller’s counter and into an open escrow file. Everything runs locally, so a dead zone is a state, never an error.
Live app: KeySign, a real estate offer written and signed at the property.
The problem: every existing tool assumes a desk and a connection
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 and disclose, verify and 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
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
One device the agent already holds. The decision is made where it’s made, at the curb, now, with compliance handled and the “why” 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.
What field research found: the deal is won at the property
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 one 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 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.
Buyers commit right after the walk-through. The agent has minutes, a phone, often one bar of signal, and a competing offer due by 5 PM.
Reconstructing the offer from scratch on a laptop costs 15 to 20 minutes and a half-dozen disconnected tools. Long enough for momentum, and the deal, to cool.
Nobody owned the driveway moment end to end. That whitespace, offer, disclosure, identity, signature, escrow, offline, is the product.
One job, three layers
Translating the field insight into one 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 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
Three alternatives explored, and why two failed
Before committing to a field-first app, the work explored the obvious alternatives and scored each against the driveway job. Two quietly reintroduced the exact thing the research said was the problem.
A back-office coordinator dashboard reintroduced 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 prefilled from the CRM
The agent doesn’t start from a blank form. Curbside opens with the buyers, financing, and verified funds already carried from the CRM, and names the pressure out loud.
The first screen decides 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: one tap to build, with the stakes and the data already in place.
Tuesday 2:47 PM · 1428 Magnolia Ct
They just said yes.
Curbside
Screen 2 · One competitive decision, everything else drafted
The builder reduces a competitive offer to the one call that requires judgment, the escalation, and drafts the rest, scoring strength live as the agent moves.
A completeness ring anchors the running state and the price field formats money as it is typed. Escalation is attached as a C.A.R. addendum (form ADM) with a ceiling derived from the price, and a 0-to-100 strength meter reacts to the escalation, the gap to asking, the close date and every contingency. Buyer-broker compensation is handled inline, RPA ¶3G with form SPBB, because since the 2024 settlement it has to be asked for in the offer and has to match the representation agreement. The result is a competitive, compliant offer with one real decision left in it.
Offer price
The offer builder
Screen 3 · The buyer review, written in plain language
Every offer tool is written for the agent. The buyer is the one signing, and until this screen they had never seen the deal in words they could read without help.
Buyer review states the offer in plain language and large type: what you are offering, what it costs in cash today and every month, and exactly how you can still walk away. It also states the ceiling. An escalation addendum is the one term that can move the number the buyers just read, and move it by six figures, so showing them the floor here and leaving the ceiling in the addendum is how somebody signs up to a price nobody said out loud. The ceiling sits under the offer in the same type, with the cash it would actually take, and it disappears when the addendum is off, because then there is nothing to disclose. The list of outs is generated from the contingency state rather than written once, so switching a protection off rewrites the paragraph and names what has just been given up. The buyers acknowledge on the device, and the acknowledgement is timestamped into the audit trail, which is also the record an agent would want if the terms are ever disputed.
Step 3 · turn the phone around
Marco & Lena, here’s your offer.
What it costs you
Buyer review
Screen 4 · Statewide disclosures assembled with the offer
The seller’s package came in this morning and the buyers have read it. The statewide buyer-side 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 twelve forms: the RPA, the escalation addendum, SPBB, the signed BRBC and agency disclosure, BIA, SBSA, MCA, the wire-fraud advisory, the Fair Appraisal Act addendum, the pre-approval and proof of funds, and the lead-paint FLD. Eleven are drafted or already on file. The FLD is flagged as needs you, because the house was built in 1948 and both buyers have to initial page 6. The RPA row carries a second answer worth as much as any of them: the app screens the deal against the FinCEN residential-transfer rule and reports that it is not reportable, because this is a financed purchase by two natural persons rather than an all-cash transfer to an entity. A tool that knows when a rule is off is easier to trust than one that sprinkles it everywhere. Leaving compliance to the end is where deals get redone. Folding it into the flow, with exactly one flag, keeps speed and correctness on the same path.
The disclosure package
Screen 5 · A guard that runs before any signature
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.
Eight checks run, and they are the checks a coordinator would run: that the vesting language and the APN agree, that the deposit is the percentage it claims to be, that the ¶3G request matches the BRBC, that the offer outlives the seller’s deadline, and that the escalation ceiling is a number the buyers could actually finance, which the app proves against their verified funds rather than asserting. Two things come back: missing page-6 lead-paint initials, which block, and a close date nine days longer than the seller asked for, which does not. One is fixed by making it a required stop in the signing flow; the other is a judgement the app leaves with the agent, and says so.
Lead-paint initials missing on FLD page 6. Both buyers. Blocks the signature.
Close of escrow is 30 days. The seller asked for 21. Advisory: your call, not the app’s.
Pre-flight
Screen 6 · Verifying identity before signing
A driveway signature is only worth something if it’s defensible, and the honest problem is that the usual way of proving identity needs the one thing a driveway does not have. KeySign uses three factors, and only one of them needs a bar of signal.
A knowledge-based check is a live query to a credit bureau. It cannot run at zero bars, and an app that promises to work in a dead zone and then quietly needs a bureau at the decisive moment is lying about its own premise. So the bureau check is cleared once at intake, when the BRBC is signed on Wi-Fi, and the signed assertion is held on the device for ninety days. What runs at the curb is a passkey on each buyer’s own phone, which is local. The SMS code is the only factor that needs signal, and at zero bars it is deferred rather than faked: the buyers still sign on the two live factors, the certificate records exactly which were live at the pen, and the code completes on reconnect. That ordering is the point, because delivery is what starts the clock under the RPA, so nothing leaves the device under-verified.
Marco Delgado · factor 3 of 3, code sent to ··· 4471
Identity
Screen 7 · A signing surface sized for a phone held outdoors
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 app 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. Nothing competes with the one thing the person is doing.
Marco, buyer signature
Signing
Screen 8 · Delivery, with offline handled as 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 of twelve documents, four marks and a SHA-256 seal goes to the listing agent, the buyers’ deal room and the brokerage compliance file. Not to escrow: there is no escrow until somebody accepts, and an app that opens one at the offer stage is an app an agent stops trusting. Delivery, not sending, is what starts the clock under the RPA, so the read receipt is recorded as its own event. Framing offline as Queued rather than an error means the agent delivers with confidence at one bar, knowing it flushes the instant signal returns.
Signed packet
12 documents · 4 marks · SHA-256 sealed
Delivery
Screen 9 · The multiple counter offer, shown as a diff
A straight acceptance in a three-offer race is the exception. What actually comes back is a multiple counter offer, and it is where the deal is won or lost.
C.A.R. form SMCO goes to every buyer at once and binds nobody until the seller signs it back, a distinction most tools bury and this screen states where a warning is actually read. KeySign renders the counter as a diff against the offer the buyers had already read: price up, close shortened to the 21 days the seller asked for, a free rent-back added, all three contingencies kept, and the ¶3G compensation accepted as written. The counter price lands under the ceiling the escalation addendum had already authorised, so the decision is one the buyers can make standing in a car park.
6:12 PM · three hours later
Seller countered.
The seller’s counter
Screen 10 · What happens after the signature
Most tools stop at “submitted.” KeySign carries the momentum forward into an open escrow file, the one 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. The driveway moment only pays off if the deal closes, and putting the clock and the parties on screen keeps the whole transaction moving. Driveway to close, in one place.
Contingency clock
The escrow file
Screen 11 · The audit trail behind a legally sound signature
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. 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.
Audit trail
The trust model
Screen 12 · Working with no signal
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 app keeps working. Drafting, disclosing, identity, signing, and submit all queue locally, then auto-flush on reconnect with a clear running count. 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 agent never has to think about the network.
Offline and reconnect
Screen 13 · Onboarding, and what stays on the device
The first run sets jurisdiction and signing mode, and is honest about what stays on the device versus what leaves it. It earns 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. 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.
What stays on this device
Onboarding
What KeySign shows
The whole driveway-to-close transaction (competitive offer, full statewide disclosure, verified identity, defensible signatures, submission, and an open escrow file) happens in one field-first app, in minutes, at one bar of signal. Speed and compliance aren’t a trade-off when they’re designed as the same motion, and 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 appExplore more work
Three more case studies about deciding under pressure with the whole picture in view: the true cost of a payment abroad, a savings figure with its assumptions shown, and a supervisor stepping into a live call.