Every small business owner shares the same quiet worry. If something happened to me tomorrow, would my family know what to do? Who would call the clients? Where are the passwords? What happens to the bank accounts, the hosting, the contracts, the tools that keep the lights on?
Most owners know the answer. No. Their family would be lost. Their business would unravel in weeks. The work of decades would slip away because nobody wrote down the map.
Stillago was built to fix that. This case study walks through how the Sizzle team, in partnership with founder Bear Wade, took this universal but unaddressed problem and turned it into a production-grade SaaS platform with a clear business model, a sharp go-to-market strategy, and a technical architecture built to earn trust when it matters most. For the product surface and positioning, see our Stillago project page.
The Problem Nobody Wanted to Solve
The gap in the market was hiding in plain sight. Estate planning tools handle personal wills. Business succession consultants serve mid-market companies with multi-million dollar exits. Between these two worlds sit millions of solo operators, single-member LLCs, agency founders, consultants, and small business owners who fall through the cracks.
These owners do not have the budget for a full business succession engagement with an attorney. They do not need a $10,000 exit strategy. But they have businesses that matter, families who depend on them, and no structured place to document what would need to happen if they were suddenly unavailable.
Existing tools did not fit. Generic estate platforms treated businesses as single-line items in a will. Password managers captured credentials but none of the operational context. Google Docs and Notion templates existed but nobody actually kept them current, and nobody trained their family to use them. The manuals that did exist were written once, never reviewed, and forgotten in a drawer.
Bear saw the gap clearly. What owners needed was not a document, it was a living system. Something they could build gradually, keep current automatically, and hand to their family with confidence.
Defining the Product
The first design decision shaped everything that followed. Stillago would not be a static document generator. It would be a structured operational manual with nine distinct sections, each purpose-built for the moment a family or team would actually need it.
The sections were chosen through extensive interviews with business owners, accountants, and estate attorneys. The First 48 Hours covers the immediate crisis window. Devices and Access handles phones and passwords. Money Map explains cash flow and accounts. Business Operations covers domains, hosting, and client relationships. People to Call lists advisors and key contacts. Keep vs Kill makes the hard calls about what continues and what winds down. Insurance, Legal, Estate consolidates policies and documents. The Long Game covers government matters and digital legacy. Keeping It Alive handles review cycles and distribution.
Each section was designed for someone under stress. Kin opening the emergency link at 2am after a medical event does not need a beautifully designed dashboard. They need a clear timeline, phone numbers that can be tapped to call, and guidance that reduces panic. Every interaction was designed with that moment in mind.
The Technical Foundation
The stack was chosen for reliability and security, not novelty. Next.js App Router for the application layer. MongoDB Atlas for data persistence. Stripe for billing. Resend for transactional email. A deliberately boring set of choices that would hold up under scrutiny.
Security was treated as a product feature, not a compliance checkbox. Sensitive fields use AES-256-GCM field-level encryption with keys validated at startup. Production deployments will not launch without properly configured secrets. Authentication uses passwordless email OTP with httpOnly JWT cookies. Rate limiting protects every sensitive endpoint. Timing-safe comparisons guard the cron job authentication. Audit logs record every meaningful action with a one-year retention TTL.
Emergency access deserved its own security model. When a designated person opens a token-protected link and enters the access code, they receive a short-lived JWT scoped exclusively to emergency read endpoints. They cannot write, cannot access owner settings, cannot do anything except read the manual. The emergency session is architecturally separate from the owner session, enforced at the middleware layer.
This matters because the whole product is a promise. The owner trusts Stillago to hold sensitive information. The family trusts the manual to work when they need it. The moment either trust fails, the product fails. Every technical decision was made with that weight in mind.
Ring the Bell: The Dead Man's Switch
The differentiator that sets Stillago apart from every other product in the space is Ring the Bell. Most succession tools are static. They assume the owner will update them. They do not.
Ring the Bell monitors owner activity. If the owner does not check in within a configured window, the system begins a graduated escalation. Email warnings first. Then a wellness check to the designated person. An owner dispute window. Eventually, if nothing resolves, the system transitions into a handover state where emergency access aligns with policy.
Building this feature correctly was the hardest engineering work in the product. False positives would be catastrophic. Sending a wellness check to a spouse because the owner was on vacation would destroy trust instantly. False negatives would be equally damaging. Missing a genuine emergency would mean the product failed at its one job.
The solution involved careful tuning of trigger windows, multiple dispute and snooze paths, and comprehensive audit logging at every transition. The cron job processes users through a state machine with explicit transitions and logged events. Every email sent, every status change, every wellness check response is recorded. The owner can see exactly what happened, when, and why.
The Fresh Check Retention Engine
The second hard problem was decay. Manuals that exist but are six years stale are almost worse than no manual. Family members trust the document, act on outdated information, and make decisions based on wrong assumptions.
Fresh Check solves this with a weekly email digest that surfaces specific fields for quick confirmation. The owner reviews a handful of high-priority items, confirms they are still accurate, and gets a streak indicator on their dashboard. The system tracks freshness per field and triggers staleness alerts when sections age beyond threshold.
This turned retention from a marketing problem into a product feature. Owners who engage with Fresh Check stay current. Owners who do not receive targeted reminders escalating in frequency. The product teaches itself to the user through structured weekly touchpoints.
The Pivot to Fractional CFOs
The most important strategic moment in Stillago's development was realizing the direct-to-owner motion was brutal. Owners do not wake up searching for emergency operations manuals. They avoid thinking about mortality. Even strong product-market fit cannot overcome a category with no search demand and a buying psychology rooted in avoidance.
The pivot was to the fractional CFO channel. Fractional CFOs serve exactly the owners Stillago was built for. They have the trust, the relationship, and the weekly conversation already open. For them, Stillago is not a mortality product. It is a client retention and differentiation tool.
This required building a second product surface inside the same codebase. CFO accounts with their own onboarding, their own shell, their own permission boundaries. A portfolio dashboard showing every client with completion percentages, last edit dates, and health status labels. An invite flow where CFOs send links, owners accept, and the relationship is established invisibly at the OTP verification step. Co-branding that carries through to the kin emergency experience, so the CFO firm's name appears at the moment it matters most.
The middleware enforces role isolation strictly. CFOs cannot access owner APIs. Owners cannot access CFO APIs. Emergency sessions remain scoped to their own read-only path. Three distinct audiences, three distinct experiences, one unified codebase.
The Letter of Intent Layer
The latest addition to Stillago addresses the one thing a manual cannot implicitly convey: what the owner wants to happen. Does the business pass to a successor? Get sold? Wind down cleanly?
The Letter of Intent sits above the nine sections as the first thing kin see when opening the emergency link. A conversational wizard walks owners through their succession path, named people, timeline, priorities, and do-nots. The system generates a personal message in the owner's voice, editable before save. Kin see the letter framed not as a legal document but as a message from someone they love.
Critically, the product stays in its lane. The Letter of Intent makes clear it is guidance, not a legal instrument. A complexity diagnostic routes owners to attorney involvement when their situation requires it. For simple cases, templated business succession documents including durable power of attorney and transfer-on-death designation can be generated from attorney-drafted templates and executed offline with a notary.
Lessons From the Build
Three lessons shaped how Stillago was built and how it continues to evolve.
First, security is a product feature. Every decision around encryption, authentication, rate limiting, and audit logging was made because trust is the product. Owners hand over sensitive information. Families depend on it working. Technical rigor is not overhead, it is the reason the product exists.
Second, completion is the real metric. A half-filled manual helps no one. Fresh Check, the complexity diagnostic, the portfolio dashboard, and the CFO channel all exist to drive completion. The product asks not whether users signed up, but whether their manual is actually ready.
Third, the go-to-market matters as much as the code. Stillago would not have found traction as a direct-to-owner product. The pivot to the fractional CFO channel changed everything. The same product, same codebase, same features now serve a buyer who actively wants what Stillago delivers.
Stillago is proof that some of the best SaaS products live in the spaces everyone else ignored. The question is never whether the problem exists. It is whether you are willing to build the system that solves it.