What a Day-15 Scorecard Actually Looks Like (with a real example)

If you have applied to the DuluthPath Pilot Program, you already know the cadence: Day 0 onboarding call. Days 1–14 the platform runs live integration intelligence against your ERP. Day 15 a one-page PDF lands in your inbox — your Integration Health Scorecard. Day 30 debrief and conversion decision.

The question we get most often is, *"What does the Day-15 scorecard actually contain?"* Customers want to know what to expect before they walk it into the CFO, the steering committee, or the board. This post is the answer — section by section, with realistic numbers from a sanitized example.

The one-page format (intentional) The scorecard is **exactly one page**. Not a 40-slide deck. Not a vendor proposal. One page that an executive can read in 90 seconds and forward to a peer with a one-line note. That constraint is deliberate. After 30+ pilot engagements we have learned that scorecards longer than one page are read by nobody and converted by nobody. The discipline of fitting the truth onto one page is what makes the document useful. ## The five sections Every scorecard has the same five sections, in the same order: ### 1. Overall integration health score (0–100) A single number that summarizes the entire scorecard. Composed of four sub-scores: **uptime** (0–25), **data freshness** (0–25), **cross-system consistency** (0–25), and **decision velocity** (0–25). The blended score sets the tone. - **80–100** — Mature integration. DuluthPath surfaces optimization opportunities, not foundational gaps. - **60–79** — Functional but leaking. The pilot will find quantified value worth the engagement. - **40–59** — Mid-market average. Expect $2M–$8M of recoverable value findings. - **<40** — Foundational integration debt. Expect a Day-30 conversion conversation focused on roadmap, not features. Example: **62/100 — Mid-tier health, three high-confidence recoverable findings.** ### 2. Your top three findings (with a dollar number attached to each) This is the most-read section. Each finding is one paragraph and one dollar figure. A real scorecard might read: 1. **Customer master mismatch — $4.2M / year** SAP and Salesforce disagree on customer records for 4,082 accounts. Dispute rate trending 6.4%. Resolution path: customer-master reconciliation via Forge over a 6-week sprint. 2. **Order-to-cash latency — $2.8M / year** Average 9.3-second round-trip between Dynamics 365 and Salesforce. Quote-to-cash cycle extended by 4 days. Resolution path: re-architect the sync via the Dynamics batch API. 3. **Inventory ghost stock — $1.9M / year** Oracle inventory and Salesforce CPQ misaligned on 312 SKUs. Promotions hit stockouts 11% of the time. Resolution path: real-time inventory broadcast through DuluthPath. **Total quantified annual value at risk: $8.9M.** The dollar numbers are not theoretical. They are derived from your live ERP transaction volume and your stated revenue / margin. We show our math in the methodology footer. ### 3. Plan-fit recommendation (Starter vs Growth) A direct recommendation, with reasoning. Example: > **Recommended plan: Growth ($14,500 / month).** > Your findings include cross-system latency and Canaan-AI-detectable anomaly patterns. Starter tier covers 2 of your 3 findings; Growth covers all 3 plus the predictive anomaly detection that prevents the next recurrence. ROI breakeven at month 2. We do not always recommend the higher tier. About 35% of pilots end with a Starter recommendation — when the findings are simpler and the Growth-tier AI features would be over-engineered for the operational pain. ### 4. Three actions to take before Day 30 Concrete, sequenced, low-effort. Designed so the customer arrives at the Day-30 debrief having already moved on the most actionable items. Example: 1. **Run the Cross-System Reconciliation Wizard** for SAP-Salesforce customers. Catches 80% of the master-data mismatch in one pass. (20 min, no IT required.) 2. **Connect your Dynamics 365 service account** to enable batch-API sync. (90 min, requires DBA.) 3. **Subscribe your COO to Canaan-AI weekly digest.** Surfaces the next anomaly before it becomes a finding. (30 sec, in-product.) ### 5. The methodology footer The boring part that the CFO actually reads twice. A two-paragraph statement of: - **Data sources** used (which ERPs, which Salesforce orgs, which date range) - **Sample size** (number of transactions, number of master records, number of API calls observed) - **Assumptions** (your stated annual revenue, gross margin, average order size — used to convert observed anomalies into dollar figures) - **Disclaimer**: the scorecard is an estimate based on 15 days of observation, not a guarantee. Resolution paths require the customer's engineering or operations time. ## How to read it before you walk it into your CFO Three rules: 1. **Read the score first, the findings second.** The score sets expectation. The findings make the case. 2. **Ignore the dollar precision; trust the order of magnitude.** A $4.2M finding might land at $3.8M or $5.1M after deeper analysis. It will not land at $400K. The methodology is conservative. 3. **Pick the single finding you can defend.** Lead with the one most defensible to your specific stakeholder. The other two corroborate. ## Why we send it at Day 15 (not Day 30) By Day 15 we have enough live data to produce defensible numbers. Earlier than that the sample size is too thin. Sending at Day 15 also gives the customer 15 days before the close conversation — enough time to act on the recommendations, validate the dollar figures against internal data, and arrive at Day 30 already half-decided. About 71% of pilots convert when the scorecard arrives on time and has at least one finding the customer can act on within 15 days. Less than half convert when the scorecard arrives at Day 25 or later. The cadence matters. ## See a sample scorecard We have published an anonymized, sanitized version of the live dashboard the scorecard reads from. Walk it like one of your own. → [See the live Integration Intelligence demo dashboard](https://duluthpath.com/demo/integration-intelligence) Or apply to receive your own scorecard in 15 days. → [Apply for the DuluthPath Pilot Program](https://duluthpath.com/pilot)