Illustrative Case Study: A Forge Assessment Operational Turnaround

What a 30-day Forge Assessment finds, and what changes in the 90 days after it.

This is an illustrative example. It is a composite built from the patterns a Forge Assessment consistently surfaces in founder-led, unglamorous companies. It is not a specific client, and no client is named or identifiable here. The figures below are representative ranges, not a guaranteed or verified outcome. If you want to see what a real engagement would find in your business, that starts with a conversation, not a case study.

The Situation

Picture a specialty distribution business doing roughly $12 million in annual revenue, founder-led since day one. Fifteen years in, the company is profitable and has a loyal customer base. It is also stuck in a way the founder cannot quite name.

Every pricing exception, every supplier escalation, every hiring decision still routes through the founder. The team is busy, but the same problems resurface month after month: a fulfillment error here, a margin surprise there, a key employee who quietly becomes indispensable because nothing is written down. Growth has not stalled outright, but it has gotten harder to produce, and it takes more of the founder’s personal bandwidth to hold each new percentage point of it in place.

This is the pattern a fractional operating partner sees constantly: a business that outgrew the founder’s ability to be the operating system. Not a failure of effort. A structural ceiling. As described in Mechanisms Not Intentions, the business is producing exactly the results its current design produces.

The Forge Diagnosis

The engagement opens with the same structure every Forge Assessment runs on: a 30-day diagnostic window, roughly five embedded working days, fixed scope, fixed price at $6,500.

Week 1, Discovery. A deep intake session on the business model, team structure, and goals, backed by a structured pre-work questionnaire. In this illustrative case, discovery surfaces a founder who can describe every problem in the business from memory but has never seen them laid out next to each other.

Weeks 2 and 3, Diagnostic. Stakeholder interviews, a review of financial and operational data, and direct mapping of how work actually moves through the business, not how the org chart says it moves. This is where the real findings surface.

Week 4, Synthesis and readout. A prioritized findings report with root cause analysis, a 90-day action plan, and a live session walking through it together.

Finding 1: A hidden operational profit leak

The pricing and margin review turns up a familiar pattern: custom pricing exceptions and rush-order accommodations that were approved one at a time, in the moment, and never rolled back up into a picture of their cumulative cost. No single exception looks like a problem. Stacked together across a year, they represent a meaningful, quietly recurring drag on margin that nobody in the business had ever measured directly.

Finding 2: A people-versus-systems bottleneck

The diagnostic maps every major handoff in the business and finds the same story repeated: two or three tenured employees are the only ones who know how key processes actually work. Nothing is documented. When one of them is out, work does not just slow down, it stops in specific, predictable places. This is not a people problem. It is a systems problem wearing a people costume, and it connects directly to the question of whether you have a people problem or a systems problem.

Finding 3: An AI-in-ops opportunity

The AI-readiness portion of the diagnostic identifies a specific, unglamorous opportunity: a large share of order-entry and fulfillment-exception handling is manual, repetitive, and well-documented enough to be a strong automation candidate, once the underlying process is cleaned up first. The finding is not “buy an AI tool.” It is a scoped opportunity map: which repetitive decision points are safe to automate now, which ones need process and data cleanup before they are trustworthy, and what ROI bar each one would need to clear before it is worth doing. Process first, then automation. No specific platform or vendor is prescribed at this stage, because that is not what the diagnostic is for.

The Intervention: A 90-Day Operating Plan

The readout does not hand the founder a slide deck and walk away. It sets a sequenced 90-day plan in motion, with a fractional operating partner embedded to drive it:

  • Rebuild the pricing exception process so approvals route through a defined threshold instead of ad hoc judgment calls, with the cumulative cost of exceptions tracked monthly instead of invisible.
  • Document the two or three highest-risk tribal-knowledge processes first, starting with the ones a single absence could stop, and assign ownership beyond the one person who currently holds it.
  • Stand up a lightweight weekly operating cadence so decisions that used to wait for the founder get made at the right level, on a schedule, with a paper trail.
  • Pilot the highest-confidence AI-in-ops candidate from the opportunity map on a narrow, well-documented slice of order-entry work, with a defined ROI checkpoint before it scales any further.
  • Every item on that list existed as a known irritation before the assessment. What changed is that they are now sequenced, owned, and measured, instead of competing for attention inside the founder’s head.

    The Illustrative Outcome

    These figures are representative of the kind of result this type of engagement targets, not a specific verified outcome. Every business is different, and results depend on what is actually found and how much of the 90-day plan gets executed.

    • Recovered margin: engagements that address a pricing-exception leak like this one commonly target 2 to 4 points of margin recovered once exceptions are tracked and governed.
    • Decision speed: moving routine decisions off the founder’s desk and into a defined cadence typically compresses turnaround on those decisions from days to hours.
    • Founder time freed: documenting tribal-knowledge processes and delegating the decisions built on top of them tends to free somewhere in the range of 8 to 12 hours a week of founder time previously spent on operational firefighting.
    • None of that comes from a tool purchase. It comes from naming the constraints in the right order and building the mechanisms that hold once the engagement ends, the same approach described in The Unboring Business and Use AI to Help You Think, Not Think for You.

      Is This the Starting Point for Your Business?

      This composite reflects patterns seen repeatedly in founder-led companies between roughly $10 million and $15 million in revenue, but the specific findings in your business will be your own. That is the point of running the diagnostic instead of guessing.

      The Forge Assessment is a fixed-scope, fixed-price, 30-day operational diagnostic: $6,500, no hourly billing, no scope creep. You get a full written report, root cause analysis of your top constraints, and a prioritized 90-day action plan, whether or not you continue past the assessment.

      Reminder: the example above is illustrative and composite, built to show how a Forge engagement actually works. It does not describe a real, named client.

      Jason Bonito is the founder of Crucible76, a fractional operating partner practice helping founder-led businesses diagnose operational gaps and build the systems that drive growth. DATA · DECISIONS · GROWTH.

Scroll to Top