Bookwiser | Premium Québec and Canada control plane

Bookwiser Québec onboarding v1

Create a real Bookwiser workspace scaffold on a French-first Québec launch path.

This page stays portal-safe: the browser only submits basic client identity input. The API issues the session, creates the client profile scaffold, and returns the onboarding path. For Québec-facing launch lanes, the commercial journey is French-first and closed-beta safe, while service choice, EMS/NMES seat mix, bundle-family review, pricing posture, and engagement acceptance remain API-owned.

Onboarding signal

Session status

Anonymous

Auth posture remains API-issued; this shell only reflects the returned session snapshot.

Onboarding signal

Recommended path

/login

The onboarding path is chosen by the API runtime, including the French-first Québec launch posture, rather than by the browser route alone.

Onboarding signal

Landing label

The landing label follows the runtime-recommended client path.

Onboarding signal

Workspace

Pending signup

Workspace scaffolding is created server-side during registration.

Onboarding signal

Client profile

Pending signup

Client-profile persistence now starts at signup instead of after a separate handoff.

Onboarding signal

Service posture

service_selection_pending

Service choice, language posture, and engagement setup remain bounded to later API-guided steps.

API base URL: https://preview-api.bookwiser.ca

Trust signals

A more modern guided-review lane still keeps the launch contract honest.

The onboarding experience can feel calmer and clearer while still telling the truth about what the browser does and does not control.

Canada-first runtime

AWS ca-central-1 production path

Shipped

The launch story stays anchored to a Canada-first AWS posture so hosted trust cues in-product match the active launch packet.

Canada data path

Review-bounded control

Audit-grade evidence above execution systems

Shipped

Bookwiser coordinates packets, approvals, evidence, and follow-through without pretending the browser owns filing, payroll submission, money movement, or trust execution.

Bounded authority

Competitor gap closure

Breadth work is real, but still incomplete

Partial

Bank-connect, Quebec depth, mobile polish, AI data-entry, and reporting are now governed as explicit expansion lanes instead of implied completeness.

Governed modernization

Certification ladder

Regulated execution remains gated

Coming Soon - Certification Needed

Formal filing, payroll submission, money movement, and similar regulated lanes stay outside the product until legal or certification posture changes.

No hidden authority

Onboarding status

Status language now makes the first-run path easier to trust.

That helps the UI feel more product-grade without flattening real commercial and legal boundaries.

Workspace scaffold

Shipped

The API creates a real workspace scaffold and next path instead of leaving the first-run experience as a thin marketing handoff.

API-owned onboarding truth

Visible in-product and already supportable within the current bounded runtime.

French-first guided review

Partial

Language, service choice, and commercial framing are real, but they still remain guided and API-owned rather than browser-certified.

Quebec launch path

Real and progressing, but still incomplete enough that UI and commercial copy must stay explicit.

Certification-bound future lanes

Coming Soon - Certification Needed

The onboarding surface can prepare future regulated pathways without implying that those authorities already exist.

Future capability

Roadmapped intentionally, but blocked on licensing, regulated partner infrastructure, or formal certification.

Self-serve regulated execution

Forbidden

This page must not imply silent filing, payroll submission, money movement, or browser-only contract authority.

Boundary preserved

Must not be implied or relabeled as shipped under the current truth contract.

Commercial journey

From first click to portfolio review, the Québec launch path now reads as one premium French-first commercial system.

This route opens the journey, but it does not own pricing, bundle selection signoff, acceptance, adhesion-language sufficiency, or regulated execution. The browser can preview the path. The API keeps the commercial and language truth.

Journey signal

Step 01

French-first workspace scaffold

Signup creates the client profile scaffold and runtime-safe session before any commercial, adhesion-style, or regulated step appears.

Journey signal

Step 02

French-first service choice

The API keeps the starter-path catalog, Québec launchpack posture, and draft commercial framing truthful before engagement acceptance.

Journey signal

Step 03

French-source engagement package

Commercial intent becomes durable only when the API persists the engagement-package version, EMS/NMES seat mix, guided bundle-family selection, acceptance hash, actor, and timestamp. The browser does not self-certify adhesion-language sufficiency.

Journey signal

Step 04

Closed-beta launch and portfolio review

Launch readiness and staff portfolio keep seat mix, bundle-family posture, signoff, pricing review, and commercial continuity visible without creating browser-owned quote, pricing, or language-validity authority.

Demo launchpack

Bookwiser sells as the control plane above execution systems

This guided entry page now carries the same demo-safe launchpack posture as staff commercial: explain why Bookwiser sits above execution systems, why bounded review is safer than unsafe autonomy, and how the platform compares against service firms and software suites without drifting into unsafe execution claims.

Launchpack signal

Positioning

Above the execution systems

Bookwiser coordinates evidence, packets, reviews, deadlines, and handoffs above ledgers, payroll tools, POS suites, practice systems, and other execution islands.

Launchpack signal

Safety argument

Bounded review beats unsafe autonomy

Automation helps the work, but posting, filing, remittance, trust execution, and money movement remain explicit stop-lines instead of hidden browser behavior.

Launchpack signal

Service-firm comparison

Visible operators, queues, and evidence

Service firms feel complete because humans absorb the work. Bookwiser answers with visible packets, owners, timelines, and review posture.

Launchpack signal

Software-suite comparison

One control plane, not scattered modules

Software suites feel complete because modules look unified. Bookwiser answers with one control plane across bookkeeping, tax-prep coordination, CRM/growth, ERP review, and partner handoffs.

Why Bookwiser wins the first conversation

Bounded review is the premium posture, not a missing feature

Bookwiser is commercially stronger when it shows the hard line clearly: the platform helps evidence, packets, routing, review, and follow-through move faster, but it does not silently become the ledger, payroll executor, trust executor, POS, ERP, or regulator actor.

Start the conversation by showing that Bookwiser sits above the execution systems instead of pretending to replace every one of them.

Explain that bounded review is safer than unsafe autonomy because packets, approvals, evidence, and human signoff stay explicit.

Compare against service firms by showing that Bookwiser makes the work visible and durable instead of black-boxing it behind a monthly service promise.

Compare against software suites by showing one operator-grade control plane that joins intake, bookkeeping, tax-prep coordination, CRM/growth, ERP review, and partner handoffs.

First-run guide

The onboarding lane now teaches the next safe move before the workspace exists

First-run onboarding, legal review, and workspace creation now read as one premium guided flow instead of a form plus disconnected follow-up screens.

Ready

Identity

Create the workspace scaffold

The browser collects only basic identity input while the API issues the session and client profile scaffold.

Auditable

Legal

Review the governed legal bundle

Québec-facing launch stays French-first and version-auditable before any deeper onboarding step becomes durable.

Pending

Continue

/login

The API returns the next onboarding path so the user lands in a guided continuation route instead of being dropped back into generic login.

The guided lane is premium, but seat mix, bundle-family posture, pricing review, signoff, and adhesion-language sufficiency remain API-owned.

Contract machine

The Québec onboarding lane now previews the real contract lifecycle behind pricing.

This route can preview term selection, seat schedules, French-first source-contract review, companion English visibility, API-recorded acceptance, and reviewed addenda without turning the browser into contract authority.

Loading state

Loading contract runtime

The portal is waiting for the API-owned runtime to return the current surface state.

Onboarding entry

French-first closed beta

Create your workspace scaffold

Successful signup leaves the user in the French-first onboarding lane rather than sending them back to generic login. Pricing, bundle-family review, signoff, and engagement-language validity remain API-owned.

Québec launch paths now start in a French-first, closed-beta-safe onboarding lane. The browser only collects identity input; the API keeps language, commercial, and signoff truth.

Existing user login

What is real

French-first workspace scaffold

The onboarding shell is premium, but the truth still comes from the API-owned registration runtime. The browser does not own pricing, bundle-family signoff, or Québec contract-language sufficiency.

The API issues a valid session cookie during signup.

The API persists a client profile scaffold instead of creating only a session.

The returned onboarding path stays pinned to a guided, French-first, closed-beta-safe onboarding flow.

Stay in onboarding Open login

Acceptation juridique versionnée

Review the governed legal bundle before moving deeper into onboarding

Signup remains a portal-safe identity step, but the legal bundle, French-first Québec sequence, and audited consent record now sit one click away in the same onboarding surface.

Chargement du bundle juridique courant…

Les versions de politiques, la surface d’acceptation et l’horodatage seront rattachés à leah@example.com côté API.

Session, routing, and boundary posture stay visible before you enter a lane.

Review the governed legal bundle before moving deeper into onboarding