An honest self-assessment.
Because juries ask. And they should.
This page exists because the most important question any funder asks isn't “is the product good?” It's “can this specific person build a company?” What follows is my answer - including the real gaps, not a sanitised version of them.
Building and running a bootstrapped startup takes five archetypes - the Hustler, the Hacker, the Hipster, the Handler and the Hound. Here's the map: which come naturally to me, where my gaps are, and the system I use to close them.
Five archetypes, mapped.
Two are my natural home. One is a functional strength with a known ceiling. Two are gaps I've engineered a system to cover - with AI agents, lean tooling and fractional expertise - so the company never depends on me being superhuman.
What each role does - and how I cover it.
The Hustler
The customer-facing lead who pinpoints the problem, articulates the vision, and stays keen to pivot on real feedback.
A career spent translating between engineers, auditors and executives taught me to sell a vision and adapt it. Donza is validated with real signal from real families.
The Hacker
Conceives the product and builds the scalable systems - architecture, APIs, the technical longevity of the company.
This is home. Two decades of engineering on one unified stack - I own the build end to end, from idea to deploy, and ship at a pace most teams can't match.
The Hipster
The creative lead for UX, UI and storytelling - turning a functional tool into something people love to use.
I build clean, intentional UIs I'm proud of - but world-class brand design and deep UX craft are a ceiling I'll hit. The plan: own the functional UX through V1, then bring in dedicated design expertise as the product matures and budget allows.
The Handler
The architect of execution - what to build, at what cost, at what time, keeping the roadmap valid and competitive.
Objective systems do the job willpower would eventually fail at: issue tracking and AI scheduling, so the roadmap runs on deadlines even when I don't.
The Hound
The analytical lead who sniffs out churn signals and growth opportunities through KPIs and user behaviour.
I automate the sniffing: product analytics and sentiment analysis surface churn and broken onboarding before they bite, so I react to what users actually do. And the analytics grind is the part of the job I'd procrastinate on - which is exactly why I automated it instead of trusting myself to do it manually.
Strengths I lead with. Gaps I close with systems.
No founder is all five archetypes - the difference is whether the gaps are named and built around. Mine are.
Why Donza. Why me. Why now.
Donza isn't a startup idea I found - it's a problem I lived for years, in a household where the invisible weight of school-age family admin was quietly eroding something important. I have two children in different classes at the same school - partially overlapping teachers, divergent schedules, two streams of letters and chats to track at once. I work in a demanding senior role. I watched the imbalance compound, and I built the thing that should have existed.
The problem is real (3.4M DACH households in the serviceable segment, no direct competitor addressing the full capture-to-action pipeline). The timing is right (LLMs make the capture layer viable in a way that wasn't true three years ago). The regulatory moat is genuine (DSGVO, DACH privacy expectations, ISO 27001 - these are purchase criteria I can meet because I helped write the standard). And the core product is already built: capture pipeline, the first agents, the Room Parent tooling.
What's not built yet: public launch, user traction data, and the growth loop. That's exactly what capital would accelerate.
I don't rely on being superhuman.
I rely on systems.
The fastest way to kill a bootstrapped startup is to overhire on full-time salaries before revenue justifies them - or to bet the whole company on one founder's stamina. I do neither.
AI agents as permanent architecture
AI handles the high-volume, repetitive work across support, ops and analytics - a permanent part of the architecture, with human-in-the-loop checkpoints exactly where judgement matters.
Fractional expertise instead of premature hires
Senior strategy - fractional CFO/CMO judgement - bought by the month for a fraction of a full-time executive hire, and added only as real milestones are met.
Institutional memory in the system
The company's operating intelligence lives in the stack and the automations, not just in my head - which de-risks key-person dependency and means no single bad week can stall the company.
Transparent stage management
Donza is pre-launch. There are no public users yet, so I have no retention data or conversion metrics - I'll show those numbers as soon as they exist. What I have instead: a built foundation, a validated problem (primary research with real families), and a detailed financial model with three scenarios, worst case first. The gap is named, and the plan to close it is right below.
The product is built.
Capital buys speed.
Donza is past the build-risk phase. What remains is scale risk - the one risk capital actually solves.
Scale infrastructure. The systems to grow past the solo ceiling without breaking what already works.
Fractional expertise. Senior CFO/CMO judgement bought by the month, added only as real milestones are met - instead of premature full-time hires.
Growth instrumentation. A professional version of the Hound: the data layer that turns early usage into real retention numbers.
And to be clear about what kind of capital: public funding - gladly. Donza is not open to VC or equity investment at this stage. Equity comes after the product has proven what it's worth - not before.
Systems > discipline.
Most founders run on willpower - a finite resource. I've engineered an operating model that absorbs the punches: capital-efficient, automated where it can be, human where it must be, and explicit about its own gaps. That's what it takes to run a bootstrapped startup - and it's how Donza is built.