This interview is with Kamyar Shah, Fractional COO, World Consulting Group.
As a Fractional COO in management consulting, how do you describe the core problem you solve for clients today?
The core problem I solve is that a business has outgrown the way it runs, but the founder is still the system.
Companies with roughly $8 million to $50 million in revenue usually haven’t failed to grow; they have simply grown past their structure. Decisions still route to one or two people, good work depends on who happens to remember how, and the calendar fills with firefighting that never ends.
My job is to replace that dependence with structure. I install clear ownership, written standards for repeatable work, and decision rights that specify who decides before the argument starts.
When that is in place, the business stops needing a hero in the room to function. The founder gets to work on the company again instead of inside every part of it. That is the real deliverable — not a strategy deck, but a company that performs on a normal Tuesday without me.
What experiences most shaped your path from CMO/analytics work to senior operations leadership and consulting execution?
What shaped me most was seeing the same failure from two different seats. On the marketing and analytics side, I watched good campaigns die because the operation behind them could not deliver what marketing promised. The data told a clear story, but the company could not act on it because no one owned the follow-through. That taught me that growth is often an operations problem wearing a marketing costume.
Moving into operations leadership, I learned the opposite lesson too: clean execution with no view of the customer or the numbers is just efficient motion in the wrong direction.
Consulting forced both lessons together. Every engagement rewards the person who can connect the market signal to the internal system that has to answer it. My path was a slow realization that marketing, analytics, and operations are the same problem seen from different rooms, and that the value is in wiring those rooms together.
Building on that, when you enter a new engagement, what is your 30-day playbook for installing systems leadership so the business performs without you in the room?
My first 30 days are about visibility, ownership, and one proof point.
- Week one: I map how the business actually works, not the org chart but the real flow of decisions, money, and handoffs. I look for where things wait and who everything depends on.
- Week two: I assign clear owners to the work that repeats and write a simple standard for each so good outcomes stop depending on memory.
- Week three: I fix decision rights. Every recurring decision gets a named owner and a rule for when it escalates, which ends the quiet bottleneck where everything waits for the founder.
- Week four: I pick one visible problem and solve it end to end using the new structure so the team sees the system work rather than just hearing about it.
I deliberately do not try to fix everything. The goal in month one is to prove the business can move without me on at least one real thing, then widen from there.
Turning to growth, what decision rule do you rely on to choose the first growth bet under tight cash and P&L constraints?
When cash is tight, my rule is simple: pick the bet with the shortest and most certain path to cash, not the biggest possible prize. When money is scarce, survival buys you the right to make bigger bets later, so I optimize for speed and certainty first.
I ask three questions of every option:
- How quickly does this turn into cash?
- How confident am I that it will?
- Can we reverse it cheaply if we are wrong?
The bet that scores best across those three wins, even when a flashier option promises more upside. I would rather protect the ability to keep playing than chase a large return I cannot fund.
Almost always that means going deeper with customers we already have and with a channel we already understand before spending to acquire something new.
Cash constraint is not the enemy of good strategy; it is the discipline that keeps you honest about what actually works.
On execution speed, how do you structure a consulting engagement so a client sees measurable results within 90 days without burning out the team?
I structure the first ninety days around one measurable win and a sustainable pace to reach it.
At the start, I agree with the client on a single outcome that matters and can be measured, so success is not a matter of opinion at the end. Then I work backward to identify a small number of changes that will move that metric, and I deliberately leave everything else alone.
Most burnout in these engagements comes from trying to fix the whole company at once. I protect the team by sequencing the work so people carry one change at a time instead of ten. I also build the improvement into how the team already works rather than adding a parallel project on top of their day.
Momentum comes from visible progress, so I favor early, smaller wins that prove the direction before we push harder. The ninety days should end with a number that moved and a team that is less tired than when we started, not more.
At the leadership level, how do you reset decision rights and KPIs when an executive team is misaligned but needs to keep momentum?
When an executive team is misaligned, the fastest reset is to make ownership and measurement explicit. Misalignment is usually not a personality problem; it is that two capable people both believe they own the same decision, or that no one does.
I start by writing down who decides what. Every major area gets one accountable owner, with the others named as input rather than veto. That single act removes most of the friction, because the argument was never really about the topic; it was about who gets to call it.
Then I tie each owner to a small set of numbers they are genuinely responsible for, so we can talk about outcomes instead of opinions.
I keep momentum by not pausing the business to do this. We set the decision rights and KPIs in motion and correct them as real decisions come up, rather than waiting for a perfect operating model. Clarity about who owns what lets a team disagree and still move.
On capability building, how do you design a one-year roadmap that blends hiring, contracting, and upskilling to close critical ops gaps?
I build a one-year capability plan by first separating what is core from what is temporary.
- Core capabilities, the ones the business needs permanently and that define how it competes, I hire for; you should own what you cannot afford to lose.
- Work that is real but spiky or specialized, I contract, so I get the skill without carrying fixed cost through the slow periods.
- Capability that already exists in the building but is underdeveloped, I close with upskilling, which is usually faster and cheaper than people expect.
The roadmap sequences these actions against the gaps that hurt most first. I do not try to fill every gap at once, because a team can only absorb so much change in a year. The honest version of this plan names what we will deliberately not fix yet. A good capability roadmap is as much about restraint and order as it is about ambition.
Across revenue operations, how do you align marketing, sales, and CRM workflows to improve CAC-to-LTV within one quarter?
Improving CAC-to-LTV within a quarter usually comes from fixing the handoffs, not from spending more.
In most companies, marketing, sales, and the CRM each tell a slightly different story, so leads leak through the gaps between them. I start by agreeing on one shared definition of a good lead and one shared view of the funnel, so everyone is measuring the same thing.
Then I look for the biggest leak, which is often not at the top of the funnel. It is frequently follow-up that never happens or customers who were won and then quietly neglected.
Retention and expansion move lifetime value faster than new acquisition, so I look there before touching ad spend. On the acquisition side, I shift budget toward the channels the clean data actually credits, rather than the ones people assume are working.
Within a quarter, the goal is a tighter, shared system where a lead does not fall through the cracks between three tools that were never talking to each other.
Finally, given your interests in economic empowerment, education, health, and the environment, how do you embed social-impact metrics into growth plans so they accelerate rather than slow execution?
I treat social impact the same way I treat any other outcome that matters. If it is real, it gets measured and owned, not left as a statement of values.
The mistake I see is bolting impact on as a separate report that competes with the business for attention, which is what makes it feel like a tax on execution. Instead, I look for the places where impact and performance point in the same direction.
Economic empowerment through how you hire and develop people, for example, tends to improve retention and capability at the same time. Where the two genuinely conflict, I make the tradeoff explicit and let leadership decide intentionally rather than by accident.
The key is to pick a small number of impact measures that leaders actually watch alongside the financial ones, so they inform decisions in real time. Impact accelerates growth when it is built into the same scoreboard, and slows it when it lives on a separate page that nobody opens.
Thanks for sharing your knowledge and expertise. Is there anything else you'd like to add?
The through line in all of this is a simple belief: structure is a form of respect. Most companies treat process as bureaucracy, but unclear expectations are what actually let people down — they set a team up to fail and then blame them for it. Nearly every problem I am hired to solve traces back to a business that grew faster than the clarity it provided its people.
My work is not about adding control; it is about making the business legible so people can spend their energy on the work instead of decoding what management wants. That is the quiet advantage.
A calmer company usually outperforms a frantic one because its people are not exhausted by confusion. If there is one thing I would want a reader to take away, it is that clarity is the kindest and most practical thing an operator can give a team.