Skip to content

Pricing

Three stages, priced separately.

Sonan deploys agents and automation for revenue teams, then keeps them maintained. Most teams start with the review. Some stop there, and that is a fine outcome. You only pay for the next stage if the last one earned it.

The ladder

Deploy where it makes sense. Maintain for as long as it earns its keep. Stop whenever you like.

Run your numbers
01 · Workflow review

$500

One time

One of your reps walks me through a real lead or deal. You get a written read on where the time goes, your systems, and what is actually worth deploying first. One hour with your rep, the written read inside a week.

  • The three biggest gapsRanked by what they are costing you, not by what is easiest to build.
  • What you already ownThe capability sitting unused in the stack you already pay for.
  • A running-cost forecastWhat this would cost per month to operate, before you commit to it.
  • A named first workflowOr a straight answer that there is not one worth doing yet.
  • $500 off if you go aheadStart a deployment within 60 days and the review price comes off it.
  • The number to moveOne measure the first workflow should change, such as hours per rep each week or days to follow-up, with a baseline taken during the review.
02 · Deployment

$7,500

Four weeks · fixed scope

One agent or workflow, deployed on your stack and tested against real work with the people who will use it.

  • Built around your stackStarting with the systems you already pay for. If an added tool is the better answer, you see what it costs to run before anything is built.
  • A scope checkpoint at week oneThe workflow, the data and what “done” means are written down and agreed before the build starts.
  • Tested before go-liveAgainst your real workflow and real records, not a demo.
  • Measured against that baselineThe readout reports the number set in the review, or at kickoff if you skipped it.
  • Documented and handed overWith a runbook you keep, plus the templates and prompts your team can adjust without calling me.
  • A named owner and a stop dateSomeone on your side accountable for it, and a defined end.
03 · Ongoing operations

From $2,000

Per month · month to month

The maintenance layer, for teams that want agents and automations working without owning the upkeep. This is where the value compounds: someone checking output, fixing what the ground shifts under, and widening what is deployed.

1 to 3 deployed workflows
$2,000
4 to 6
$3,000
7 or more
$5,000
  • A named person reviewing outputOn a schedule, checked against your CRM and call records, not only when something breaks.
  • The monthly cost forecastSo usage never becomes the surprise it usually does.
  • Repairs when things changeYour CRM updates, a connector moves, a model is retired. Someone fixes it.
  • The next workflowAdded at a predictable rate rather than in another project.
  • A response window in writingFour hours to acknowledge something that has stopped, one business day for everything else.
  • One build day a monthSo a change you want is a routine request rather than a new project.

Before you buy

When you should hire nobody.

  • If the tool you already own covers it. Your CRM and your automation platform ship more capability than most teams use. Part of the review is telling you which parts are already solved, including the parts I would not charge you for.
  • If the data is not ready. Automation on top of a CRM nobody trusts produces faster bad decisions. Fix the foundation first, and that may be all you need.
  • If nobody will own the review. Every workflow here needs a named person on your side checking output on a schedule. If that person does not exist, it will be switched off within a quarter, and you should not pay for it.

A short review that ends in “you do not need this yet” is a good outcome for both of us. It is cheaper than a deployment nobody adopts.

Questions

Reasonable objections.

If everything is handed over, why is there a monthly fee?

Because handover covers what was built, not what happens after. Models change, your CRM changes, connectors move, and someone has to check whether the output is still correct. That drift shows up in months two to four, once your CRM and your process move under the build, which is why the checks run on a schedule rather than on request. The monthly work pays for that person and that upkeep. If you would rather own it entirely, stop after the deployment and the runbook is yours.

What does the review actually cost me compared to just trying it?

Less than a failed deployment. Its job is to tell you whether a deployment is worth doing, and to put the running cost in writing before you commit rather than after. Go ahead within 60 days and the $500 comes off the deployment.

Can I skip straight to the deployment?

Yes, if you already know which workflow to fix and already know where the gaps are. The review exists because most teams disagree internally about both of those.

Am I locked in to the monthly work?

No. It is month to month, opt-in, and cancellable with thirty days notice. You keep everything built to that point, including the runbook and the documentation.

We already have ChatGPT or Copilot. Why not use that?

Keep it. It is good at single tasks: a recap, a summary, a first draft. A workflow already knows where your data lives, runs the same way for every rep, follows your qualification framework, gets checked for accuracy, and has a known monthly cost. If the tool you have already covers the gap, the review will say so.

Do I have to buy anything new?

Usually not. The first question is what you already run and where the gaps actually are. If there is no reliable CRM in place, that is the first thing to fix, because nothing downstream works without it.

Start with a free call

Not sure a review is worth it yet? Start with a free 30-minute discovery call.

Book a discovery call