About $268,000 a year of work is done at standard rates and not recovered in fee, and it follows who scoped the engagement.

Realization on comparable fixed-fee work varies thirteen points by the partner who scoped it, because the adjustments that make the difference are applied only when Ellen scopes.

Across the last twelve months the firm realized 92.7 percent of standard-rate value on $6.3M of fixed-fee work. Ellen Marchetti's engagements realized at 97 percent, Marcus Delgado's at 92, and Rob Askew's at 85. Had Marcus and Rob's fixed-fee revenue realized at Ellen's rate, the firm would have billed about $268,000 more for the same hours.

The cause is specific. All three partners scope from the same proposal template, the same rate card, and the same assumptions tab in the pricing workbook. Ellen then adjusts for what the tab cannot see: whether the sponsor is a repeat client, whether the portfolio company closes its books inside ten days, whether the engagement lands before or after the close, which engagement manager is free, and how likely a founder-led company is to widen the scope. Her adjustments are sound and mostly consistent. They exist nowhere except in the proposals she personally scopes, so the other two partners scope without them, and the realization follows.

Most of proposal development is in good order, and it matters to say so. The template is a competent document, the rate card is reissued every January, the win rate is ordinary for sponsor-referred work and does not vary in a way that means anything, and BigTime records the hours cleanly. The problem is confined to how the scoping sources are kept and what sits on top of them.

What we recommend

Write down the scoping rules with an owner against each one, mark which copy of each source is current, and put a proposal drafter in front of the partners that drafts from those sources and cites every figure and every scope sentence. Pilot it on the five-week operational diagnostic, where the gap is measured and the engagements repeat. Of the $268,000, we would expect to reach $140,000 to $190,000 inside twelve months, and we would agree the measures up front so you can judge it in your own numbers.

We sat in on seven live scoping calls and then reconciled what we saw against twelve months of records.

Interviews about a workflow return the procedure. We wanted proposal development as it is done today, so the two and a half weeks were spent alongside the three partners through seven scoping calls and the proposals that followed them: the request in proposals@, the call with the sponsor, the search for comparable past proposals, the pricing, the scope and assumptions, the partner review, and the send. Three of the seven calls were Ellen's, two were Marcus's, and two were Rob's. Where what we saw differed from what the template and the tab said, we recorded both.

The observed calls tell you how and why. They do not tell you how much, so the second half of the diagnosis reconciled them against your records: 61 proposals in HubSpot and the Proposals library for the trailing twelve months, realization by engagement out of BigTime for the 26 that were won, the proposal template in its three copies, the pricing workbook and its assumptions tab, the rate card in force and the one on SharePoint, and the SOWs in DocuSign.

What we could measure, and what we could not

• Measured from your recordsProposals submitted and won by partner, turnaround from request to proposal out, realization by engagement and by the partner who scoped it, and hours charged against hours planned on completed diagnostics.
• Measured by observation, and therefore a sampleHours per proposal and how those hours are spent. Seven proposals is enough to show the shape and not enough to be precise. The hours figures in this document carry that caveat wherever they appear.
• Could not be measuredWhy a proposal was lost. HubSpot has a closed-lost stage and no reason against it, and neither our observation nor your records can reconstruct one. This is the largest hole in the picture and it is worth closing whatever else you decide.

One engagement scoped before the diagnosis began, ENG-2634 at Tolland Wire Products, was in its second week as this document was written and appears again in the analysis as the live instance of the pattern.

A proposal takes 5.5 business days against the five the sponsors usually ask for, and the two slowest steps are the two that wait on information.

The sequence itself is sound and all three partners run it the same way. What varies is how long each step takes, and the variation concentrates in the two steps that depend on information held somewhere else: finding the comparable past proposals and case examples, which are in the Proposals library, the Engagements library, and the partners' own OneDrive folders, and confirming which rates and scoping assumptions are current, which means checking the January email against the SharePoint copy and the tab.

Fourteen of the 61 proposals went out after the date the sponsor asked for. That is 23 percent of everything the firm proposed last year. What happens to those fourteen is examined on its own sheet, because the relationship between a late proposal and a lost one is easy to over-read.

Everything a proposal needs is written down, and the four sources every proposal depends on have no marked current version, no owner, and no review date.

Whitlow Ferris Partners is not a firm that keeps its method in somebody's head. The proposal template, the pricing workbook, the rate card, the case one-pagers, and eleven years of readout decks are all written down, in the ordinary ways firms write them down, and most of it is good. What is missing is custody: which copy is current, who owns it, when it was last checked, and where the reasoning behind a scoping choice is recorded.

The pattern decides what the build has to do first. The two maintained sources are the two that a piece of software already keeps for you. The four with no custody are the four that live in documents and habits, and those are the ones every proposal turns on.

These are the numbers any later work gets judged against.

Captured before anything changes, so that improvement is measurable in your records and not in our claims. All four are drawn from the trailing twelve months.

The four measures, as of today

• Turnaround: 5.5 business days, medianFrom the sponsor's request to the proposal out. The sponsors' usual ask is five. 14 of 61 went out after the date asked for.
• Hours per proposal: 14, medianFrom the observed sample. 4.2 of them finding material and confirming what is current.
• Realization on fixed-fee work: 92.7 percent, revenue-weightedEllen 97 percent, Marcus 92, Rob 85, on $2.9M, $2.0M, and $1.4M of fixed-fee revenue. Examined on the next two sheets.
• Win rate: 42.6 percent26 of 61. Recorded as a baseline and not as a finding.

The realization spread survives when you control for the engagement mix, which is what makes it a real finding.

Realization does differ by partner, and on its own that proves little, because the three of you sell different work. Rob scopes more diligence-phase and first-engagement work, Marcus carries the sponsor pricing conversations, and engagement shapes realize differently for reasons that have nothing to do with who scoped them. So the raw comparison is the beginning of the analysis and not the end of it.

To settle it we isolated one product all three of you sell and scope the same way: the five-week operational diagnostic, priced at the same standard fee from the same rate card. Twenty-one of them completed in the last twelve months. On that like-for-like set the spread does not disappear. It is 13 points of realization, and 85 hours per engagement between Ellen's diagnostics and Rob's, on the same product at the same fee.

Two things follow from the like-for-like cut. The first is that the gap is not experience: Rob co-founded the firm and has scoped diagnostics for eleven years, and his run 85 hours over Ellen's on the same product. The second is that hours track the same order as realization. Ellen's eight diagnostics ran 535 hours against 520 planned, Marcus's seven ran 560, and Rob's six ran 620. The fee is the same on all of them, so every hour over plan comes straight out of realization.

What Ellen does differently is on the record in her proposals and nowhere else. Where a portfolio company does not close its books inside ten business days, her scope includes a data-readiness week and the fee includes it. Where the company is founder-led, her assumptions and exclusions are tighter. The other two partners scope from the tab, which knows about neither.

The hours over plan are data cleanup nobody scoped, and scope that widened at founder-led companies.

We read the engagement files and the BigTime hours by week on the 21 comparable diagnostics. The overrun sits in two places. The first is the opening weeks, where the team cleans up the client's data before the diagnostic can start, at companies that close their books slowly and were scoped as though they did not. The second is the later weeks, at founder-led companies where the owner added questions mid-engagement and nobody had written an exclusion that let the partner say no.

The same pattern is visible in a live engagement. ENG-2634 at Tolland Wire Products was scoped by Rob from the assumptions tab with no data-readiness week, at the standard fee of $161,000. Tolland closes its books in about twenty days. At week two the engagement is eleven percent over budget on hours, all of it in data cleanup, on a fixed fee.

Late proposals win less often, and we do not count that as money, because the direction of cause is not established.

Fourteen of the 61 proposals went out after the date the sponsor asked for. Those fourteen won at a much lower rate than the rest, and it is tempting to price the difference. We have not, because proposals are often late for the same reasons that make them hard to win: a complicated scope, a sponsor who asked for it in two days, a first engagement with a new sponsor where the comparable material takes longer to find. The relationship is real. What it is worth cannot be read from these records.

So turnaround stays out of the value on the next sheet and goes on the list of things the build should make measurable. If the median falls from 5.5 days to the five the sponsors ask for, and the late count falls with it, the win rate on those proposals will show whether lateness itself was costing wins, in your own records and without anyone having to argue about it.

The gap is $268,000 a year, and we would expect $140,000 to $190,000 of it to be reachable inside twelve months.

Marcus realized 92 percent on $2.0M of fixed-fee work and Rob 85 percent on $1.4M. Ellen realized 97 percent. Bringing both to her rate is five points on $2.0M and twelve points on $1.4M, which is $100,000 plus $168,000, or $268,000 a year of standard-rate value worked and not recovered in fee. Closing the whole distance is not a realistic target, because some of what Ellen does is eleven years of pattern recognition that no written rule will fully capture, and because a rule written in the first quarter takes the rest of the year to reach every proposal.

So the honest number is a share of that gap. What share is a judgment, and we cannot measure it for you. Below is the arithmetic with the judgment left in your hands. Change the assumption and the number moves.

What is deliberately not counted

Turnaround, for the reason on the previous sheet. The 255 hours a year of finding material is also not counted as money. Freed partner hours only become fee if they go to more proposals, more billable work, or the sponsor relationships, and which of those happens is your decision, not an outcome we can book on your behalf.

Two other measurements from the diagnosis are recorded and not valued, because they belong to other workflows. The last six hires reached sixty percent utilization at a median of 7.5 months, against the four to five the partners expected. Nine of the 26 readouts in the past year had three or more slides changed inside the last forty-eight hours before they were presented. Both are evidence for later phases of the build and neither is in the $268,000.

Of the fifteen tasks in a proposal, eight go to software and four do not move at all.

This is the part of the diagnosis that decides what gets built. We broke proposal development into its tasks and put each one where it is handled best, on the evidence of what we watched. Some tasks want software. Some want a person with a better view of the firm. Some want a process fix and no technology whatsoever. Some are right as they are, and the correct recommendation for those is to leave them alone.

Write the firm's scoping rules down with owners, build the proposal drafter on them, and let the measures decide whether it widens.

The build has two parts, and the order matters. The first is the memory: the firm's rules written down once, each with an owner and the reason beside it, and the records the rules apply to. Ten rules came out of the diagnosis, and the four that proposals turn on are the scoping rule (SC-4, Ellen), the fee rule (FR-2, Ellen with Marcus on sponsor pricing), the staffing rule (ST-5, Priya), and the sponsor preferences (SP-2, Marcus). Beside them sit the kept records: the account summaries, the engagement records, the case examples, the rate card in force, and the playbook.

The second part is the proposal drafter, which reads from that memory and nothing else. It assembles the draft proposal and SOW with every figure and every scope sentence citing its basis, runs the plain-code checks (rates against RC-2026, weeks against SC-4, the fee against the ninety-percent floor, the discount against FR-2), lists what it could not settle, and hands the draft to the partner. The partner scopes, approves, and sends. The five-week operational diagnostic is the right pilot because it is the product where the gap is measured, the engagements repeat, and the baseline already exists.

What comes after, if the measures say so

The same memory can carry other readers, and none of them is in this recommendation. A deliverable assembler that builds a readout skeleton from the playbook module and the engagement's own extracts. A desk that answers a new consultant's questions from the playbook and the approved rules, and says so when something is not documented. A Monday brief with utilization, pipeline, realization, unbilled work, and receivables, every number linked to its BigTime or HubSpot record. A debrief line that reads the final readout and the debrief call and queues the changes to Priya. Each would be its own scoped piece, agreed on its own evidence, after the drafter has earned it.

Five positions are fixed before any build starts, and four risks are named so they can be watched.

A diagnosis that only says what could be automated is half a diagnosis. These are the limits we would hold to, and we would rather you hold us to them in writing.

• The scope and the fee stay with the partnerNo exception, no threshold at which this relaxes, and no measured improvement that would justify revisiting it. A proposal is a commitment the firm makes to a sponsor, and a partner makes it.
• No proposal leaves without a named partner approving and sending itThe software drafts and checks. It never sends. The approval is recorded against the proposal record with the name and the time.
• The ninety-percent floor is a stop, not a warningA draft priced below ninety percent of standard-rate value cannot be sent. It goes to an exception queue and needs Ellen's written approval, recorded with the reason (FR-2).
• Nothing is drafted from an unapproved sourceEllen approves the scoping rule and the fee rule, Marcus the sponsor preferences, Priya the staffing rule, before anything reads from them. If the owner has not approved it, the software does not use it.
• Nothing leaves your Microsoft 365 tenantEverything runs inside the firm's own environment under the firm's own permissions. No sponsor material, no client data, no fee history moves to an outside service.

The risks we would watch

• Some of Ellen's adjustments will not reduce to a ruleThe close cycle and the repeat-sponsor discount are rules with numbers in them. Her read of how likely a founder is to widen the scope is a judgment, and writing it down as a rule would make it wrong in the cases that need it most. The build writes down what is a rule, records what is a judgment as a question the drafter asks the partner, and does not pretend the second is the first.
• A sponsor may want the partner's voice, not a templateDan Kowalczyk has worked with Ellen for three years and reads her proposals as hers. The draft is a starting point the partner rewrites where it matters, and the pilot measures whether the sponsor notices. If a sponsor does, the partner writes more of it by hand and the software keeps the arithmetic.
• The rate card changes in JanuaryRC-2026 is in force until the new card is issued. If the memory still says RC-2026 in February, every draft is wrong by the increase. The rate card entry gets a review date of the first business day of January and an owner, and the drafter refuses to price from a card past its review date.
• The temptation to let the drafter sendOnce the drafts are reliable, sending them without a partner reading them will look like a way to save an hour. It is the position above, and it does not relax with a measured result, because the hour saved is the hour in which the partner scopes the engagement.

There is a general position underneath these. Your partners hold the proposal; software does tasks inside it. However much of the drafting the software takes on, every task rolls up to a person who owns the result, and the system is designed so that person can always see what the software did and why.

The first ninety days have four owners inside the firm, three measures, and a gate at the end.

The first three weeks are yours and need nothing from us. The rest runs as a weekly working session with a short written note after each one, and everything built stays in your tenant and belongs to you at every point.

Who owns what at Whitlow Ferris Partners

• Ellen MarchettiNames the current proposal template and retires the other two copies. Sits with us while the scoping rule (SC-4) and the fee rule (FR-2) are written down with their reasons, about two hours a week for four weeks. Approves both before the drafter reads from them. Approves every fee under the ninety-percent floor.
• Marcus DelgadoWrites down what is known about each repeat sponsor's preferences (SP-2), starting with Larkspur Ridge. Owns sponsor pricing inside FR-2 and the carve-out pricing gap, which stays visible as a known gap until he records a position.
• Priya RamanOwns the staffing rule (ST-5) and the current versions of the deliverable templates and the playbook. Decides which of the two PB-100 copies is the approved one.
• Carla StimsonAdds the who-scoped field in BigTime and reports realization by engagement and by partner monthly under the definitions in UT-1. Puts the rate card in force where proposals are written and holds its review date. Adds the loss reason to the HubSpot closed-lost stage.

What is measured, from your own records

• Realization by engagement and by who scoped itFrom BigTime, monthly. Today 97 percent, 92, and 85 by partner on fixed-fee work; 13 points apart on comparable diagnostics. The measure that carries the value, read on diagnostics scoped after the pilot begins and completed.
• Hours per proposalToday 14 at the median, with 4.2 of them finding material and confirming what is current. Logged per proposal in BigTime from the first week, so the next figure is a record and not a sample.
• Turnaround from request to proposal outToday 5.5 business days at the median against the five the sponsors ask for, with 14 of 61 late. Logged from the arrival date in proposals@.

Agree this scope and its measures, or stop with this document. At the ninety-day gate the three measures decide what happens next, and stopping is one of the four available answers. Everything built to that point runs in your tenant, belongs to you, and comes with a written handover. We do not resell anything and take nothing from any tool we recommend; our interest is in the measures moving, because that is what would earn the next piece of work.