---
type: synthesis
title: Executive Reading Guide
aliases:
  - reading guide
  - where to start
  - one-page primer
modified: 2026-04-11
tags:
  - synthesis
  - reading-guide
  - navigation
  - adoption-case
---

# Executive Reading Guide

> The one-page primer for Squire leadership. What SuiteCentral 2.0 is, why it matters right now, what's been verified, what's being asked for, and where to find every load-bearing claim in the wiki. Structured value-first — the pilot ask is at the bottom, not the top.

## What this page is

A **synthesis of the Brain1 wiki's current state** as of 2026-04-07, organized as a reading path for a Squire executive who has ~15 minutes and wants to walk the adoption case end-to-end without getting lost in the 22 ingested sources and 25+ wiki pages. It mirrors the live demo's [[pages/concepts/three-review-paths|three review paths]] but points at the wiki's internal pages (which have been cross-referenced and reconciled) rather than the external URLs.

## Who this is for

A **Squire executive** — specifically someone at the reconciliation level where all three role concerns (cost, correctness, throughput) have to be satisfied. Typically [[pages/entities/jonyce-bullock|Jonyce Bullock]] (CEO of Squire & Company). Also useful for any reviewer who wants the condensed view of what the corpus says.

---

## 1. What SuiteCentral 2.0 actually is

Two framings, both correct, used in different contexts (per [[pages/concepts/suitecentral-2-overview]]):

- **Platform framing**: an enterprise integration platform with a 16-module footprint (12 core + 4 extension/platform). See [[pages/concepts/module-library]] for the full catalog.
- **Positioning framing**: an **AI integration governance layer** — the control plane between AI clients (ChatGPT, Claude, etc.) and native ERPs (NetSuite, Business Central). Per the hook video: *"We don't replace the ERPs but act as the control plane between AI clients and native ERPs."*

The positioning framing is the moat. Everyone has AI integration; **nobody has AI integration governance**. That's the differentiator.

**Architecturally**, the governance layer is built from four enterprise safety mechanisms that wrap every AI action:
1. **Reasoning Trace Engine** — logs justifications (DB-persisted)
2. **Governance Pacer** — prevents throttling (respects NetSuite API limits: 5 concurrent / 10 RPS)
3. **DLP PII Shield** — redacts sensitive data (8 patterns: SSN, credit card, email, phone, DOB, passport, bank account, driver license)
4. **Approved To Apply** — cryptographic verification of human sign-off

---

## 2. Why this matters right now (the strategic window)

**Three forces create a 6–12 month window** for Squire to establish a defensible position:

1. **Market pressure**: Oracle, Microsoft, and OpenAI are shipping native AI + MCP capabilities. The "old problem" of connecting systems is being solved by everyone. The new problem is *how to govern* the AI that connects them. (Per [[sources/ai-governance-layer-video]] "The world changed last week.")
2. **Regulatory pressure**: the EU AI Act takes full effect **August 2, 2026**. High-risk AI systems used in financial processes must provide reasoning traces, human oversight, and risk assessments. Black-box AI mappings will not pass audit. The Colorado AI Act (SB 24-205) also takes effect **June 30, 2026**. Both are shown on the [[pages/entities/compliance-dashboard|compliance dashboard]].
3. **Business pressure**: [[pages/entities/squire|Squire]] just acquired [[pages/entities/hintonburdick|HintonBurdick]], which **doubled its client base**. Manual consulting doesn't scale. The acquisition forces the question: automate with governance, or get commoditized.

The pitch's own thesis: **"Speed without control is now a liability."** The competitive window is measured in months, not years. See [[pages/concepts/competitive-landscape]] for the full date-stamped view of competitors.

> ⚠ **Style-guide note**: the "6-12 month window" phrasing is flagged on [[pages/concepts/suitecentral-2-overview]] as tension with the [[pages/concepts/canonical-metrics|canonical wording guide]] which wants that phrasing avoided unless date-anchored. The substance is fine; the phrasing needs a refresh date if presented verbatim to the board.

---

## 3. What's been verified (production proof, not pitch deck)

The most important line in the entire corpus:

> **"This isn't a pitch deck — it's production code."**
> — [[sources/read-elevator-pitch]] Beat 3

### The canonical test numbers (per [[pages/concepts/production-proof]])

- **100% suite pass rate** (419 suites)
- **9,476 tests passing** (34 skipped) across unit + integration + E2E
- Full breakdown: 9,286 unit (23 skipped) + 170 integration (11 skipped) + 20 E2E portal
- **Line coverage**: 64.59% across 45,757 lines of production TypeScript
- Total repository: **~854K text LOC** across 2,282 tracked files

### The 4 production AI providers (per [[sources/04-technical-proof]])

| Provider | Model | Role | Cost/mapping |
|---|---|---|---|
| OpenAI | GPT-4o | Primary | $0.02 |
| Anthropic Claude | Claude 3.5 Sonnet | Secondary | $0.003 |
| OpenRouter | Multi-model | Routing/fallback | Free tier |
| LMStudio | Llama 3.1 8B | On-premise/fallback | Free (local) |

AI accuracy (verified Oct 2025): **95–99% field mapping**, 90%+ confidence calibration, +5–15% multi-provider consensus boost.

### The 8-row claim-to-proof matrix (per [[pages/concepts/claim-proof-matrix]])

Eight pitch claims each tied to a specific proof artifact. All 8 marked "Shipped." If a reviewer is skeptical, this is the 10-minute verification lap.

### SOC 2 alignment (per [[pages/entities/compliance-dashboard]])

All 5 Trust Services Criteria mapped to production code with specific source file paths: CC6 Security (JWT, RBAC, timing-safe validation), A1 Availability (health checks, circuit breakers, K8s auto-scaling), PI1 Processing Integrity (confidence scoring, hallucination detection, reasoning traces), C1 Confidentiality (DLP/PII, encryption), P1 Privacy (GDPR/CCPA, audit logging, 90-day retention).

**Squire-specific anchor**: SuiteCentral 2.0 has been verified against **Squire's actual NetSuite sandbox `TSTDRV2698307`** with full CRUD across customer / vendor / transaction / custom record / saved search objects.

---

## 4. What's different (the competitive moat)

Per [[pages/concepts/oracle-comparison]], the 8-row feature matrix shows what Oracle NSIP **does not have** that SuiteCentral 2.0 **does**:

| Capability | Oracle NSIP | SuiteCentral 2.0 |
|---|:---:|---|
| Reasoning Traces | ❌ | ✅ DB-persisted |
| Confidence Breakdown | ❌ | ✅ Multi-signal (semantic + pattern + historical) |
| Hallucination Detection | ❌ | ✅ Built-in with risk scoring |
| Dual-ERP Support | ⚠ NetSuite only | ✅ NetSuite + Business Central |
| Approve-to-Apply | ❌ | ✅ Human-in-the-loop gate |
| Cost Transparency | ❌ | ✅ Per-provider cost at mapping time |
| DLP / PII Protection | ❌ | ✅ 8 patterns (GDPR / CCPA) |
| Governance Pacer | ❌ | ✅ API rate limit enforcement |

**The critical context**: Oracle NSIP is Oracle Integration Cloud Release 3 **rebranded**, not a new product. Oracle is playing catch-up, and they're making MCP tools free — which reduces the *connector* moat but not the *governance* moat.

**The 6 production connectors** (per [[pages/concepts/canonical-metrics]]): NetSuite, Business Central, Salesforce, HubSpot, ShipStation, Oracle. Spans ERP + CRM + logistics.

---

## 5. What Squire specifically gets (the transformation thesis)

Per [[pages/entities/squire]] and the hook video (00:07):

> **"This platform transforms Squire from an integration provider to a platform leader who governs integrations."**

The adoption case is a **business-model evolution**, not a tool upgrade. Concretely:

- **Before**: Manual consulting. 15 hours per integration (~2023 baseline). Linear scaling — more clients means more consultants.
- **After**: Automated with governance. Manual mapping → <1 hour (base case) or 30 seconds (hero case). **1 engineer manages 50 clients** instead of 10 — 5× support scalability.
- **HintonBurdick context**: the acquisition doubled Squire's client base. Without automation, the delivery model breaks. With SuiteCentral 2.0, the acquired client base is absorbable. The CEO soundbite for [[pages/entities/jonyce-bullock|Jonyce Bullock]]: *"Scale 10× clients without 10× consultants."*
- **Recurring revenue upside**: SuiteCentral 2.0 is also positioned as a **product Squire could license to other firms**. The year-1 target (per the hook video) is **60+ customers** post-pilot — which is the SaaS commercialization path.

**Current state**: Squire runs **SuiteCentral 1.0** in production. The pilot moves them from 1.0 to 2.0.

---

## 6. The three role lenses (for the reconciliation view)

Each functional leader has their own concern. Per [[pages/synthesis/three-role-decision-frame|The Three-Role Decision Frame]]:

| Role | Concern | Veto power | Key soundbite / ask |
|---|---|---|---|
| [[pages/role-briefs/cfo|CFO]] | Cost | "financially reckless" | Scenario-stress the 25–157% ROI range; verify the ROI calculator at $2,495/mo SaaS; day-90 gate includes economics + adoption proof |
| [[pages/role-briefs/cto|CTO]] | Correctness | "engineering-reckless" | Watch clips, verify SOC 2 TSC mapping, see the 4 named safety mechanisms in action, validate 95% accuracy methodology; [[pages/entities/reuben-cook|Reuben Cook]] is the Squire-side tech leader |
| [[pages/role-briefs/coo|COO]] | Throughput | "will break operations" | KPIs defined before pilot starts, weekly operating cadence with named owners, 5–10 client selection, expansion only on measurable outcome attainment |

All three must clear for pilot approval. The synthesis page has the full consolidated "what to ask for" list across all three roles (15 items total).

---

## 7. What's being asked for (the pilot, at the end)

Per [[pages/concepts/pilot-30-60-90]], the full ask is actually **two sequential phases**, not one:

### Phase 1: 30-day evaluation (BEFORE the $50–75K commitment)

Week 1 demo review → Week 2 technical deep-dive → Week 3 pilot client selection → **Week 4 decision checkpoint** (the commit point).

No billable work starts in Phase 1. Squire is walking the review experience and selecting which 5–10 clients would be the pilot target. If Week 4 is a "go," Phase 2 begins.

### Phase 2: 90-day pilot ($50K–$75K)

| Days | Phase | Activities |
|---|---|---|
| 1–30 | Setup and Baseline | Assign sponsor + owner, select pilot clients, baseline metrics, preflight checks |
| 31–60 | Controlled Execution | Deploy field mapping + sidecar workflows, weekly KPI pack, compliance evidence export checks |
| 61–90 | Scale Decision | Compile ROI + case studies, **go/no-go board**, scale only if all gates pass |

### The four Gate Metrics (per [[pages/concepts/pilot-30-60-90]])

At Day 90, **all four must pass** for approval to scale:
1. **Time-to-integrate**: ≥ 50% reduction
2. **Error rate**: ≥ 70% reduction
3. **Economics**: Trend within approved ROI range (25–157%)
4. **Governance**: Evidence package exported and reviewed (via the [[pages/entities/compliance-dashboard|compliance dashboard]]'s one-click export)

### ROI scenarios (per [[pages/concepts/roi-scenarios]])

| Scenario | Time Reduction | Error Reduction | 3-Year ROI |
|---|---|---|---|
| Conservative | 70% | 90% | **25%** |
| **Base Case** | **75%** | **95%** | **75%** ← the expected value |
| Optimistic | 85% | 98% | **157%** |

**The 25–157% range that appears throughout the corpus is the endpoints**; the expected value is **75%** (base case). Base case net annual benefit: $65,460 ($95,400 labor savings − $29,940 platform cost). SaaS price: **$2,495/month**.

### Decision options (per [[pages/entities/compliance-dashboard|the Pilot Decision Memo]])

| Option | Description |
|---|---|
| **A: Approve pilot now** | Proceed with full 30/60/90 plan and weekly steering cadence |
| **B: Conditional approval** | Approve after **one** additional technical check OR budget clarification |
| **C: Defer** | Revisit after market or internal constraints change |

### The 6-position pilot org chart

The memo requires six named positions:
1. Executive sponsor (one named person, executive-level accountability)
2. Technical owner (day-to-day technical work)
3. Operating owner (day-to-day operational work)
4. CFO sign-off
5. CTO sign-off
6. COO sign-off

---

## 8. New since the first draft: what's been added (April 2026)

### The revenue model ($4.4M-$7.4M Year 3)

See [[pages/concepts/revenue-model]] — three revenue channels (Partner $10K/yr, Direct SaaS $2,495/mo, Enhancements $995-$1,495/mo), phased investment ($505K Year 1 → $2.455M cumulative), $35M-$89M platform valuation at 8-12× ARR.

### Andy's 3 Questions — standalone or integrated?

A Squire executive asked three questions ([[pages/entities/squire]]): (1) Is it standalone? *Yes, it can be.* (2) Can Squire integrate it? *Also yes — it's the AI upgrade path for existing SuiteCentral modules.* (3) What's the end goal? *Keep Squire competitive.* **Deployment strategy is Squire's decision.**

### What's production vs demo

See [[pages/concepts/production-vs-demo]] — the honest trust document. 5 production connectors + 1 beta (Oracle) + 10 fixture-based + 200+ planned. All 9 AI providers production-ready. Claude upgraded to 4.5 Sonnet.

### The Squire readiness checklist

See [[pages/entities/squire-readiness-checklist]] — 4-phase, 2-3 day evaluation path written for Squire. Connection → AI → Real Data → Scale. Grade: A+.

### Competitive update: competitors have shipped AI

See [[pages/concepts/competitive-landscape]] — **Celigo upgraded to CRITICAL THREAT** (shipped MCP, AI Assist, Mapper 2.0). Oracle confirmed critical (free MCP tools). Workato now relevant (agentic AI). **Strategic pivot: "Everyone has shipped AI. Nobody has shipped governance."**

---

## The one-page summary (TL;DR) — refreshed April 2026

**What**: SuiteCentral 2.0 is a production-ready AI integration governance layer — a control plane between AI clients and ERPs that adds reasoning traces, confidence scoring, hallucination detection, human-approval gates, PII redaction (14 patterns, 6 field-gated), and API rate limiting on top of any ERP integration work.

**Why now**: Market pressure — **competitors have shipped AI** (Celigo = critical threat, Oracle = free MCP tools, Workato = agentic AI). Regulatory pressure (EU AI Act Aug 2, 2026). Business pressure (HintonBurdick acquisition doubled Squire's client base). The moat is governance depth, not AI access.

**What's proven**: **9,476 tests** passing across **409 suites** (April 2026 canonical), 4 production AI providers (Claude upgraded to 4.5 Sonnet), 95–99% field mapping accuracy, 5 SOC 2 TSC categories mapped to production code with source-file paths, verified against Squire's actual NetSuite sandbox `TSTDRV2698307`.

**What's different**: 8-row competitive matrix shows Oracle NSIP is missing every governance capability. Celigo has shipped AI but has NO governance layer. SuiteCentral 2.0 is priced at the low end of the iPaaS range ($2,495/mo). **"Everyone has shipped AI integration. Nobody has shipped AI integration governance."**

**What Squire gets**: Platform-leader transformation. Can be standalone OR integrated into existing SuiteCentral products (Squire's choice). 5× support scalability. Base case 75% 3-year ROI. $4.4M-$7.4M Year 3 ARR across three revenue channels. $35M-$89M platform valuation.

**How to verify**: Walk the [[pages/entities/squire-readiness-checklist|Production Readiness Checklist]] (2-3 days). Start with [[pages/concepts/production-vs-demo|What's Real vs Demo]]. Check the [[pages/concepts/claim-proof-matrix|Claim-to-Proof Matrix]] (all 8 rows Shipped).

**The ask**: 30-day evaluation (no cost), then — if Week 4 gate passes — a 3-month $50–75K pilot across 5–10 clients with four measurable Gate Metrics at Day 90.

---

## How to navigate the wiki from here

If you want to go deeper on any section above, the next-level pages are:

| Topic | Page |
|---|---|
| What it is | [[pages/concepts/suitecentral-2-overview]] |
| The 16 modules | [[pages/concepts/module-library]] |
| Architecture deep-dive | [[sources/mcp-gateway-architecture]] + [[sources/ai-provider-system]] + [[sources/04-technical-proof]] |
| Production proof | [[pages/concepts/production-proof]] |
| Governance evidence | [[pages/entities/compliance-dashboard]] |
| Competitive position | [[pages/concepts/oracle-comparison]] + [[pages/concepts/competitive-landscape]] |
| The pilot structure | [[pages/concepts/pilot-30-60-90]] |
| The three review paths | [[pages/concepts/three-review-paths]] |
| Claim verification | [[pages/concepts/claim-proof-matrix]] |
| ROI economics | [[pages/concepts/roi-scenarios]] |
| Squire transformation case | [[pages/entities/squire]] + [[pages/entities/hintonburdick]] |
| Cross-role reconciliation | [[pages/synthesis/three-role-decision-frame]] |
| Style guide for wording | [[pages/concepts/canonical-metrics]] |

Or if you want the live site version of the same material, start at [[pages/entities/demo-site|demo.kstratmdconsulting.com]] → [[sources/15-start-here-async-standalone|the Start Here page]] and pick a review path (A: Executive 12 min, B: Leadership 25 min, C: Deep Proof 50 min).

## Sources

This guide synthesizes across 22 source-summaries. The pages cited above each list their primary sources. The headline anchors:

- [[sources/01-executive-summary]] — the 10-slide top-of-funnel
- [[sources/15-start-here-async-standalone]] — the live navigation hub
- [[sources/09-claim-proof-matrix]] — the 8-row verification matrix
- [[sources/16-pilot-decision-memo]] — the terminal decision artifact