Find unknowns
Missing information, dependencies, and unanswered questions that would stall design.
Our Process · 02
Prepare cleanlybefore design.
Onboard is a fixed $995 USD stage that gathers access, systems, processes, assets, and technical requirements — so Blueprint designs from evidence, not assumptions. You leave with a Project Readiness Report.
$995 USD
What happens
Why Onboard exists.
Find what is missing, what is risky, and what Blueprint should solve — before design begins.
Find risks
Data, integration, access, and workflow issues that change scope if they stay hidden.
Get organized
Assets, access, and business information the next stages can actually use.
Set direction
What Blueprint needs to solve — from evidence, not assumptions.
$995 USD
What’s included.
A fixed readiness stage — the evidence, not the design.
Structured project intake
A calm file of goals, owners, and what this work is actually for.
Requirements review
Systems, integrations, users, data, and access — SuiteDash first, other doors when they apply.
Risk & blocker analysis
Data, integration, access, and workflow issues that would change scope later.
Readiness recommendations
What to resolve, what can wait, and what Blueprint should treat as a constraint.
Project Readiness Report
A documented foundation Blueprint can design from — not a pile of notes.
The Readiness Report is yours whether or not you continue to Blueprint.
Discovery
What we gather.
SuiteDash is the usual canvas. The same intake applies when the work spans other WrightClick doors.
Business overview
What you do, who you serve, and what this project is for.
Current systems
Tools in use today — SuiteDash or otherwise — and who owns them.
Users & roles
Who needs access, and what they should be able to do.
Key processes
The paths that matter: intake, delivery, billing, handoffs.
Data & migration
What should move, what can stay, and what is messy.
Integrations
What must connect, and what should stay alone.
Branding & assets
Logos, docs, lists, and files the next stages will need.
Security & access
Logins, permissions, and who can grant them.
Constraints & priorities
Deadlines, budget bounds, and what cannot slip.
How we work
Four steps to readiness.
Intake, review, analyze, then write the Project Readiness Report Blueprint should start from.
Intake
Collect access, assets, and the questions that start the file.
Review
Systems, integrations, users, data, and how work happens today.
Analyze
Risks, blockers, gaps, and what would stall Blueprint.
Report
A Project Readiness Report Blueprint can design from.
The ladder
Where Onboard sits.
Assessment checks fit. Onboard gathers the truth. Blueprint decides how it should work.
Free
Free Assessment
Is this a fit?
Map goals and current tools before you commit to a paid stage.
Onboard
What are we working with?
Understand and prepare — access, systems, and the readiness Blueprint needs.
Blueprint
How should it work?
Architecture, workflows, and a Build roadmap from the Readiness Report.
Boundaries
What this stage is —and is not.
Onboard is
- Structured discovery
- Requirements gathering
- Current-system review
- Risk identification
- Readiness analysis
- Project Readiness Report
- Blueprint prep
Onboard is not
- Building automations
- Configuring workflows
- Dashboards
- Migrating data
- Implementing integrations
- Portal build
- Launching
Details
After Assessment.
Onboard follows a Free Assessment when you are ready to proceed. It is readiness for Blueprint — not a build.
Onboard is the bridge to Blueprint. Next is Blueprint, designed from the Project Readiness Report — not assumptions.
Still early? Start at Free Assessment.
WrightClick path
Four clear stages.
Standard engagement ladder for SuiteDash work and other WrightClick doors. You are on Onboard.
01
Free Assessment
Free
Map your goals, current tools, and where WrightClick fits before you commit.
View Free Assessment →02Onboard
$995 USD
Gather access, assets, users, data, and integrations so design starts clean.
You are here →03Blueprint
$1,999 USD
Design the architecture, workflows, and plan before build.
View Blueprint →04Build
Scoped
Implement what the Blueprint approved — systems, migrations, and integrations.
View Build →FAQ
Straight answers.
Why can’t we just start with Blueprint?
Blueprint designs from evidence. Without Onboard, we guess at access, systems, processes, and constraints — then redesign mid-plan. Onboard is the readiness stage so Blueprint starts from what is true.
Why does Onboard cost $995?
It is a fixed readiness stage, not a down payment on Blueprint. Gathering access, reviewing systems, spotting risks, and writing a Project Readiness Report takes real time. The fee stays the same so the work is honest — not padded into a later design quote.
Does Onboard include SuiteDash configuration?
No. Onboard collects requirements and readiness. Configuration, workflows, and automations belong to later stages. SuiteDash is the usual canvas; the same rule applies across doors.
What do I receive?
A Project Readiness Report: what we found, what is missing, risks and blockers, and recommendations so Blueprint can design from evidence.
What happens to the Readiness Report?
It becomes the input to Blueprint. The report is the documented foundation — access, systems, processes, assets, and technical requirements — so design is not a guessing game.
Am I obligated to continue to Blueprint?
No. Onboard is a standalone stage. The Readiness Report is yours whether or not you continue. You can stop, take it in-house, or move to Blueprint when ready.