Restoration wins on documentation, estimate accuracy, and how fast the office closes what the field already saw. GroundTruth reads email, meetings, and chat for aging homeowner asks, stalled job handoffs, and crews booked twice. Cited or silent.
Maple Ave homeowner asked for a dry-out update Thursday. Three days later, no owner reply. Crew finished Friday.
SOURCE · homeowner mail Mar 5 · job chat Mar 6where job and homeowner promises actually live
we deploy to you, so we never hold your data
no source pointer, no claim. That is the reason to believe.
A status or scope question sits open while the crew moves to the next loss. Age and thread trail, before the online review writes itself.
Moisture readings and photos left the truck. Estimating or billing has not closed the file. Two desks, one job, no owner.
TPA or carrier program changed documentation requirements. One branch never got the thread. The job still runs the old checklist.
Both sites claim Friday morning. Coverage is a calendar fact, not a hope in the morning standup.
Scope grew on site. The office estimate did not move. Carrier and homeowner each hold a different truth.
Open jobs, carrier promises, and change orders still resolve only through a PM whose last day is on the calendar.
Reply gaps stretch. The word "still" shows up. A dry-out or invoice ask sits open before the program call gets cold.
Late updates or incomplete packages keep recurring on one program account. Count and status against the record.
Now Monday opens with open job and homeowner gaps, not with hope that someone else caught them.
Homeowner on Maple Ave asked for a dry-out update Thursday. Three days, no owner reply. Crew finished Friday.
SOURCE · homeowner mail Mar 5 · job chat Mar 6 · no outbound sinceField uploaded moisture logs Tuesday. Estimating still shows pending. Carrier desk followed up Thursday.
SOURCE · field upload Mar 3 · estimate queue Mar 4 · carrier mail Mar 5Friday: two Category 2 water jobs both list the same crew lead 7 a.m. to noon. No backup named.
SOURCE · schedule board Mar 6 · crew calendar Mar 6Program photo standard changed in HQ chat. West branch absent from the last three process threads.
SOURCE · HQ chat Mar 5 · West branch absent from program mailsNames and digest items are invented samples so you can see the shape of the report. Not a client result.
Microsoft 365, Google Workspace, or mixed. Email, meeting transcripts, and chat. Read-only. Mail keeps flowing as it does today.
It stands up in your environment. We never hold your data. Your record stays yours.
Aging homeowner and carrier asks, field-to-office stalls, program rules that missed a branch, double-booked crews, estimate drift, departing PMs. Cited or silent on every claim.
An owner note every Monday, plus recaps to meeting organizers. A human still sends every outbound.
Meeting organizers get a recap minutes after the call ends: highlights, minutes, and an action table with assigner, assignee, and due date, drawn from the transcript. A conflict check flags heated moments so the room can reset. Actions that never find an owner surface in Monday's digest. Optional meeting notes stay tied to that meeting only, which everyone in the room already witnessed.
The useful default at this size is the team, the job, and the change. Individual-level reporting is available only where leadership approves it in writing during setup. HR, legal, and compensation mail is excluded at the source.
A weekly note goes only to the person, then is deleted on the server. It is not an input to reviews. Managers cannot open it. Leadership sees anonymous aggregates only. Capacity building, not a manager dashboard.
Priced by who GroundTruth reads, not by headcount. You set the ingestion scope at setup; the invoice follows it.
Microsoft 365, Google Workspace, or mixed. Legacy mail or transcript systems add wiring.
Delegated push updates are standard. IT-coordinated pull in your change window adds coordination.
Which sources we wire at setup, and how many systems sit behind them.
Charged only for people whose mail and chat GroundTruth may read. Scope is your call, in writing, at setup.
The digest lands on the owner's desk whether scope is 10 people or 100. The floor reflects that.
Optional. Weekly note to the person only, deleted on the server. No manager view. Pausable anytime.
Start with leadership and one department; expand scope when it earns it.
For comparison: a fractional chief of staff runs $4,000 to $8,000 per month and still is not in every customer or project thread.
You decide who sits in ingestion scope, and that list is the invoice. Expanding coverage to another department or office is a scope conversation, not a renegotiation. HR, legal, and compensation mail stay excluded at the source regardless of scope. GroundTruth deploys in your environment, on your Azure tenant; we never hold your data and your record stays yours. You bring your own LLM API keys: model usage bills directly from your provider to you, at their rates. We never mark up a token.