How to build a commercial operating system in 90 days

When founders ask me what I actually do during a fractional engagement, the honest answer is: I build the commercial operating system they didn't have time to build themselves.

That phrase — commercial operating system — isn't jargon. It's the infrastructure underneath growth that most early-stage startups skip past because they're too busy chasing the next tactic. It's the difference between a company where growth is a founder's job and one where growth is something the business does on its own.

After co-founding and scaling Yuno, Switzerland's first consumer electronics rental platform, and evaluating over 200 business models at a corporate venture studio, I've found that building this system takes about 90 days when done properly. Not because the work is complicated, but because the work has to happen in a specific order, and each phase depends on the one before it.

Here's the framework I use.

Days 1–14: Diagnosis

The first two weeks are about understanding the business as it actually is — not as the pitch deck says it is. Most founders have a mental model of their company that is 6 to 12 months out of date, built on assumptions that were true at an earlier stage and never revisited.

In practice, diagnosis means three things.

Mapping the current commercial reality. What's actually driving revenue right now? Which channels are working, which aren't, and which ones does the founder believe are working but actually aren't? This requires digging into real data — CRM exports, ad accounts, analytics, customer interviews — not just reading the weekly dashboard.

Understanding the customer. Who is actually buying, why are they buying, and what do they have in common? Most early-stage startups have a stated ICP and an actual ICP, and the two rarely match. Five structured customer conversations in the first two weeks usually reveal more than six months of founder intuition.

Finding the real bottleneck. Every early-stage company has dozens of problems. Only one or two actually matter. Diagnosis ends when you can write down the single most important commercial problem in one sentence, and everyone on the leadership team agrees that's the right sentence.

Diagnosis is the phase founders are most tempted to skip. It feels slow. It doesn't produce visible output. But skipping it is how companies end up running six growth experiments in parallel and learning nothing from any of them.

Days 15–30: Strategy and unit economics

Once you know what the real problem is, you can build a strategy that addresses it. This phase is where most consultants stop — they hand over a 40-page strategy document and leave. That's a mistake, because strategy without implementation is just expensive opinion.

The goal of weeks three and four is to produce two artifacts.

A one-page commercial strategy. Not a deck. One page. It covers positioning, ICP, the core value proposition, the primary go-to-market motion, and the three to five priorities for the next quarter. If it doesn't fit on one page, it's not a strategy — it's a wish list. The constraint forces clarity.

A unit economics model. For every business that's past product-market fit, you need to know what a customer actually costs to acquire, how much they pay, how long they stay, and what the margin profile looks like over their lifetime. This usually lives in a single spreadsheet that becomes the backbone of every commercial decision from this point forward. Without it, you can't price intelligently, you can't decide which channels to invest in, and you can't tell whether growth is making you money or losing it.

These two artifacts become the anchor for everything that happens in the next sixty days.

Days 31–60: Building the operating cadence

Strategy that nobody executes against is worthless. The middle month is about building the rhythm that turns strategy into weekly action.

The weekly growth review. A 45-minute meeting, same time every week, same structure every time. What moved last week, what didn't, what we're testing this week, what we need to decide. The meeting isn't a status update — it's a decision-making forum. If nobody's disagreeing, the meeting isn't working.

The dashboard. A single, simple dashboard that shows the five to seven metrics that actually matter. Not twenty metrics. Not a beautiful BI tool. Something everyone on the team can read in 30 seconds and walk away with a shared understanding of whether the business is winning or losing. Most early-stage startups over-engineer this and end up with dashboards nobody looks at.

The prioritization system. A clear way of deciding what gets worked on next. In early-stage companies this usually takes the form of a weekly experiment backlog — a list of things the team is testing, with each experiment tied to a specific hypothesis and a way to measure whether it worked. Without this, the team ends up doing whatever the founder mentioned in the last meeting.

The written context. Whatever lives in the founder's head needs to get written down. Pricing logic. Positioning. Customer insights. The rationale behind decisions that have already been made. This is the most tedious part of the work and also the most valuable, because it's what allows the next hire to contribute without needing six months of founder attention.

By the end of day 60, the commercial function should be running without the founder needing to make every decision.

Days 61–90: Execution and iteration

The final month is where the system gets stress-tested. Strategy is theory until you start shipping against it.

This phase is about three things.

Running the experiments. The prioritized backlog from weeks five to eight starts shipping. Some experiments work. Most don't. The point isn't to be right — the point is to be learning fast enough that each week compounds on the last.

Adjusting the model. Real data from real experiments starts updating the unit economics model, the dashboard, the strategy. This is where the operating system proves its value: when something isn't working, the team knows within days rather than months, because the cadence is built to surface problems early.

Transitioning ownership. By day 90, the fractional partner should be doing less and the team should be doing more. If everything still depends on the fractional partner being in the room, the engagement has failed. The goal is a team that can run the operating system without you — with you staying on as senior support rather than daily operator.

What comes after day 90

Ninety days isn't the end of the work. It's the end of the build phase. After that, the operating system either keeps running and compounds — in which case the founder's role shifts from doing commercial work to reviewing it — or the system breaks, which usually means one of two things: the strategy was wrong and needs revisiting, or nobody on the team has been empowered to actually own the system day to day.

Most of the time, when a 90-day build works, the fractional engagement transitions into an ongoing one-day-a-week retainer where the operating system gets refined over the next six to twelve months. Sometimes the founder is ready to make a full-time senior hire, and the fractional partner hands over a team and a system that are ready to run. Both outcomes are good ones.

The one mistake founders make with this framework

The mistake is treating this as a linear checklist. It isn't. Diagnosis reveals things that change the strategy. Strategy reveals gaps in the unit economics. The operating cadence exposes weaknesses in the strategy. Each phase informs the others, and the 90 days are less about checking boxes and more about building a system that can keep learning after the engagement ends.

If your company doesn't have a commercial operating system yet, the good news is that 90 days is enough to build one. The bad news is that the work doesn't happen on its own — someone has to own it, build it, and transfer it to the team. For most early-stage companies, that person doesn't yet exist internally. That's the gap fractional commercial leadership is designed to fill.

About the author: Fabian Herrmann is a fractional commercial partner based in Berlin. He co-founded Switzerland's first consumer electronics rental platform, and scaled it to 12,000 contracts and 22 employees as Chief Commercial Officer. He now works with seed to Series A startups building their commercial operating systems from scratch.