Additional named phone user + number
For another named user: available Canadian number selection, suite-native assignment, voicemail, emergency-address validation, a non-emergency call test, and handoff.
Available by requestCustom quote after review
What you get
A working setup, its recovery path, and the instructions to own it.
The package is designed around an operational handoff. Product names may change; ownership and acceptance boundaries do not.
The interactive map needs JavaScript. The complete text outline is available below.
Read the complete map as text
Startup Digital Foundation
- 01 · Customer ownership
- What this layer does
- Purpose: the business controls the identities, services, billing relationships, and recovery decisions that matter.
- Named identities
- Setup: one to three named users, MFA, role boundaries, and a tested break-glass path.
- Proof: owner and recovery custodian recorded.
- Domain and workspace
- Setup: one client-owned domain and one Microsoft 365 or Google Workspace tenant.
- Proof: administrative custody read back with the founder.
- Business phone
- Setup: one client-selected Canadian number assigned to one named user or account.
- Proof: assignment and non-emergency test recorded.
- AI account and API key
- Setup: one client-owned provider account and one project-scoped key, with billing and usage protections where available.
- Proof: custody, safe storage, and revocation steps handed over.
- What this layer does
- 02 · Working system
- What this layer does
- Purpose: the small operating layer people use every day is organized, supported, and understandable.
- Communication
- Setup: business email, calendar, meetings, and the assigned business number.
- Proof: sender and calling paths checked.
- Files and work
- Setup: one document home, a simple work view, and a usable SOP index.
- Proof: location and ownership inventory delivered.
- Devices and passwords
- Setup: a supported baseline for up to three business devices and a client-controlled team vault.
- Proof: device and administrator records delivered.
- One low-risk automation
- Setup: a bounded workflow with an owner, manual fallback, error path, and disable step.
- Proof: fallback and disable step exercised.
- What this layer does
- 03 · Recovery + handoff
- What this layer does
- Purpose: the founder receives evidence, guidance, and a practical way back in without depending on the provider.
- Backup and restore
- Setup: a client-owned backup path and one agreed item restored and recorded.
- Proof: bounded restore receipt delivered.
- Evidence
- Setup: states, owners, and read-back evidence distinguish verified work from open work.
- Proof: evidence matrix reviewed with the founder.
- Guides and inventories
- Setup: quick-start guidance, administrator guidance, and current ownership inventories.
- Proof: operator read-back completed.
- Closeout
- Setup: provider access is transferred or removed, while residual risks remain visible for acceptance.
- Proof: access closeout and remaining risks recorded.
- What this layer does
This shows the delivery relationship between the layers. It is not a network architecture diagram or a promise that every vendor supports the same controls.
Delivered together
The system and the explanation.
- Inventories
- Users, administrators, devices, domains, vendors, data owners, and recovery owners.
- Working guides
- Employee quick-start, administrator notes, onboarding, offboarding, outage, and account-loss steps.
- Evidence
- A control matrix that separates verified, not applicable, open, and blocked items.
- Recovery receipt
- A record of one agreed restore path, including exactly what that test did and did not prove.
Customer owned
Subscriptions and renewals do not disappear inside a bundle.
The customer owns the domain, tenants, administrative identities, data, telephone number, AI provider account and credentials, billing relationships, and renewal choices. Vendor costs are separate and require approval before any purchase or activation.
The fit check separates the fixed setup quote from vendor subscriptions, calling plans, usage, renewals, and taxes so those costs remain visible.
- Customer owner
- Named founder or delegated administrator Recorded
- Recovery custody
- Placed directly in customer-controlled custody Transferred
- Administrator access
- Customer access confirmed; provider access closed out Read back
- Evidence pack
- Inventories, control states, and bounded restore receipt Delivered
- Residual risk
- Open decisions, dependencies, and accepted exceptions Visible
Closeout is complete only when ownership, recovery, evidence, and unresolved decisions are legible to the customer.