Pricing
Pricing without the guesswork.
Every business has different systems, workflows, constraints, and priorities. I don’t want to give you a canned package price before I understand what actually needs to be fixed.
Before any work begins, we’ll define the scope, deliverables, timeline, and total cost in writing.
No surprise invoices. No open-ended consulting bill.
Start the conversationWays to work together
How engagements are structured
The right engagement depends on the problem, not on fitting your business into a predefined package.
01
Focused Projects
For a specific workflow, integration, automation, or operational problem with a defined outcome. Most focused projects are quoted as a fixed fee once the scope is understood.
Examples may include
- improving a repetitive workflow
- connecting systems that do not work well together
- reducing manual follow-up
- building a practical automation
- improving access to business information
02
Broader Implementation
For projects involving multiple systems, workflows, teams, locations, or more substantial implementation work. These engagements are scoped individually based on complexity, dependencies, operational risk, and the amount of change required.
Examples may include
- multi-system workflow redesign
- AI workspace implementation
- cross-department automation
- process standardization
- more substantial integration work
03
Ongoing Support
For businesses that want continued maintenance, improvements, troubleshooting, training, or help identifying the next useful opportunities after an initial implementation. Ongoing support is available when useful; it is not required.
Examples may include
- workflow maintenance
- troubleshooting
- small improvements
- employee support and training
- platform changes
- identifying additional opportunities
The variables
What affects the price?
The cost of an engagement is usually driven by the work required to make the solution reliable inside the business—not simply by the number of tools involved.
- 01
Number of systems involved
- 02
Integration complexity
- 03
Number of workflows being changed
- 04
Quality and structure of existing data
- 05
Existing process consistency
- 06
Testing requirements
- 07
Security and access requirements
- 08
Number of users, teams, or locations involved
- 09
Training and documentation needs
- 10
Third-party platform limitations
- 11
Ongoing support requirements
- 12
Risk associated with the workflow being changed
A simple workflow with a clear problem may be relatively straightforward. A process involving several systems, exceptions, approvals, and business-critical actions requires more discovery, testing, and implementation work.
Before work begins
You’ll know the price before I start.
After discovery, I’ll provide a written Statement of Work that explains exactly what we are agreeing to.
- What I’m building or changing
- What is included
- What is not included
- What it will cost
- How payment works
- The expected timeline
- What each side is responsible for
- What success looks like
If the scope changes, we agree on the change before additional work is performed.
Payment structure
How payment works
For most fixed-scope projects, the standard payment structure is:
- 50%
- before work begins
- 50%
- upon completion of the agreed deliverables
Ongoing support or retainer engagements are generally billed monthly in advance.
Third-party software, platform, API, usage, transaction, or licensing costs are normally paid directly by the client unless otherwise stated in the project scope.
Different projects may require a different payment structure. Any change will be stated clearly in the written Statement of Work before work begins.
A responsible quote
Why there isn’t a price list
A workflow involving one spreadsheet and a few repetitive steps is not the same project as an implementation involving accounting software, inventory, email, customer data, approvals, and multiple employees.
Putting the same price on both would not be transparent. It would just be arbitrary.
The goal of discovery is to understand enough of the problem to give you a real scope and a real price before you commit.
As engagement patterns become more standardized, common project ranges or starting prices may be published here.
Start with the work
Have something that should work better?
Tell me what is slowing the business down, getting missed, or taking more effort than it should. We’ll start there.
Let’s look at it