Buyer close pack
Close the right launch motion, with the right exclusions.
Sales, procurement, order-form review, and implementation need one answer: what can be sold now, what evidence must attach, and what wording stays blocked. This pack combines live clearance, claims guard, commercial defaults, and managed-beta gates into one close artifact.
4
launch motions
3
commercial plans
7
close checks
40
blocked claims
Close decision
Invoice-led paid beta is the current safest close motion with named evidence and explicit exclusions.
Recommended motion: invoice-paid-beta. This is the launch scope sales can carry forward only when the listed evidence and exclusions are attached.
THESMIOS_SMOKE_URL=https://www.thesmios.com npm run check:buyer-close-pack
Managed private beta
Conditionally launchable for a named design partner with signed scope, operator fixture evidence, manual support fallback, and launch acceptance.
Commercial treatment: sell with exclusions.
Required evidence: Advisory readiness output; Launch proof bundle output; Tenant launch room snapshot; Tenant launch dossier download; +2 more.
Invoice-led paid beta
Conditionally launchable only after customer acceptance, billing profile, invoice/order-form evidence, and authenticated fixture proof are attached.
Commercial treatment: sell with exclusions.
Required evidence: Tenant billing profile saved as invoice-only or Stripe-ready; Order-form billing terms and owner; Authenticated access/RLS proof output; Issuer, evidence, audit export, and privacy fixture outputs when in customer scope; +1 more.
Self-serve paid launch
Blocked. Strict readiness must be ready and Stripe fixture proof must pass before self-serve checkout is enabled.
Commercial treatment: do not sell.
Required evidence: Strict readiness passing; Stripe fixture output; Notification fixture controlled-send output; Support notification lifecycle fixture output; +1 more.
Broad enterprise expansion
Blocked. Enterprise SSO, SAML, HRIS, official issuer credentials, and SCIM fixture evidence remain customer/vendor-specific.
Commercial treatment: do not sell.
Required evidence: SCIM fixture output for the chosen IdP; OIDC/SAML broker proof or managed-setup exclusion; HRIS and official issuer credential proof; Security/procurement approvals; +1 more.
Order-form scope
| Section | Owner | Required fields | Acceptance text |
|---|---|---|---|
| Customer and tenant scope | joint | Legal customer name and billing entity; Tenant workspace name, data residency, and primary domains; Named tenant owner, billing owner, support owner, privacy approver, and security approver; Approved worker cohort size and go-live date | Customer confirms the named tenant, owners, launch cohort, region, and go-live target are accurate before worker data is imported. |
| Commercial plan and limits | customer | Selected plan: design_partner, paid_beta, or enterprise_setup; Active passport, admin seat, verifier seat, share, audit export, and integration limits; Invoice/PO route or Stripe readiness proof; Renewal, cancellation, pause, and expansion terms | Customer accepts the plan limits and agrees that unlisted overages or expansion work require written approval before use. |
| Included launch capabilities | thesmios | Employee-owned compliance passport modules; Evidence upload, credential review, scoped verifier shares, audit trail, tenant KPIs, privacy requests, and audit exports; Named connector credentials or explicit manual-upload fallback | Thesmios will provide only the included launch capabilities and customer-keyed integrations listed in the order form. |
| Exclusions and roadmap boundaries | joint | Excluded roadmap capabilities; Managed-beta capabilities requiring customer-specific proof; Credential-required integrations and external approval dependencies | Both parties acknowledge excluded, demo, planned, manual, managed, or credential-required capabilities are not live production commitments until separately scoped and evidenced. |
| Launch acceptance gates | joint | Production readiness summary; Authenticated owner/granted/denied access smoke result; Tenant launch-room snapshot; Retention schedule, privacy request route, support route, and rollback owner | The tenant is not accepted as live until launch gates are attached or explicitly scoped out in the written acceptance note. |
Close checklist
Every signature has a proof dependency.
The checklist splits work across sales, operator, customer, finance, security, and enterprise owners before order-form send, signature, and go-live.
Choose the launch motion and copy its allowed and blocked wording into the opportunity notes.
Owner: Sales
Evidence: Buyer close pack JSON; Launch claims guard JSON; Launch clearance output.
If missing: Do not send order-form language until the launch motion and exclusions are visible.
Select invoice/manual billing unless Stripe self-serve has passed strict proof.
Owner: Finance
Evidence: Order-form billing terms; PO or invoice owner; Tenant billing profile once authenticated.
If missing: Use a no-charge design partner scope or hold paid-beta signature.
Attach customer scope, data boundaries, launch cohort, and accepted exclusions.
Owner: Customer
Evidence: Signed order form or written approval reference; Approved worker cohort and compliance modules; Customer launch room sections; Tenant billing profile saved as invoice-only or Stripe-ready; Purchase-order terms or invoice contact; +5 more.
If missing: Keep the tenant in setup and do not represent the launch as accepted.
Attach procurement, DPA/SLA, residual-risk, fixture, and privacy/security evidence required by scope.
Owner: Security
Evidence: /api/product/procurement-evidence; /api/product/security-assurance; /api/product/production-proof; Authenticated fixture outputs for in-scope controls.
If missing: Do not mark regulated buyer security review as complete.
Run public proof, collect operator fixture proof when approved, and attach launch-room/dossier outputs.
Owner: Operator
Evidence: CONFIRM_LAUNCH_OPERATOR_SEED=thesmios-launch-seed run output; Owner, granted-employer, and denied-employer smoke results; Authenticated tenant launch-room snapshot; check:issuer-fixture output when issuer keys and auth fixtures are configured; check:evidence-fixture output when job runner secret is configured; +2 more.
If missing: Run only demo/setup workflows; do not import live worker traffic.
Confirm SSO/SCIM/HRIS/official issuer claims are either proven, managed setup, credential-required, or excluded.
Owner: Enterprise
Evidence: Launch intake owner files; Tenant SSO evidence or exclusion; Tenant vendor evidence or exclusion; SCIM fixture output when enterprise provisioning is in scope.
If missing: Exclude hands-off enterprise automation from the order form and launch acceptance.
Re-run launch clearance and strict readiness after any dependency changes.
Owner: Operator
Evidence: THESMIOS_SMOKE_URL=https://www.thesmios.com npm run check:readiness -- --strict; THESMIOS_SMOKE_URL=https://www.thesmios.com npm run check:launch-proof-bundle -- --include-fixtures --strict --env-file /tmp/thesmios-auth-smoke.env.
If missing: Keep self-serve and broad enterprise motions blocked.
Buyer-safe claims
Use included wording only with evidence attached.
Worker compliance passport
Worker compliance passport is included for a named managed launch tenant once the matching tenant evidence and acceptance gates are attached.
Order-form treatment: List in included launch capabilities only with tenant launch-room evidence, acceptance stage, and proof output attached.
Invoice and order-form billing
Invoice and order-form billing is included for a named managed launch tenant once the matching tenant evidence and acceptance gates are attached.
Order-form treatment: List in included launch capabilities only with tenant launch-room evidence, acceptance stage, and proof output attached.
Companies House
Companies House can be enabled after approved production credentials, customer approval, and fixture proof are attached.
Order-form treatment: List under customer dependencies or optional scope; do not commit automation until credentials and fixture proof pass.
Home Office / UKVI right to work
Home Office / UKVI right to work can be enabled after approved production credentials, customer approval, and fixture proof are attached.
Order-form treatment: List under customer dependencies or optional scope; do not commit automation until credentials and fixture proof pass.
DBS Update Service
DBS Update Service is available only as managed beta or manual fallback with scoped rollout limits and explicit customer acceptance.
Order-form treatment: List as managed/manual scope with automation exclusions, named owner, and acceptance evidence.
US E-Verify
US E-Verify is available only as managed beta or manual fallback with scoped rollout limits and explicit customer acceptance.
Order-form treatment: List as managed/manual scope with automation exclusions, named owner, and acceptance evidence.
Blocked wording
Keep these claims out of the close.
Anything listed here must be excluded, moved to a customer-specific dependency, or funded through a separate statement of work.
Proof commands
Close pack changes only when evidence changes.
Buyer close pack smoke
Buyer close page and JSON endpoint are deployed, complete, public-safe, and wired into launch proof bundles.
THESMIOS_SMOKE_URL=https://www.thesmios.com npm run check:buyer-close-pack
Launch claims guard
Buyer-safe wording, blocked wording, and order-form treatment are current.
THESMIOS_SMOKE_URL=https://www.thesmios.com npm run check:launch-claims-guard
Managed beta readiness
Invoice-led/manual launch path and self-serve/enterprise exclusions are current.
THESMIOS_SMOKE_URL=https://www.thesmios.com npm run check:managed-beta-readiness
Owner intake packet
Owner-specific requests for missing inputs, approvals, proof commands, and blocked claims are generated outside git.
THESMIOS_SMOKE_URL=https://www.thesmios.com npm run prepare:launch-intake -- --output-dir /tmp/thesmios-launch-intake
Launch proof bundle
Public launch, API, evidence-pack, deployment-parity, and advisory-readiness checks pass before buyer handoff.
THESMIOS_SMOKE_URL=https://www.thesmios.com npm run check:launch-proof-bundle -- --output /tmp/thesmios-public-launch-proof.json
Boundaries