Making personal mail feel considered before anything is sent

The people keeping holiday-card lists, family addresses, or community contacts need more than rows of data: they need an easy way for someone to share an address, a reminder before a meaningful date, and a path from a draft to something that can actually be sent.

Existing categories pull in opposite directions. A spreadsheet puts every step on the owner; a CRM turns friendship into pipeline management. Dear Friends started with a quieter premise: keep the list personal, ask as little as possible from recipients, and leave physical mail under the sender's control.

Share one link. Remember the date. Prepare something real.

The product is organized as three connected habits rather than a feature inventory. A friend adds an address without creating an account; the owner keeps the person and their dates in one private workspace; and the system prepares the label, letter, or eligible digital audience without pretending to mail a physical item.

That sequence also defines the interaction standard. Public mutations derive ownership from the server, high-consequence actions preview their audience, saved state follows actual persistence, and partial failures remain recoverable instead of collapsing into a generic success message.

The owner workspace combines searchable contacts, groups, delivery preferences, birthdays, notes, verification status, a geographic view, calendar events, subscription imports, and estimated mail-by dates. Public collection and verification remain account-free for recipients.

The writing path supports reusable Markdown drafts and first- and last-name merge tags. From the same server-derived audience, the owner can export Avery-ready address files, generate personalized letter PDFs, or confirm an email send to contacts explicitly marked digital.

The inspected release branch contains 166 commits from March through July 2026 and is merged into the remote default branch. The repository includes the application, twelve ordered database migrations, public and authenticated routes, transactional email builders, scheduled jobs, CI configuration, and a live-application link.

In a disposable copy of the inspected source, TypeScript completed successfully and all 99 Vitest unit and security tests passed with caching disabled. Those tests cover schemas, capabilities, tenant boundaries, verification, calendar URL handling, reminder timing, export formatting, geocoding, and cron authentication.

No usage, revenue, retention, or correspondence-outcome analytics were found. The case-study claims are therefore limited to implemented behavior, repository and release history, passing source-level checks, and current product captures with illustrative data.

Earlier concepts blurred the boundary between preparing mail and mailing it. The stronger product contract is narrower: Dear Friends helps collect, remember, write, export, and send eligible email; printing, penning, stamping, and posting physical correspondence remain with the person who knows the recipient.

The engineering work reinforced the same lesson. Trust is not a tone-of-voice layer added at the end. It lives in signed capabilities, single-use verification, tenant-safe relationships, audience previews, persistence feedback, retry semantics, timezone handling, and fail-closed scheduled routes.

The next evidence gap is behavioral. A future iteration should measure where owners stop between collecting an address and preparing correspondence, and whether quiet reminders lead to a completed export or send without becoming another notification feed.