# Business Reading Path For Squire Technology Leadership evaluating SuiteCentral 2.0 for adoption. > This is a curated reading order — not the full catalog. The [meta-index](index.md) lists every page. > **Tone**: engaging, informational, encouraging — without overly selling. > **Structure**: value first, pilot ask last. Lead with *why this matters to Squire*, end with *what approval looks like*. This path mirrors the **Path A (Executive, 11-12 minutes)** reading flow from the live demo site's [[pages/concepts/three-review-paths|three review paths]], with links to the reconciled Brain1 wiki pages rather than the external URLs. If you want to go deeper after the executive pass, jump to **Path B (Leadership, 25 minutes)** further down. --- ## If you only have 5 minutes — the TL;DR Read **[[pages/synthesis/executive-reading-guide|the Executive Reading Guide]]**. It's a one-page primer synthesizing the entire corpus, structured value-first, with the ask at the bottom. --- ## Path A: Executive (11-12 min, value-first) ### Step 1: What SuiteCentral 2.0 is and why it matters right now *(3 min)* 1. **[[pages/concepts/suitecentral-2-overview|SuiteCentral 2.0 at a glance]]** — the dual framing (enterprise integration platform + AI integration governance layer), the four named differentiators, the four enterprise safety mechanisms, and the middle-intelligence-layer architecture. 2. **[[pages/entities/squire|Squire]]** — the adoption case's *business pressure*. Recent HintonBurdick acquisition doubled Squire's client base; manual consulting doesn't scale; survival-grade market shift requires automation with governance. 3. **[[pages/entities/hintonburdick|HintonBurdick]]** — the specific operational crisis behind "why now." ### Step 2: The value proposition — what Squire gets *(3 min)* 4. **[[pages/concepts/embedded-intelligence|Embedded Intelligence]]** — the principle that value appears where users already work, not in a separate admin console. 5. **[[pages/modules/context-sidecar|Context Sidecar]]** — the *killer app*. Zero-click ERP-embedded intelligence. Vendor/customer/invoice/PO contexts with pause-payments mitigation for high-risk states. 6. **[[pages/modules/mdm-central|MDM Central]]** — golden-record master data across NetSuite + Business Central. Built into the core, unlike standalone MDM products. 7. **[[pages/concepts/module-library|The 16-Module Library]]** — full catalog of 12 core + 4 extension/platform modules. Breadth proof for Squire's operational stack. ### Step 3: The production proof — verifiable evidence, not pitch claims *(3 min)* 8. **[[pages/concepts/production-proof|Production Proof]]** — 9,476 tests passing across 391 suites, 95–99% field-mapping accuracy, 4 production AI providers (OpenAI, Claude, OpenRouter, LMStudio), Squire's actual NetSuite sandbox `TSTDRV2698307`, and 5 SOC 2 Trust Services Criteria mapped to production code paths. 9. **[[pages/concepts/claim-proof-matrix|The Claim-to-Proof Matrix]]** — 8-row structural anchor mapping every pitch claim to a specific verification URL. All rows marked "Shipped." ### Step 4: The economic case *(2 min)* 10. **[[pages/concepts/roi-scenarios|The ROI Scenarios]]** — Conservative 25% / **Base Case 75%** / Optimistic 157% 3-year ROI. $2,495/month SaaS price. Base-case net annual benefit $65,460. Adjustable baseline inputs for CFO stress-testing. 11. **[[pages/concepts/competitive-landscape|The Competitive Landscape]]** — date-stamped view of Celigo, Boomi, MuleSoft, Oracle NSIP, MCP ecosystem. SuiteCentral 2.0 priced below Celigo and MuleSoft; at low end of Boomi range. ### Step 5: The ask — what approval actually looks like *(1 min, at the end)* 12. **[[pages/concepts/pilot-30-60-90|The 30/60/90 Pilot]]** — 30-day evaluation phase (no commitment) precedes a 90-day $50–75K pilot (5–10 clients). Four Gate Metrics at Day 90: 50% time-to-integrate reduction, 70% error rate reduction, economics within ROI range, governance evidence reviewed. **That's the Executive path.** Every step above is in the wiki with cross-references and source citations. --- ## Path B: Leadership (25 min, recommended — go deeper) If Path A lands and you want the full leadership-level review, walk Path B next. It adds three layers: role-specific concerns, competitive differentiation, and the cross-role reconciliation view. ### Expand the competitive story and the commercialization case 13. **[[pages/concepts/competitive-landscape|Competitive Landscape (April 2026)]]** — Celigo CRITICAL THREAT, Oracle confirmed critical, Workato now relevant. Strategic pivot: "Everyone has shipped AI. Nobody has shipped governance." 14. **[[pages/concepts/oracle-comparison|Oracle NSIP vs SuiteCentral 2.0]]** — 8-row head-to-head feature matrix. 15. **[[pages/concepts/revenue-model|The Revenue Model]]** — three channels targeting $4.4M-$7.4M Year 3 ARR, $35M-$89M valuation. 16. **[[pages/concepts/production-vs-demo|What's Real vs Demo]]** — the honest inventory of what's production-ready vs demo/fixture, for CTO trust. 17. **[[pages/entities/squire-readiness-checklist|Squire Readiness Checklist]]** — the 4-phase, 2-3 day evaluation path Reuben should walk. ### Pick your role brief (parallel choice, not a triptych) In the live demo, step 6 of Path B is a **parallel choice** — each functional leader reads the brief that matches their job. In the wiki, read the one that matches your concern: 15. **[[pages/role-briefs/cfo|CFO Role Brief]]** — financial decision-maker view. Capped pilot, transparent ROI, payback signal, day-90 economics gate. 16. **[[pages/role-briefs/cto|CTO Role Brief]]** — technical decision-maker view. 95%+ AI accuracy, 4 safety mechanisms to verify, SOC 2 Trust Services Criteria mapping. 17. **[[pages/role-briefs/coo|COO Role Brief]]** — operational decision-maker view. 5–10 client scope, weekly cadence, day-60 + day-90 gates. ### If you're reconciling all three (the CEO view) 18. **[[pages/synthesis/three-role-decision-frame|The Three-Role Decision Frame]]** — comparison-lens page for a CEO-level reviewer (e.g., [[pages/entities/jonyce-bullock|Jonyce Bullock]]) who must reconcile cost (CFO), correctness (CTO), and throughput (COO) into one pilot decision. --- ## The decision artifacts (for when the review is done) 19. **[[pages/entities/compliance-dashboard|The SOC 2 Compliance Dashboard]]** — the governance evidence export tool with 5 TSC categories mapped to source-code paths. The CTO should open each panel and click "Export Evidence Package." 20. **The Pilot Decision Memo** — referenced throughout [[pages/concepts/pilot-30-60-90]]. The copy-ready memo template with 3 decision options (A: approve now, B: conditional, C: defer) and a 6-position pilot org chart (Executive sponsor, Technical owner, Operating owner, CFO/CTO/COO sign-offs). --- ## The role-specific decision-makers (named) - **[[pages/entities/jonyce-bullock|Jonyce Bullock]]** — CEO of Squire & Company. Primary concerns: growth, scale, moat, recurring revenue. CEO soundbite: *"Scale 10× clients without 10× consultants."* - **[[pages/entities/reuben-cook|Reuben Cook]]** — President of Squire Technology. Primary concerns: architecture, security, production readiness. Tech soundbite: *"ERP-native AI that respects governance limits."* --- ## Tone and audience note Per the notebook's own instruction (which the user typed directly into NotebookLM): > *"Audience: Squire Technology Leadership. Tone: Engaging, Informational, Encouraging without overly selling. Goal is to help them see why this is a product they would want to upgrade/adopt and worth looking into."* That's why this reading path is **value first, pilot last**. Leading with the ask is the opposite of "without overly selling." See the [[pages/concepts/canonical-metrics|canonical wording style guide]] for how to phrase specific claims. --- *Last refreshed: 2026-04-07. Mirrors Path A from the live demo site's review flow.*