AI for consulting firms should start with the engagement archive, not a proposal bot. In one management consulting deployment, a 140-person firm recovered a published 1,200 hours per quarter and $480,000 a year, at 129% Year 1 ROI and a 5.3-month payback, against $210,000 of Year 1 investment. The sequence was knowledge search, then proposals, time capture, deliverable formatting, and the remaining internal work. The failure mode is a draft generator with nothing sourced behind it: partners rewrite every page. The workflow menu lives on the professional services page.
Rank the leak before you pick a tool
Pull one quarter of where senior time actually goes before anyone picks a product. The published assessment covered a firm of 95 consultants and 45 operations staff, $32 million in annual revenue, growing 20% year over year, with overhead scaling in a straight line with headcount. Consultants billing $250–$400 an hour were spending 35% of their time on work that did not require a consultant. The case states that slice as roughly $4.8 million a year in wasted billable capacity.
The same assessment put the admin leaks on a clock:
| Leak | Hours / quarter | What the time was |
|---|---|---|
| Proposal generation | 320 | 4–8 hours each, across 40+ proposals |
| Knowledge retrieval | 280 | SharePoint, Outlook, Teams, and a partner's memory |
| Deliverable formatting | 240 | Structure and presentation, not the analysis |
| Internal operations | 200 | Work that grew with the firm, not with the advice |
| Listed total | 1,040 | Before the hours nobody entered |
A second $4.8 million figure appears in the same case, and it is a different pool. Memory-based Friday time entry left 15–20% of billable time unrecorded. On $32 million of revenue, the case calls that roughly $4.8 million in potential unbilled work. Wasted capacity and unrecorded billings are both real. Adding the two figures double-counts the story. Keep them in separate lines when you build the business case.
Under the hours sat the file pile: 8 years of deliverables, proposals, and methodologies across 47,000 SharePoint files, no naming convention, no tags, search limited to the filename. That pile is why the archive is the first system. A proposal assistant that cannot retrieve a prior engagement writes a confident draft a partner will throw out. You have paid for a rewrite.
The archive comes before the proposal
The readiness assessment ran two weeks and cost $12,000: 15 interviews across partners, consultants, and operations, plus shadowing a full proposal and a delivery cycle. It set the sequence before any build. Knowledge base first. Then proposals. Then time entry. Then deliverables. Then operational automation. Reverse that order and the later tools have nothing true to stand on.
What phase 1 actually shipped
Phase 1 ran weeks 1–8. It ingested 12,000 of 47,000 files — the case calls that slice the most relevant — into vector search over the archive. Access followed practice area and client authorization. The same index served a Slack bot and a web page. A consultant asks in Slack and gets a sourced answer in 4 seconds, with links to the underlying deliverables. Embedding every draft and personal note brings the obsolete file back with the same confidence as the one a partner still stands behind.
Proposals after the index exists
The proposal assistant came after search worked. It generates a full draft from a structured brief. Creation time fell from 4–8 hours to 45 minutes of review. The 45 minutes is the product. The draft is the input to a person who still owns the recommendation, the pricing, and the scope. In the first full quarter with everything live, that assistant recovered 260 hours, worth $78,000 at the case's $300 an hour average.
If retrieval is wrong, those 45 minutes become a rewrite and the 260 hours disappear. Gate the draft on sources the reviewer can open. A brief that cites three prior engagements is a proposal. A brief that cites none is a writing exercise.
Phase 2, weeks 9–14, added report and presentation drafts: structure, formatting, and data presentation, with the consultant supplying the analysis. Phase 3, weeks 15–24, covered client intake, monthly partnership reporting, and compliance documentation. The program ran six months across three phases. Those week numbers are that deployment's schedule.
Time capture is the cash line
Search returns hours to the day. Time capture returns money the firm already earned and failed to bill. The assistant runs every morning. It suggests entries from calendar, email, document, and channel activity. A person approves with one tap. It does not invent a code and post it.
Capture moved from 80–85% to 94%. The case values that lift at $95,000 in the measured quarter. The managing partner estimates $380,000 a year in additional billings. Keep that yearly figure labeled as the partner's estimate. The measured number is the quarter.
The failure mode is a suggestion people accept without reading. Then Friday is reconstructed wrong, and the invoice is wrong. Keep the approval tap, because the entry hits a bill. If reviewers change most suggestions over a month, fix the activity feed — calendar titles that say "busy," mail that is not client work — before you rewrite the prompt.
Fund the archive first when it is the larger hour pile. Here, retrieval was 280 hours a quarter and proposals were 320. Time capture showed up as recovered billings, separate from those hours. A firm already capturing in the mid-90s has little to gain from the morning suggestion.
The payback math operators should copy
Read the first full quarter with all three phases live, then read the headline. The case publishes these line items for that quarter:
| Workflow | Hours | Value |
|---|---|---|
| Knowledge base | 280 | $84,000 at a $300/hour average |
| Proposal assistant | 260 | $78,000 |
| Deliverable tools | 240 | $72,000 |
| Operational automation | 200 | $36,000 at a $45/hour ops rate |
| Monthly reporting | 40 | $12,000 |
| Time capture | — | $95,000 from the capture-rate lift |
| Quarter, as itemized | 1,020+ | $377,000 |
The published headline metric on the same proof is 1,200 hours per quarter and $480,000 a year, with a 5.3-month payback and 129% Year 1 ROI. The itemized quarter is 1,020+ hours and $377,000. Both figures are in the case study. This post does not explain the difference, and it does not annualize the quarter by multiplying $377,000 by four. The case annualizes, with continued optimization, to $480,000 a year.
Year 1 investment was $210,000: a $12,000 assessment, a $156,000 build, and $4,500 a month to operate. That operate line is inside the published band for Managed AI Operations, $3,000–$20,000 a month. It is one engagement's retainer, not a price-list SKU.
- The AI Transformation Sprint is $25,000 for two weeks: workflow map, ROI model, build-versus-buy, and a scoped pilot that credits toward a build.
- Gigabit Agents start from $8,000 flat per agent for one production workflow.
- A multi-workflow year — assessment, several builds, and an operate retainer — is the $80,000–$500,000 Year 1 range. This proof landed at $210,000, inside that range, because it was three phases.
An $8,000 agent is the right purchase when one workflow is already scoped and the source of truth exists. It is the wrong purchase for 47,000 unsorted files plus proposals plus time capture. Buy the Sprint when you cannot yet rank the leaks. Buy the agent when the rank is done and one path is ready to ship.
What to do this week
1. Export one quarter of proposals. Count them, the hours on each, and where the precedent lives. 2. Time five retrievals. If finding a prior deliverable takes longer than writing the paragraph, the archive is the first build. 3. Pull last quarter's capture rate. Near 80–85%, keep the unrecorded slice as its own dollar line. Leave it off the wasted-capacity figure. 4. Write the order: index the files you would quote, then the draft that cites them, then morning suggestions a person approves. 5. Price the diagnostic. The $25,000, 2-week AI Transformation Sprint ranks the leaks and scopes phase 1. Vertical patterns are on the professional services page. The phase result is the consulting proof.
The deployment left the consultants in place. They open an engagement by asking what the firm has already done, and the largest gains showed up with the people who used to wait on someone else's memory. The published return is 1,200 hours a quarter, $480,000 a year, payback in 5.3 months, on $210,000 in Year 1. If proposals still start from a blank page, book the $25,000 Sprint. If one workflow is already scored, a Gigabit Agent from $8,000 is the smaller fixed purchase.
