A quick conversation to understand fit, urgency, and whether an audit or build makes sense.
Clear pricing for how I usually work.
Most engagements begin with a short discovery call. From there, the work usually fits into an audit, an implementation, or an ongoing retainer. The goal is to make scope and expectations easier to understand before we start.
Projects are priced around one real business workflow rather than around vague monthly consulting.
Ongoing support exists for teams that want monitoring, iteration, and new automation over time.
Start with the free call if you are unsure.
If you already know the workflow that needs attention, we can use that call to decide whether the next best step is a paid audit, a direct implementation, or a simple recommendation with no project attached.
AI Readiness Audit
A documented review of your operations, tools, and automation opportunities so you know exactly where to start and what the strongest ROI cases are.
- 60-90 minute operations interview
- Workflow and tooling review
- Prioritized automation opportunities
- Written findings and recommendations
- Timeline and cost guidance for next steps
- Readout call to review the plan
Implementation
A custom build for one business problem, designed around your workflow, team, systems, and rollout needs.
- Discovery and scoping session
- Custom implementation around your workflow
- Integration with your current systems where needed
- Progress check-ins during the build
- Launch support and onboarding
- 30-day post-launch support included
Retainer
Best for teams that already have a system live and want support, iteration, monitoring, and additional automation over time.
- Maintenance and workflow updates
- Monitoring and issue response
- Monthly strategy and prioritization
- New improvements as the process evolves
- Priority support and direct communication
- Month-to-month flexibility
The work is meant to be practical and easy to own.
Scoped to a real problem
The work starts from an actual operational bottleneck, not from a vague request to “use AI somewhere.”
Built for adoption
The implementation has to fit the people and tools already in place or it will not stick.
Clear next steps
You should leave each phase knowing what was decided, what was built, and what comes next.
Pricing questions I hear most often
Can a project skip the audit stage?+
Yes. If the problem is already well understood and narrow enough to scope directly, we can move into an implementation without a separate audit engagement.
What drives the implementation range?+
The main variables are workflow complexity, integration needs, data quality, and how much rollout support the team needs.
Do you offer long-term contracts by default?+
No. Most work is scoped as a project, and retainers are useful only when there is an ongoing reason to keep improving the system.
Use the discovery call to pressure-test the opportunity before spending more.
If the workflow is not a strong fit for AI, I would rather say that early than force the wrong project.