The Handbook That Vets Its Own Author
A free 55-page Florida guide for executors deciding what to do with the estate's house.
The Problem
When someone dies owning a house in Florida, the person settling the estate gets a mailbox full of letters from companies wanting to buy it, and almost no neutral explanation of what they are actually allowed to do. Most of them have never done this before. They are the most responsible or most clerically able person in the family, already carrying enough, and about to be bombarded by people trying to rush them. The rules that matter most, like homestead, the insurance vacancy clock, and the property tax reset, surprise nearly everyone.
What It Does
The site offers a free handbook by email. The handbook opens by naming who wrote it, that the author buys houses, and how the business makes money, then walks the reader through the first 30 days, the kind of probate they are in, whether they even control the house, what it costs each month to wait, and every realistic option for the property side by side. It ends with a ten-question checklist for vetting any buyer, written to be used on the author. The site also gives away five printable tools with no email required: the First 30 Days checklist, a fillable carrying-cost worksheet, an options comparison sheet, the ten questions, and a special situations triage sheet. Anyone who does request the handbook gets it by email within a minute and can unsubscribe with one click.
Anyone appointed, or expecting to be appointed, personal representative of a Florida estate that includes a house, condo, or land. Many of them live out of state.
Outcome
The site is within its first month. The only traffic so far is a cold email campaign to personal representatives in two Florida counties: 267 contacted, 131 opened, 4 replied, and no handbook signups yet. Those are the real numbers, and the page will be updated when they change.
Screenshots
How It's Built
The handbook is written in a single Markdown source file with a no-parallel-copies rule, and a Python build renders it through WeasyPrint into two PDF editions, screen and print, on a locked design system with a two-column layout that puts each statute citation in the outer margin beside the paragraph it supports. Each companion tool is built from the same design system as its own PDF, and the carrying-cost worksheet is a fillable form. The website is an Express 5 app in TypeScript on Node, rendered with EJS templates, running on Replit as a VM deployment behind the custom domain. Signups go through a rate limiter and a hidden honeypot field, then upsert into a SQLite leads table keyed on the normalized email, so a repeat signup reuses the existing row and unsubscribe token instead of creating a duplicate. Resend sends the handbook email with a link to the PDF, a one-click unsubscribe header, and a personal unsubscribe URL built from a 64-character random token. A new lead also fires an internal notification without waiting for it to finish. The thank-you page optionally collects first name, county, and probate stage onto the same record. A password-protected admin page lists leads and contact messages and exports a CSV. Cloudflare handles DNS and routes the public inbox to the business mailbox; cold outreach runs from a second domain through Smartlead.
By the numbers
- chapters
- 13
- pages
- 55
- words
- about 14,700
- distinct Florida statute sections cited in the margins
- 30
- tear-out checklists bound into the guide
- 4
- free downloads on the site with no email gate
- 5
- routes the site serves
- 15
- first commit to first publish
- 2026-07-27 to 2026-08-04, 8 days
- cold emails sent, first campaign
- 267 leads contacted
- opened
- 131 (21.3%)
- replied
- 4 (1.6%)
- bounced
- 14 (2.3%)
- handbook signups
- 0
Key Decisions
Disclose on the cover and again on page 2 that the publisher buys houses, then put the full business explanation in Chapter 12 near the end
The reader judges it better once the guide has either earned their trust or it hasn't.
State in print that listing with an agent usually nets more than a direct sale, with a worked example that shows it
Transparency is the marketing. In a niche where competitors hide their incentive, honest dealing is the competitive advantage.
Write the buyer-vetting checklist so it can be used on the author
A buyer who can't pass their own checklist shouldn't be sent one.
Give away the five tools with no email gate and gate only the full handbook
Ideally the email gets captured so the conversation can continue, but that should not be the reason someone does or does not get the materials. If the free tools are usable, the reader can decide whether the handbook is worth an email address. Either way they can unsubscribe.
No urgency language, no cash-offer framing, no popups, no countdowns, no fake social proof, anywhere on the site or in the guide
These people are doing a job they have never done before, outside their comfort zone, and are about to be bombarded by people trying to rush them. The whole point is a clear framework: here is what is important, everything else can wait and be decided later.
Handbook delivery and internal notifications fail open
A Resend failure must never block or surface an error to a visitor completing an opt-in. The lead is stored either way and the visitor still lands on the thank-you page.
Cold outreach runs from a second domain, not estatehouseguide.com
Keeps the primary domain's sending reputation clean.
Date the guide 'Current as of August 2026' rather than forward-dating it, with a real 2027 revision planned
Load-bearing figures like the federal estate tax exclusion and the summary administration limit change on a fixed schedule.
Describe navigation paths in print instead of deep-link URLs
Print degrades gracefully. Agency phone numbers and URLs change; the resources page keeps the current version.
What broke & how it was fixed
Three things, all after the first publish. The rate limiter refused requests in production because Replit sits behind a reverse proxy and the app was not told to trust it; fixed by trusting exactly one proxy. The handbook route resolved the PDF relative to the process working directory, which differs in production from development, so the file 404ed until the path was rebuilt relative to the compiled server directory. And the resources page linked a Documents to Gather PDF that had never been generated; the card was removed rather than left pointing at a 404.
Where else this applies
The pattern is a trust-first handbook: a genuinely useful reference that names its own commercial interest up front and gives the reader the tools to check it. It works in any niche where the buyer of a service is overwhelmed, one-time, and surrounded by pitches that hide their incentive: inherited land, timeshare exits, small business sales, senior downsizing. The same shape turns a cold list into people who reach out on their own terms, and the site underneath it is small enough to rebuild for a new niche in about a week.