Work fonio.ai
Built for 5, still running at 60+
How the CRM and pipelines set up before fonio.ai's first sales hire carried the company from founder-led sales to a 35-person sales team, without ever being rebuilt.
Summary
- 8 weeks
- I built fonio's CRM and pipelines in March 2025, eight weeks before the first sales hire.
- 4 to 65
- CRM users on the same setup, with no rebuild and no second migration.
- 80x
- On it, fonio grew from around €120K to over $10M ARR and from under 800 to 10,000+ customers.
- 11,000+
- closed-won deals in one CRM across sales, self-serve and partners, with product usage syncing in automatically.
Before and after, in numbers
| Metric | March 2025 | August 2026 | Growth |
|---|---|---|---|
| Recurring revenue | around €120K ARR | $10M+ ARR | over 80x |
| Paying customers | under 800 | 10,000+ | 12.5x |
| Team | about 5 people | 60+ people | 12x |
| Sales team | 1 founder | 35+ people in 10+ countries | |
| Closed-won deals | around 1,150 | 11,000+ across three pipelines | around 10x |
| CRM users | 4 | 65 | 16x |
| Funding raised | €0, bootstrapped | €3M pre-seed and $17M seed | $140M valuation |
Seventeen months of growth. The architecture was built in the first three and is still the one in use today.
The starting situation
fonio needed to turn a working founder-led sales motion into something a team could run, and the system underneath had to be in place before that team arrived.
By March 2025, the company was seven months past its first paying customer and still bootstrapped: around €120K ARR, fewer than 800 customers and a team of about five, four of them with CRM access.
Sales was Daniel Keinrath. He ran up to 16 product demos a day, roughly one every half hour, while Matthias Gruber built the entire product on his own. There was no sales team, no partner team and no pipeline, and the systems that would soon have to carry all of it belonged to a founder whose calendar was already full of demos.
fonio had clear product-market fit. What it lacked was infrastructure that could scale: demand was arriving faster than the company could handle, and the state of every deal lived in the founder's system.
I was brought in at that point to design and build that structure together with Daniel, starting from the sales motion he had already proven. The first sales hire started eight weeks later.
Choosing the CRM: why fonio moved from Attio to HubSpot
fonio was running on Attio, a genuinely strong CRM. We moved to HubSpot based on three requirements:
- Growth was overwhelmingly inbound, so lead capture and nurturing had to work natively inside the CRM.
- Self-serve, sales-led and partner-led business had to live in one system and stay cleanly separated.
- The incoming Head of Sales had to be productive from his first week.
The third requirement is the one most CRM selections underweight. Steve Gruber arrived fluent in HubSpot, so his ramp-up went into the pipeline instead of into learning a tool. HubSpot's roots as a marketing platform covered the first requirement.
Choose the CRM for the growth channel you are betting on and for the people who will work in it every day. An outbound-led company at the same revenue could well land on a different tool.
The first project
Roughly 200 hours, about five full-time weeks spread over the first three months:
- Requirements definition with the founders
- CRM selection
- Selection of an implementation partner for second-level support
- Full data migration from Attio to HubSpot
- Build of the first automated sales and partnership pipelines
All of it was live before Steve Gruber's first day.
Scaling sales and partnerships on the same foundation
| Phase | Period | What changed |
|---|---|---|
| Build | Months 1 to 3 | CRM selected and migrated, pipelines built in around 200 hours |
| Transition | Months 3 to 9 | Steve Gruber and David Leibovitz take ownership, partner base reaches around 500 |
| Scale | Months 10 to 15 | 35+ salespeople in 10+ countries, 10,000+ customers |
Sales
Steve Gruber joined in May 2025. Designing a system and running it every day are different jobs, so I reworked the pipeline alongside him and the CTO until it matched how a rep actually sells. The same pipeline went from one founder selling to 35+ salespeople in 10+ countries, and from around 300 to 4,500+ closed-won deals.
Partnerships
Daniel ran partnerships himself at first, with the Partner Pipeline tracking them in the background. David Leibovitz took over day to day in late 2025, at roughly 500 partners. I kept adapting the pipeline structure as he grew the programme past 2,000 closed-won partner deals.
Sales and partnerships both changed owner within nine months. The architecture stayed in place and kept evolving with the new operators. Neither pipeline had to be rebuilt.
Funding and growth, month by month
| Date | Milestone | Context |
|---|---|---|
| Aug 2024 | First customer | Founders only |
| Mar 2025 | Engagement begins, CRM migrated | Under 800 customers, around €120K ARR |
| May 2025 | Steve Gruber joins | Sales moves beyond the founder |
| Late 2025 | David Leibovitz takes over the partner pipeline | Around 500 partners |
| Dec 2025 | €3M pre-seed, one of Europe's largest | Around €4M ARR, bootstrapped until then |
| Apr 2026 | Alexander Brix joins as CCO | 30+ employees |
| Jun 2026 | $17M seed at a $140M valuation, led by 20VC | Around 10,000 customers, 50+ people |
| Aug 2026 | Passes $10M ARR | 60+ employees |
From first paying customer to $10M+ ARR in exactly two years. The step from about €4M to over $10M ARR came in the last eight months, while headcount doubled.
fonio raised nothing until the model was proven to around €4M ARR. The infrastructure investors underwrote in December 2025 and June 2026 was already 9 and 15 months old.
What I built
CRM architecture
I migrated all data from Attio to HubSpot and designed the structure from scratch: how records relate to each other, which fields exist and what each pipeline stage means. One of those fields, a Fonio UID, links every CRM record to the matching account in the product. It is an unglamorous detail, and it is what later allowed product usage to update the CRM automatically.
Three pipelines
Each one carries a different part of the business:
- Sales Pipeline 2.0, from around 300 to 4,500+ closed-won deals (15x)
- Self-serve, from around 600 to 4,500+ closed-won deals (7.5x)
- Partner Pipeline with four partner types, from around 250 to 2,000+ closed-won deals (8x)
Lifecycle automation
Workflows update contacts and deals on their own, for example marking someone an "Active User" as soon as they start using the product. Deals move to closed won automatically when the payment comes through Stripe, because that is the moment the deal is actually won. Sales, self-serve and partner business stay cleanly separated inside one CRM, even as the number of people working in it grew from 4 to 65.
The decisions behind the build
Four decisions shaped the system more than any single feature:
- Which parts of the business need a pipeline of their own
- At what point a self-serve customer gets passed to a salesperson
- What counts as a qualified lead when most volume arrives inbound
- What the founders need to see to decide on the next hire
These decisions are why a system designed for five people still works for sixty.
fonio's founders, reps and partners closed the deals, on the strength of a product the market wanted. My part was the system they ran on: all 11,000+ closed-won deals went through it, deal volume rose nearly 10x, and nothing had to be rebuilt to absorb it.
Questions
Did the CRM cause fonio's growth?
No. The product and the people did. The infrastructure absorbed a nearly 10x rise in deal volume without a rebuild, so fonio could add salespeople, partners and markets as fast as it wanted.
Why leave a CRM that was working?
Attio worked fine. The move was driven by fonio's inbound-led growth, the need to run three business models in one system, and a Head of Sales who already knew HubSpot. A company with an outbound-led motion might reach a different conclusion.
What happened after the engagement ended?
I remain fonio's CRM system admin, so the architecture keeps adapting as the organisation changes.
Engagement scope and deliverables cover March 2025 to June 2026 and are corroborated by public fonio.ai statements and press coverage. Growth, funding and team figures are fonio's overall business results, achieved by its founders and team. They are shown here as the context this infrastructure had to support.
Next step
Planning your first sales hire?
I build the revenue infrastructure founder-led B2B startups in DACH need before the team arrives, so it grows with the company and never has to be rebuilt.