An AI workflow can work on launch day and drift a month later. A tool changes, a new person takes over, an exception appears, or the team quietly returns to the old process. Ongoing help should have a clear job: keep useful work reliable and improve it at a pace the team can absorb.
That is different from buying an open-ended promise to transform the business. Before a monthly commitment, name the workflow, the person who owns it, the work included, and the evidence you will review.
What Ongoing Partnership includes
Applied Margin's Ongoing Partnership starts at $1,500 per month with a three-month opening term. At that starting scope, it includes two 45-minute working sessions each month and one lightweight skill or workflow improvement.
Those sessions use the team's actual work. We can review outputs, work through an exception, improve instructions, and help an operator use and check the workflow. The improvement is agreed in advance so everyone knows what fits in the month.
It is not an unlimited implementation service. A new integration, custom application, or larger rollout is scoped separately. Software, model, hosting, and other platform costs remain separate. The written scope confirms what we will maintain, measure, and deliver before the engagement starts.
What a useful month can look like
Consider an HVAC dispatcher who already uses a first-draft follow-up workflow. In one working session, the team brings examples that were incomplete or sounded wrong. We trace the issue to a missing input or an unclear instruction. The lightweight improvement might be a better review checklist and a revised template. In the next session, the operator practices with representative examples and checks whether the change helped.
For an agency, the same pattern might improve an existing weekly client-update workflow. The account lead brings a draft, its source notes, and the corrections they had to make. We refine the instructions and review step, then compare the next examples.
These are illustrations of possible work, not client results or a promise of a new system every month. The right improvement depends on the workflow and the agreed scope. If the work needs engineering or a new connection between tools, we scope an Implementation separately.
Measure the work, not the meeting count
Two sessions are a delivery format. The useful question is what the team can do afterward.
Pick a measure that fits the change: fewer missing facts in a draft, less rework, a shorter review step, or an operator who can spot and recover from an error. Record the starting point. Review the same kind of work after the change. Hours are capacity, not automatic cash savings; the business still has to use that capacity.
Keep the instructions and decisions somewhere the team can access. The named operator should understand the inputs, verify the output, and know when to stop or escalate. A subscription does not remove human accountability.
When a project makes more sense
If you know what needs building, a defined project may be the better choice. Implementation starts at $3,500 for a focused knowledge use case using agreed materials and users. Broader automation, integrations, and custom software are scoped and priced separately. A starting price is not a quote for every system.
Process redesign, a source-grounded knowledge assistant, or connected workflows are capabilities we can combine when the work calls for them. They are not a checklist of packages every client must buy. Team rollout is also scoped to the actual users and workflow.
If the team is still getting started, the AI Workflow Sprint is $1,500 fixed. It includes one team of up to five people, a short leadership kickoff, two hands-on working sessions, two to three reusable workflows, written instructions, a prioritized opportunity map, and one follow-up session. Session lengths and scheduling are agreed before booking. Software, integrations, and subscriptions are separate; the Sprint does not automatically credit toward a later build.
The Sprint has standalone value even if we never implement anything else. An optional paid Margin Scan remains available when deeper discovery is the real need. A workflow you have already documented can move directly into implementation scoping.
Before you commit
Use these questions with your partner or the person who will operate the workflow:
- Which existing workflow are we improving?
- What is included in the monthly scope, and what needs a separate project?
- Who brings the examples and owns the work between sessions?
- What will we compare before and after the improvement?
- What software or usage costs sit outside the service fee?
- What will we review before continuing beyond the opening term?
A useful monthly relationship has a clear purpose. It should not require you to imagine a year's worth of unbuilt systems to justify the first invoice.
FAQ
What does an ongoing AI partner do for a small business? Helps the team keep agreed workflows useful, improve them with real examples, and maintain clear ownership. The work depends on the written scope; a title such as fractional chief AI officer does not define the deliverables.
Does the starting price include a new build every month? No. The $1,500 monthly starting scope covers two 45-minute working sessions and one lightweight skill or workflow improvement, with a three-month opening term. Larger builds, integrations, and software costs are separate.
Do I need a Sprint or a Scan before implementation? No. We need enough understanding to scope the work responsibly. That can come from a Sprint, optional deeper discovery, or work you have already mapped.
Let’s talk about your business. Tell us what is working, what keeps breaking, and whether you need team practice, implementation, or ongoing help. A free introductory conversation helps establish the right next step; it does not include an audit or implementation plan.