Pricing & proposals
Start with a free diagnostic, use paid discovery when the operating problem needs a formal design, and approve implementation only after scope, access, complexity, responsibilities, and acceptance are understood.
Four engagement levels
The assessments are different diagnostic entry points. They route businesses into one of four commercial levels rather than creating a separate paid service for every diagnostic question.
Best for
One priority workflow that needs a formal implementation design
Duration
Approximately 10 business days
Working sessions
Up to three stakeholder interviews
Deliverables
Current-state map, system inventory, target design, and implementation boundary
Decision point
Approve, revise, or stop before production implementation access
Operating-Layer Blueprint: $3,500 fixed within this stated boundary.
Check assessment suitabilityFree
Diagnostic entry point
Identify the operating problem and the most appropriate next step before detailed discovery or implementation access.
Does not include stakeholder interviews, detailed architecture, custom workflow mapping, or an implementation plan.
$3,500 fixed
Approximately 10 business days
Turn one priority workflow into a documented current state, target design, implementation boundary, and proposal.
This is paid discovery and design. It does not include production configuration, migration, integration, or automation.
$9,500-$17,500
Typical project budget
Implement one bounded workflow such as RFQ intake, estimating handoff, proposal control, document control, follow-up, or reporting.
The final price is quoted after scope, access, migration, integration, and approval complexity are confirmed.
$30,000-$75,000+
Phased custom programme
Connect several workflows, shared records, reporting, permissions, integrations, and controlled automation across the business.
A paid blueprint is required before the final scope, phases, responsibilities, timeline, and fixed price are agreed.
All figures in USD
Ranges are planning guidance before a written proposal. Taxes, approved travel, and third-party platform or usage charges are excluded.
Budget drivers
System restrictions, poor historical data, document variation, AI evaluation, security requirements, and compressed schedules create real design and validation effort.
These allowances are not automatic line items. The proposal uses only the factors that apply after the relevant systems, samples, permissions, data volumes, and constraints have been reviewed.
Payment milestones
Commercial stages match the size of the engagement and the moments when design, build, deployment, and handover can be inspected.
Blueprint
100%
Before kickoff
The fixed discovery engagement begins once scope, participants, confidentiality, and payment are confirmed.
Implementation under $20,000
50 / 30 / 20
Kickoff / build approval / handover
Payments follow delivery progress and named approval points rather than elapsed time alone.
Larger phased engagement
30 / 30 / 30 / 10
Kickoff / design / deployment / handover
Each phase has agreed deliverables, responsibilities, acceptance criteria, and approval authority.
Commercial boundaries
Dependable delivery requires more than a fee. The agreement identifies inputs, authority, dependencies, exclusions, tests, acceptance, and what happens when circumstances change.
Software subscriptions, hosting, storage, API, AI usage, vendor licences, and approved travel are paid separately by the client.
Work outside the signed scope begins only after the effect on price, timing, responsibilities, and acceptance is documented and approved.
The client provides authorised access, accurate available information, named decision-makers, and timely reviews. Hidden constraints or delayed approvals may change the plan.
A proposal states deliverables, exclusions, dependencies, test conditions, handover outputs, and the people authorised to accept the work.
The accepted implementation includes a defined period to correct defects against scope. Monitoring ownership transfers at handover, while enhancements and vendor-driven changes remain visible new work.
Review handover and closureCorrection of accepted-scope defects during the stated 30-day or 60-day period, with the agreed reporting and resolution process.
New features, changed rules, extra records, vendor changes, expanded integrations, new reports, and ongoing administration are scoped separately.
Pricing questions
The written proposal remains the controlling commercial document for a specific engagement.
View the complete FAQWorkflow assessment
Describe the operational problem, systems, owners, restrictions, and desired result. Do not provide passwords, API keys, MFA codes, or unrestricted production access through the public assessment.
