Pricing
Invest in operations that can scale.
Operational Discovery Audit on a fixed fee. Enterprise transformations are scoped fixed-fee following the audit. Optional follow-on support is quoted per engagement after handover. Fees exclude taxes and third-party costs unless stated otherwise.
Our guarantee
Fixed scope, fixed fee. You see the price before we start, with no hourly surprises on the audit or the build.
You keep everything, and can run it
Workflows, docs, and configs are yours, with no lock-in and no proprietary wrapper. Documentation and a handover mean your team can keep it running without us on call.
Qualified, founder-led delivery
Secure implementations delivered by qualified professionals with direct access to the architect doing the work. Scope, milestones, and controls agreed before kickoff.
Direct, fast replies
You hear back within 1 to 2 business days, straight from the person doing the work, not a ticket queue.
How it works
From readiness to handover
01
AI Governance Checklist
Free
15 controls to review with your operations and IT leaders.
Get the checklist02
Operational Discovery Audit
Fixed fee
Vendor review, operational baseline, and a prioritized business case.
Discuss an audit03
Scoped build
Scoped fixed fee
Enterprise transformations are scoped fixed-fee following the audit, with complexity reflected in your proposal.
Scope a transformation04
Handover & follow-on
Optional
Your team runs what we built. Book scoped fixes, integrations, or reviews when you need them, quoted per engagement.
See after deliveryWhat you pay for
Three tiers. No hidden scope.
Most clients start here
Operational Discovery Audit
- Vendor, model, and data-flow inventory
- Retention, access, and approval review
- Baseline for operating costs and billing delays
- Prioritized roadmap and business case
- Written findings and a scoped build proposal
Scoped build
- CRM, ERP, and operational integrations
- AI extraction and drafting where appropriate
- Human approvals and exception handling
- Deployment, monitoring, and acceptance checks
- Source, documentation, and team handover
Follow-on support
- Workflow fixes and small integrations
- Exception handling and monitoring tune-ups
- Governance reviews when vendors or access change
- Agreed response window defined in the proposal
- Quoted per block or phase
FAQ
Answers to the questions we get
Where do we start?
Use the free 15-point AI Governance Checklist with your IT and operations leads, or book a scoping call. An audit with a fixed fee agreed before kickoff establishes the risks, operational baseline, and priorities before a build.
What does the audit include?
The Operational Discovery Audit combines a vendor and data-flow review with an operational business case. You receive written findings, a prioritized roadmap, and a proposal for the build. The systems and workflows covered are agreed before kickoff.
How are transformation projects priced?
Enterprise transformations are scoped fixed-fee following the audit. Your proposal defines the exact scope, fee, and acceptance criteria based on stack complexity and delivery milestones.
What happens after handover?
Your team runs the workflows using the runbooks and configs we deliver. If something breaks or the business changes, you can request scoped follow-on work (fixes, integrations, or governance reviews), quoted per engagement with clear deliverables.
Are software costs and taxes included?
Quoted fees exclude applicable taxes unless stated otherwise. Vendor subscriptions, hosting, and model usage are separate unless expressly included in the proposal.
Do we need ongoing support after the build?
No. Handover is designed so your team can operate without us. Follow-on support is optional when you want help with a specific change, not a default fractional leadership role.
What is administrative burden?
It is the unpaid ops work your tools leave behind: retyping data, chasing status, assembling reports, and rebuilding the same setup checklist. Busywork is how it feels day to day. Administrative burden is the load that grows with volume even when headcount does not.
What happens on the hardest days?
The cracks show. Month-end, a volume spike, three new clients at once, or a key person out sick. The handoffs that felt manageable on a quiet Tuesday stack up. Late invoices, missed follow-ups, Slack as the system of record. Hard days do not create the burden. They reveal it.
Can automation reduce administrative burden?
Yes, when it removes hops instead of judgment. Automation should move data, assemble first drafts, and surface exceptions. Your team still decides and handles the weird cases. If the process itself is unclear, we fix that in the audit before anyone automates.
Can we approve actions before they happen?
Yes. Approval steps can be scoped for actions such as sending documents, updating important records, or placing orders. We agree which steps need an authorized person before they proceed. That list is set per engagement; it is not a default applied to every existing workflow.
What happens if an automation fails?
The project scope defines how failures are flagged, what gets recorded, who is responsible, and how recovery starts. After a build handover, your team owns day-to-day response unless you choose optional ongoing support. That support is not 24/7 monitoring unless we explicitly agree it.
What kinds of companies do you work with?
Our focus is scaling mid-market operations, typically 100 to 500 employees, and enterprise teams with complex handoffs across CRM, ERP, and field tools. We work with finance, operations, and IT leaders to prioritize margin, cash flow, and governance.
What does an engagement look like?
Start with an Operational Discovery Audit, move into a phased operational transformation with handover to your team, and book scoped follow-on work only when you need extra delivery capacity.
How is this different from hiring a developer?
We treat ownership, exceptions, and maintenance as part of the build. That means agreed permissions, approval steps where they matter, a recorded path when something fails, and documentation so your team can run the workflow. Optional support is there if tools or volume shift after handover.
How long does a typical project take?
Timing depends on integration access, controls, and rollout complexity. We agree milestones during the audit and deploy in phases so your team can validate working systems early.
Do you replace our existing tools?
No. We connect them. The point is to make what you already have work together without a person in the middle.
Where are you based?
Ottawa. Most discovery work starts remote; onsite time depends on the audit.
Do you set up Claude, ChatGPT, Gemini, or Cursor?
Yes. A lot of teams bought seats and never got past chat. We set up projects, skills, and the connections into Slack, email, CRM, and files, then automate the handoffs those tools still leave to people.
What tools do you automate with?
Whatever you already pay for. Common stack: Claude, ChatGPT, Gemini, Cursor, n8n, Zapier, Make, Slack, HubSpot, QuickBooks, Shopify. We do not ask you to rip and replace the system of record.

Get started
Build the business case for better operations
Review your AI controls, then build a business case for better operations.