Practical answers · updated regularly
Direct answers to the questions people ask before paying for an AI agent, automation, website or cloud build. Short version first; detail when you need it.
The answer library
Search the full library or filter by service. Every card includes the direct answer before you decide whether to read the detail.
24 answers
A usable AI agent for a small business starts around $150 for a chat assistant trained on your own answers, and $300–$500 once it books from a live calendar or takes phone calls. Running costs are separate and usually small — typically a few dollars to a few tens of dollars a month in model and telephony usage.
Zapier is the easiest to start with and the quickest to get expensive. Make is cheaper at volume and better for branching workflows, with a steeper learning curve. n8n is the most flexible and the only one you can self-host, which matters when runs are high or data cannot leave your infrastructure.
An AI receptionist handles the repetitive end well: answering common questions, qualifying an enquiry, and booking from a live calendar, at any hour. It should not handle pricing exceptions, complaints, or anything it has not been given a clear answer for — those belong to a person, and the handoff is what makes the rest safe.
If information is being retyped between tools, you need automation. If enquiries are simply not arriving, automation will not help — a shorter form and one clear next step usually will, and it costs less. The test is whether your problem is after the enquiry or before it.
Buy the monthly product if the job is one sentence: answer the phone, use one calendar, and take a message. Have one built when the assistant must follow your rules, write into tools you already use, and refuse to invent a price or a slot. A hosted plan is often $49–$500 a month. A defined build here starts at $150 for chat and $500 for voice.
Hire the person who can say what happens when a step fails at 2am, how a duplicate is caught, and where the workflow will live. A screenshot of a happy path is not proof. A first workflow connecting two tools starts at $120 here; a multi-source intake with de-duplication starts at $250.
Use a WhatsApp AI agent when customers already message you there and a person is retyping the same answers. Use Meta’s official platform for a number you cannot afford to lose. The WhatsApp Business app is free and enough for a single phone. A build on top is worth it only once messages must land in your CRM with a human handoff. Message fees are Meta’s, by country, and they are separate from the build.
Hire a Salesforce freelancer when the org already exists and the work is specific: fields, page layouts, flows, assignment, or a report the team actually opens. You do not need a rebuild to tidy that up. A first pass starts at $150. Custom objects and flows start at $300. Connecting Salesforce to the rest of the stack, or standing up AWS around it, is a larger written scope from $480.
A chat assistant trained on your answers takes 3–5 working days. One that books from a live calendar takes 7–10. Voice with a CRM record takes 2–3 weeks. A single automation is often 2–4 days; a full intake is 1–2 weeks. Those dates assume access and answers arrive when asked. Waiting on a login moves the date more than the build does.
A missed call, a form, and a social message should become one record: who it was, where it came from, and a follow-up with a date and an owner. If that write fails, a person should be told and the original message kept. Buying an AI receptionist before this exists answers the phone and then loses the lead in the same spreadsheet as before.
You own the agent if the phone number, the model account, the calendar, and the CRM are in your name, and you can change the opening line, read recent conversations, and switch the assistant off without messaging the person who built it. A working demo on someone else’s login is a rental. Support after handover is 7, 14, or 30 days for the agreed scope, not a permanent on-call.
A website chatbot meets people who are already on your site and willing to type. An AI receptionist meets people who dial your number. A human answering service is a person taking that call, often to pass a message on. If customers call while you are on a job, start with the phone. If they browse and ask the same questions, start with chat. If the caller is upset or the decision is not written down, a person should take it.
Buy an AI workflow when a person is retyping the same record between a form, an inbox, and a CRM. Buy an AI agent when a customer is waiting for an answer in chat, on WhatsApp, or on the phone. The agent should still end by writing that record. A workflow starts at $120. A chat agent starts at $150. If nothing is arriving, neither one is the first purchase.
Hire a freelancer when the job is one assistant or one workflow, the boundary is written, and the accounts will be in your name. Hire an agency when you need several people on call, more than one location, or a compliance programme that has to outlive a single builder. A package here is $120–$500 for a defined scope. That is not a multi-month agency engagement, and it should not be described as one.
Hire the developer who can show the boundary, what happens when a step fails, and whose account the agent lives in. Pay for one small scope first. A chat assistant on answers you have already written starts at $150 and takes 3–5 working days. A developer who says the assistant can answer anything, or who quotes a build with no running cost, is selling a demo.
A website AI chatbot, as sold here, is a widget that answers up to twenty questions you wrote, collects a name and an enquiry, and emails you. That is $150, delivered in 3–5 working days, with 7 days of fixes. It does not offer calendar slots and it does not answer the phone. Those are the $300 and $500 packages. A widget pointed at a general model, with no approved answers, will invent facts about your business.
A person should take over when the question is not in the approved answers, when the customer asks for a human, or when the assistant would have to invent a price, a policy, or an apology. The $150 chat package emails you the enquiry and stops. A defined handoff is part of the $300 booking package. An agent that keeps talking past that line is the one that makes something up.
Email automation should file the message, match the person you already have, and draft a reply a human sends. It should not email the customer on its own unless the wording is one you approved in advance. Connecting an inbox to your CRM is a workflow from $120. A model that negotiates, discounts, or apologises is an agent, and it needs a written boundary.
Hire for Salesforce when the org already exists and the job is fields, a flow, a report, or a permission clean-up. Hire for AWS when something you run needs a server, storage, a domain, or a deploy you can roll back. They are separate scopes on one gig. The $150 package is one of them, not both. I configure Salesforce. I do not sell Apex, and I do not claim a certification.
A success message means the workflow finished its steps. It does not mean the CRM row exists, the email left the building, or the same person was not created twice. The $120 package emails you when a step fails. Keeping the failed payload so it can be replayed, and making a retry safe, is the $450 package. Ask where a failed run is visible before you trust the green check.
An AI scheduling assistant should book only a slot your live calendar marks free, for the right duration, with the gap you actually need between jobs. An empty hour is not free if you are travelling, the service is the wrong length, or that person does not do that job. Offering real availability is the $300 package. Chat that only collects a preferred time is $150, and a person still confirms it.
Let an AI receptionist answer after hours only when the night rules match the day rules: the same approved answers, the same live calendar, and the same reasons to stop. If you cannot do the job in the morning, it should say so and take a message, not book a promise. Voice on a phone number is the $500 package. After-hours is a setting on that agent, not a separate product.
A landing page is one responsive page, one validated form, and submissions to your inbox. That is $180, in 4–7 working days. A business site of up to six pages, with the form wired into a CRM, is $350. A web or mobile app with accounts and an admin view is $500 and takes 3–5 weeks. If people are not arriving, start with the page. An app will not create the enquiry.
Send the answers the assistant is allowed to give, access to the calendar or CRM in an account you own, and one real enquiry that was messy. Without those, the date moves, because approval takes longer than the install. A chat assistant is 3–5 working days once twenty answers and site access are in hand. I will not start the build on a login that only I control.
