Configure
Structures, settings, and components from the approved Blueprint — in your account.
Our Process · 04
Build what you approved.
Build implements the approved Blueprint inside your environment: configure, automate, test, and launch. Every environment is different, so pricing is set after your free assessment. Blueprint is required before we start.
Priced after assessment
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 implementation can include.
The Standard package covers these areas, up to the included quantities. 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.
Priced after assessment
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?
Standard Build of the approved Blueprint, within the included quantities.
Scope from your Blueprint
Standard Build. Included quantities.
We implement what the approved Blueprint named, up to these caps. Past a cap, the extra is a change order or Phase 2, and we say so before we build it.
CRM pipeline
1 primary, up to 6 stages
Forms / intake
3
Automations / flows
5
Documents / templates
5
Dashboards / views
2
Project / task templates
2
Client portal path
1 happy path
Billing workflow
1 invoice / payment path
Integrations
1 named — or none, if the Blueprint says so
Roles & permissions
Standard set from the Blueprint
Testing + launch
Included
Handoff
1 walkthrough and notes
If the Blueprint needs more than the Standard package, the extra is scoped as a change order or Phase 2. The SuiteDash software subscription is not included. 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 named it and it fits the included quantities, it is in the Standard Build.
Small adjustment
A small change that stays inside those caps may fit without a change order.
New requirement
Past a cap, or a new path, is a change order or Phase 2.
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
- Work past the included quantities
- 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. The Standard package implements that plan within the included quantities — especially for SuiteDash, and the same rule applies across other WrightClick doors.
Not sure where you are? Start with a Free Assessment, or review Onboard and Blueprint.
WrightClick path
Four clear stages.
Standard engagement ladder for SuiteDash work and other WrightClick doors. You are on Build.
- Find the friction
Free Assessment
Map your goals, current tools, and where WrightClick fits before you commit.
View Free Assessment → - Gather what matters
- Plan it clearly
- Build it safely
FAQ
Straight answers.
Does Build include a SuiteDash subscription?
No. You hold the SuiteDash subscription (or your stack). Build covers 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.
How is Build priced?
Build is priced after your free assessment, once the approved Blueprint shows what needs to be built. It implements that plan within the included quantities. If the Blueprint needs more, the extra is a change order or Phase 2, and we say so before we build it. The SuiteDash subscription is still not included.
Can I add features during Build?
If it was in the approved Blueprint and it fits the included quantities, it is in the Standard Build. A small adjustment inside those caps may fit. Past a cap, or a new path, is a change order or Phase 2 — we will say so before we build it.
Do I need Blueprint before Build?
Yes. Build implements what you approved, within the Standard package quantities. Without Blueprint, we would not know what to configure — or what belongs in a change order. 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.