The Foundations Package
Build Your Operating System Before You Scale
Where you probably are right now
You’re about to grow—fast.
Maybe you just closed a funding round. Maybe you’re entering a new market. Maybe you’ve committed to doubling headcount in the next 12 months.
The opportunity is real. The plan is solid. The resources are there.
But here’s what keeps you up at night:
Your current infrastructure won’t survive the growth.
Right now, you’re 20-30 people. Things mostly work because:
Everyone knows each other
You can get alignment in a single meeting
Tribal knowledge fills the gaps
Your best people compensate for the chaos
But you know—you know—that at 50 people, this breaks completely.
You’ve seen it happen at other companies. Rapid growth → organizational chaos → quality drops → culture fractures → people burn out → growth stalls.
You don’t want that story.
You want to scale without breaking what you’ve built.
And that means getting your foundations right—before the pressure hits.
Why most companies get this wrong
Mistake #1: They wait until it’s already broken
By the time they invest in structure, they’re already at 80 people and in crisis mode. Now every change is disruptive, expensive, and met with resistance.
The best time to build foundations is when you still have breathing room.Problem #2: Your team doesn’t know how to build it
They’re great at execution, but they’ve never designed a process from scratch. They don’t know what “good” looks like, so they either overcomplicate it or keep it too vague to be useful.
Mistake #2: They think hiring solves it
“We’ll just hire a VP of Ops / COO / Head of People. They’ll figure it out.”
But here’s what actually happens: that person walks into a structurally ambiguous environment, spends 6 months trying to understand what’s broken, proposes changes, gets pushback, burns out, leaves.
You can’t hire someone to build foundations on quicksand. You need the foundations first.
Mistake #3: They over-engineer
They bring in a Big 4 consultancy who delivers a 200-page deck with “best practices” from Fortune 500 companies.
None of it fits. None of it gets implemented. You paid €150K for a deck that sits in Google Drive.
You don’t need corporate-scale processes. You need the simplest structure that lets you scale from 20 to 50 without chaos.
What you actually want
You want to grow with confidence.
You want to know that when you hire 10 new people, they’ll ramp quickly—not spend 2 months reverse-engineering how things work.
You want decisions to keep moving at the same speed, even as the team doubles.
You want your systems to scale with you—not become the thing that slows you down.
Most importantly: you want to avoid the regret of scaling on broken foundations.
You’ve seen what happens when companies do that. You’ve watched friends at other startups burn out trying to fix structural debt while also hitting growth targets.
You want better. And you’re willing to invest now to get it right.
Why I can help you with this
I've spent 14 years working across corporate marketing, digital agencies, and startups—always in roles that required cross-functional coordination and operational clarity.
That breadth gave me something rare: the ability to see structural problems that others miss—and fix them fast.
Here's what that's looked like in practice:
At a digital agency, I diagnosed a broken ticketing system where work was piling up and lead times were spiraling. Within 6 weeks, I redesigned the workflow and cut open tickets by 60% while significantly reducing processing time. The team went from firefighting to having breathing room.
At a mid-sized company, I worked with a 30-person department that was drowning in reporting chaos. I implemented process improvements that dramatically improved knowledge retention and made reporting faster and calmer. Information stopped living in people's heads—it lived in systems.
At a startup, I helped leadership move from daily reactiveness to weekly planning cadence. I redesigned the org structure, clarified roles and responsibilities, implemented a project management tool, and introduced new ways of working. The result? Less chaos, more clarity, and a team that could actually execute instead of constantly reacting.
I've developed a diagnostic framework—the Structural Stress Scale—that helps me quickly identify where teams are breaking:
Decision latency (everything bottlenecks)
Ownership ambiguity (unclear who owns what)
Information silos (knowledge trapped in heads)
Coordination overhead (heroic effort, mediocre results)
I specialize in building operating systems for growing companies—the structural foundations that let you scale from 20 to 50+ people without losing speed, quality, or sanity.
I don't bring you generic "best practices." I build systems that fit:
Your actual work
Your culture
Your pace
Your team's capability
And I do it fast—8 weeks, not 6 months.
More importantly: I build WITH your team and leadership, not FOR them.
Systems only stick when leadership understands them. If you hire me thinking "great, now this is off my plate," it won't work. You need to be involved—not doing the work, but understanding what we're building and why.
What you're buying isn't just systems. You're buying the organizational know-how to build and maintain systems that scale.

