We take a company's existing new-hire packet — the forms, the handbook, the way things actually get done there — and rebuild it as their own online onboarding system. Their name and logo lead. Their roles, their locations, their Day 0–90. Subtract Architect Studios builds it and stays credited as the provider.
How the swap works: flip to the client-branded version and the client's name and mark take the header — the SAS provider credit in the footer stays exactly where it is. The sample client shown is illustrative, for pitch demonstration only.
Our standardized curriculum — token conservation, AI optimization, and security training for employees. Built once by SAS, delivered to many companies, always SAS-led content. It has its own portal and its own blueprint.
Separate platform — not part of this page's buildBespoke per company: their new-hire packet, their role pathways, their Day 0–90 journey, their logo leading. Priced and built like a custom system, because it is one.
You are viewing this platformEvery client's platform runs the same spine — before day one through the first quarter — but the content inside each stage is theirs: their forms, their people, their milestones. Pick a stage to see what the new hire and their manager each get.
Six components, assembled per company. Nothing ships from a generic template — each one is filled from the client's own material during the build.
The paper/PDF new-hire packet — offer paperwork, tax and eligibility forms, handbook acknowledgment — rebuilt as guided online steps with nothing to print, lose, or re-send.
A new hire doesn't get everyone's onboarding. Each role gets its own pathway: the tools, training, and first assignments that role actually needs, in the order they'll use them.
Who their manager is, who their buddy is, where things are, who to ask for what — the client's own org chart and locations, so day one doesn't start with guessing.
Scheduled 30/60/90-day check-ins with prompts built from the client's own expectations for the role — so reviews happen on time and cover the same ground for every hire.
The client's handbook and policies as searchable, readable pages — with acknowledgment tracking, so HR can show who has read what, and when.
HR and managers see every hire's progress at a glance — who's complete, who's stalled, what paperwork is outstanding — instead of chasing it by email.
The platform is built around how the company actually hires. These are the pathway shapes we build from — each one mapped to the client's real roles during discovery.
Use this in a pitch conversation or a discovery call: pick the company's shape and the pieces they need, and it drafts the packet outline for their custom platform. Nothing is saved or sent — it's a working sketch for the conversation in front of you.
One view across every active hire — who's done, who's stuck, what paperwork is still out. The numbers below are a sample layout for demonstration, not a real client's data.
| New hire | Pathway | Stage | Status |
|---|---|---|---|
| Sample hire A | Office & Administration | Week 1 | On track |
| Sample hire B | Field & Crew | Day 30 | On track |
| Sample hire C | Sales & Client-Facing | Day 0 | Form outstanding |
| Sample hire D | Management | Day 60 | Check-in due |
Five stages, scoped per company. The client's team only has to show up to the first two — we do the building.
We sit with HR and a couple of managers: how hiring works today, where it breaks, what "ready" means per role.
Their existing packet, handbook, and forms are inventoried and mapped onto the Day 0–90 spine. Gaps get named, not papered over.
The platform is built with their branding leading, their pathways and policies in place, SAS credited as provider.
The next real hires go through it. We watch where they stall and fix the platform before it scales.
Full rollout to all hiring. The company runs it day to day; SAS stays on as provider for updates and changes.
The Custom Onboarding Platform now carries its own blueprint document — separate from the training platform's blueprint, because the products are separate. This is its structure.
The packet builder above drafts a per-company outline; this download is the platform blueprint structure itself — the document skeleton a client build is specified against.
Both platforms share one content spine underneath — a lesson or a policy written once, adapted per audience — but they are sold, branded, and built as two separate systems.