The first 90 days of Co-Management — what happens step by step

Introduction — Co-Management is not an audit with a slide deck

If you run a service business — a software house, an agency, a creative studio, an e-commerce with a strong service arm — and you feel that everything still runs through you, then this article is for you. Not for someone looking for another report to file away in a drawer. Not for a founder who wants to "outsource strategy" and come back a month later for a PDF. For you — someone growing faster than their processes can keep up, who is starting to suspect that the problem isn't a lack of ideas, but the lack of someone who will genuinely take the weight of execution onto themselves.

Co-Management at ECG is work in a Founder-to-Founder relationship. I enter your company at the highest decision-making level — not as an advisor on the sidelines, not as a contractor executing assigned tasks, but as an operating partner. We share the risk and the success, working in a hybrid model (cash + success fee, and in advanced cases equity). It means I'm playing toward the same goal as you. If the company doesn't grow, I don't get paid in full either. That's "skin in the game" — and it's the fundamental difference between Co-Management and everything you could buy on the consulting services market until now.

This article breaks down the first 90 days of the partnership into its component parts. Week by week, I'll show you exactly what happens: when we come in, what we diagnose, when the first real changes begin, how we measure the effect, and what the decision about next steps looks like. No beating around the bush, no corporate-speak. Each phase ends with something you can touch — a document, a working system, a measurable result. This isn't a promise. It's a description of how I actually enter a company.

Why 90 days specifically? Because it's the smallest stretch of time in which you can complete a full cycle: truly understand the company, introduce changes that will stick, and measure the effect against a hard starting point. Shorter — and you're left with cosmetics, a few improvements that dissolve in the first hot week. Longer, without a clear milestone — and you lose discipline, and the partnership turns into vague "helping." That's why we treat the first 90 days as a separate, self-contained stage with its own beginning, middle, and end, even if the whole partnership lasts 6–12 months. It's the foundation. Without it, the rest has nothing to stand on.

The premise is simple: after reading this text, you should know exactly what you're signing up for before you sign up for anything. Most of the founders I talk to have some experience with a consulting firm behind them that ended in disappointment — a nice document, zero change in daily life. That's why I don't want you buying a pig in a poke. I want you to see exactly what happens in week two, week eight, and week twelve, what resistance you'll encounter along the way and how we defuse it, and what specifically stays in the company once we're gone. This is a map of the first 90 days drawn from the perspective of someone who has walked this path with founders many times — not theory, just the practice of entering a company.

Consulting gives you a PDF and wishes you luck. Co-Management gives you a partner who stays in the company, takes responsibility for decisions, and only leaves once the system works without both of us. The difference is like the difference between a map and a driver who gets into the car with you and drives the hardest stretch together.

You'll find a full description of the format on the Co-Management page. Below — what happens from day zero to day ninety.

How Co-Management differs from consulting and an interim COO

Before we get to what happens week by week, you need to understand one thing: there are three completely different ways someone from the outside can "help your company." And most founders confuse them, which leads them to buy not what they actually need. Consulting, Interim COO, and Co-Management are not three levels of the same service. They are three different relationships, three different levels of responsibility, and three different models of risk-sharing. Let's go through them one by one, because whether you should even keep reading depends on it.

Consulting delivers strategy and disappears

Classic consulting works on a simple pattern: someone comes in, analyzes your company from the outside, runs a series of interviews, prepares recommendations, and presents them at a closing meeting. You get a document — sometimes very good, sometimes very thick — telling you what you should change. And that's where the consultant's role ends. Implementation? That's your problem now. Execution? Your team. Making sure anyone actually gets off the ground? You, the founder, who has no time anyway.

Consulting has its place. If you genuinely only need an outside perspective, a fresh pair of eyes, and direction — a lightweight diagnostic format can be exactly what's needed. At ECG we call it Advisory and Audit: 2–3 weeks, an AS-IS process map, a roadmap of changes, a closing session with the founder, no commitment to further work. You walk away with a plan. But honestly: a plan is only the first five percent of the journey. Most strategic recommendations die not because they were bad, but because no one had the time, energy, or mandate to implement them. A PDF doesn't implement itself. And you, who are already the bottleneck, won't suddenly become less busy just because you have a nice document.

Pay attention to the word "disappears." That's the essence of classic consulting — the relationship has a pre-programmed ending that arrives precisely at the moment the hardest part begins, which is implementation. The consultant bears no consequences for whether their recommendations worked. If the implementation failed, you can always say "execution fell short on your side" — and formally it will be true. This model has a built-in asymmetry of risk: the consultant risks their time, you risk the company's future. For many founders of growing service businesses, that's not enough. They need someone who will not only point a finger at the problem, but stay long enough to see whether the solution actually worked — and bear the consequences if it didn't.

Interim takes the wheel for a while

An Interim COO or Interim PM is a completely different story. Here, someone doesn't advise from the sidelines — they enter the company and take the operational wheel. From day one, they take responsibility for putting work in order: project workflow, communication, the sprint and status system, reporting to you. This is a real operator, not a voice from behind a slide deck. The Interim COO/PM format at ECG is typically 3–6 months of intensive work, after which the system stays in the company — with you or with your internal PM.

The key word is "temporary." An interim is, by definition, meant to step back. They come in, put out a specific operational fire, organize the work, onboard your successor, and leave. It's a great solution when you need COO-level competence "starting tomorrow," but a full-time hire is too much or too soon. An interim buys you the operational effect without the costs of recruitment, onboarding, vacations, and benefits. But an interim works at the level of operations — they organize how the company delivers. They don't get into the question of where the company should go as a business, how its value should grow, what your narrative before an investor looks like, or the path to an exit. That's not their role and not their horizon.

An interim is a huge step beyond consulting — because here someone genuinely takes responsibility for operations, reports to you weekly, manages resources and escalations. This is not a voice behind a screen, but hands inside the machine. But the billing model stays simple: you pay a monthly rate for the operator's time and responsibility. It's a fair, predictable arrangement — you buy the operational effect instead of a headcount. The difference versus Co-Management isn't about the quality of work, but about two things: the horizon (operations vs operations plus strategic company value) and the risk structure (a rate for time vs a share of the success). If your problem is "projects are stuck because of me, because I run everything personally," an interim is often the ideal choice. If the problem sounds more like "I want this company to be worth twice as much in two years, and I'm looking for a partner for that journey" — that's already Co-Management territory.

Co-Management = a partner at the highest level

Co-Management combines the highest level of operational responsibility of an interim with the strategic horizon that consulting never touches — and adds something neither of them has: shared risk. I enter your company at the highest decision-making level, as an operating partner. I don't execute assigned tasks. I co-manage. I'm present in board meetings, I take responsibility for decisions, I represent the board in conversations with partners, key clients, and in advanced cases investors. We work in a Founder-to-Founder relationship — because I, too, understand what it means to build a company and carry its weight.

The partnership is long-term: typically 6–12 months, sometimes longer. After the first 3 months we do a review and adjust the scope. And most importantly — the model is hybrid. Part of the compensation is cash, part is a success fee tied to the effect we generate together. In advanced cases, equity and a Co-Founder formula come into play. This is not billing hours. This is sharing risk and sharing success.

The three pillars Co-Management stands on capture this dual track. The first is the Value Creation Plan — a jointly built value creation plan and operating model: a 12–24 month strategy, success metrics, a map of the key growth decisions. The second is the initiative roadmap — an ordered list of growth and optimization moves with priorities: team capacity planning, pricing and positioning, operating standards and a decision system. The third is co-managing implementation — working shoulder to shoulder with your team, weekly operational sprints, representing the board in conversations, support with M&A and due diligence. These are the three pillars that will accompany you throughout the entire first 90 days — and they are what distinguishes an operating partner from someone who merely organizes operations.

Who is it for? Co-Management makes sense in three situations. For a pre-seed/seed-stage startup that needs "zero to one" in operations and sales — someone who will go through the hardest phase with you. For a growing service business that wants to reach a higher revenue level without adding headcount — through better processes and a higher margin per project. And for a founder who is simply looking for a partner for long-term growth rather than firefighting — someone who can say "no" and look at the company on the scale of a year, not a sprint. If you recognize yourself in any of these pictures, keep reading, because the 90 days below describe precisely your path.

A consultant earns the same whether their recommendations worked or not. An interim earns for the time they spend organizing operations. An operating partner earns in full only once your company has genuinely grown. Three different services, three different levels of engagement — but only one in which my interest is literally the same as yours.

This distinction is not academic. Which of these three formats you need determines whether the first 90 days will look the way I describe below. Because what you're about to read is specifically the Co-Management path — the entry of an operating partner, not an advisor or a temporary operator.

Day 0 — before we come in

The first 90 days don't begin on day one. They begin earlier — at the moment we call day zero. It's everything that happens before I even cross the threshold of your company operationally. And it's the moment that decides the success of everything else more than any SOP or authority matrix. Because Co-Management is a relationship, and a relationship can't be implemented. It has to be built before we start co-managing.

Intro call and chemistry

It all starts with a conversation. 15–30 minutes online, no commitment. I don't hard-sell anything on that call — if it's not the right time or not the right format for you, I'll tell you straight. That's not a polite cliché. Co-Management means we'll spend the next 6–12 months together at the highest level of your company, making decisions together that genuinely carry weight. If there's no chemistry, no mutual trust, no similar way of thinking about business — there's no point starting. Better to find that out on the intro call than in week seven.

On that call we do a preliminary diagnosis. I show you where, in our view, the real problem lies — not the one you report yourself, but the one that becomes visible after a dozen questions about your day as a founder. We map it across four areas and form the first hypothesis: what will give you back the most time. It's the moment when you assess me, and I assess whether your company is at a point where Co-Management makes sense. Chemistry works both ways.

It's worth understanding that this intro call is part of a broader process that begins even earlier — with screening. Before we even sit down to talk, a short form or message lets both sides check whether we're a fit at all: three questions about the company's stage, the team, and operational pain points, a decision within 24 hours on whether it makes sense to talk further. If we're not a fit — I'll point you to who can help more. This is not a sales funnel designed to catch you. It's a filter meant to save both of us time. Co-Management is too serious a relationship to enter with someone for whom it isn't the right format or the right moment.

What we settle before day 1

If both sides say "we're in," before we start operationally we have to settle the things that can't be postponed. First — the financial model. Co-Management is a hybrid formula: we set the ratio between cash and success fee, define what effect we settle against after 90 days and beyond, and in advanced cases we discuss equity. This is a conversation that must be honest and clear from the start, because the whole point of "skin in the game" is that we both know exactly what we're playing for.

Second — the core team. We settle who I'll be talking to in the diagnostic phase: usually 3–10 key people who genuinely know the company's operations from the inside. They don't have to be managers — often the most truth about where the company gets stuck is known by the people on the front line: those running projects, talking to clients, hitting the same walls every day. We also settle how we'll communicate my entry to the team — because the way a founder introduces an operating partner lays the foundation for either later adoption or resistance.

Third — the scope of the mandate. An operating partner enters at the highest level, so it has to be clear to you, to me, and to the team that I have a real mandate to co-decide, not the status of "a consultant who can be ignored." Without that mandate, everything else turns into advisory from the sidelines — which is exactly what Co-Management is not. This is the moment when, as a founder, you have to make a conscious decision to give up part of your decision-making space. Not the whole company — the space. That distinction is crucial, and I'll come back to it more than once, because this is precisely where most of the resistance is born.

What the founder experiences

Let's be honest about what you feel at this stage. Most founders feel a mix of relief and resistance on day zero. Relief, because someone finally wants to take on the weight you've carried alone for years. Resistance, because you're letting someone into the highest level of a company you built from scratch — a company that is an extension of you. Questions come up: "Will he really understand my company?", "Will the team accept him?", "Won't I lose control?", "Isn't this admitting I failed because I couldn't do it alone?"

All of this is normal and healthy. Co-Management is not about taking your company away from you — it's about you ceasing to be the only point through which everything has to pass. You don't lose control; you gain a command center that, for the first time in a long while, lets you see the whole company at once instead of chasing fifteen threads in your head. And the fact that you're asking for an operating partner is not a failure. It's exactly what founders do when they want their company to grow in value, rather than merely survive another quarter of chaos. This resistance doesn't disappear on day zero. We defuse it over the following weeks — through action, not promises.

Weeks 1–3: Diagnosis and trust

I come in. The first three weeks are a phase in which I change almost nothing yet — and that's deliberate. Because before I rebuild anything, I have to understand how your company really works. Not how you think it works. Not how it's described in an out-of-date Notion. How it really works, on a Monday morning when a client writes that the deadline is slipping and half the team doesn't know who's supposed to make the call. This is the diagnostic phase and — equally important — the trust-building phase. Because an operating partner without the team's trust is just an expensive observer.

What the consultant does

In these first weeks, ninety percent of my work is listening and observation. I get into the company's rhythm: I'm in meetings, I read the communication, I track how work flows and — most importantly — where it gets stuck. I don't come with a ready-made deck for every occasion or an off-the-shelf methodology I try to force onto your company. I come with an outside perspective and a hard, cold look at where the company burns time, energy, and money. This is deliberate restraint: the first weeks are observation and interviews, without introducing changes. The team sees that I listen before I start co-deciding — and that's the first brick of trust.

This restraint is often the hardest thing for founders to accept, because intuitively you want the operating partner to start "fixing" right away. But any change introduced before understanding the company is a gamble. Processes that look senseless from the outside often have a hidden logic — they came about because they once solved a real problem that isn't visible from the perspective of day one. A partner who doesn't respect this and starts rearranging the furniture blindly will, at best, waste energy, and at worst destroy something that was working and lose the team's trust right at the start. That's why I spend the first weeks asking "why does it work this way" far more often than "this needs to change." This isn't passivity. It's gathering ammunition before the execution phase, which arrives in week four at full force.

At the same time, this phase serves a purely relational function. The team observes me as closely as I observe them. People want to know whether I'm just another "outside consultant" who will come in, make some noise, and disappear, or someone who genuinely understands their work. Every well-asked question, every moment of attentive listening builds capital that I'll spend later, when it comes to hard decisions. Without that capital, no new process will hold — because processes are held up by people, not documents.

Interviews with 3–10 people

The heart of the diagnosis is conversation. I conduct interviews with 3–10 key people: with you, with managers, with operational staff, with those running projects and on the front line with the client. I ask what works, what doesn't, where they lose the most time, what frustrates them, what they don't understand about the way the company works. These conversations have two functions. The first, obvious one: I gather raw data on how the company functions. The second, less obvious but equally important: people feel, for the first time in a long while, that someone genuinely listened to them. This builds adoption of the later changes, because the system we build is created together with the people who will use it — rather than imposed on them from above.

In these conversations I look especially for discrepancies. Because the most interesting thing isn't what everyone says in agreement, but where the pictures diverge. The founder says the client onboarding process is clear — and three people on the team describe it completely differently, each in their own way. That's a signal: the process exists only in the founder's head, not in the company. A manager claims escalations work — and an operational person says that when there's a problem, they message the founder directly anyway, because "that's the fastest way." These are the moments when the diagnosis stops being theory. The gap between how the company thinks it works and how it actually works is a map of bottlenecks drawn in human voices.

I also ask directly about the founder — because Co-Management is, to a large extent, a project around one person. Where does the team wait for your decisions? On which matters are they afraid to decide themselves, because "the founder will want to approve it anyway"? What passes through you only because it always has, not because it must? The answers to these questions are sometimes uncomfortable, but they're gold. Because they show precisely the points where your calendar is held hostage by the absence of clear rules — and which we'll defuse in the execution phase.

AS-IS workflow map

From the interviews and observation comes an AS-IS process map — a faithful picture of how the company really works today, with all its bottlenecks and workarounds. I map the full project workflow: from the moment a client appears, through sales, onboarding, delivery, to closing and settlement. On this map I mark the bottlenecks — the places where work stalls, waits for a decision, or comes back to you because no one else has the mandate to make the call. It's the same diagnostic discipline we apply in the first pillar of the EMS® framework — Analysis. The AS-IS map is not a decorative diagram. It's a tool that shows in black and white how many times a day the company stops at you.

The word "AS-IS" is key here. It's a map of the "as is" state, not the "as it should be" state. The temptation to immediately draw the target process is huge — but premature. First you have to see reality without embellishment. Only once we have an honest picture of how work actually flows can we consciously design the target state, which will differ from the current one at specific, justified points — rather than in an abstract "it would be nice if." On the AS-IS map, three things interest me most: where work waits (queues and bottlenecks), where work comes back (rework loops, revisions, reversed decisions), and where work passes through the founder even though it doesn't have to. These three patterns are usually seventy percent of the time and margin losses in a service business.

The AS-IS map is also the first document I show you and the team together. And it's usually a turning point — because people see the whole company at once for the first time, not just their own slice. The founder sees how many things actually stop at them. The team sees how their work connects to the work of others. From this shared map a shared language is born — and a shared agreement on what hurts most. It's the foundation for everything that comes next.

Baseline KPIs

What you don't measure, you can't improve — and worse, you can't prove that you improved it. That's why a critical part of the first three weeks is establishing a baseline, the starting point against which we'll compare results after 90 days. Without that baseline, all later discussion of the effect is just talk. Specifically, we measure:

1. Founder's time — how many hours per week you genuinely spend on operations, coordination, firefighting, and decisions that someone else could make. This is the number that usually shocks founders most.
2. Margin per project — how much actually remains on a project after accounting for the team's real time, scope creep, and revisions. Not the margin from the quote, but the actual margin.
3. Decision cycle time — how much time passes from the moment a matter requiring a decision appears to the moment the decision is actually made. And how many of those decisions have to pass through you.

These three numbers are the foundation. They're what we return to in week twelve to show a hard, measurable effect — not the impression that "things are better," but the specifics.

Why is the baseline so important in Co-Management specifically? Because the model is based on sharing success. The success fee, which I'll cover in detail later, only makes sense when both sides agree on the starting point. Without a baseline, the conversation about the effect after 90 days turns into a dispute between two impressions: I claim it was much better, you feel little has changed, and no one is right because no one has the data. The baseline defuses this conflict before it appears. That's why we measure it honestly and together, rather than in a way that looks favorable later. If the founder's time at point zero is, say, sixty hours a week, then we write down sixty — because only then will the fifteen hours regained over 90 days be something real, rather than a number stretched to fit an invoice.

Measuring these KPIs is often a sobering moment for the founder in itself. Most people running a company have no idea how much they really work until someone sits down and counts it with them, hour by hour. Same with margin per project — many founders live in the belief that projects are profitable, and after counting the team's real time, revisions, and scope creep, it turns out some were on the edge of zero or below the line. Simply seeing these numbers, even before any change, is sometimes valuable in itself — because it shows where the company is really losing money.

Typical resistance and how we defuse it

In this phase resistance appears — both on your side and on the team's side. The team often reacts with wariness: "who is this, why are they here, did they come to fire us, are they reporting to the founder." You, in turn, may have a moment of unease: "I'm paying for this, and so far they're only listening and asking questions — when do the results start?"

The worst thing an operating partner can do in the first week is start rearranging the furniture before understanding why it stands where it stands. A change introduced without a diagnosis isn't courage — it's arrogance that costs the team's trust. And without the team's trust, no new process will hold.

We defuse resistance with transparency. We tell the team straight why I'm here and what I'm not doing — I didn't come to fire anyone, I came to take the chaos off them and off the founder. To you I show that the restraint of the first weeks is an investment: every change I introduce after a good diagnosis has a many times greater chance of holding than a change introduced blindly. Trust is built here through consistency — I do exactly what I said I would, at the pace I said I would.

In my experience, the team's resistance almost never stems from an aversion to change as such. It stems from fear: that change means judgment, reduction, loss of position, or pointless extra work. When that fear is named and defused — when people see that the goal is to take the chaos off them, not to control them — resistance turns into alliance. Often the biggest skeptics of the first week become the strongest ambassadors of the new system by the eighth, because they're the ones who feel the relief most when the daily improvisation disappears. That's why I don't fight resistance with force. I listen to it, because it usually hides valuable information about what the diagnosis hasn't yet caught.

Deliverable + effect after week 3

The diagnostic phase doesn't end with an impression. It ends with something concrete you can hold in your hand. After the third week you have:

• An AS-IS process map with marked bottlenecks — a visual, black-and-white picture of how the company really works and where it gets stuck.
• Baseline KPIs — hard starting numbers: your founder's time, the real margin per project, decision cycle time. The zero point we return to in 90 days.
• A prioritized list of bottlenecks — ordered by what costs the company the most time and money, plus what can be unblocked fastest.
• Shared understanding — you, me, and the team have, for the first time, the same data-based picture of the company. No more "it seems to me."

The effect after week three is both psychological and strategic: for the first time in a long while you see your company from the outside, without sugarcoating, and you know exactly what we tackle first. It's the end of guessing. From week four we move from diagnosis to execution.

Weeks 4–8: First changes and the system

This is the phase where Co-Management shows what really sets it apart from everything else. Because now I'm not writing recommendations — I'm introducing changes. Shoulder to shoulder with your team, not remotely from a slide deck. The five weeks from the fourth to the eighth are the moment when a system starts to emerge from the chaos, and you start to feel the first real relief. It's the most intense and most satisfying stretch of the first 90 days.

Switching mode to execution

The first and most important change is in the mode of my work. Until now I listened and mapped. Now, with a hard diagnosis and the mandate of an operating partner, I move to execution. We take the list of bottlenecks from the diagnostic phase and start defusing them one by one, by priority. This isn't "advising on what you could change." These are decisions that are genuinely made and genuinely enter the company's life. I co-manage — meaning I'm responsible for the change not only being announced, but actually taking hold in daily work.

Decision authority matrix

The first thing we tackle is usually the deepest cause of you being the bottleneck: the absence of clear rules about who can make which decisions. We build a decision authority matrix — a document that states, in black and white, who can decide what, up to what amount or up to what level of risk, without asking you. This sounds trivial, yet it's one of the most powerfully effective changes in the entire implementation. Because suddenly dozens of decisions that came back to you every day have an owner at the team level. The premise is hard: if a decision can be made lower down, it should be made lower down. Your calendar starts to clear not because someone is doing your job for you, but because the company finally has clear rules of the game.

The matrix is built concretely, not as slogans. We take the real categories of decisions that came up in the interviews as ones that keep coming back to the founder: budget decisions up to a certain amount, approvals of scope changes at the client, prioritization between projects, staffing decisions, deviations from standard. For each of them we set a threshold and an owner: what the PM can approve alone, what requires consultation, what really must reach you. And here comes the hardest part — not for the team, for you. Because the authority matrix works only when the founder stops reversing decisions made in line with it. If you give someone the right to decide up to ten thousand, and then with every such decision you keep probing and correcting anyway, the team will quickly learn that the matrix is a fiction, and everything will come back to your desk. My role as an operating partner is also to keep an eye on you — so that you don't sabotage your own relief.

Over time, the matrix becomes more than a document — it becomes the language in which the company talks about decisions. Instead of "I'll ask the founder," you hear "this is the PM's call, per the matrix." Instead of the paralysis of "who's supposed to settle this," there's a clear answer. This is exactly the element of organizational architecture that, in EMS®, we call the decision authority matrix — and it's the one that translates fastest into the founder's regained time. Not flashy, but fundamental.

Communication hub

The second great bottleneck in service businesses is communication smeared across fifteen tools. Slack here, Notion there, Linear somewhere else, agreements in emails, decisions on calls no one noted down. The result: no one knows where the source of truth is, and you are the company's living index, because only you remember where things were agreed. We consolidate this into a single communication hub with clear rules: which channel for what, what is async and what is sync, where decisions are made and where they're recorded. The end of fifteen tools, each with a different version of the truth. This directly unburdens your head — you stop being the company search engine.

Consolidation doesn't mean buying yet another tool and declaring that now everything lives there. That's the most common mistake, which only adds a sixteenth tool to the fifteen existing ones. It means something harder: setting the rules and switching off what's redundant. We define where ongoing project communication takes place, where lasting knowledge lives, where tasks are, and where decisions are. We settle what is async — meaning it doesn't require an immediate response and has no right to pull anyone out of their work — and what really must be sync. And crucially: we settle that a decision not recorded in the agreed place does not exist. This removes the role of company memory from you. You stop being the person everyone messages "because you surely know where it was."

Migration usually takes a few weeks and requires consistency — because old habits come back. Someone, out of habit, writes a decision in chat instead of the agreed place; someone starts another document outside the system. In this phase I make sure the new hub genuinely becomes the single source of truth, rather than another layer on top of the chaos. The effect, once it clicks, is felt across the whole company: response time shrinks, the pre-meeting hunt for information disappears, and you stop being the communication bottleneck. It's one of those elements the team appreciates fastest, because it lifts daily frustration off everyone, not just the founder.

First SOPs

In parallel, we start building SOPs — standard operating procedures for the processes that recur most often and go wrong most often. We don't write an encyclopedia right away. We take three or four of the most painful, most frequent processes and describe them so that anyone on the team can carry them out without asking you. These are usually: onboarding a new client (so every client is brought in equally well, rather than "everyone their own way"), the status report (so the client and the team know where the project stands without involving you), and the escalation path (so it's clear what happens when something goes wrong — who escalates, when, and to whom, before it reaches your desk). These first SOPs are the foundation of a library that will grow over time and stay in the company forever.

Why these three specifically? Because they're the processes that touch most often and most painfully. Client onboarding is the first impression and the foundation of the whole partnership — when everyone does it their own way, some clients get a great start and some feel chaos from day one, which casts a shadow over the entire project. The status report is where the founder's time most often leaks away — because when there's no standard, the client writes to you directly asking "where do we stand," and instead of strategy you're answering status questions. The escalation path is a safety valve — when it's missing, every problem escalates to the founder by default, because that's the only known route. These three SOPs defuse the three most common reasons your phone rings.

What's crucial is how we write them. An SOP isn't there to look nice in the documentation — it's there so that someone new can carry out the process well, without asking. That's why we build them together with the people who actually run the process, not from behind a desk. We describe the real flow, with concrete steps, decision points, and a "definition of done" — a clear moment at which it's known the process is finished. A good SOP is one the team actually uses, because it makes their life easier, not one that sits in Notion and no one looks at. This distinction decides whether the SOP library becomes a living asset of the company or a dead document. Over these weeks we build the foundation; the rest of the library grows throughout the rest of the partnership, process by process.

Weekly sprints

All of this happens in the rhythm of weekly operational sprints. Each week has a clearly defined "what, who, by when" and — crucially — ends with a measurable result. Not "we worked on communication," but "the communication hub works, the team has migrated, three old tools have been switched off." This sprint rhythm does two things at once: it keeps the pace of change and gives you weekly, tangible proof that the company is moving forward. You get a dashboard: what's done, what's lagging, what's next. No black box.

This rhythm is more than a project management technique for the change. It's a pattern that stays in the company for good — because the same sprints in which we implement changes become the way the company will work day to day afterward. We teach the team to think in weeks: plan, deliver, summarize, correct. This builds the habit of closing things, the absence of which is one of the main causes of chaos in service businesses — where everything is "in progress," nothing is finished, and work drags on endlessly. A sprint forces the question "is this done?" every seven days, rather than "someday, when there's time."

For you, the most important thing is the founder's dashboard. It's your shift in perspective from fifteen threads in your head to a single view: what's done, what's lagging, what's next. Instead of fishing the company's status out of ten conversations and your own memory, you have it in one place, updated every week. This is the first moment you start to feel what a "command center" means — and the first moment you can start looking at the company from a distance, rather than drowning inside it. This shift from "inside the machine" mode to "above the machine" mode is one of the most important psychological breakthroughs of the first 90 days.

1-on-1 sparring + Value Creation Plan

Co-Management is not only operations. Alongside the implementations, we run a weekly strategic 1-on-1 sparring — sessions where we work on where the company should go as a business, not just how it should deliver. In this phase we start building the Value Creation Plan — a shared plan for creating the company's value over a 12–24 month horizon: goals, success metrics, a map of key growth decisions, positioning, pricing. This is the level consulting doesn't touch and an interim doesn't have in scope. An operating partner works on two tracks at once: organizing today's operations and building tomorrow's value. These sessions are also a space where I'm your sparring partner — someone who can say "no" and with whom you can talk through decisions you previously had no one to discuss them with.

This second track is what sets Co-Management apart from everything else. Because as operations start to get organized and your calendar clears, the natural question becomes: what am I actually regaining this time for? The Value Creation Plan answers that question. This isn't order for order's sake — it's order so that the company can grow in value. Do we want to raise the margin through repositioning and new pricing? Move into a higher client segment? Build a repeatable sales model instead of relying on referrals? Prepare the company for a round or an exit in two years? These are the questions I ask you in the sparring sessions — and which we seek answers to together, grounding them in the operational data we're just starting to collect.

The 1-on-1 sparring also has a value many founders don't expect at the start: it breaks the loneliness. Running a company is often a lonely game — you have no one to talk the hardest decisions through with, because the team looks at you as the person who has all the answers, and other founders are competitors or don't know your context. An operating partner in a Founder-to-Founder relationship is someone who understands the weight you carry, has a real mandate to disagree, and has no interest in nodding along. These weekly conversations are sometimes the most valuable part of the whole partnership for founders — because for the first time in a long while they're not in it alone.

Resistance and defusing it

This phase has its tensions. Change always hurts — even good change. Part of the team may defend old habits: "we've always done it this way," "what do we need these procedures for," "this will slow us down." Natural resistance appears toward the authority matrix, because some people felt comfortable when every decision came back to the founder anyway — less responsibility on their shoulders. We defuse this not by decree, but by co-creation. We build SOPs and rules together with the people who will use them, in workshops, not by fiat. When the team sees that the new processes genuinely take the chaos off them rather than adding bureaucracy, adoption grows. Your resistance in this phase is often the temptation to go back to the old way — because when someone else makes a decision differently than you would have, your hand reaches for the phone on its own. Here, too, my role is to keep an eye on you — so that you don't sabotage your own relief.

Deliverable + effect after week 8

After the eighth week the company looks and works differently. Specifically, you have:

• A working decision authority matrix — the team makes decisions at their level, dozens of matters stop coming back to you.
• One communication hub instead of fifteen tools — with clear rules and a single source of truth.
• The first working SOPs — client onboarding, status report, escalation path — carried out without your involvement.
• A weekly sprint rhythm with measurable results and a founder's dashboard.
• The first version of the Value Creation Plan — a strategic direction for 12–24 months, which we work on in the 1-on-1 sparring.

"For the first time in three years I know what my team is doing, and I don't have to be in every thread." This is the sentence we hear from founders most often precisely at this stage. It's the moment you stop being the company's only point of contact with itself — and start to breathe.

The effect after week eight is already felt in your calendar and in your head. The company starts to run on a system, not on you. The last four weeks of the first stage we devote to consolidating what we've built, measuring it, and deciding what's next.

Weeks 9–12: Stabilization, KPIs, roadmap

The last phase of the first 90 days is not about slowing down — it's about consolidating and proving. The system exists, but fresh habits are fragile. We devote these four weeks to making the changes part of the company's bloodstream, to making sure someone inside can maintain them without me, and to hard-measuring what actually changed against the week-three baseline. It's also a moment of honest decision: do we continue the partnership, or do I leave you a working system and step back.

Consolidating the system

The new system has to move from "we're implementing" mode into "this is just how we work" mode. In weeks 9–12 we finalize the SOPs that proved themselves and fix the ones that needed correction in practice. Because a good SOP isn't the one written most beautifully, but the one the team actually uses. The sprint rhythm, communication hub, and authority matrix are by now grounded enough that they start to run on inertia, rather than because someone reminds people about them. My presence becomes lighter and lighter — and that's deliberate. An operating partner who wants to be indispensable is doing their job badly. We measure ourselves by the company's success, not by the company's dependence on us.

Onboarding an internal operator / COO

The system has to have an owner inside the company. That's why in this phase we onboard an internal operator — someone from your team who takes over the daily maintenance of the system, or your COO, if you have one or are just hiring one. We hand over the full documentation: the SOP library, the command center with KPIs, the authority matrix, the meeting and communication rules. We teach them not only the "how" but also the "why" — so they can develop the system, not just reproduce it. This is the mechanism that guarantees no vendor lock-in: the company is meant to work without us, not be dependent on us. It's the philosophy we apply in every ECG format — the system stays in the company, forever, and it's yours.

Choosing the operator is an important decision we make together. Sometimes it's someone who showed up in the interviews as a natural organizer — the person the team already went to informally for decisions. Sometimes it's a freshly hired COO whose onboarding suddenly became much easier, because instead of building a system from scratch they get one that's ready, documented, and working. And sometimes, in smaller companies, you partly become that operator yourself at this stage — except you now work with a command center and clear rules, not in firefighter mode. Whoever it is, the knowledge transfer is gradual and supervised: the operator first observes, then leads under my watch, and finally leads alone. This isn't a one-off "handover of documents," but a real induction of a person into the role.

This mechanism is something that distinguishes ECG from firms whose business model relies on you never stopping paying. We build ourselves so that the company, after the first stage, is able to run without us — and if a working system is all it needs at this stage, then great. No vendor lock-in is not a slogan; it's built into the way we transfer knowledge. That's why the documentation is complete, the operator is genuinely trained, and the team's habits are grounded enough to hold on their own inertia. It's exactly the same principle we apply in EMS® implementations: what stays after us is a system that works, not a dependency that has to be fed.

Full measurement after 90 days vs baseline

Now we return to the numbers from week three and compare. This is the moment of truth for the whole first stage — hard data, not impressions:

1. Founder's time — how many hours per week you've regained versus the baseline. With the founders of service businesses we work with, the typical effect is up to +15 hours per week regained — that's genuinely two to three working days returning to strategy, sales, or life.
2. Team efficiency — an increase in throughput and pace of delivery. The average effect of ECG implementations is +17% team efficiency — with the same team, thanks to better processes and clear decision rules, rather than adding headcount.
3. Margin — an improvement in profitability after tightening scope, controlling time, and making better decisions. Across implementations we record +8.5 percentage points of EBITDA margin.
4. Decisions without the founder — the share of matters that used to come back to you and now close at the team level. This is often the most strongly felt change in daily life.

These numbers don't come from a slide deck. They come from comparing the company's real state today with its state 90 days ago — which is why the week-three baseline was so important.

Initiative roadmap for what's next

The first 90 days lay the foundation. But Co-Management is a 6–12 month partnership, so we look further. From the Value Creation Plan we derive an initiative roadmap — an ordered list of growth and optimization moves for the coming months, with priorities and metrics. It might be team capacity planning, a rebuild of pricing and positioning, further SOPs, automation and AI in operations, and in some companies preparing the investor narrative, support with a round, or M&A. The roadmap shows you in black and white that the first 90 days are only the start of value creation, not the finish.

Decision: do we continue or step back

And here we arrive at the honest conversation. After 90 days you have a working system, a measured effect, and a clear picture of what's next. We decide together: do we continue in the Co-Management formula to execute the roadmap and keep building the company's value — or do I leave you a working system and step back, because that was all the company needed at this point. Both answers are fine. Co-Management is not about tying you to us. After the first stage we do a review and honestly adjust the scope to what the company actually needs. If the system works without us and there isn't a strong enough strategic "why" to stay — we say so straight.

The fact that this decision is real and open is part of the honesty of the whole model. Many founders enter the first 90 days with a quiet fear that this is the start of an endless dependency — that soon there'll be no way out. It's exactly the opposite. The first 90 days are designed so that at their end the company can stand on its own two feet, if that's precisely what it needs. Continuation makes sense only when there's a concrete, strategic reason: a growth roadmap that requires a partner, preparation for a round or an exit, a scale of challenges that justifies continued presence at the highest level. If there's no such reason, continuation would be a cost without justification — and I'll tell you that, even if it means the end of the partnership.

In practice, this conversation rests on numbers, not emotions. We have the week-three baseline and the week-twelve measurement in front of us. You can see what changed, how strongly, and where there's still room. You can also see the initiative roadmap and what executing it would require. On this basis we make the decision like two founders looking at the same data — not like a salesperson and a client. That's the whole idea of the Founder-to-Founder relationship: we play toward the same goal even at the moment we settle whether we keep playing together.

Deliverable after week 12

After the twelfth week, regardless of the decision about continuation, the following stays in your company:

• A measured, hard effect vs baseline — regained founder's time, increased efficiency, improved margin, more decisions without you.
• A trained internal operator or COO — someone in the company who will maintain and develop the system.
• A full SOP library and process documentation — living, used, not sitting on a shelf.
• A command center with KPIs — one view of the company instead of fifteen threads in your head.
• A Value Creation Plan + initiative roadmap — a strategic direction and concrete next moves.
• A clear decision about what's next — continuation or a clean, honest handover.

The financial model — what "skin in the game" means

The whole difference of Co-Management ultimately comes down to one question: how we settle up. Because it's the financial model that decides whose interests are truly aligned with yours. A consultant invoices for recommendations. An interim invoices for time. An operating partner settles against the effect — and that's not a marketing slogan, but the structure of the agreement. "Skin in the game" means that if your company doesn't grow, I don't get paid in full. I take on the risk with you, because I believe that together we'll turn that risk into a result.

Cash + success fee

The basic Co-Management model is hybrid: part of the compensation is cash, and part is a success fee tied to the effect we generate together. The cash secures engagement and covers the real, intensive work of the operating partner from day one. The success fee is what aligns our interests — it's tied to measurable results that we define together at the start and that we can demonstrate thanks to the baseline and the measurements after 90 days. That's why the diagnostic phase and setting the KPIs are so important: without a hard starting point you can't honestly settle the effect. We set the cash-to-success-fee ratio individually, depending on the company's stage, risk profile, and growth ambitions.

Think about what this structure does to my behavior as a partner. In a purely hourly model, the longer the partnership lasts and the more hours there are, the more the provider earns — that's a built-in incentive not to hurry and for the company to stay dependent. In a model with a success fee it's the opposite: I earn more when the company reaches a real result faster, and when that result holds. I have a literal interest in the changes being lasting, rather than flashy for show. I have an interest in you regaining your time, in the margin growing, in the company becoming worth more. This isn't a matter of my character or goodwill — it's written into how we settle up. "Skin in the game" means I don't have to promise you that I'm playing toward your goal. The compensation structure does that for me.

For you, the hybrid model also means lower entry risk. You don't pay the full rate for a promise. You pay part for the real work you see every week, and I receive the larger reward only once the effect is proven in numbers. This reverses the typical asymmetry of the consulting services market, where you pay upfront and pray that it works. Here, part of my compensation is hostage to whether we deliver together. If we don't deliver — I bear the consequences alongside you. It's the most honest arrangement you can have with someone from the outside: their success is literally a function of yours.

Equity / Co-Founder for advanced cases

By default, Co-Management is a fee-based formula, without equity. But for advanced cases there's a deeper option — Co-Founder, meaning a capital entry, where part of the compensation converts into equity. This is a formula for founders looking for a partner for a truly long road: toward a significant jump in value, a financing round, or an exit, and who want the operating partner to be tied to the company as tightly as possible. We always settle this path individually — there's no template here, because every ownership structure and every ambition is different. Important: equity is an option, not a condition. You can work in full Co-Management without giving up a single percent of the company.

How we settle the effect after 90 days

The first 90 days are also a natural settlement point. With the week-three baseline and the week-twelve measurement, we have hard data: how much the founder's time dropped, how much efficiency rose, how the margin moved, how many decisions came off your plate. These are the basis on which we calibrate the success fee and on which we make the decision about continuation. After the first 3 months we do a review and adjust both the scope and the model. The whole point is transparency: at no point do you pay for fog. You pay for an effect that's visible in numbers. And if there's no effect — that's not a conversation about an invoice, but about whether this format even makes sense for your company. You'll find the full logic of the format and model on the Co-Management page.

What stays in your company after 90 days

The most important test of any partnership with ECG is the question: what stays once we're gone. Because an operating partner who makes the company dependent on them has failed. Co-Management is built so that after 90 days you're stronger — not more dependent. Here's what genuinely stays in your company, regardless of whether we continue the partnership:

• A decision authority matrix — clear rules about who decides what, and up to what level, without you. Your calendar stops being the company's bottleneck.
• An SOP library — living, used procedures for key processes: client onboarding, status report, escalations, and the others that grew along the way.
• One communication hub — the end of fifteen tools and of you as the company's living index. A single source of truth.
• A command center with KPIs — one view of the company instead of fifteen threads in your head. You know what works, what's lagging, and why.
• A trained internal operator or COO — someone in the company who will maintain and develop the system when we're gone.
• A Value Creation Plan and initiative roadmap — a strategic direction and concrete next growth moves.
• New team habits — perhaps the most valuable, because they stay for years and work even without a document.

All of this is yours, forever. No vendor lock-in — the system works without us. We don't sell you dependence on more hours of consulting. We sell you a company that works predictably and without your presence in every thread.

It's worth pausing on what these assets mean together, rather than separately. Individually, the authority matrix, the communication hub, or the SOP library are tools — useful, but not revolutionary. Together they create something the company didn't have before: the ability to operate independently of one person. That is the real product of the first 90 days. Not documents, not processes, not a dashboard — but a company that has stopped being an extension of your head and become a system capable of running on its own. This translates directly into business value: a company dependent on the founder is hard to scale, hard to sell, and fragile. A company running on a system is worth more — literally, in the eyes of an investor or a buyer.

There's also a dimension that can't be captured in a list of assets, and which founders most often point to as the most important: regained peace of mind. When the company runs on a system, you can leave for a week and everything doesn't collapse. You can focus on strategy, sales, or product instead of putting out fires. You can finally work a reasonable number of hours without the constant feeling that something is about to fall apart. This is precisely the difference between the work of a firefighter and the work of a human being — and it is, ultimately, why founders decide on Co-Management.

Before Co-Management you work like a firefighter — putting out fires, of which there'll be just as many tomorrow. After 90 days you work like a human being: the company runs on a system, decisions have owners, and you finally have space for strategy, service, and life. This isn't order for order's sake. It's regained time and regained control over your own company and your own life.

You'll see what this looks like for real founders in the case studies section. And the full philosophy of why we build ECG exactly this way you'll find on the About ECG page.

FAQ — the most common questions about the first 90 days

How does Co-Management differ from consulting?

Consulting delivers strategy in a PDF and disappears — implementation stays on your plate. Co-Management means I genuinely co-manage the company: I enter at the highest decision-making level, take responsibility for decisions, am present in board meetings, represent the board. I don't sell "strategy alone." I work shoulder to shoulder with your team, not remotely from a slide deck. And — most importantly — I settle against the effect in a hybrid model (cash + success fee), rather than for the mere fact of delivering recommendations.

How long does the partnership last?

Typically 6–12 months, sometimes longer. It's a long-term partnership, not firefighting. The first 90 days — described in this article — are the foundation: diagnosis, first changes, the system, measurement, the roadmap. After the first 3 months we do a review and adjust the scope to what the company actually needs. The first 90 days are not a rigid cage — they're a stage after which we jointly decide what the road ahead looks like.

Do I have to give up equity?

No. By default, Co-Management is a fee-based formula, without equity. You can work in full Co-Management without giving up a single percent of the company. Equity and the Co-Founder formula are an option for advanced cases — founders looking for a capital partner for the road toward a significant jump in value, a round, or an exit. We always settle this individually, and it's never a condition for starting the partnership.

What if our personalities don't fit, or I want out?

Chemistry is crucial — that's why we check it on the intro call and in the first diagnostic phase, before anything starts. After the first month, either of us can end the partnership without contractual penalties. Co-Management is a relationship at the highest level of the company, and there's no point dragging it out if there isn't mutual trust and a similar way of thinking about business. We'd rather find that out early than halfway through.

What if my team won't accept someone from the outside?

That's exactly why the first weeks are listening and observation, without introducing changes. The team sees that I first understand how they really work before I start co-deciding. We build SOPs and new rules together with the people who will use them — in workshops, not by decree from above. Adoption is high because the change is shared, not imposed. When the team sees that the new processes take the chaos off them rather than adding bureaucracy, resistance quickly melts away.

Can I keep just the system and withdraw the partnership after 90 days?

Yes — and that's entirely fine. After 90 days you have a working system, a measured effect, and a trained internal operator. If that's all the company needed at this point, I leave you all of it and step back. No vendor lock-in is the foundation of our approach — the system is meant to work without us. We make the decision about continuation together and honestly, based on whether there's a strong enough strategic "why" to go further.

How much does it cost?

The model is hybrid: part cash, part a success fee tied to the effect we generate together. The specific pricing depends on the company's stage, the scale of operations, and growth ambitions — which is why we set it after the intro call (15–30 min, free) and a preliminary diagnosis. The point of "skin in the game" is that a significant part of my compensation depends on real results that we can show in numbers thanks to the baseline from the diagnostic phase. You don't pay for fog — you pay for the effect.

Co-Management vs Interim COO — which format to choose?

Interim COO/PM is a temporary operator who takes over operations for 3–6 months, organizes the work, and steps back once the team is ready to run on its own. They work at the level of operations — a great choice when you need COO-level competence "starting tomorrow," but a full-time hire is too much or too soon. Co-Management goes deeper and longer: it's an operating partner at the highest level, for 6–12 months, working simultaneously on operations and on the company's strategic value, sharing risk and success with you. If you want to organize delivery — Interim. If it's about growing the company's value and you're looking for a partner rather than a temporary operator — Co-Management.

The first 90 days begin with a single conversation

Let's recap what the first 90 days of Co-Management are. Weeks 1–3: diagnosis and trust — the AS-IS map, baseline KPIs, a shared picture of the company without sugarcoating. Weeks 4–8: first changes and the system — the authority matrix, the communication hub, the first SOPs, the sprint rhythm, the Value Creation Plan. Weeks 9–12: stabilization, measurement, and the roadmap — consolidating the system, onboarding an internal operator, a hard effect vs baseline, the decision about what's next. Each phase ends with something you can touch. And everything we build stays in your company — yours, forever.

But let's be honest to the end. Co-Management is not for everyone. If you're a solo freelancer just building a team — it's not the right moment. If you're looking for a "cheap person to click things," rather than a strategic partner — it's not the right format. If you only want to tune up your tools, without a real change in the way you work, or you're looking for a ready-made template rather than a solution tailored to your company — we'll tell you straight on the first call. Co-Management makes sense for the founder of a growing service business who feels they're the bottleneck, has the budget for developing operations but no time to implement it — and is looking for a partner for growing the company's value, not for firefighting.

The first 90 days don't begin with a contract or a strategy. They begin with a single conversation, in which we check whether we're a fit at all. No hard pitch. If it's not the right moment or not your format — we'll tell you straight. And if it is — it might be the most important operational decision you make this year.

The rest comes down to one decision: do you want to keep carrying the company alone, or let in a partner who will take the weight of execution onto themselves, so that you can return to what really matters.

Book a free consultation — 15–30 minutes online, a concrete diagnosis with no commitment. You can also first get to know the full format on the Co-Management page, compare it with Interim COO/PM, see real founder results, or learn about the ECG philosophy.