AI consultation
Free
Subject to availability
We map your workflow, spot the useful opportunities, and help you pick a sensible first project.
Pricing
Fixed prices.
Clear scope.
Start with a free consultation. Most automations run from $100 a month, and custom software from $500 a month. When the work is bigger than that, we price it as a fixed-price project. Here’s where those usually land, and what moves the price.
Three ways
to start.
Most businesses start with one job they’d like off their plate. We agree on the price before any work starts.
Workflow automation
from $100/month
For one repetitive job
Connect the tools you already use and let the routine take care of itself, supported month to month.
Custom software
from $500/month
When a spreadsheet won’t stretch further
A tool built around how your business works, for when off-the-shelf software doesn’t fit.
Bigger projects,
fixed prices.
When the work spans several workflows, systems, or teams, we quote a fixed price against a written scope before anything starts. These are the ranges projects usually land in.
| Project | Typical price | Timeline | What you get |
|---|---|---|---|
| PilotMost teams start here | $5,000–$15,000 | 3–6 weeks | At least one workflow that pays for itself in its first six months. Connected to up to two systems, with a review step where a person approves the output, tested on real work, then 30 days of fixes and adjustments while your team settles in. |
| Operations buildSee a worked example ↓ | $15,000–$60,000 | 6–20 weeks, in phases | Two to six related workflows that share data, approval rules, and reporting. Each phase is working before the next one starts, so your team is using the first workflow while we build the second. |
| Full platform | From $60,000 | Set in the scope | One integrated system to run the whole company: your workflows, data, and reporting in one place, with its own screens and user roles for every team, connected to the tools you keep. |
Before we quote a pilot, we work out with you what the workflow costs today and what it will cost to build and run. If it won’t pay for itself within six months, we’ll tell you, and suggest a smaller place to start.
What $30,000
actually buys.
An illustrative operations build for a 30-person professional services firm, where client work starts as an email and ends as an invoice. It isn’t a client result. It’s how we’d scope one.
- Weeks 1–3
Intake, complete.
Each new inquiry starts intake on its own: the right questions are asked for the type of work, documents are requested and collected, and what comes back is reconciled against the client’s answers and the firm’s records, with gaps flagged. A partner reviews every completed intake before the firm takes on the client.
- Weeks 4–5
Accepted work starts itself.
Once a partner accepts the client, the engagement letter goes out for signature, and the signed letter opens the client folder and the kickoff tasks, with reminders for anything the client still owes.
- Weeks 6–7
Billing without the chase.
Time entries are checked against the engagement, and invoice drafts are prepared in the accounting system for someone to review and send.
- Week 8
One report on Monday.
Pipeline, active engagements, overdue documents, and unbilled time in one weekly report. The numbers are calculated straight from the source systems; AI writes the summary, not the math.
Then 30 days of fixes and adjustments, and a handoff your team can run with.
Closer to $15,000
- Two to three simple workflows
- Two or three systems with good integrations
- One team, one location
- Data that’s already in reasonable shape
Closer to $60,000
- Five to six complex workflows
- Four or more systems, or one with limited access
- Several teams or locations with different rules
- Data cleanup or custom reporting
Included
- A written scope with acceptance tests for every workflow
- A review step wherever the output reaches a client or moves money
- Testing on real work before each phase goes live
- Training for the people who’ll use it
- Documentation and a handoff your team, or another developer, can pick up
- 30 days of fixes and adjustments after launch
Not included
- Software subscriptions and AI usage, billed to your own accounts
- Large data cleanup projects, quoted separately
- Changes to the scope, which we price in writing before doing the work
After launch,
support that fits.
Software changes underneath every automation: a vendor renames a field, a password expires, a new kind of request shows up. Monthly plans include their own support. For pilots and bigger builds, support is a separate plan.
System care
$750–$1,500/month
For a pilot or bigger build
Monitoring, troubleshooting, checks after your vendors change something, and a small monthly allowance for adjustments. New workflows are quoted separately.
Ongoing development
$2,500–$5,000/month
For teams that want to keep building
Reserved build time, one priority at a time, and a monthly review of what’s working and what to build next. System care is included.
Who owns what we build?
On a fixed-price project, you do. Software and AI accounts are opened in your name, and the code, prompts, and documentation are yours when the project ends.
What does it cost to run?
It depends on the tools and the volume. We estimate subscriptions and AI usage in writing before you commit, and you pay those providers directly, with no markup from us.
What if the scope changes?
We price the change in writing before doing the work. Nothing shows up on an invoice that you haven’t agreed to.
Pricing
questions.
What do the monthly plans include?
One automation, or one tool, built for a specific job and supported month to month. We agree on the price before we start, and you can see it working before you commit to anything bigger.
When does it become a fixed-price project?
When the work spans more than one workflow, several systems, or several teams. At that size a fixed price against a written scope is usually better value, and you know the total before we start.
How do you know a pilot will pay for itself?
We work it out with you before we quote: the hours the workflow takes today, the mistakes it causes, and what the pilot will cost to build and run. If the numbers don’t pay back within six months, we’ll say so.
Can we skip the pilot and start with a bigger build?
Yes, if the workflows are well understood and the systems are accessible. Many teams still prefer to see one workflow working before committing to more.
Do you work outside San Luis Obispo?
Yes. We’re based in San Luis Obispo and work with teams across the Central Coast in person, and with teams elsewhere remotely.
Have a workflow
in mind?
Tell us what it is and which tools it runs through. We’ll tell you which of these it looks like, and whether it’s worth doing at all. The first call is free, subject to availability.
Tell us about the workflow