Configure
Structures, settings, and components from the approved Blueprint — in your account.
What happens
What Build means.
Execution against the plan — configure, automate, test, launch. Not open-ended tinkering.
Automate
Triggers, notifications, and handoffs the plan already approved — nothing extra for the sake of it.
Test
Workflows, permissions, and the client path validated before anyone relies on them.
Launch
Prepared for real use, then handed off so your team can run it.
Accounts
Your environment.Our implementation.
We configure inside your SuiteDash account — or the stack the Blueprint named. You keep the subscription. We do the build work.
You provide
- SuiteDash subscription (or your stack)
- Portal and domain
- Business data
- Access
- Decisions
WrightClick provides
- Configuration
- Workflow implementation
- Automation
- Testing
- Launch prep
Blueprint is the guide for what gets built.
Scope
What implementationcan include.
Specific scope comes from the approved Blueprint. SuiteDash is the usual canvas; the same list applies when the work spans other WrightClick doors.
CRM
Companies, contacts, and stages the Blueprint named.
Forms & intake
What you collect, from whom, and where it lands.
Automations
Triggers, notifications, and handoffs already approved.
Projects & tasks
Delivery work tracked the way the plan described.
Client portal
The happy path clients and staff will actually use.
Documents
Files, proposals, and templates tied to the next step.
Billing workflows
Invoices and payments that follow the work.
Integrations
Connect what must stay. Leave what should stay alone.
Roles & permissions
Who can see what — matched to real jobs, not “admin for all.”
How we work
Five steps to launch.
Confirm the approved list, configure, automate, test, then launch — without reopening design.
Confirm scope
Revisit the approved Blueprint so the Build list is still the list.
Configure
Structures, settings, roles, and components from the plan — in your account.
Automate
Triggers, notifications, and handoffs the Blueprint already approved.
Test
Workflows, permissions, and the client path on real routes — before go-live.
Launch
Prepare for real use, then hand off so your team can run it.
The ladder
Where Build sits.
Onboard gathers the truth. Blueprint decides how it should work. Build makes the approved plan real.
$995 USD
Onboard
What are we working with?
Access, assets, users, and the current system — so design starts from reality.
Blueprint
How should it work?
Architecture, workflows, and a Build roadmap you can approve.
Build
How do we make it real?
Implementation priced from the approved Blueprint.
Scoped
Why pricing varies.
Build is scoped from the approved Blueprint. Two implementations are rarely the same — the plan writes the work before we start, so the fee is not a guess and not a fixed package.
Workflows and structure
- Workflows
- Automation complexity
- CRM depth
- Portal setup
- Forms and documents
Connections and launch
- Projects
- Integrations
- Migration
- Testing
- Training
The SuiteDash software subscription is not included in the Build fee. You keep the account. We implement what you approved.
Protection
How we protect scope.
Mid-build ideas are welcome. They are not automatically in the Build.
In Blueprint
If the approved plan already named it, it is in the Build. Included.
Small adjustment
A small change that does not add a new workstream may fit inside the scoped Build.
New requirement
A new feature or path is a scope change — or the next phase.
Boundaries
What this stage is —and is not.
Build is
- Blueprint implementation
- Configuration
- Automation
- Portal setup
- Testing
- Launch prep
- Handoff
Build is not
- SuiteDash subscription
- A WrightClick-hosted portal
- A bundled software platform
- Unlimited future development
- Unscoped features
- Permanent admin
- Third-party licenses
Handoff
Typical completion.
A short checklist — so launch is a handoff, not a mystery.
Configured and tested
- Approved Blueprint items configured
- Automations live and tested
- Portal path usable
Ready to run
- Roles and permissions checked
- Handoff notes and training
- Known follow-ups documented
Details
After Blueprint.
Build starts when you approve the Blueprint. That is how we keep scope and price aligned — especially for SuiteDash implementations, and the same rule applies across other WrightClick doors.
Need the earlier stages? Assessment, Onboard, Blueprint.
WrightClick path
Four clear stages.
Standard engagement ladder for SuiteDash work and other WrightClick doors. You are on Build.
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.
View Onboard →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.
You are here →FAQ
Straight answers.
Does Build include a SuiteDash subscription?
No. You hold the SuiteDash subscription (or your stack). The Build fee is implementation — configuration, automation, testing, and launch prep — not software licensing.
Does WrightClick create a new portal?
No. We configure inside your account, per the approved Blueprint. Build is not a WrightClick-hosted portal and not a bundled platform we operate for you.
Why does pricing vary?
Implementations differ. Workflow count, automation complexity, CRM, portal, forms and documents, projects, integrations, migration, testing, and training all change the work. Blueprint writes that scope before we start — so the fee is not a guess.
Can I add features during Build?
If it was in the approved Blueprint, it is in the Build. A small adjustment that does not add a new workstream may fit. A new requirement is a scope change or a future phase — we will say so before we build it.
Do I need Blueprint before Build?
Yes. Build implements what you approved. Without Blueprint, scope and price would be a guess — which is how teams rebuild mid-project. Start at Free Assessment if you are earlier in the path.
What happens after Build?
Handoff: you can run what we implemented. Ongoing support is available separately — it is not assumed, and it is not permanent admin inside your account.