SPATCO grew to $350M on relationships, field expertise, and hustle. The next $450M needs a system behind it. Sales Cloud, Marketing Cloud, and Data Cloud Foundations — sitting on top of the SAP system of record you already trust.
Figures shown are illustrative — the structure is what matters.
Not theory — these came straight from Kevin's team. Hover or tap any card to see how the Phase 1 platform answers it.
Sales activity lives in SAP, SharePoint, and email at the same time. Sales, sales support, and estimating each log into different places to move one deal forward — and no single record holds the whole story.
Roughly 80–90% of new business comes from existing relationships. There's no fit-scoring, no lead prioritization, and reps have no visibility into account whitespace — so growth tracks the relationships, not the market.
About 30 trade shows a year. Leads get captured on badge scanners and hand-built spreadsheets — then disappear. Nobody can say what happened to a lead after the show, or what any event actually returned.
This is the scope being finalized today — nothing speculative. Click any card for what it does specifically for SPATCO.
One opportunity record across sales, sales support, and estimating — replacing the SAP + SharePoint + email scramble.
In Scope · SignedTurns ~30 trade shows a year from a spreadsheet exercise into a measurable pipeline engine with real attribution.
In Scope · Phase 1Unified account and contact profiles across lines of business — the included-value layer that makes whitespace visible.
In Scope · Included ValueField Service, Revenue Cloud, and Agentforce are deliberately out of scope today. They appear later in this site only as forward-looking direction, tied to SPATCO's existing SAP Field Service agreement window — not as anything being sold now.
Salesforce is the engagement layer — Sales Cloud, Marketing Cloud, and Data Cloud Foundations sit inside it. SAP stays the system of record underneath.
The single loop that closes the Slide 2 gap: a trade-show lead becomes a CRM record and gets followed up automatically. Three steps, no manual hand-offs.
A badge scan at one of SPATCO's ~30 annual shows writes straight into a Marketing Cloud campaign — tagged to the event, the booth, and the rep who scanned it. No badge-scanner export, no overnight spreadsheet cleanup.
Marketing CloudThe lead lands in Sales Cloud with the account already matched against unified Data Cloud profiles — so the rep immediately sees whether this is a net-new prospect or an existing customer buying a second line of business.
Sales Cloud + Data CloudAn automated journey goes out within hours while SPATCO is still fresh. Rep activity, quote, and outcome all attach to one opportunity — which is what finally makes "what did that show return?" a reportable number.
Campaign Influence ReportingWhy this loop first: it is the shortest path from a real SPATCO pain point to a number Scott and John can see on a dashboard. Nothing here depends on AI, and nothing here touches SAP's role as the system of record.
Dana stops by Booth B12. One scan captures name, company, and interest area — no clipboard, no end-of-show spreadsheet.
No more guessing the route or calling dispatch for the next stop. Everything Marcus needs is already on his phone.
Scope Note
Field Service is Phase 2 — not in today's signed scope. This walkthrough shows where the platform goes once the Phase 1 foundation is in place, timed against SPATCO's existing SAP Field Service agreement window.
Phase 1 consolidates the scattered front-end tools into one platform. It does not touch the ERP — SAP remains the system of record, connected by a clean two-way sync.
Phase 1 is a data and engagement foundation, not an AI program. The trust layer is here because SPATCO's IT team asked the right question early: does proprietary data ever train someone else's model?
SAP stays the system of record — Salesforce syncs with it as the front-end engagement layer.
To be finalized with the implementation partner during discovery. No integration tooling is assumed or committed in the current scope.
SPATCO's data stays SPATCO's data. No customer data is retained by the model provider, and nothing SPATCO puts into the platform is ever used to train an outside model. Zero data retention, dynamic grounding, and toxicity/audit controls are built into the platform — not bolted on later.
Value already included with Phase 1 licensing — not a future purchase.
Phase 1 applications: Sales Cloud and Marketing Cloud, with reports and dashboards for leadership visibility.
Deliberately absent: Agentforce and advanced AI agents. They sit above this stack and are a later conversation — after the foundation is live and the data is clean enough to be worth reasoning over.
These are the KPIs the deal team selected for the business case. Figures shown are illustrative — the structure is what matters.
68% of accounts buy one thing. That is the whitespace.
Baseline before Phase 1: 22.5 selling hours per week.
Recaptured hours compound as adoption climbs.
Matters most when headcount grows toward the $800M plan.
Visibility into who is stalling, before the quarter ends.
The bottom row is the point — you can finally cut what doesn't work.
Leaders see where pipeline is thin before the quarter closes.
Same $18.4M, normalized so small branches aren't hidden behind big ones.
50% recapture. Half the reclaimed time is assumed to convert to real selling activity — the rest absorbs into the day.lift %. Models the share of event investment currently lost because leads go into a spreadsheet and never get worked.Figures marked SPATCO actual come from the deal team's discovery with Kevin Bretcher's organization. Figures marked industry benchmark are defaults to be replaced with SPATCO data during the business-case build. The $115,000 investment covers implementation services only; Salesforce license subscription is priced separately.
Phase 1 isn't a technology project. It's the operating system for the next $450M of growth.
One opportunity record across 36 locations means Kevin can forecast the business instead of assembling it. Pipeline becomes a system output, not a monthly reconciliation exercise.
Thirty events a year stop being a cost line and start being a measurable channel. When the board asks what marketing returned, there's a number attached to a campaign.
Clean, unified data is the prerequisite for everything that comes after — Field Service, deeper automation, and eventually AI. Get the foundation right and the rest becomes a decision, not a rebuild.
SAP stays the system of record. Finance, inventory, and service contracts don't move. Salesforce sits on top as the engagement layer — additive, not disruptive.


The scope is defined, the partner is lined up, and the schedule holds an August 10 start with a November 27 go-live. The only thing left is the decision.