--- title: Susco GroundTruth Flier Master --- Susco GroundTruth Flier Master SUSCO GROUNDTRUTH · FLIER MASTER 26-49 51-100 101+ Show all SUSCO *Building systems to unleash human potential* **GROUNDTRUTH**For owners of 26-49 person companies # Who owns the promise you made the client on Tuesday? Six days later, still nobody. At 40 people, you hired managers so you would not live in every thread. That works until a customer ask loses its owner, a handoff stalls between desks, or a file due Friday never appears. GroundTruth reads email, meetings, and chat for those gaps. **Sources attached, or quiet.** The Q3 deliverable was promised to the client in last Tuesday's review. Six days later, no owner and no file. SOURCE · client review notes Mar 3 · Priya Shah follow-up mail to the client Mar 3, 9:14 a.m. **Email, meetings, chat** where customer and project promises actually live **In your environment** we deploy to you, so we never hold your data **Sources attached, or quiet** no source pointer, no claim. That is the reason to believe. What owners at this size stop missing **Every open yes that still has no name** Someone said yes in a meeting you did not need to attend. Now you see the commitments that are still nobody's, before the customer asks again. **The decision that flipped in chat** The official plan did not move. Two reps still quote the old number. You get the decision with the source, or nothing. **The handoff where both desks wait** Your first real departments, and the first stalls between them. Each side thinks the other has it. You see the open loop against your own baseline. **The same service miss, still open** The same customer or internal pain in nine threads. Escalation stopped. The miss did not. Count, status, and the trail back to the record. **A customer promise aging with no owner** Reply gaps stretch. The word "still" shows up. An invoicing or delivery ask sits open. At this size, one lost account is a bad year. **The complaint that returns every month** Customer or vendor, recurring without an owner or a fix. Tracked by count and status so "we handled that" has to survive the record. **Open work that would walk out with an inbox** At 40 people, one departure can take a whole function's memory. Open customer and project threads stay on a list, not in someone's head. **Meetings that leave with owners, not hope** Organizers get a recap minutes after each call: actions with owners and due dates, plus a conflict check. You get the pattern of open work, not more seat time. Now Monday opens with the open gaps, not with hope that someone else caught them. A Monday that protects delivery and accounts Leadership · Week of March 9 · Sources attached, or quiet · Open gaps The Q3 deliverable was promised to the client in last Tuesday's review. Six days later, no owner and no file. SOURCE · client review notes Mar 3 · Priya Shah follow-up mail to the client Mar 3, 9:14 a.m. The onboarding discount was reversed in Tuesday's meeting. Two reps quoted the old number this week. SOURCE · sales meeting transcript Mar 3 · sent mail Mar 5 and Mar 6 A key account's invoicing ask is four months old with no owner. Reply gap moved from 1.1 days to 3.6 days. SOURCE · 12 threads, Feb 2 to Mar 8 · ask raised Dec 9, recurred Jan, Feb, Mar Names and digest items are invented samples so you can see the shape of the report. Not a client result. Page 1 of 3Susco Solutions, LLC · Harvey, LA · GroundTruth drafts. A person decides. Sources attached, or quiet. SUSCO *Building systems to unleash human potential* **GROUNDTRUTH**For owners of 26-49 person companies How the gaps close 01**Connect the stack** Microsoft 365, Google Workspace, or mixed. Email, meeting transcripts, and chat. Read-only. Mail keeps flowing as it does today. 02**Deploy in your house** It stands up in your environment. We never hold your data. Your record stays yours. 03**Watch for delivery gaps** Unowned commitments, flipped decisions, stalled handoffs, aging customer asks, departing context. Sources attached, or quiet on every claim. 04**Send a Monday digest** An owner note every Monday, plus recaps to meeting organizers. A human still sends every outbound. Every internal meeting, minuted before lunch 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. Reporting altitude and follow-through notes **You set the reporting altitude** 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. **Optional follow-through notes stay with the owner** An optional weekly note can list open client and vendor commitments still with that owner. It is not a review input and not a manager dashboard. Decide together on the call Which sources first: email, meeting transcripts, chat.  ·  Which core stack we wire; that shapes the install scope.  ·  Who sits in ingestion scope.  ·  Whether optional client and vendor follow-through notes are offered. Honest limits **Setup depends on the stack you run.** Install fees follow Microsoft 365, Google Workspace, or a mix. No price on this page. **Sources attached, or quiet.** No source pointer means no claim. Extraction is a net, not a court record. **Humans send everything.** GroundTruth drafts. A person decides what leaves the building. **This expands capacity.** People keep the work. The system finds open promises the record already holds. Page 2 of 3Susco Solutions, LLC · Harvey, LA · What your company already promised. Sources attached, or quiet. SUSCO *Building systems to unleash human potential* **GROUNDTRUTH**For owners of 26-49 person companies # What it costs. One number, not per seat. You pay for who GroundTruth reads, not for headcount. You set the ingestion scope at setup. The invoice follows that list. Install: \[scoped on the call\] scoped by complexity **Your stack**Email · meetings · chat Microsoft 365, Google Workspace, or mixed. Legacy mail or transcript systems add wiring. **Deployment model**Push or pull Delegated push updates are standard. IT-coordinated pull in your change window adds coordination. **Sources ingested**What turns on Which sources we wire at setup, and how many systems sit behind them. Recurring: per person in ingestion scope **Ingested person**\[scoped on the call\] Charged only for people whose mail and chat GroundTruth may read. Scope is your call, in writing, at setup. **Platform minimum**\[scoped on the call\] The digest lands on the owner's desk whether scope is 10 people or 100. The floor reflects that. **Follow-through notes**+\[scoped on the call\] / mo Optional. Weekly note to the person only, deleted on the server. No manager view. Pausable anytime. What a typical deal looks like ScenarioInstallMonthlyYear 1Year 2+ Leadership team only (10 in scope, single stack)\[scoped on the call\]\[scoped on the call\]\[scoped on the call\]\[scoped on the call\] Whole company in scope (30 people, single stack)\[scoped on the call\]\[scoped on the call\]\[scoped on the call\]\[scoped on the call\] Whole company, with follow-through notes (45 in scope, 15 opted in)\[scoped on the call\]\[scoped on the call\]\[scoped on the call\]\[scoped on the call\] Under 37 people in scope, the \[scoped on the call\] floor is your number: whole-company coverage without per-seat math. For comparison: a fractional chief of staff runs \[scoped on the call\] per month and still is not in every customer or project thread. Scope is the price. Scope is the promise. 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. **Book a stack and scope call.** Walk away with your install number, who GroundTruth reads first, and what your Monday digest would look like. **504-264-9343**suscosolutions.com Page 3 of 3Susco Solutions, LLC · Harvey, LA · GroundTruth drafts. A person decides. SUSCO *Building systems to unleash human potential* **GROUNDTRUTH**For owners and CEOs # Which handoff stalled delivery this week? You find out after the customer does. Past a few dozen people, excellence breaks in the handoffs: departments, a second office, desks that each hold part of the customer or the job. Commitments, delays, and open asks live in email, meetings, and chat. GroundTruth reads that record so Monday closes gaps instead of discovering them late. **Sources attached, or quiet.** The client moved Friday cutoff in email. West Office was not on the thread. Field work still runs the old rule. SOURCE · client mail Mar 6, 4:22 p.m. · West Office absent from the last three cutoff mails **Email, meetings, chat** where delivery and account follow-through actually live **In your environment** we deploy to you, so we never hold your data **Sources attached, or quiet** no source pointer, no claim. That is the reason to believe. What mid-market owners stop missing **Cross-team reply time that slows delivery** How long Finance waits on Operations, against your own baseline. Not a peer scoreboard. The stall is now a pattern you can act on. **A change that never reached the delivering team** HQ trained. The other office never got the thread. Coverage is a fact of who was on the mail, not a survey after the fact. **The same service miss, still open** The same handoff pain in nine threads. Escalation stopped. The miss did not. Recurring themes, each pointed back to a source. **Two desks, both waiting** Finance thinks Operations has it. Operations thinks Finance does. Promises between departments, with an owner or a flag. **The decision that flipped in chat** The official plan did not move. You get the decision from mail, meetings, and chat with a source, or silence. **Open work tied to a departing lead** Customer and project threads that still resolve only through someone leaving. The work stays on a list, not walking out with the inbox. **A customer promise aging with no owner** Reply gaps stretch. The word "still" shows up. Flagged with the thread trail before the renewal call gets awkward. **The complaint that returns every month** Customer or vendor, recurring without an owner or a fix. Tracked by count and status so "we handled that" has to survive the record. Now Monday briefs you on stalled handoffs and aging accounts before the customer does. A Monday that protects delivery and accounts North Branch Leadership · Week of March 9 · Sources attached, or quiet · Open gaps The Q3 deliverable was promised to the client in last Tuesday's review. Six days later, no owner and no file. SOURCE · client review notes Mar 3 · Priya Shah follow-up mail to the client Mar 3, 9:14 a.m. The client moved Friday cutoff in email. West Office was not on the thread. Field work still runs the old rule. SOURCE · client mail Mar 6, 4:22 p.m. · West Office absent from the last three cutoff mails Three teams described the same handoff stall this month. Delivery is waiting on the other desk. SOURCE · nine threads, Feb 10 to Mar 7 · theme: "waiting on the other desk" A key account's invoicing ask is four months old with no owner. Reply gap moved from 1.1 days to 3.6 days. SOURCE · 12 threads, Feb 2 to Mar 8 · ask raised Dec 9, recurred Jan, Feb, Mar Names and digest items are invented samples so you can see the shape of the report. Not a client result. Page 1 of 3Susco Solutions, LLC · Harvey, LA · GroundTruth drafts. A person decides. Sources attached, or quiet. SUSCO *Building systems to unleash human potential* **GROUNDTRUTH**For owners and CEOs How the gaps close 01**Connect the stack** Microsoft 365, Google Workspace, or mixed. Email, meeting transcripts, and chat. Read-only. Mail keeps flowing as it does today. 02**Deploy in your house** It stands up in your environment. We never hold your data. Department mail stays yours. 03**Watch the delivery gaps** Reply-time stalls, left-out offices, aging customer asks, recurring service misses, departing leads. Sources attached, or quiet on every claim. 04**Send a Monday digest** An owner note plus team notes for the people who run the desks. A human still sends every outbound. Every internal meeting, minuted before lunch 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. Reporting altitude and follow-through notes **You set the reporting altitude** The useful default at this size is the team, the department, the job, the change, or the office. Individual-level reporting is available only where leadership approves it in writing during setup. HR, legal, and compensation mail is excluded at the source. It is never read and filtered later. **Optional follow-through notes stay with the owner** An optional weekly note can list open client and vendor commitments still with that owner. It is not a review input and not a manager dashboard. Decide together on the call Which sources first: email, meeting transcripts, chat.  ·  Which core stack we wire; that shapes the install scope.  ·  Who sits in ingestion scope across departments and offices.  ·  Team and department digest vs named-person view, and whether optional client and vendor follow-through notes are offered. Honest limits **Setup depends on the stack you run.** Install fees follow Microsoft 365, Google Workspace, or a mix. No price on this page. **Sources attached, or quiet.** No source pointer means no claim. Extraction is a net, not a court record. **Humans send everything.** GroundTruth drafts. A person decides what leaves the building. **This expands capacity.** People keep the work. The system finds open promises the departments already wrote down. Page 2 of 3Susco Solutions, LLC · Harvey, LA · What your company already promised. Sources attached, or quiet. SUSCO *Building systems to unleash human potential* **GROUNDTRUTH**For owners and CEOs # What it costs. Priced by who it reads. You pay for who GroundTruth reads, not for headcount. You set the ingestion scope at setup. The invoice follows that list. Install: \[scoped on the call\] scoped by complexity **Your stack**Email · meetings · chat Microsoft 365, Google Workspace, or mixed. Legacy mail or transcript systems add wiring. **Deployment model**Push or pull Delegated push updates are standard. IT-coordinated pull in your change window adds coordination. **Sources ingested**What turns on Which sources we wire at setup, and how many systems sit behind them. Recurring: per person in ingestion scope **Ingested person**\[scoped on the call\] Charged only for people whose mail and chat GroundTruth may read. Scope is your call, in writing, at setup. **Platform minimum**\[scoped on the call\] The digest lands on the owner's desk whether scope is 10 people or 100. The floor reflects that. **Follow-through notes**+\[scoped on the call\] / mo Optional. Weekly note to the person only, deleted on the server. No manager view. Pausable anytime. What a typical deal looks like ScenarioInstallMonthlyYear 1Year 2+ Leadership team + one department (25 in scope, single stack)\[scoped on the call\]\[scoped on the call\]\[scoped on the call\]\[scoped on the call\] Two offices, mixed stack (60 in scope, 20 coached)\[scoped on the call\]\[scoped on the call\]\[scoped on the call\]\[scoped on the call\] Full rollout, high complexity (100 in scope, 40 coached)\[scoped on the call\]\[scoped on the call\]\[scoped on the call\]\[scoped on the call\] Start with leadership and one department; expand scope when it earns it. For comparison: a fractional chief of staff runs \[scoped on the call\] per month and still is not in every customer or project thread. Scope is the price. Scope is the promise. 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. **Book a stack and scope call.** Walk away with your install number, who GroundTruth reads first, and what your Monday digest would look like. **504-264-9343**suscosolutions.com Page 3 of 3Susco Solutions, LLC · Harvey, LA · GroundTruth drafts. A person decides. SUSCO *Building systems to unleash human potential* **GROUNDTRUTH**For CEOs of 100+ person companies # Which division still runs last week's rule? You hear it in the QBR, not on Monday. Divisions, multiple offices, and two layers between leadership and the work. Customer promises, project handoffs, and open commitments live in email, meetings, and chat. GroundTruth reads that record and briefs you every Monday on what still needs an owner. **Sources attached, or quiet.** The carrier moved Friday cutoff in email. The West division was not on the thread. Their field teams still run the old rule. SOURCE · carrier mail Mar 6, 4:22 p.m. · West division absent from the last three cutoff mails **Email, meetings, chat** delivery and account follow-through across every division and office **In your environment** your tenant, your keys, your record. We never hold your data **Sources attached, or quiet** no source pointer, no claim. That is the reason to believe. What CEOs at 100+ stop missing **A division left off the change** HQ decided. One office got the thread, another did not. Coverage is a fact of who was on the mail, not a survey after the fact. **Cross-department stalls that slow delivery** Reply time against your own baseline, not a peer scoreboard. The stall between divisions shows up before anyone names it. **The same service miss, still open** The same handoff pain in nine threads across two departments. It stopped climbing the ladder long before it stopped costing money. **The decision that flipped in chat** The official plan did not move. You get the decision from mail, meetings, and chat with a source, or silence. **Open work that still resolves through one departing inbox** At this size, someone consequential is always leaving. Open customer and project threads become a handover list, not a hope. **A customer promise aging with no owner** Reply gaps stretch. Escalations rise a level. Flagged with the thread trail before the QBR surprise. **The complaint that returns every month** Customer or vendor, recurring without an owner or a fix, tracked by count and status across every department so "we handled that" has to survive the record. **Optional follow-through notes people will actually use** Weekly notes can list open client and vendor commitments still with that owner, then delete after delivery. No manager view, no review input, no admin override. Leadership digests stay on client and vendor gaps. At your size, that guarantee is what makes the notes adoptable. Now Monday closes open gaps across divisions before the QBR surfaces them. A Monday that protects delivery and accounts Executive Leadership · Week of March 9 · Sources attached, or quiet · Open gaps The carrier moved Friday cutoff in email. The West division was not on the thread. Their field teams still run the old rule. SOURCE · carrier mail Mar 6, 4:22 p.m. · West division absent from the last three cutoff mails Fourteen open threads and three commitments still resolve only through a director whose last day is March 27. SOURCE · thread ownership map Mar 7 · resignation mail Feb 28 A key account's invoicing ask is four months old with no owner. Reply gap moved from 1.1 days to 3.6 days. SOURCE · 12 threads, Feb 2 to Mar 8 · ask raised Dec 9, recurred Jan, Feb, Mar Names and digest items are invented samples so you can see the shape of the report. Not a client result. Page 1 of 3Susco Solutions, LLC · Harvey, LA · GroundTruth drafts. A person decides. Sources attached, or quiet. SUSCO *Building systems to unleash human potential* **GROUNDTRUTH**For CEOs of 100+ person companies Built to pass your IT review GroundTruth deploys in your own Azure tenant, wired read-only into email, meeting transcripts, and chat. Nothing changes about how mail flows. HR, legal, and compensation mail are excluded at the source and never read. You bring your own LLM API keys, so model usage bills directly from your provider at their rates; we never mark up a token. Updates ship push or pull, on your change window, tested in rings before they reach you. How the gaps close 01**Connect the stack** Microsoft 365, Google Workspace, or mixed. Email, meeting transcripts, and chat. Read-only. 02**Deploy in your house** Your tenant, your keys, your record. We never hold your data. 03**Watch the delivery gaps** Left-out offices, stalled cross-department handoffs, recurring service misses, aging accounts, departing context. Sources attached, or quiet on every claim. 04**Brief the leadership** A CEO note every Monday, division notes for the people who run them, recaps to meeting organizers. A human still sends every outbound. Every internal meeting, minuted before lunch Meeting organizers get a recap minutes after the call ends: highlights, minutes, an action table with assigner, assignee, and due date, and a conflict check 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. Decide together on the call Which sources first: email, meeting transcripts, chat.  ·  Which core stack we wire; that shapes the install scope.  ·  Who sits in ingestion scope across divisions and offices.  ·  Reporting altitude, and whether optional client and vendor follow-through notes are offered.  ·  Which model provider and API keys we wire. Page 2 of 3Susco Solutions, LLC · Harvey, LA · What your company already promised. Sources attached, or quiet. SUSCO *Building systems to unleash human potential* **GROUNDTRUTH**For CEOs of 100+ person companies # What it costs. Not your headcount. You pay for who GroundTruth reads, not for headcount. You set the ingestion scope at setup. The invoice follows that list. Install: \[scoped on the call\] scoped by complexity **Your stack**Email · meetings · chat Microsoft 365, Google Workspace, or mixed. Legacy mail or transcript systems add wiring. **Deployment model**Push or pull Delegated push updates are standard. IT-coordinated pull in your change window adds coordination. **Sources ingested**What turns on Which sources we wire at setup, and how many systems sit behind them. Recurring: per person in ingestion scope **Ingested person**\[scoped on the call\] Charged only for people whose mail and chat GroundTruth may read. Scope is your call, in writing, at setup. **Platform minimum**\[scoped on the call\] The digest lands on the owner's desk whether scope is 10 people or 100. The floor reflects that. **Follow-through notes**+\[scoped on the call\] / mo Optional. Weekly note to the person only, deleted on the server. No manager view. Pausable anytime. What a typical deal looks like ScenarioInstallMonthlyYear 1Year 2+ Executive team + division heads (40 in scope)\[scoped on the call\]\[scoped on the call\]\[scoped on the call\]\[scoped on the call\] Two divisions (120 in scope, 40 coached)\[scoped on the call\]\[scoped on the call\]\[scoped on the call\]\[scoped on the call\] Broad rollout (250 in scope, 100 coached)\[scoped on the call\]\[scoped on the call\]\[scoped on the call\]\[scoped on the call\] A 40-person scope at a 300-person company bills like a 40-person company. Expanding a division into scope is a conversation, not a renegotiation. For comparison: a chief of staff runs \[scoped on the call\]+ a year and still is not in every customer or project thread. Scope is the price. Scope is the promise. 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. **Book a stack and scope call.** Walk away with your install number, who GroundTruth reads first, and what your Monday digest would look like. **504-264-9343**suscosolutions.com Page 3 of 3Susco Solutions, LLC · Harvey, LA · GroundTruth drafts. A person decides.