Building A-du: Part Four

You've probably signed a lease this way.

The landlord emails you a PDF. You don't have a printer, so you find one, at work, at a library, at a friend's place. You print twelve pages, sign the spots with the little flags, then realize you don't have a scanner either, so you photograph each page on your kitchen counter at a slight angle with a shadow across the signature. You email it back. Somewhere in there a page gets missed. The landlord countersigns their own copy. Now there are two PDFs, in two inboxes, and neither one is clearly the lease. Six months later something comes up, and you're both scrolling through old email trying to reconstruct what you actually agreed to.

This is the fourth post in my series on building A-du, the ADU platform I started. We've covered who is on the other side of a listing, how screening works, and what happens when it doesn't pass. This post is about the good day, the one where it all comes together and a tenant gets the keys. It's about the lease. And it starts with me deciding that A-du would never, ever be the print-sign-scan-email platform I just described.

A lease is a contract. That sounds obvious until you watch how casually most rentals treat it, scattered across attachments and filenames like lease_FINAL_v2_signed_REAL.pdf. I wanted something different: a lease that exists as one single thing, signed by both people through a real e-signature, with the final executed copy kept safe in the platform, and every step, from "tenant said yes" to "both parties signed," visible on the lease itself. One lease. One source of truth. No mystery.

How signing works on A-du

The signing itself runs through Anvil, a service that's very good at exactly this one thing. The landlord starts the lease from inside A-du; we gather up the details (the unit, the reservation, the tenant, the agreed terms) and Anvil turns it into a real, ready-to-sign document. Both people sign it right inside A-du, so the tenant never gets bounced off to some unfamiliar third-party website to enter their signature into a void. As each person signs, the platform takes note and updates the lease. When both signatures are in, we pull down the finished, executed PDF and its signing certificate and store them privately, so the landlord and the tenant can each open their own copy from their dashboard, whenever they need it.

There is no version living only in someone's email. There's no half-signed copy drifting around as a loose file. There's one lease, and at any moment it's in exactly the state it's really in.

The pet rule problem

Now, the part almost every rental platform forgets.

Landlords very often need to add something to a lease after it's been written up. A pet rule. A parking arrangement. Who handles the lawn. A clause about the shared driveway. Sometimes that addition has to be its own separately signed document.

The lazy way to handle that is to tear up the lease and reissue the whole thing, or worse, to email the addendum over as one more attachment and hope it gets signed. We don't do either. On A-du, an addendum, we call it a supplemental, is its own real document, with its own signature and its own record. The tenant sees any pending ones waiting in their dashboard. And here's the part that matters: the platform will not let the tenant make their final move-in payment until every supplemental on the lease has been signed. The unsigned pet rule is impossible to miss, because the keys are on the other side of it.

That's a small piece of design with a big human consequence. In my experience, the pet rules and house rules are exactly where the real, day-to-day agreement between a landlord and a tenant actually lives. Bury one in an email attachment, and you've built the perfect setup for a fight six months later, when a tenant gets penalized for breaking a rule they can honestly say they never saw. The platform simply shouldn't allow that to happen, so it doesn't.

What it means for you

If you're a landlord, you generate the lease inside A-du, both of you sign, and the finished document and its certificate land in your records automatically. Need to add a pet rule or a parking clause afterward? You add it as a supplemental, and the platform holds the tenant's move-in until it's signed. Nothing important slips through.

If you're a tenant, you sign your lease and anything attached to it from right inside A-du, the same calm, modern way you'd sign to close on a house or open an investment account. Your executed lease is always there in your dashboard. You will never again photograph page seven of twelve on your kitchen counter.

None of this changes the price. The first 15 published listings on A-du Rent pay no landlord service fee, locked permanently. Generating and signing the lease is simply part of what the platform does for you, not an upsell waiting at the finish line.

What I keep coming back to

The thing I underestimated was how many quiet states a lease moves through: drafted, sent out, signed by one person, fully executed, replaced, cancelled. Treat any of that as a simple done-or-not and you'll be wrong within a week, usually in a way that confuses a real person at a stressful moment. We taught the platform to track each step honestly, so it always knows where a lease truly stands and can tell you plainly.

I also learned to design for the hiccup. Sometimes the signing service sends us the same notification twice, or out of order, or late, the ordinary weather of software talking to software. Partway through the project, our signing partner even rebuilt their own system on us mid-stream. Because we'd built A-du to double-check the truth instead of blindly reacting, none of it ever cost anyone a signature or scrambled a lease. You never saw any of that turbulence, and that's precisely the point. The work that keeps your most important document boringly reliable is work you're never supposed to notice.

---

Next time: a confession. For months, we were calling our own customers by the wrong word, right there in the product, and it was quietly shaping the relationship in a way I didn't like. The story of realizing it, and why fixing it was worth months of careful, invisible work.