---
type: source
title: 'Source: 33-SUITECENTRAL-DEPLOYMENT-OPTIONS.md'
aliases:
  - 33 deployment options
  - deployment options source
  - deployment infographic source
modified: 2026-06-14
tags:
  - source
  - suitecentral
  - deployment
  - squire
  - technical-proof
---

# Source: 33-SUITECENTRAL-DEPLOYMENT-OPTIONS.md

## What this source is

NotebookLM-ready deployment-options source for Squire. It includes the deployment-options infographic link, the interactive dashboard link, and a searchable text transcription of the six-tier model.

## Key claims

- SuiteCentral 2.0 should be presented as a deployment spectrum, not a replacement roadmap.
- The first-to-bill wedge is NetSuite Sync Error AI Assist plus AI Field Mapping on one existing SyncCentral deployment.
- Tiers 0-2 are mostly code-present today and primarily require Squire activation/proof.
- Tier 3 has embedded host code but still needs live tenant install evidence.
- Tiers 4-5 are later packaging/native-product motions and should wait for pilot economics.

## Live artifacts

- Infographic: https://demo.kstratmdconsulting.com/docs/architecture/suitecentral-deployment-options-infographic.png
- Interactive dashboard: https://demo.kstratmdconsulting.com/suitecentral-deployment-options-dashboard.html
- Repo source: `public/Squire-Executive-Package-v2/33-SUITECENTRAL-DEPLOYMENT-OPTIONS.md`

## Best reviewer questions

- Which deployment tiers are mostly ready in code today?
- What exactly does Squire need to activate for Tier 2?
- Why start with Sync Error AI Assist before AI Field Mapping?
- Why is the embedded host a follow-on proof rather than the first billing path?