Ermetis

A sample built on fictional content. Holcombe Mechanical is not a real company and this reflects no real engagement.

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

Holcombe Mechanical is a fictional $16M commercial mechanical contractor. It runs Microsoft 365, BuildOps for field service, and QuickBooks for the books, and its pricing knowledge has 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. Margin on comparable rooftop retrofits varied 4.5 points between the three estimators. The blended gap is 1.8 points on $8.6M of project revenue, about $155,000 a year, and $85,000 to $110,000 of that looks recoverable in the first twelve months. About 28 percent of estimating time went to chasing current vendor pricing and working out which version of the workbook to use.

12:04The drafter watches this shared inbox from inside Holcombe’s Microsoft 365 tenant. It picked up the RFQ, read the attachment, pulled the Store 118 history from BuildOps, and started drafting. Nobody did anything yet; Doug has not even seen the email.

12:29The draft never goes to the customer. It lands in the channel the estimators already watch, twenty-seven minutes after Dana’s email, and the button opens the review screen. Doug picks it up after lunch.

HQQuoting review · BEX-118 +
‹ › ↻🔒holcombemech.sharepoint.com/sites/quoting/review/BEX-118
SharePointSearch this site
Holcombe Quoting

Bexley Foods · Store 118 · RTU replacement

Draftwaiting on estimator review · assembled 12:29
LineAmountSource, click to open
(2) 15-ton packaged rooftop units, gas/electric$47,300
Curb adapters and sheet metal transitions$6,180
Crane, two night picks$4,400
Controls tie-in and startup$3,850
Demo and disposal$2,760
Labor, 148 hours, journeyman and apprentice blend$16,730
Grocery rooftop adder, labor +12%$2,010
Bid total · margin 24.1%$83,230

Checks · plain code, run when the draft was assembled

✓ PassedThe math: quantities, extensions, and the total re-computed. Not a model’s opinion.
✓ PassedCompleteness against the proposal checklist on SharePoint: permits noted, exclusions stated, night-work terms in.
✓ PassedMargin: 24.1% against the 22% floor in the margin memo.
⚑ FlagOne vendor price is 61 days old. The coil-coating option on the alternate exceeds the intake rule’s 45-day threshold. Queued: reconfirm with Mansfield Supply.
⚑ FlagThe repair option lands at 17.8% margin, below the floor. The comparison Bexley asked for needs an estimator’s decision.

12:29This is the page the Teams button opens, on Holcombe’s own SharePoint. Click any source to see exactly where a number came from. Nothing ships from this screen; the draft waits for Doug.

HQQuoting review · BEX-118 +
‹ › ↻🔒holcombemech.sharepoint.com/sites/quoting/review/BEX-118
SharePointSearch this site
Holcombe Quoting

Bexley Foods · Store 118 · RTU replacement

In reviewDoug Wetzel · 1:42
Doug’s edit, on the crane line

Two picks changed to three. His note, saved with the line: “Store won’t clear the east lot for staging. Third pick, or we pay the crane to wait.” New total $85,430, margin 23.6%, still over the floor; the math re-ran on save.

FLAG 1 · RESOLVEDMansfield reconfirmed the coil-coating price this afternoon; the intake path now holds a quote dated today.
FLAG 2 · DECIDEDDoug presents replace only, with a note to Dana on why repair does not pencil. His decision is recorded with the bid.
The edit does not vanish into this one bid. The staging constraint is recorded against Bexley Store 118 in the memory, so the next draft for this site starts from three picks, and rule DW-7 stays exactly as Doug approved it.
✓ Approved by Doug Wetzel, 1:58. The Word proposal filled from the template on SharePoint and went to Dana on Holcombe letterhead. The bid, the edit, and both flag decisions are logged.

1:42Same screen, Doug’s half of it. He edits, decides the two flags, and approves. The system drafted; the person judged. That order never reverses.

2:03This is what Dana receives: a clean proposal on Holcombe letterhead, filled from the template they already use, sent five minutes after Doug approved. The citations, the flags, and the log never leave Holcombe’s side; the customer just gets a fast, consistent, correct bid.

Under the hood· what ran, and where everything lives · drawn by Ermetis, not an app─  ▢  ✕
WHERE IT PULLS FROM SharePointapproved workbook · rate sheets BuildOpsservice history · via its API Vendor intake folderdated quote PDFs QuickBooksjob-cost actuals · exports HOLCOMBE’S MICROSOFT 365 TENANT Outlook · the RFQ arrivesshared inbox watched, attachment read The drafter agentreads with Holcombe’s permissions Plain-code checksmath · thresholds · checklist Teams · Quoting channeldraft posted, flags called out The review screendraft · citations · flags · log Doug approvesjudgment stays with the person The proposal, in Wordto Dana, from their template what Doug edits goes back into the memory

What runs it

The drafter is an agent configured in Holcombe’s own Microsoft 365 tenant. It reads the workbook, the intake folder, and BuildOps under the permissions Holcombe already set. Nothing about this workflow leaves their environment.
The model drafts; code checks. Language models assemble the draft and the citations. The math, the age thresholds, and the checklist run as plain code, so a check either passes or a person looks at it.

Where the knowledge lives

The approved workbook is one Excel file on SharePoint with an owner, a version, and Doug’s pricing rules written next to the numbers they modify. The two personal copies that used to circulate were reconciled into it.
The vendor intake path is a folder plus a rule: one current quote per line, dated, replaced on arrival. The 45-day flag threshold is part of the rule.

What gets recorded

Every draft, edit, flag decision, and approval is logged, with who and when. Doug’s crane edit was saved against the site, so the memory got better because the quote went through.

 This is the whole machine. Four places the knowledge already lives, one agent inside the tenant, checks that are code, a person with the last word, and edits that flow back in.

What this took, in this fictional world

The draft was ready twenty-seven minutes after Dana’s email. Doug’s review took about twenty minutes, most of it on the repair-versus-replace decision, which is exactly where his time belongs. Before the system, a bid like this took him most of two days to turn around.

The same workflow, elsewhere

At a distributor, this is the quote desk drafting from pricing tiers and availability. At a professional-services firm, it is proposals drafted from past engagements and approved rates. The pattern is the same: drafted from what the company knows, every number showing its source, a person approving.