You already have a recurring workflow with an owner, realistic examples, and a meaningful business measure.
Scope the Trusted Workflow Pilot.Professional services Pricing
Start with one workflow. Invest further when it proves valuable.
The standard starting point is a fixed-scope Trusted Workflow Pilot. It establishes a baseline, implements and tests the new operating method, enables the team, and ends with evidence for a scale, revise, automate-selected-steps, or stop decision.
01 How the commercial path works
A measured implementation first. Expansion only when warranted.
You have several possible workflows but cannot yet identify the best pilot candidate.
Use the optional Workflow Selection Sprint.The pilot compares the new method with the baseline and makes the next investment explicit.
Scale, revise, automate selected steps, or stop.A proven workflow may justify a portfolio rollout, managed enablement, or a separately scoped systems build.
The intervention depends on the evidence.02 Published starting prices
Final scope reflects workflow complexity, review and security requirements, delivery format, participants, and systems involved. Each statement of work names the inclusions, boundaries, owners, and payment milestones before kickoff.
Trusted Workflow Pilot
Implement one recurring workflow, test it on real work, and make a measured rollout decision.
Included
- One recurring workflow in one business function
- Five to twelve participating users
- Current-state map and baseline measurement
- Workflow implementation, realistic testing, and quality controls
- Role-specific enablement and an operating playbook
- Before-and-after measurement and a rollout recommendation
Workflow Portfolio Rollout
Apply the proven method to related workflows, teams, or practices.
Included
- Multiple related workflow redesigns
- Shared operating standards and reusable context libraries
- Evaluation systems and manager enablement
- Internal champion preparation
- Adoption measurement and cross-team governance
Managed Workflow Enablement
Maintain implemented workflows, onboard users, and keep performance visible.
Included
- Workflow-performance reviews and adoption reviews
- Office hours and manager coaching
- New-user onboarding
- Evaluation-rubric, context, and playbook maintenance
- Exception reviews and governance refreshes
Automation and Systems Build
Productionize selected steps only after the workflow has been tested and assigned an owner.
Included
- Production integration and human approval gates
- Document processing, internal assistants, or knowledge retrieval
- CRM and project-management connections where appropriate
- Monitoring, error handling, and operating documentation
- Maintenance and infrastructure priced to the selected system
03 Commercial terms
What is included, what is separate, and when you pay.
Travel, licenses, security review, minimums, and custom integrations are handled explicitly—never left as an assumption after work begins.
Milestones stated before kickoff
Standard fixed-scope work is invoiced 50% at kickoff and 50% on delivery. Managed enablement is billed monthly in advance. Larger rollouts and systems builds use milestones defined in the statement of work.
Pass-through and specialist costs
Software and AI-tool licenses are paid by the client. Pre-approved travel is invoiced at cost. Legal or regulatory advice, production infrastructure, and third-party vendor fees are not included.
Data boundaries agreed first
Approved tools, data classes, and access boundaries are agreed during scoping. A standard security questionnaire is included; extended procurement, custom controls, or enterprise security reviews are scoped separately.
Published prices are starting points
The Trusted Workflow Pilot starts at $8,000. Portfolio rollout starts at approximately $18,000. Managed enablement starts at $3,000 per month. Final fees reflect workflow complexity, participants, review requirements, and delivery format.
Custom systems are separate work
Major integrations and production software engineering are excluded from the standard pilot. They require technical discovery and a separate statement of work covering build, monitoring, maintenance, infrastructure, and support.
Clear scope, ownership, and change control
Each engagement uses an MSA and statement of work. Scope changes, additional workflows, extra participants, and revisions beyond the agreed review cycles are priced before the work expands.
04 Standard pilot boundaries
The pilot price covers workflow implementation—not an open-ended transformation program.
Not included in the standard pilot
- Enterprise-wide transformation strategy
- Large custom integrations or production software engineering
- Unlimited revisions or ongoing operational staffing
- Tool licenses, production infrastructure, or third-party fees
- Legal or regulatory advice
- Done-for-you delivery of the client’s core professional work
A clear first step Bring one workflow
Scope the work before you commit to the spend.
A 30-minute conversation is enough to assess fit, clarify the standard pilot boundary, and identify what would affect the final fee.
Scope a workflow pilot