The cost follows the process you want to improve
Business automation cost depends on what needs to happen, which tools need to connect and what happens when the normal process goes wrong. A reliable connection between two existing apps is different from a shared system for jobs, staff, documents and customer updates.
At JS Automates, focused automations start from $100 USD. That is a starting point for a small, defined task, not a price for a complete CRM or business system. Larger builds are quoted after we agree what the first version must do. A one-hour consultation is $100 if you want to work through the choices first.
Start with one outcome: an accepted order becomes a preparation job with its agreed details, or a received repair item becomes a record your team can follow through to collection. List the steps needed to reach that outcome before comparing prices.
Three scopes that involve different amounts of work
These are illustrative scopes, not packages or price bands. They show why two requests described as “an automation” can require very different work.
| Illustrative scope | What the build covers | What needs deciding |
|---|---|---|
| One reliable connection | An approved record creates or updates the matching record in another tool. | Field matching, duplicate handling and what the owner sees if the connection fails. |
| A multi-stage workflow | An accepted job moves through preparation, work and completion with the right staff tasks and customer messages. | Who approves each handover, how changes are handled and when a message should stop. |
| A custom internal system | A shared place for jobs, item records, notes, photos, documents and different staff permissions. | Access rules, existing records, the screens people need and the first complete process to deliver. |
Separate the build price from running costs
Ask for a quote that separates development from the services the system uses. Development is the work of agreeing the scope, building, checking and handing over that version. A subscription or usage charge belongs to the connected service, not automatically to the developer.
A workflow using software you already pay for may need little additional running cost. Another may need an automation subscription, paid messaging, hosting or storage. AI usage is relevant only when the process actually needs an AI model. Free tiers can be useful, but their limits should be checked against your expected usage.
Optional ongoing support and future features should be discussed separately. Ask who owns the accounts, what happens if you stop a subscription and who deals with a failed connection. Do not assume every custom project requires a monthly maintenance contract, or that every connected service is free.
| Cost to check | Useful question |
|---|---|
| Development | Which working process, checks and handover are included? |
| Software subscriptions | Can we use the accounts I already have? |
| Usage charges | What changes when there are more messages, jobs or AI requests? |
| Hosting and storage | Where do the records live, and what are the limits and backup arrangements? |
| Later support or changes | What is included after delivery, and what is a separate request? |
Measure the time that could actually be released
For a few normal working days, note how often the task happens and how long it takes. Include finding the details, copying them, checking the result and correcting mistakes. Separate that repeated work from the judgement that a person still needs to make.
Here is a hypothetical example. A customer-status task takes 15 minutes and happens 20 times a week. That is 300 minutes, or five hours of current work. If an improved process still takes five minutes per case for checking and exceptions, it could release 200 minutes, or three hours and 20 minutes. The example is an assumption to test, not a promised saving.
In the calculator, enter the current time and the time you expect to remain. Add a build estimate only when you have a scope or a quote. Include running costs and try a lower-volume case. An hourly value helps compare options, but having time back is not automatically the same as cutting a cash expense.
Some benefits do not fit neatly into a money total: a clearer job overview, fewer missed handovers, consistent customer messages and less dependence on one person remembering everything. Record those alongside the estimate instead of assigning them invented revenue.
Illustrative calculation: 20 × 15 minutes = 5 hours. After 20 × 5 minutes of remaining work, the possible time released is 3 hours 20 minutes per week.
What can make a project more involved?
Old records may need cleaning before they can be moved. Different staff may need different permissions. A tool may not provide the connection you need. The same job may change several times after it is approved. Each of these affects the work involved.
Exceptions are part of the scope. Decide what happens if a customer changes the date, a payment has not arrived, required details are missing or a message fails. Someone should be able to see the problem and take over without recreating the whole job.
A useful first phase finishes one complete journey. It might take an approved order into the work list and send its confirmation while leaving stock management for later. A smaller complete process is easier to assess than several disconnected features.
What to bring when you ask for a quote
Describe how the work happens today, what gets repeated and what you want the owner, team or customer to be able to do. Name the tools that need to stay. Give a rough weekly volume and the time spent on the repeated task. You do not need to know the technical solution.
Include one normal case and one difficult case, with private details removed. State which decisions stay with you, what information people need and how you would judge the first version useful.
Use the project brief to put those details together. If the main question is which approach to choose, bring it to a one-hour consultation. If you already know the process you want improved, ask about a scoped build. The next step is a clear agreement about what will work, not a guess at the price of “automating everything”.
What would make your business easier to run?
Describe the process, the repeated work and the tools you use. I can build a complete improvement around your business.
Plan my automation improvement
See custom CRM development, or talk through the choices in a consultation.
Discuss your project