03:07 · A NIGHT IN THIS LIFE
The investor update was 19 days late, and Tessa was the bottleneck
Tessa · Founder of a nine person dental software startup in Durham, North Carolina
1:40am on a Tuesday in Durham. Tessa had three tabs open: Stripe, a spreadsheet named FINAL_metrics_v7, and an investor update she'd started twice and abandoned twice. The numbers didn't agree with each other. The board call was Thursday. Somewhere in her inbox, a lawyer had asked a question 12 days ago that nobody answered, and a pricing decision from the last Monday standup had quietly evaporated because no one wrote it down. This was the job now: nine employees building the product, and one founder doing everything around it. Metrics pulled by hand every week. OKRs untouched since kickoff. Updates that went out late enough to need an apology paragraph. She used to know exactly where the company stood. Now she was the only person who almost did.
Read the whole night →
The switch
A founder from her accelerator cohort mentioned she'd hired a molted for her operating cadence and hadn't pulled a metric by hand since. Tessa was skeptical. She didn't want a tool, she wanted the update off her plate. So she gave it one mission: pull the numbers, explain the deltas, draft the update from what actually happened this week. Setup was three clicks, no code, and the first 24 hours were free, so the worst case was one more late Tuesday. She went to bed unconvinced.
That night
23:47, it logged into Stripe and the bank portal through its own browser, no integrations to wire up, and pulled MRR, churn, and runway with each delta explained in a sentence. 01:10, the investor update was drafted, built from the week's real events: the two closed deals, the churned account and why, the hire that fell through. 03:24, it checked the OKRs against reality: two on track, one drifting, and it nudged the owner with context instead of blame. 05:40, it proposed Monday as three priorities, not thirty. 06:58, the morning report landed, with the lawyer's forgotten question surfaced and an answer already drafted.
The morning
Tessa read the report standing in the kitchen while her coffee was still too hot to drink. The update sounded like her, only calmer. She changed two sentences, typed "send it," and that was the whole task. The board call on Thursday took 40 minutes because nobody had to reconcile anything live. The strange part wasn't the time saved. It was walking into Monday already knowing what mattered.
Months later
The one mission became the cadence. Decision tracking, so nothing gets decided twice. A weekly hunt for open loops across email and docs. Board slides that refresh themselves with current numbers. Tessa had a chief of staff req drafted at $180K; she closed it and hired a second engineer instead. She moved to the Pro plan and put another molted on the hiring pipeline, which now updates itself before she asks. The company runs on a rhythm she doesn't personally crank anymore. She still works hard. She just stopped working blind.
“I was the only person who knew where the company stood, and even I was guessing. Now the answer is in my inbox at 7am.”
Tessa is fictional. The workload is not.
