AI consulting cost depends on the work being purchased: practical team training, discovery, implementation, or ongoing support. Applied Margin’s AI Workflow Sprint is $1,500 fixed, Implementation starts at $3,500, and Ongoing Partnership starts at $1,500 per month. An optional Margin Scan costs $1,500 for seven business days. These are prices for defined scopes, not a market average or a promise that every AI project fits the starting price.
Compare the full cost of getting a workflow into use, including software, internal participation, review, and upkeep. A useful quote tells you what will be delivered, who on your side will own it, what is excluded, and how the work will be checked. You do not need to purchase every kind of help. The right engagement depends on what your team needs to accomplish next.
What should each price actually buy?
The first question is whether the quote buys capability in your team, an informed decision, a working system, or continuing support. A provider can do several of those jobs, but the proposal should separate them enough for you to understand the commitment.
| Work purchased | Applied Margin price | What the defined scope buys | What to ask any provider |
|---|---|---|---|
| Hands-on team training | AI Workflow Sprint: $1,500 fixed | Practice, reusable workflows, instructions, and an opportunity map for one team of up to five | Who participates, what they keep, and what happens after the sessions |
| A working system | Implementation: from $3,500 | Entry scope: one company-knowledge use case using agreed materials and users | Which capability is included, how it is tested, and who owns the handoff |
| Continued improvement | Ongoing Partnership: from $1,500/month | Two 45-minute working sessions and one lightweight improvement each month; three-month opening term | Which work fits the monthly scope and which changes need a new proposal |
| Optional deeper discovery | Margin Scan: $1,500 / seven business days | Review of one operating area and a ranked implementation decision | Whether investigation is necessary before committing to a solution |
The Sprint also includes a short leadership kickoff, two hands-on working sessions, two to three reusable workflows, verification guidance, and one follow-up session. Session lengths and scheduling are agreed before booking. Custom software, integrations, and subscriptions are separate. Its fee does not automatically credit toward a later build.
The $3,500 Implementation entry includes agreed materials organized and configured, source-linked answers, permissions and usage boundaries, evaluation questions, a correction workflow, a team walkthrough, and a 30-day correction window. Connected systems, custom workflows, and process redesign receive a separate fixed proposal. The starting price does not cover an arbitrary integration project.
Ongoing Partnership’s entry scope is working sessions and one lightweight improvement. Embedded delivery, monitoring, broader rollout, and new builds are separately scoped. See the current services and scope before comparing a proposal against a headline price.
How do hourly, fixed-price, and retainer quotes differ?
An hourly arrangement buys time. It can work for a narrowly understood support need or investigation whose effort cannot yet be estimated reliably. Ask for an agreed ceiling, a way to track work, and a decision point before more time is used. A low hourly rate tells you little about total cost when the number of hours is open.
A fixed-price arrangement buys an agreed scope. It makes the commitment easier to compare if the deliverables and acceptance criteria are specific. Changes still need a process: what counts as a defect, what adds a capability, and who approves the extra work? Without those distinctions, “fixed” can hide disagreements rather than remove them.
A retainer pays for continuing availability or a recurring scope of work. Those are not interchangeable. Find out whether the fee buys defined sessions, a specific improvement, monitoring, or implementation capacity. A monthly invoice should not imply that every type of support is included.
Applied Margin publishes a fixed Sprint, scoped implementation proposals, and a defined starting Partnership scope. There is no published hourly offer. These billing choices should follow the work; a business with one clear implementation need should not assume a monthly commitment is the only route.
If you are comparing providers, place their exclusions beside their deliverables. A higher quote that includes tested handoff may cover work a lower quote leaves to your staff. That does not make the higher quote automatically better. It makes the difference visible enough to evaluate.
What changes the cost of implementation?
The amount of coordination and verification matters alongside the amount of code. A workflow drawing from approved documents is different from one that must reconcile records across systems, respect several permission levels, and recover from failed connections.
Consider an agency asking for an internal answer assistant. The scope depends on whether its approved procedures are current, who may read them, and how people will verify an answer. If the request expands to combining client information across accounts, creating tasks, and preparing outbound messages, there are more access and review decisions to resolve.
Be explicit about the conditions you will supply. If your team needs to clean source files, approve credentials, or provide representative cases, ask when that work happens and whether it changes the schedule. Internal preparation is real effort even when it does not appear on the provider’s invoice.
Deeper investigation is useful when important choices are still unresolved. It is not automatically required for a documented solution. When a Paid AI Assessment Is the Right Starting Point explains when the optional Scan fits without making it a gate before every build.
What upkeep belongs in the budget?
A workflow can need attention after its first acceptance test. Source material changes, a staff member leaves, a vendor alters an integration, or a model starts producing a different shape of answer. The budget needs to name who notices, checks, and responds.
Ask about the activities separately: keeping source material current, reviewing failures, rerunning representative checks after changes, managing access, and answering operator questions. Some can stay with your team. Others may need a support agreement or a separately scoped repair. None should be assumed to happen indefinitely because implementation once took place.
Distinguish a correction window from ongoing improvement. The entry knowledge implementation includes a 30-day correction window. That is not an unlimited promise to absorb future vendor changes, new use cases, or additional integrations. The proposal should state the relevant responsibilities rather than leaving you to infer them from “support included.”
The ongoing-partner note explains what the starting monthly scope covers. Choose it when the working sessions and lightweight improvement are useful. If you need system monitoring or an embedded implementation workstream, obtain a specific scope and price.
Which surprises should you remove before signing?
Ask for one written view of service fees and third-party charges. You should know who purchases software, who controls the accounts, how usage is billed, and whether a proposed price depends on a particular volume. Usage-based costs need assumptions and a process for reviewing unexpected increases.
A software resale margin is not something to infer from a vague bundle. If a provider resells services or includes a markup, the commercial terms should make that arrangement clear. Applied Margin keeps software, model, hosting, and platform costs separate from implementation; Partnership platform usage remains visible and passes through at cost.
Also identify what would trigger a change in scope: a new department, a new data source, another approval role, or a different output. Written boundaries protect both sides from treating a new capability as a small correction merely because it appears in the same screen.
Avoid paying for undefined outcomes such as “make the business AI native” without concrete deliverables. You should be able to explain the purchase to a partner who missed the sales call. The spouse-or-CPA decision guide offers a way to make that explanation specific.
How would you calculate a plausible payback?
Start with cash flows if you are calculating financial payback. Capacity can be valuable, but a salaried employee having more available time does not automatically reduce payroll or produce a new sale.
Hypothetical math: suppose a focused knowledge implementation costs $3,500. Assume no additional upfront cash expense, and assume a measured workflow releases time after allowing for review, source maintenance, and exceptions. Of that released time, ten hours per month previously incurred avoidable overtime at $50 per hour. Assume those overtime payments actually stop, while recurring software costs are $100 per month. These are illustrative assumptions, not vendor prices, client results, or a forecast.
| Cash-flow item | Hypothetical calculation | Monthly effect |
|---|---|---|
| Overtime payments actually avoided | 10 hours × $50 | $500 less cash spent |
| Recurring software | Assumed cost to verify against the chosen tools | $100 cash expense |
| Additional salaried capacity | Available time without a payroll reduction | $0 immediate cash savings |
| Net monthly cash benefit | $500 − $100 | $400 |
Hypothetical math: simple payback is $3,500 divided by $400, or 8.75 months, if every assumption holds. This simplified model excludes financing, tax effects, and any additional implementation or support costs. Add relevant costs before using it for your decision. It is not a payback commitment.
If the supposed overtime is never actually avoided, the $500 cash benefit disappears. The project may still help quality or capacity, but that requires a different justification. If review takes more effort than expected, the estimate also changes. Use observed results and a stop-or-revise decision rather than defending the initial spreadsheet.
Let’s talk about your business. Bring the work you want to improve, what you already pay for, and the questions a proposal needs to answer. We can discuss the appropriate starting point before you commit to paid work.
FAQ
Is there a free option before I commit to paid work?
Applied Margin offers a free introductory conversation to understand your business and identify a suitable next step. It does not include an audit, report, or implementation plan. You can also use the public Field Guide on your own. A paid engagement makes sense when you want defined help applying the work to your team, operating area, or system.
Does Applied Margin charge per hour?
Applied Margin does not publish an hourly service offer. The AI Workflow Sprint has a $1,500 fixed fee, implementation receives a defined proposal, and Ongoing Partnership has a specified monthly starting scope. Ask which deliverables, participation, and exclusions apply to your engagement. The billing format should make the commitment clear rather than leave the amount of work open to interpretation.
Can I apply the Margin Scan fee toward implementation?
Yes. The optional Margin Scan’s existing terms allow the full $1,500 fee to apply to an Applied Margin implementation authorized within 14 days. This is a Scan-specific credit. The Scan’s Clarity Guarantee is also limited to that assessment. Neither benefit automatically extends to the AI Workflow Sprint, and an implementation remains a separate scope and purchasing decision.
What about subscriptions and other software costs?
Software, model, hosting, and platform charges are separate from implementation fees. Ask which accounts you need, who controls them, and how recurring usage could change. Do not estimate the full budget from the service fee alone. The AI budgeting guide separates seats, funded workflow work, and upkeep so you can make those assumptions visible.
Does the starting implementation price cover a custom automation?
The $3,500 entry price covers one defined company-knowledge use case with agreed materials and users. It includes source-linked answers, permissions, evaluation questions, a correction workflow, a team walkthrough, and a 30-day correction window. Custom automations, integrations, process redesign, and connected systems receive separate fixed proposals. Use the specific deliverables in your quote when deciding whether the cost fits.