Three quotes, three different planets

A plumbing company owner asks three people the same question: what would it cost to connect the phones to the schedule, so a missed call turns into a booked job instead of a sticky note. A software vendor quotes a monthly fee per user. An agency quotes a project in the tens of thousands. A nephew offers to wire something together over a weekend.

All three are real prices for real things. They are just not prices for the same thing, which is why automation pricing feels random from the outside. This guide breaks the number into parts you can price yourself.

You are choosing between three purchases

Most quotes you will hear describe one of three different purchases, and the first step is knowing which one is on the table.

  • Renting a platform. Software by the month, usually per user. Cheap to start, repeats forever, and shaped for the average business rather than yours.
  • Buying a custom build. You pay once for software built around your process, then a modest monthly amount to keep it maintained. More up front, yours afterward.
  • Connecting what you already own. Your CRM, phone and SMS, scheduling and accounting systems already hold the data. The project just moves it between them so nobody retypes anything.

There is a fourth number nobody quotes: the cost of doing nothing, paid out in wages every week the manual steps continue. Most pricing decisions get easier once that number is on the page.

What actually drives the price

Cost in automation does not follow how impressive the result looks. It follows how many systems the work touches and how many exceptions it has to survive.

  • Systems touched. Reading from one system and writing to another is the base case. Each extra system, whether CRM, POS, phone and SMS, accounting or scheduling, adds connection and testing time.
  • Exceptions. The happy path is cheap. The customer with two addresses, the partial refund, the duplicate record: handling the odd cases well is where the hours go.
  • Approval points. Deciding where a person reviews before anything sends or posts takes design time, and it is worth every hour.
  • Data cleanup. If years of records are inconsistent, part of the budget goes to making them trustworthy before anything automated runs on them.

Ask any builder to walk through their estimate in those four terms. If they cannot, that tells you something too.

Honest numbers to anchor on

Our pricing is a fair anchor for studio work at this scale. Custom software and automation typically runs $1,000 to $5,000, and most builds take a few days to a month.

You get a written quote and a statement of work before any work starts. Billing is flat rate or $50 an hour, invoiced weekly, so you watch spend as it happens rather than discovering it at the end. Three rounds of revisions are included.

After launch, monthly plans cover updates, maintenance and uptime, with a 99.9 percent uptime target on hosted builds. You keep ownership, documentation and a proper handover either way, so the work is yours whoever maintains it later.

Run the payback arithmetic

Skip industry benchmarks and use your own payroll. Pick one task, measure it for a week, then do the multiplication.

  1. Pick one manual task. Say the office retypes job details from the phone log into the schedule, then again into invoicing.
  2. Time it honestly across all its steps. Call it 15 minutes per job.
  3. Multiply by volume. At 40 jobs a month, that is 600 minutes, or 10 hours a month.
  4. Price the hours. At $25 an hour, the task costs $250 a month, which is $3,000 a year.
  5. Compare to the build. If removing the retyping costs $2,500 once, it pays for itself in about ten months and keeps paying after that.

Run the same math on renting. A platform at $30 per user per month for six people is $2,160 a year, every year, whether or not it fits how you work. Neither answer is always right, but the arithmetic will tell you which is right for this task.

When automation is the wrong buy

Some tasks should stay manual, and a builder who says so early is saving you money. Walk away from automating when any of these is true.

  • The task is rare. Something done twice a quarter almost never earns a build, however annoying those two afternoons feel.
  • The process is still changing every month. Automate after it settles, not while you are redesigning it.
  • The volume is tiny. Ten invoices a month at five minutes each is under an hour. Live with it, or fix it with a template.
  • The real problem is a person or a policy. Software cannot settle a disagreement about who owns the schedule.

A good estimate should include a shorter list than the one you brought. Hearing that part of your list is not worth building should cost you nothing.

How to get a real number for your shop

Scope is what turns a vague range into a price. The tighter the task, the tighter the quote, so bring one bottleneck rather than your whole operation.

  • Write the task as one sentence with a trigger and a finish line. When a call is missed, a text goes out and the job lands on the schedule.
  • List the systems it touches by category: phone and SMS, scheduling, CRM, accounting.
  • Note the exceptions you already know about, and where you want a person to approve before anything sends.
  • Bring your own payback arithmetic, so you know your walk-away number before anyone quotes you.

We run this as a free fixed-scope workflow walkthrough: we map how the work moves, rank the bottlenecks and attach an impact estimate to each, and the plan is yours to price with anyone. If a build makes sense, the quote and statement of work arrive in writing first, every action the system takes is logged, and exceptions always route to a person with the context in front of them.