SUBTRACT ARCHITECTStudios • Two Platforms for Client Companies
0%
0 / 40
Two separate platforms SAS sells • Not internal SAS training • For client companies
Two platforms. Training is one job. Onboarding is another.
We split them — on purpose. Platform 1 is standardised training every company needs: Token Economics, token conservation, AI optimization & security. Platform 2 is a custom in-house onboarding platform built for one company at a time — their packet, their roles, their Day 0–90. Different products, different builds, one shared content spine underneath. A company can buy either — most buy both, kept separate.
SHOWN WITH SAS BRANDING AS MASTER. FOR A CLIENT, THEIR LOGO LEADS ON BOTH PLATFORMS — SAS CREDIT STAYS ON AS PROVIDER. PROGRESS IS SESSION-ONLY.
Two platforms, kept separate
Onboarding is its own platform — not a track inside training — sold and built separately. Here's the line between them, and why keeping them apart protects both.
Two products • One provider
● Platform 1 — Standardised • Repeatable • Same for every client
Token Economics / AI Optimization / Security Training
Our curriculum, built once, sold many times. Every employee learns to spend fewer tokens, choose the right model, use AI safely, and defend the company — Tracks 1–6.
Track 1 Core for Everyone — identity, phishing, data, safe AI
Track 2 Token Conservation, Security & AI Optimization
“In-house” means the client's house. A company's own new-hire system — their handbook, tools, policies, role pathways and 30-60-90 — built around how they work. No two builds are the same.
Day 0–90 journey — Day 1 gate → Week 1 → 30 / 60 / 90 sign-off
Custom packet builder — handbook, tools, policies, role paths
Manager check-ins — structured reviews, not attendance
Handoff to Platform 1 — new hires flow into Core + Track 2 in Week 1
Why separate? Training is a product — standardised, priced per seat, updated centrally (scam alerts monthly, model pricing as it changes). Onboarding is a service build — bespoke per company, priced as a build, changed only by that company. Coupling them would mean every client's handbook edit touches the training build, and every training update risks breaking a client's packet. Separate doors, same kitchen: one content spine (security, token conservation, AI rules) feeds both, adapted per audience.
Both platforms, offered as your company's own
Whichever platform a company buys, it arrives as that company's version — Platform 1 as their training portal, Platform 2 as their own onboarding / new-hire packet, under their name. Try the pitch swap: type a company name and see the branding flip on both.
Client-branded • SAS as provider • Both platforms
How the branding works
Two layers, always in this order:
1 — Client logo leads. In a pitch and in delivery, the client company's logo and name replace SAS at the top — the header, welcome screen, and new-hire packet cover. To their employees, this is their company's training.
2 — SAS branding stays on. Subtract Architect Studios logos and credit stay on the program as the provider behind it — footer, “Powered by / Training by SAS” line, and module credits. We don't disappear; we just don't lead.
What they get — two platforms Platform 1: Core + token conservation (Track 2) + security & AI optimization (Tracks 1, 3, 4, 5, 6). Platform 2: their custom Day 0–90 onboarding build — handbook, tools, policies, role pathways — separate from Platform 1, linked at Week 1.
Pitch preview — swap the logo
Type a prospect's name to preview their branded version. Nothing is saved — it's a live pitch mock.
−
Subtract Architect StudiosCorporate Training Portal — Master version
Welcome — two platforms, one place to start
Platform 1: Training — core, token conservation & AI optimization, security protocols, threats, scams, management. Platform 2: Your custom Day 0–90 onboarding.
In the client version, the client's mark leads at the top — and the SAS credit line stays in the footer, exactly as it does here.
Two Blueprints — one per platform
The old single blueprint is split. Blueprint A specifies the training product. Blueprint B specifies the custom onboarding build. SAS pitches from both — a client can take one without the other.
Blueprints A + B • Client-company edition
What this is — and is not
Two products SAS sells. Platform 1 (Training) and Platform 2 (Custom Onboarding) are sold separately to companies, for those companies' employees. SAS is seller/provider for both.
Neither is internal SAS training. “New hires,” “all staff,” “managers,” “your teams” always mean the client company's people. “In-house” in Platform 2 means the client's house.
Branding, both platforms: client logo/name leads — header, welcome, packet cover. SAS logos + “Training / Platform by Subtract Architect Studios” credit stay on as provider.
Blueprint A — Platform 1
Training: Token Economics / AI Optimization / Security
Standardised. Same structure in every client's version; only branding + company policies/tools examples change. Updated centrally by SAS.
Track 1 — Core for Everyone (5) — Passwords/passkeys/MFA • phishing • data & sharing • safe AI • incident reporting.
Track 2 — Token Conservation, Security & AI Optimization (6) — Token Economics 101 • prompt cost reduction • right model/right task • agentic cost control • monitoring/governance • AI budget strategy.
34 modules • Foundation → Practitioner → Leader • Priced as a product
Blueprint B — Platform 2
Custom Onboarding: Your In-House New-Hire Platform
Bespoke. Built per company from their handbook, tools, policies and roles. No standard packet — the blueprint is a build spec, filled in with the client.
Journey — Day 0–90 (6 core modules, 0.1–0.6) — Welcome & your story • Day-1 security gate (no access before it) • your tools & ways of working • AI acceptable use & data basics (your rules) • role pathway & first assignments • 30-60-90 check-ins & manager sign-off.
Custom sections (client chooses) — Company handbook & values • Tools & access map • Policies & sign-offs • Role pathways by department • Manager check-in templates • First-week checklist.
Build inputs we need from the client — Logo/brand • org chart & roles • tool stack • policies • who approves access • 30-60-90 expectations per role.
Handoff rule — Week 1, new hires cross into Platform 1 Track 1 Core, then Track 2. Platform 2 owns the journey; Platform 1 owns the curriculum. The link is a handoff, not a merge.
6 core modules + custom sections • Day 0–90 • Priced as a custom build
Download both blueprints
One file, two blueprints — A (Training) and B (Onboarding) kept separate inside it, with the same client-company wording.
Blueprint A + Blueprint B in one file — client logo leads, SAS credit retained, platforms kept separate.
SUBTRACT ARCHITECT STUDIOS — TWO PLATFORMS, TWO BLUEPRINTS
Client-Company Edition (split rebuild, Nov 1 2026)
COMMON RULES (BOTH PLATFORMS)
- Products SAS sells to companies, for those companies' employees. SAS is seller/provider.
- NOT internal SAS training. "New hires / staff / managers / your teams" = the client company's people. "In-house" = the client's house.
- Branding: client logo/name leads (header, welcome, cover). SAS logos + provider credit stay on (footer, credits).
============================================================
BLUEPRINT A — PLATFORM 1: TRAINING
Token Economics / AI Optimization / Security
Standardised product, built once, sold many times. 34 modules, Tracks 1-6.
============================================================
Track 1 — Core for Everyone (5, Foundation)
Track 2 — Token Conservation, Security & AI Optimization (6, Practitioner) — token conservation, right model/right task, agentic cost control, governance, AI budget
Track 3 — Security Protocols: Design + Practice (6, Practitioner)
Track 4 — Malware, Virus & Threat Education (6, Foundation)
Track 5 — Scam Intelligence, living track (6, Foundation; CISA / FTC / FBI IC3, monthly)
Track 6 — Management Strategy & Leadership (5, Leader; client managers/execs only)
Electives A-D — Finance/Admin, Property/Real Estate, Frontline/Reception, IT/Operations (after Day 30)
============================================================
BLUEPRINT B — PLATFORM 2: CUSTOM ONBOARDING
In-House Custom Onboarding Platform — bespoke per company
6 core modules + custom sections, Day 0-90
============================================================
0.1 Welcome to Your Company
0.2 Day-1 Security Gate (no access before MFA/passkeys/password manager + data rules)
0.3 Tools, Access & How Your Company Works (client's stack)
0.4 AI Acceptable Use & Data Handling Basics (client's rules)
0.5 Role Pathway & First Assignments (per role)
0.6 30-60-90 Check-ins & Manager Sign-Off
Custom sections: handbook/values, tools & access map, policies & sign-offs, role pathways, manager templates, first-week checklist.
Handoff: Week 1 new hires cross into Platform 1 Track 1, then Track 2. Platform 2 owns the journey; Platform 1 owns the curriculum.
WHY SEPARATE: Training is standardised and centrally updated. Onboarding is bespoke and changed only by that client. Separate doors, same kitchen — one content spine feeds both.
Training / Platforms by Subtract Architect Studios — Intelligence by Subtraction
Platform 1 — Training Product
Token Economics / AI Optimization / Security
Standardised curriculum — Tracks 1–6, 34 modules. Same in every client's branded version. Search and filter below apply to Platform 1 only; Platform 2 has its own workspace underneath.
34 modules • Tracks 1–6
FOUNDATION = EVERYONE • PRACTITIONER = ROLE DEPTH • LEADER = MANAGERS & EXECS. MARK COMPLETE — SESSION-ONLY.
No Platform 1 modules match that search. Try “token”, “phish”, “incident”, “prompt”, or “backup”.
Platform 2 — Custom Build • Separate from Platform 1
In-House Custom Onboarding Platform
Not a track inside training. This is a company's own new-hire platform, built for that company: their Day 0–90 journey, handbook, tools, policies and role pathways. The 6 core modules below are the fixed spine — everything around them is customised per client.
Day 0–90 • 6 core + custom
Your new hires' Day 0–90 journey — Platform 2 only
Security before access, every time. No system or customer-data access before the Day-1 gate is complete.
Hard rule — Platform 2 gateMFA / passkeys on, password manager set up, data rules signed off — before any access (Module 0.2).
Day 1
Secure firstWelcome to your company • Day-1 security gate (0.2)
Week 1
Tools & foundationsYour tools & access, AI acceptable use, data basics — then handoff to Platform 1 Track 1
Day 30
First check-inRole pathway underway • Manager review • Electives assigned
Day 60
Trusted contributorReal work under review • Scenario labs passed
Day 90
Sign-off30-60-90 review • Role pathway confirmed
What makes Platform 2 custom — per company
🏢 Your handbook & story
Your values, how decisions get made, who does what — written in your voice, not a template.
🧰 Your tools & access map
Exact stack, who provisions what, Day-1 checklist tied to your systems — not generic software names.
📋 Your policies & sign-offs
AI acceptable use, data handling, remote work — your rules, with tracked sign-off per hire.
🗺️ Role pathways
A different Week 1–90 path per role/department, with first assignments under review.
👥 Manager check-ins
Structured 30-60-90 templates with outcomes, not attendance — manager owns the sign-off.
🔗 Handoff to Platform 1
Platform 2 ends where training begins: Week 1 hires flow into Track 1 Core + Track 2. One link, two systems.
Build your onboarding packet — pick your sections
For a pitch, tick what this company needs. This previews the custom build scope for Platform 2.
Your Platform 2 packet outline
Updates live. This is the build spec we'd confirm with the client before building.
Role Electives — Platform 1
Part of the Training platform, on top of Tracks 1–6 — assigned by role and risk, not by rank. Assigned via Platform 2 at Day 30, delivered in Platform 1.
Platform 1 Electives • Assign after Day 30
Elective A
Finance / Admin
For anyone who touches invoices, payroll, or payments.
Payments fraud & BEC deep dive (extends 5.1)
Two-person payment verification drills
Vendor bank-change procedure
Elective B
Property Management / Real Estate
For teams handling closings, rents, and tenant data.
Wire fraud at closing — verify out-of-band
Tenant data: collection, storage, redaction
Rental & listing scams (extends 5.5)
Elective C
Frontline / Reception
For the first voice and first inbox a scammer meets.
Phone & visitor verification scripts
Fake tech-support & helpdesk calls (5.4)
Calm escalation without blame
Elective D
IT / Operations
For admins and operators who hold the keys.
Least-privilege reviews & access audits (3.1)
Patching, backups & tested restores (3.4, 4.4)
Incident runbook leadership (3.5)
Platform 1 · Track 5 Alert Center — Scam Intelligence
The living face of Platform 1 Track 5. Short alert lessons from current patterns — if an employee sees one, the rule is the action: stop, and verify through a separate trusted channel.
Platform 1 • Track 5 • Monthly • All staff
Sources — regulator-grade only: Scam Intelligence lessons and alerts are sourced only from CISA, the FTC, and FBI IC3. No social-media roundups, no unsourced “viral scam” claims. New patterns enter the track only with a regulator source behind them.
Security Protocol Builder — Platform 1
Part of Platform 1, Track 3 (Module 3.6) and the Track 6 workshop for managers. Pick only the controls your team will actually follow, then copy or download the one-page protocol.
Platform 1 • Track 3.6 • Track 6.1
1 — Choose your controls
Tap to include a control. Aim for 6–9 for a team protocol.
2 — Your one-page protocol
Updates live as you choose. Share it in your team channel and review it monthly.
Protocol design rule (Track 3): Risk assessment → policy → checklist → drill. Every rule needs an owner, a verification step, and an exception path. If a rule has none of those, subtract it.
Knowledge Check
Five questions drawn from Tracks 1, 2, 4, and 5 — a sample of the checks built into the client packet. This is a learning check, not a test — explanations appear after each answer, keyed to the track numbering.