The first time I walked into a boardroom at RHI Magnesita, I was wearing my best suit and carrying a laptop that was two models behind the executives’ machines. The room held twelve people from the client side. I was one person from mine. The power imbalance was visible in the furniture: they had leather chairs. I had the guest seat.
Over the next fifteen years of consulting, I worked with companies that had revenue in the billions while my own revenue was measured in thousands. The size difference should have been disqualifying. It wasn’t — because the value I offered existed in a space that large companies struggle to fill on their own.
Why Giants Hire Tiny Firms
Large companies have strategy departments, innovation teams, and consulting relationships with firms whose names you’d recognize. They don’t lack resources or expertise. What they lack is perspective.
When you’ve been inside a large organization for years, you develop institutional blindness. The processes that waste time are invisible because they’ve always been there. The market shifts that threaten the business are obscured by internal politics. The simple solutions that a fresh pair of eyes can see in a week take internal teams months to reach because they’re too close to the problem.
That’s the niche. Not scale. Not brand. Not headcount. Perspective.
The subtraction audit emerged from this work. Large companies don’t need more ideas — they need someone to tell them which ideas to kill. A tiny firm with a clear framework can do this more effectively than a large firm with a large team, because the large firm has incentives to expand scope (more scope = more fees) while the tiny firm has incentives to clarify scope (clear scope = efficient delivery).
The Credibility Challenge
The first question every large client asks, implicitly or explicitly: why should we trust a company your size with a project this important?
My answer evolved over fifteen years:
Year 1-3: Case studies. I had very few, so each one had to be detailed, specific, and demonstrably valuable. One excellent case study beats ten mediocre ones. The automation project that saved 40% of a factory’s time became my lead case study because the numbers were specific and verifiable.
Year 3-7: Methodology. Instead of selling “consulting,” I sold a specific framework. Not “I’ll come in and help with innovation” — “I’ll run a subtraction audit that identifies your highest-impact opportunities in four weeks.” The methodology was the product. My size was irrelevant because the methodology was the value.
Year 7-15: Reputation. Enough engagements produced enough results to create a referral network. Large clients came through introductions from other large clients. The network did the credibility work before I walked into the room.
The Operational Reality
Working with a FTSE 250 company as a three-person firm (at my consulting practice’s largest) requires specific operational discipline:
Pricing for value, not time. Large companies have procurement departments that will try to negotiate your hourly rate. The moment you accept hourly pricing, you’re competing against large firms with lower effective rates due to junior-staff leverage. Instead, price for the project outcome. “This engagement produces X deliverable within Y weeks for Z fee.” The value conversation is about the deliverable, not the hours.
Scope control. The project that nearly bankrupted us was an enterprise engagement that expanded beyond control. Enterprise clients will always have more problems than your engagement covers. The scope document is your protection. Define what’s included and what isn’t before a single hour of work begins.
Communication frequency. Large companies are used to regular status updates, documented meeting notes, and structured reporting. A tiny firm that communicates like a startup — informal, sporadic, casual — creates anxiety in an enterprise client. I sent weekly status updates every Friday, regardless of whether there was significant news. The consistency built trust.
Decision-making patience. Enterprise decisions move slowly. Approvals require multiple stakeholders. Budgets require procurement review. Contracts require legal review. A project that starts in February might not have a signed contract until June. The cash flow implications are significant — the profit first system helps manage the gap between engagement start and payment receipt.
The Size Advantage
Being small wasn’t just manageable — it was an advantage in specific ways:
Speed of response. When the client’s strategy shifted mid-engagement, I could adjust within 48 hours. A large consulting firm would need internal approvals, team reassignment, and scope renegotiation. My velocity was a direct competitive advantage.
Direct access to the expert. In a large firm, the senior partner sells the engagement and junior consultants deliver it. In my firm, the person in the meeting was the same person doing the work. Clients consistently cited this as a primary reason for choosing a small provider.
Honest advice. A large firm has incentives to expand scope, extend timelines, and recommend further engagements. A small firm that values its reputation has incentives to deliver results and move on. I regularly told clients “you don’t need more consulting on this — you have what you need to execute.” That honesty built trust that produced referrals worth more than any extended engagement.
The Mistakes I Made With Enterprise Clients
Not every engagement went smoothly. The patterns of failure were as instructive as the patterns of success.
Mistake one: Underestimating the decision chain. In a small company, the person you pitch is the person who decides. In a FTSE 250 company, the person you pitch may need four additional approvals before a purchase order is generated. I lost two early enterprise opportunities because I assumed verbal enthusiasm from a department head meant a signed contract was imminent. It wasn’t. The department head needed budget approval from finance, legal review from compliance, and a procurement process that took eight weeks. By the time the process completed, the champion who loved my proposal had moved to a different project.
The fix: early in any enterprise conversation, ask “what does the approval process look like for an engagement like this?” Map the decision chain before you invest time in the pitch. Adjust your timeline expectations accordingly, and build the cash reserve to survive the gap between verbal commitment and signed contract.
Mistake two: Over-delivering without recognition. In small client relationships, over-delivery builds loyalty directly — the client sees it, appreciates it, and rewards it with repeat business. In enterprise relationships, over-delivery without formal documentation goes unnoticed. The project sponsor knows you went above and beyond. The procurement team sees a standard engagement. The budget committee sees a line item. Your extra effort is invisible to the people who control the renewal.
The fix: document every deliverable that exceeds the original scope. Not to nickel-and-dime — but to make the value visible. “This deliverable was not included in our original scope but was provided as part of our commitment to your success.” This documentation builds the case for scope expansion in future engagements and ensures the value is visible beyond your immediate contact.
Mistake three: Treating the enterprise like a monolith. A company with 5,000 employees isn’t one client. It’s dozens of potential clients, each with different needs, budgets, and decision-makers. My first enterprise engagement produced one project. My second — once I understood the internal structure — produced three projects across two departments, because I actively explored adjacent opportunities within the same organization.
The Long Game With Enterprise
The 5-year perspective applies to enterprise relationships more than any other type. The first engagement is an audition. The second is confirmation. The third is a relationship. By the fourth, you’re a trusted partner, and the sales process that took six months for the first project takes two weeks for the fifth.
My longest enterprise relationship lasted seven years. The first year produced one project worth EUR 15,000. The seventh year produced three projects worth a combined EUR 120,000. The growth wasn’t because my rates increased dramatically. It was because trust accumulated, referrals multiplied, and my understanding of their business deepened to the point where I could identify and propose opportunities they hadn’t yet recognized.
The tiny firm serving the industrial giant isn’t an anomaly. It’s a model that works — when the value is specific, the methodology is clear, and the delivery is impeccable. Size isn’t the variable that matters. Value is.
