Model 01
Fixed-Scope Pilot
Validate one workflow — an AI agent, an automation, a feature — against real data before committing further.
Pricing
Scoped to the work, not sold off a rate card.
We don't sell fixed-price software off a shelf, and we won't quote a number before we understand what you actually need built. Below is how we structure engagements and what determines cost — so you know what to expect before the first call, even without a price list.
How we structure engagements
Every engagement fits one of four models, depending on how defined the scope is and whether you need a one-time build or ongoing ownership. We'll recommend the model that fits after a scoping call, not before it.
Model 02
Project-Based Build
A complete product, agent platform, or system delivered against an agreed specification.
Model 03
Dedicated Team
Engineering capacity embedded with your team, working your backlog and priorities.
Model 04
Ongoing Partner
Continued ownership after launch — uptime, model and dependency updates, and iteration.
Compare engagement models
Use this side-by-side view to narrow the best starting structure. The final recommendation follows discovery because risk, integrations, and ownership can change the right model.
| Compare | Fixed-Scope Pilot | Project Build | Dedicated Team | Ongoing Partner |
|---|---|---|---|---|
| Best when | You need to prove one workflow | You have a defined outcome and launch | You need steady delivery capacity | You need ownership after launch |
| Typical duration | 4–8 weeks | 2–6 months | Month-to-month | Month-to-month |
| Scope | One workflow and deliverable | Defined scope with change control | Roadmap and backlog driven | Operations plus planned iteration |
| Billing structure | Fixed scope / milestones | Project milestones | Monthly capacity | Monthly retainer |
| Long-term lock-in | No | No | No; short notice period | No; short notice period |
| Natural next step | Expand, hand off, or stop | Support plan or handoff | Scale team up or down | Continue operating and improving |
What actually determines your price
Two projects that sound similar in a first conversation can differ in cost by a wide margin once we look at what's underneath. These are the factors we scope against on every call:
Workflow complexity
How many decision points, exceptions, and edge cases the process actually has, versus how many it appears to have from the outside.
Integrations required
The number of existing systems — CRM, ERP, ticketing, internal databases — the build needs to read from or write to.
Data readiness
Clean, structured, accessible data is a different starting point than fragmented data spread across disconnected tools.
Compliance & security scope
Data residency rules, audit trail requirements, and access controls add work that isn't visible in a feature list.
Team model
A single embedded specialist scopes and bills differently than a dedicated multi-person engineering team.
Timeline
A compressed launch date changes staffing and sequencing, which changes cost independent of scope.
Where to start
If you already know what you want built, book a discovery call and we'll follow up with a scoped estimate — typically within a few business days. If you're not yet sure where AI or automation would actually pay off, start with the free AI audit instead: no charge, no obligation, and it maps real opportunities before either of us commits to a number.
Frequently asked questions
Why don't you publish fixed prices?
Because a generic rate card would be misleading in both directions: it would overprice a well-scoped, straightforward build, and underprice a workflow that turns out to need five system integrations and a compliance review. The variables that actually drive cost — workflow complexity, data readiness, number of integrations, and team model — differ enough between businesses that a flat number on a website is a guess, not a quote. A short scoping call gives you an accurate range for your specific case instead of a number we'd have to walk back later.
How soon can I get an actual number?
Most clients get a scoped estimate within a few business days of an initial call. For a free AI audit, we map one or two real workflows, rank feasible opportunities, and outline a 30-60-90 day direction before any paid work is proposed. For a defined-scope project, we follow that with a fixed-price or fixed-scope proposal once we understand the systems involved.
Is there a minimum engagement size?
Most engagements start as a fixed-scope pilot on a single workflow, which keeps the initial commitment small and lets you see real output against real data before expanding scope. We don't publish a hard minimum, but very small one-off requests are usually a better fit discussed directly on a scoping call than forced into a project or retainer structure.
Do you require long-term contracts?
No. Pilots and project-based builds are fixed-scope engagements with a defined end date. Dedicated-team and ongoing-partner arrangements run month-to-month with a short notice period rather than a long lock-in, so the relationship continues because it's working, not because of a contract term.
What payment structure do you use?
Project-based work is typically billed against milestones — for example at kickoff, midpoint, and delivery. Dedicated-team and retainer engagements are billed monthly. The specifics are confirmed in the proposal before any work starts.
Does the free AI audit cost anything or commit me to a project?
No. The free AI audit has no charge and no obligation to move forward. It exists to give you a concrete map of feasible AI and automation opportunities, with risks and dependencies called out, so you can decide whether paid implementation makes sense — and if it does, we already have most of what's needed to scope it accurately.
Ready to find out what this costs for your case?
Tell us the workflow or system you're trying to build, and we'll follow up with a scoped estimate.
Start a Project