Founder Diary
Building SnapLedger in public — product decisions, lessons and customer stories, in Richard's own words.
Start here
Post 0
Why I'm Starting This Diary
One month after launch — who I am, why I'm building SnapLedger, and the café question from my partner Alex that changed everything.
July 1, 2026·6 min read
Post 1
The Moment I Stopped Building Tools
SnapLedger began as expense tracking. Then Alex's documents — and a lawyer friend's thirty apps — taught me the real problem isn't more tools. It's connecting information.
July 2, 2026·5 min read
Post 2
Trust Is an Engineering Problem
SnapLedger's biggest challenge isn't AI or accounting or competition — it's trust. And trust isn't bought or certified. It's engineered, one deliberate decision at a time.
July 3, 2026·5 min read
All entries
Post 60Launching Snappy PM: Letting AI Understand Workflows from Real ProjectsAugust 31, 2026Post 59Software's Front Door Is Shifting from Menus to ConversationAugust 30, 2026Post 58AI-Native Isn't About Spending More Tokens — It's About Redesigning WorkflowsAugust 29, 2026Post 57AI Doesn't Lack Knowledge — It Lacks Trusted ContextAugust 28, 2026Post 56When AI Agents Start Working, Responsibility Must Be Designed InAugust 27, 2026Post 55Cursor Got Cut Off: Why an AI SaaS Can't Bind Itself to One ModelAugust 26, 2026Post 54A Finance Tool for ProcrastinatorsAugust 25, 2026Post 53France's E-Invoicing Is Here: What Should Freelancers Prepare Now?August 24, 2026Post 52Making Snappy More ThoughtfulAugust 23, 2026Post 51Why Some Documents Can't Be DeletedAugust 22, 2026
Get the Founder Diary + regulatory updates for your country
One email per week, only when there’s something real — Richard’s founder diary and the regulatory updates that matter where you live. Free, unsubscribe any time.