Ermetis

A sample built on fictional content. Whitlow Ferris Partners is not a real firm and this reflects no real engagement.

A proposal request comes in. Watch it become a sent proposal.

Whitlow Ferris Partners is a fictional management consulting firm working for private-equity portfolio companies. It runs Microsoft 365, BigTime for time and billing, HubSpot for the pipeline, and QuickBooks Online for the books, and its method and its positions on scoping and fees have been organized and approved. The drafter works inside those systems. Each step below is the screen a real person would be looking at.

What it is worth

The diagnosis measured this workflow. On 21 comparable five-week diagnostics, realization ran 97, 93, and 84 percent across the three partners, a 13-point spread. The gap is $268,000 a year of standard-rate value the firm worked and did not recover, and $140,000 to $190,000 of that looks recoverable in the first twelve months. About thirty percent of proposal time went to finding comparable past proposals and case examples and confirming which rates and scoping assumptions were current.

Tue 9:10Megan wrote to Marcus, the partner she knows, and copied proposals@. The drafter watches that shared mailbox from inside WFP’s Microsoft 365 tenant. It picked up the request, read the deal summary and the org chart, pulled the Redfield account summary (ACC-REDF) and the two comparable engagements, and started drafting. Nobody at WFP has done anything yet; Ellen has not seen the email.

Tue 11:40The draft never goes to the sponsor. It lands in the channel the partners already watch, two and a half hours after Megan’s email, and the button opens the review page. Ellen picks it up the next morning.

WFProposal review · P-2026-041 +
‹ › ↻🔒whitlowferris.sharepoint.com/sites/proposals/review/P-2026-041
SharePointSearch this site
WFP Proposals

Redfield Growth Partners · Coastal Fleet Services · 100-day plan

Draftwaiting on partner review · assembled Tue 11:40
Fee lineWeeksAmountSource, click to open
Engagement partner, Marcus Delgado, two days a week2$64,000
Principal, Greg Hollis, finance-function workstream, two days a week2$48,000
Engagement manager5$90,000
Senior consultant5$70,000
Consultant5$55,000
Second consultant, weeks three to five3$33,000
Fixed fee · five weeks · no discount, new sponsor22$360,000

Scope · each sentence with the entries it came from

Team shape. An engagement partner and a principal at two days a week, an engagement manager, a senior consultant, and a consultant for the five weeks, with a second consultant from week three. The partner and the principal are named because the sponsor is buying them; the other seats are roles until Priya Raman confirms the names at review, her call under ST-5.
Scope boundary. The plan names the initiatives, the owners, and the milestones. Implementation is scoped separately.

Checks · plain code, run when the draft was assembled

✓ PassedRates: all six lines checked against RC-2026 weekly rates, and weeks times rate and the total re-computed in code.
✓ PassedScope weeks against SC-4: five weeks holds. The data-readiness trigger applies and is flagged below.
✓ PassedDiscount logic against FR-2: new sponsor, no discount, fee at full standard-rate value, so no written approval is needed.
✓ PassedTemplate: PT-7 is the current proposal template and SOW; no other version was read.
⚑ FlagNo repeat-sponsor discount applies. Redfield Growth Partners is a new sponsor and this is the first engagement (ACC-REDF). FR-2 gives ten percent off a diagnostic to repeat sponsors only. A partner confirms.
⚑ FlagData-readiness week proposed. The deal summary says Coastal Fleet closes its books in about eighteen days. SC-4 adds a week when the close runs past ten business days. Proposed: Greg Hollis one week ($24,000) and the senior consultant one week ($14,000), $38,000. A partner decides.

Tue 11:40This is the page the Teams button opens, on WFP’s own SharePoint. Any source opens with a click and shows where a fee line or a scope sentence came from. Nothing goes to Redfield from this screen; the draft waits for a partner.

WFProposal review · P-2026-041 +
‹ › ↻🔒whitlowferris.sharepoint.com/sites/proposals/review/P-2026-041
SharePointSearch this site
WFP Proposals

Redfield Growth Partners · Coastal Fleet Services · 100-day plan

In reviewEllen Marchetti · Wed 8:30
Ellen’s addition, the data-readiness week

Greg Hollis one week ($24,000) and the senior consultant one week ($14,000), $38,000, added as its own fee line ahead of the five weeks of plan design. Her reason, saved with the line: “Coastal Fleet closes in eighteen days and three of the branches are still on the acquired companies’ ledgers. The finance baseline won’t hold if we start before the data is clean, and that’s where the overruns have come from.” New total $398,000; the rates re-ran against RC-2026 on save.

Ellen’s edit, the scope-boundary sentence

The PT-7 sentence replaced with her own: “The plan names each initiative, its owner, and its first-hundred-day milestones. Delivery of the initiatives, interim roles, and PMO support are scoped separately, at the sponsor’s request, once the plan is approved.” This was the v7-EM language from her OneDrive copy; it is saved to PT-7 as the approved template language. Ellen owns PT-7, so the edit saves directly; the same edit from another partner would have queued to her.

FLAG 1 · CONFIRMEDNo discount. Redfield is a new sponsor on its first engagement, and the fee holds at standard rates under FR-2. Her note to Marcus is recorded with the proposal.
FLAG 2 · ACCEPTEDThe data-readiness week goes in as proposed, shown as its own line in the fee summary so the sponsor sees what it is for.
The edits do not vanish into this one proposal. The scope-boundary sentence is now the approved language in PT-7, so every draft after this one starts from it, and the data-readiness reason sits with P-2026-041 in the memory, where the next 100-day plan draft for a company with a slow close can cite it.
✓ Reviewed and approved by Ellen Marchetti, Wed 8:52. The deck filled from PT-7 and the SOW from its Word template, and Marcus Delgado sent both to Megan at 9:15. The draft, both edits, and both flag decisions are logged.

Wed 8:30Same page, Ellen’s half of it. She adds the week, tightens one sentence, decides the two flags, and approves. The software drafted and the partner decided.

Wed 9:15This is what Megan receives: the proposal deck and the SOW, filled from the templates the firm already uses, sent by Marcus Delgado, who holds the relationship. The citations, the flags, and the log stay on WFP’s side.

Under the hood· what ran, and where everything lives · drawn by Ermetis, not an app─  ▢  ✕
WHERE IT PULLS FROM SharePoint · WFP KnowledgePT-7 · PB-100 v4 · RC-2026 · the rules SharePoint · Proposalspast proposals · the P-2026-041 record SharePoint · EngagementsENG-2611 · ENG-2598 · case examples HubSpotthe sponsor record · via its API WFP’S MICROSOFT 365 TENANT Outlook · the request arrivesshared inbox watched, attachments read The proposal drafterreads with WFP’s permissions Plain-code checksrates · weeks · discount · template Teams · Proposals channeldraft posted, flags called out The review pagedraft · citations · flags · log Ellen approvesjudgment stays with the partner The deck and the SOWto Megan, from PT-7 what Ellen edits goes back into the memory

What runs it

The drafter is software configured in WFP’s own Microsoft 365 tenant. It reads the Knowledge, Proposals, and Engagements libraries and the HubSpot sponsor record under the permissions the firm already set. Nothing about this workflow leaves their environment.
The model drafts; code checks. Language models assemble the scope, the fee lines, and the citations. The rates against RC-2026, the weeks against SC-4, the discount logic against FR-2, and the template version run as plain code, so a check either passes or a partner looks at it.

Where the knowledge lives

The scoping and fee rules are written entries with an owner and a reason next to each: SC-4 for scoping, with the data-readiness trigger, and FR-2 for fees and discounts, both owned by Ellen Marchetti.
The rate card RC-2026 is one sheet on SharePoint marked as current. The RC-2024 copy that sat beside it is retired, and the January email is no longer where the rates live.
The proposal template PT-7 is one template, the deck and the SOW together. The v6 copy one principal still used is retired, and Ellen’s scope-boundary sentence went into it on Wednesday from this review.

What gets recorded

Every draft, edit, flag decision, and approval is logged, with who and when. Ellen’s data-readiness reason is saved with P-2026-041, so the memory got better because the proposal went through.

 This is the whole machine. Four places the firm’s knowledge already lives, one piece of software inside the tenant, checks that are code, a partner with the last word, and edits that flow back in.

What this took, in this fictional world

The draft was ready two and a half hours after Megan’s email. Ellen’s review the next morning took about twenty minutes, most of it on the data-readiness decision, and the proposal went out on Wednesday against a Friday ask. Before the drafter, the firm’s median was fourteen hours of partner and manager time per proposal and five and a half business days from the request to the proposal out.

The same workflow, elsewhere

At a law firm, this is the engagement letter drafted from the approved rate schedule and comparable past matters. At an accounting firm, it is the advisory proposal drafted from the fee schedule and the last few engagements of the same kind. The pattern is the same: drafted from what the firm has already approved, every figure showing its source, a partner approving.