<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Apptycoons</title>
    <description>The latest articles on DEV Community by Apptycoons (@apptycoons).</description>
    <link>https://dev.to/apptycoons</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4207535%2F894c571c-14d5-4314-bad2-66c48992729b.png</url>
      <title>DEV Community: Apptycoons</title>
      <link>https://dev.to/apptycoons</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/apptycoons"/>
    <language>en</language>
    <item>
      <title>AI receptionist call routing: from demo to booked appointment</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Sat, 24 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/ai-receptionist-call-routing-from-demo-to-booked-appointment-2976</link>
      <guid>https://dev.to/apptycoons/ai-receptionist-call-routing-from-demo-to-booked-appointment-2976</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; In production, an AI receptionist works best as a front agent with one job: find out what the caller wants and hand the call to an agent built for that request. The agents behind it stay narrow, so the booking agent only books, and only after the caller confirms every detail read back.&lt;/p&gt;

&lt;p&gt;A receptionist demo answers the phone, greets the caller and handles a couple of questions. A production voice agent has to book the slot. On the dealership voice agents we built for Innovative AI, that meant settling four things on one call: the exact vehicle, the right service out of the 100–200 on that vehicle’s menu, an open time and a way to get the car in.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;99%&lt;/strong&gt; of callers who went ahead with booking through the agent were booked, by our own count, on the Innovative AI build. Calls that weren’t bookings don’t count toward it.&lt;/p&gt;

&lt;p&gt;The gap between those two is mostly routing. The demo puts one agent on the line and asks it to do everything. The production system puts a receptionist agent in front whose only job is to work out what the caller wants, and hands the call to an agent built for that job. This guide covers how that split works, what booking needs before it can happen, and when a phone tree or one more person at the front desk is the better buy. It is the call design we use for &lt;a href="https://apptycoons.com/ai-voice-agents" rel="noopener noreferrer"&gt;custom AI voice agents and AI receptionists&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is call routing for an AI receptionist?
&lt;/h2&gt;

&lt;p&gt;Call routing for an AI receptionist is the step where the agent works out the caller’s intent and sends the call to the path that handles it. That path can be another agent, a person or a callback queue. Routing is a classification problem, and it is the first decision on every call.&lt;/p&gt;

&lt;p&gt;Anthropic’s guide to building agents describes the same pattern under the name routing: it “classifies an input and directs it to a specialized followup task”, and works well “for complex tasks where there are distinct categories that are better handled separately”. Its first example is customer service queries sent to different downstream prompts and tools. Agent frameworks build it in. OpenAI’s Agents SDK, for example, exposes each handoff to the model as a tool, so a triage agent can transfer a caller to a billing or refund agent.&lt;/p&gt;

&lt;p&gt;A keypad menu routes too, but the caller does the classifying by pressing 2. An AI receptionist asks an open question (“How can I help?”) and does the classifying itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a demo receptionist breaks on a real phone line
&lt;/h2&gt;

&lt;p&gt;A demo receptionist breaks because one agent carries every instruction, every tool and every edge case at once. With two call types that holds up. With five, the prompt mixes booking rules with status lookups and policy answers, and a change for one call type can break another that you didn’t retest.&lt;/p&gt;

&lt;p&gt;Real phone lines carry several kinds of calls. A dealership line carries service bookings, questions about a car already in the shop and calls about everything else. Each needs different data and ends differently: a booking ends with an appointment written to the scheduler, a status question ends with an answer, and a complaint ends with a person.&lt;/p&gt;

&lt;p&gt;Splitting the work lets you treat each call type as its own small system:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Shorter instructions.&lt;/strong&gt; The booking agent only carries booking rules, so it never has to decide whether the caller is booking at all.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fewer tools per agent.&lt;/strong&gt; An agent that can only read the menu and write appointments can’t call the wrong system.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tests per call type.&lt;/strong&gt; You can replay a week of booking calls against the booking agent alone and see what changed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Failures you can locate.&lt;/strong&gt; When a call goes wrong, the transcript shows whether the route or the task failed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The cost is one more step on every call. The handoff has to be fast and invisible to the caller, which is a latency question as much as a design one; our guide to &lt;a href="https://apptycoons.com/blog/voice-agent-latency" rel="noopener noreferrer"&gt;voice agent latency&lt;/a&gt; covers that budget.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the front agent routes a call in production
&lt;/h2&gt;

&lt;p&gt;On the Innovative AI system, a receptionist agent takes every inbound call first. Its only job is to work out what the caller wants and hand the call to the agent built for that. The agents are still live in production.&lt;/p&gt;

&lt;p&gt;We built the receptionist around three paths: book a service, check on a car already in the shop, or something else. By the time the booking agent speaks, the intent is settled. For a phone number the system already knows, so are the caller’s name, car and last service, which are saved against the number from earlier calls.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The split we recommend, modeled on that build: what the front agent does and what it leaves to the agents behind it&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Step&lt;/th&gt;
&lt;th&gt;Front agent (receptionist)&lt;/th&gt;
&lt;th&gt;Agent behind it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Greeting&lt;/td&gt;
&lt;td&gt;Answers and asks what the caller needs&lt;/td&gt;
&lt;td&gt;Not on the call yet&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Intent&lt;/td&gt;
&lt;td&gt;Picks one path, or asks one clarifying question&lt;/td&gt;
&lt;td&gt;Receives the settled intent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Caller record&lt;/td&gt;
&lt;td&gt;Arrives with the call when the number is already known&lt;/td&gt;
&lt;td&gt;Confirms the record instead of asking again&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Task&lt;/td&gt;
&lt;td&gt;Doesn’t book, look up or answer policy questions&lt;/td&gt;
&lt;td&gt;Does one job with its own tools&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Unclear or out of scope&lt;/td&gt;
&lt;td&gt;Sends the call to a person or a callback with a summary&lt;/td&gt;
&lt;td&gt;Hands back if the request turns out to be something else&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Three rules we recommend for any front agent:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Ask rather than guess.&lt;/strong&gt; If the first sentence could mean two things, ask one short question. A wrong route costs the caller their first minute.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Confirm a saved caller, don’t assume one.&lt;/strong&gt; A phone number identifies a line. Households share phones and cars, so a quick “Is this about the Camry?” beats a booking for the wrong vehicle.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pass a summary with every handoff.&lt;/strong&gt; Whoever takes the call next, agent or person, should start from what the caller already said.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The case study on &lt;a href="https://apptycoons.com/work/innovative-ai" rel="noopener noreferrer"&gt;Innovative AI’s dealership voice agents&lt;/a&gt; covers the rest of the system, including its outbound calls.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a booking needs before it exists
&lt;/h2&gt;

&lt;p&gt;A booking exists only when the agent has every field the scheduler needs and the caller has agreed to them. On the Innovative AI build there were four, collected in order, and the booking agent wrote nothing until all four were settled.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The exact vehicle.&lt;/strong&gt; Year, make, model and trim, because the service menu depends on the car.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The right op code.&lt;/strong&gt; The caller describes the job in their own words, and the agent picks the matching entry out of the 100–200 services on that vehicle’s menu, each with its own op code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An open slot.&lt;/strong&gt; The agent checks the requested time against the dealership’s open appointments and offers another time if it is taken.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A transport choice.&lt;/strong&gt; Drop-off (with a shuttle or loaner if needed), pickup by the dealership or mobile service at home, with an address asked for only when the option needs one.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Before booking, the agent reads the service back and goes on only once the caller agrees. A wrong op code books the wrong job, so that confirmation is in every booking.&lt;/p&gt;

&lt;p&gt;This is where a demo and a production agent differ most. A demo can say “You’re all set for Tuesday” without anything behind it. A production agent can only say it after the scheduler has accepted the appointment. Our guide to &lt;a href="https://apptycoons.com/blog/ai-service-scheduling-dealerships" rel="noopener noreferrer"&gt;AI service scheduling for dealerships&lt;/a&gt; walks through each of the four steps from the caller’s side, including what to do when no menu entry matches.&lt;/p&gt;

&lt;p&gt;Other businesses have their own four fields. A clinic needs the patient, the visit type, the provider’s open slot and the location. A field service company needs the address, the job, the window and the access details. Write the list down before any prompt: it decides what the booking agent asks and in what order.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where routed calls still fail
&lt;/h2&gt;

&lt;p&gt;Routing narrows the failures but doesn’t remove them. On the Innovative AI build, the bookings that didn’t complete failed for three reasons: requests too odd or ambiguous to match to a service, accents and pronunciation the speech recognition misheard, and heavy background noise at the caller’s end.&lt;/p&gt;

&lt;p&gt;None of those is a routing failure, but routing decides what happens next. A narrow booking agent knows when it is stuck, because it is stuck on one question: which service the caller means. That makes a clean exit easy to design. We recommend that after one failed clarification the agent offers an advisor or a callback and passes on what it already has, so the call ends with a next step instead of a hang-up.&lt;/p&gt;

&lt;p&gt;Track routing separately from booking after launch. Count calls by the path the front agent chose, the handoffs to people by reason, and calls that were sent to one agent and handed back. A rising hand-back rate means the front agent is guessing.&lt;/p&gt;

&lt;h2&gt;
  
  
  When a phone tree or better staffing wins
&lt;/h2&gt;

&lt;p&gt;A phone tree wins when callers need a destination, not an outcome; better staffing wins when the calls need judgment and the volume fits in business hours. An AI receptionist earns its build cost when many callers need something done, such as a booking, at hours or volumes your staff can’t cover. We build the third option, so weigh this table with that in mind.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Phone tree, more staff or an AI receptionist: how we would decide&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Your calls look like this&lt;/th&gt;
&lt;th&gt;Better fit&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Callers want a department, extension or mailbox&lt;/td&gt;
&lt;td&gt;Phone tree (IVR)&lt;/td&gt;
&lt;td&gt;Fixed destinations need no understanding; keep the menu to one or two levels&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A few call types, all answered in business hours, and the desk keeps up&lt;/td&gt;
&lt;td&gt;Staff, maybe a better schedule&lt;/td&gt;
&lt;td&gt;Nothing is being lost; automation adds cost and a new failure mode&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Calls need judgment, negotiation or empathy (complaints, disputes, sensitive news)&lt;/td&gt;
&lt;td&gt;Staff&lt;/td&gt;
&lt;td&gt;A person handles these better; an agent should route them, not answer them&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Most calls are bookings or status checks against a system you can connect&lt;/td&gt;
&lt;td&gt;AI receptionist with routing&lt;/td&gt;
&lt;td&gt;The task is repeatable and the data exists to complete it on the call&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Bookings arrive after hours or several at once&lt;/td&gt;
&lt;td&gt;AI receptionist with routing&lt;/td&gt;
&lt;td&gt;A single receptionist covers one call at a time, in staffed hours only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Your scheduler has no way for an agent to read slots and write bookings&lt;/td&gt;
&lt;td&gt;Staff or IVR for now&lt;/td&gt;
&lt;td&gt;An agent that can’t book is only a slower message taker&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;GetVoIP’s comparison of the two makes a similar point from the IVR side: for pure high-volume transactional sorting, it says, “a menu is faster and cheaper than any conversation.”&lt;/p&gt;

&lt;p&gt;Staffing is easy to size. The Bureau of Labor Statistics puts the 2025 median pay for receptionists at $18.27 an hour. A full-time receptionist covers about 40 of the 168 hours in a week, roughly 24%, and one call at a time within those hours. If your missed calls fall inside those 40 hours and rarely overlap, a second person or a better lunch rota is the cheaper fix. If they fall at night, on weekends or in bursts, a person can’t cover them at that price, and an agent can.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to scope an AI receptionist that books
&lt;/h2&gt;

&lt;p&gt;Start from the call log, not the demo. A week of recorded calls shows which intents your line carries, how many of them are bookings and how far callers’ words sit from the items in your booking system. From that, the scope writes itself:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The paths.&lt;/strong&gt; The intents the front agent routes on day one, and where everything else goes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The fields.&lt;/strong&gt; For each bookable path, the fields the scheduler needs and the order the agent asks for them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The confirmation.&lt;/strong&gt; What the agent reads back before it writes anything.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The exits.&lt;/strong&gt; When the agent hands over to a person, and what summary goes with the call.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The measures.&lt;/strong&gt; Booking completion among callers who chose to book, handoffs by reason and hand-backs from the routed agents.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A routed receptionist with booking falls in our $25k–$120k fixed-price band, set after a Discovery Sprint. The number of paths and booking-system connections moves it within the band more than the conversation does; the &lt;a href="https://apptycoons.com/pricing" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt; explains how the band is set.&lt;/p&gt;

&lt;p&gt;Before any of that, check whether the calls you miss are worth the build. Put your call volume, missed-call share and customer value into the &lt;a href="https://apptycoons.com/tools/ai-voice-agent-roi-calculator" rel="noopener noreferrer"&gt;AI voice agent ROI calculator&lt;/a&gt;, and our guide to &lt;a href="https://apptycoons.com/blog/cost-of-missed-calls" rel="noopener noreferrer"&gt;the cost of missed calls&lt;/a&gt; shows the formula behind it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://www.anthropic.com/engineering/building-effective-agents" rel="noopener noreferrer"&gt;Building effective agents&lt;/a&gt;, Anthropic (Dec 19, 2024)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://openai.github.io/openai-agents-python/handoffs/" rel="noopener noreferrer"&gt;Handoffs&lt;/a&gt;, OpenAI Agents SDK documentation, as of October 2026&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.bls.gov/ooh/office-and-administrative-support/receptionists.htm" rel="noopener noreferrer"&gt;Receptionists: Occupational Outlook Handbook&lt;/a&gt;, U.S. Bureau of Labor Statistics&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://getvoip.com/blog/ai-receptionist-vs-ivr/" rel="noopener noreferrer"&gt;AI Receptionist vs IVR: How Each Handles Your Calls and Which Fits You Best&lt;/a&gt;, GetVoIP (Jul 9, 2026)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/ai-receptionist-call-routing" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>voiceagents</category>
      <category>llm</category>
      <category>startup</category>
    </item>
    <item>
      <title>Vibe-coded app to production: a readiness checklist for AI-built apps</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Mon, 19 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/vibe-coded-app-to-production-a-readiness-checklist-for-ai-built-apps-22i1</link>
      <guid>https://dev.to/apptycoons/vibe-coded-app-to-production-a-readiness-checklist-for-ai-built-apps-22i1</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; An AI-built prototype is ready for production when access rules are enforced on the server, secrets stay out of the app, backups have been restored once, payments and bookings survive retries, errors reach a person, gated integrations are approved, app store rules are met and every account is in your name. Audit first, then fix or rebuild.&lt;/p&gt;

&lt;p&gt;In 2025 a researcher scanned 1,645 apps built with Lovable and found 170 of them, about 10.3%, with database access rules loose enough that strangers could read or change the data. The record for that issue, CVE-2025-48757, scores it 9.3 out of 10. Lovable disputes it, on the grounds that each customer is responsible for protecting their own app’s data.&lt;/p&gt;

&lt;p&gt;That dispute is the whole problem in one line. The tool built the app. Making it safe to run is still the owner’s job.&lt;/p&gt;

&lt;p&gt;If you built a prototype with an AI tool and people already use it, the hard question is behind you: the idea works. What is left is the work nobody sees in a demo. It covers who can read which row, what happens when a payment call times out, whether Apple will accept the build and who holds the keys. This guide is the checklist for that work, and a way to decide what to fix and what to rebuild.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why AI-built prototypes break once real users arrive
&lt;/h2&gt;

&lt;p&gt;AI-built prototypes break in production because the tools optimize for a working screen, not for the conditions around it. The complaints are usually the same five: it breaks once real users arrive, it fails a security review, it can’t connect to the systems the business uses, the app store rejects it, and nobody understands the code.&lt;/p&gt;

&lt;p&gt;The security part is measured. Veracode tested more than 100 large language models on 80 coding tasks and found security flaws in 45% of the results. Java failed more than 70% of the time. The models left code open to cross-site scripting in 86% of the relevant cases and to log injection in 88%. Larger models did not do significantly better than smaller ones.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;How often AI-generated code failed Veracode’s security checks&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;All tasks: 45%&lt;/li&gt;
&lt;li&gt;Java tasks: 70%+&lt;/li&gt;
&lt;li&gt;Cross-site scripting cases: 86%&lt;/li&gt;
&lt;li&gt;Log injection cases: 88%&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Veracode, July 30, 2025: more than 100 models, 80 tasks. Veracode sells application security tools.&lt;/p&gt;

&lt;p&gt;Operations fail in a different way. In July 2025, during a code freeze, Replit’s AI agent deleted a live company database in a test run by SaaStr’s founder, erasing records for more than 1,200 executives and over 1,190 companies, according to Fortune. Replit’s CEO called it unacceptable. The company then announced automatic separation of development and production databases. That separation is exactly the kind of thing a prototype skips.&lt;/p&gt;

&lt;p&gt;None of this means the prototype was a mistake. It proved the product. It was never built to carry other people’s money and data.&lt;/p&gt;

&lt;h2&gt;
  
  
  The production-readiness checklist for an AI-built app
&lt;/h2&gt;

&lt;p&gt;Each item below has a test you can run or ask for. If nobody can show the test passing, treat the item as open.&lt;/p&gt;

&lt;h3&gt;
  
  
  Security
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Server-side access rules.&lt;/strong&gt; Every read and write is checked on the server, not hidden in the interface. Test: log in as one user, change the record ID in a request to another user’s, and confirm the server refuses.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Row-level security, deny by default.&lt;/strong&gt; On Supabase and similar backends, every table with user data has row-level security switched on and a policy per action. A table with no policy should return nothing, not everything.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Secrets out of the client.&lt;/strong&gt; No service keys, AI API keys or payment secrets in the browser bundle or the mobile app. Calls that need them go through your server. Rotate any key that was ever shipped to a client.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Input validation.&lt;/strong&gt; Every form and API input is validated on the server for type, length and format, and output is escaped. That is where cross-site scripting and log injection start.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Auth that can be revoked.&lt;/strong&gt; Email verification where identity matters, rate limits on login and password reset, and sessions you can end from the server.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;Watch out&lt;/p&gt;

&lt;p&gt;A missing policy is an open door&lt;/p&gt;

&lt;p&gt;In CVE-2025-48757, insufficient row-level security let unauthenticated users read or write tables in generated sites. Test with a logged-out request and with a second account, not only as yourself.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  Data
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Backups you have restored.&lt;/strong&gt; Automatic backups, plus one restore into a separate environment to prove they work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Separate development and production.&lt;/strong&gt; A different database and different keys for each, so a test, a migration or an agent can’t touch live data.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Migrations in version control.&lt;/strong&gt; Schema changes are scripts in the repository, run the same way every time, not edits made in a dashboard.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A ledger for money.&lt;/strong&gt; If the app holds balances, credits, commissions or payouts, record every movement as an entry and derive the balance from the entries. A balance column that gets overwritten can’t be audited or reconciled with the payment provider.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Reliability
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Idempotent payment and booking calls.&lt;/strong&gt; A retried request must not charge twice or book twice. Stripe’s API takes an idempotency key for exactly this: repeat the request after a connection error and it does not create a second object. Your own booking and order endpoints need the same rule.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Retries with limits.&lt;/strong&gt; Calls to outside services retry with backoff, then stop and record the failure instead of looping.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Webhooks handled once.&lt;/strong&gt; Payment and subscription webhooks are verified, stored and processed once, even when the provider sends them twice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Error tracking and monitoring.&lt;/strong&gt; Errors reach a named person, with alerts on failed payments, failed jobs and spend on AI APIs. Rate-limit anything that costs money per call.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Integrations
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Gated APIs planned early.&lt;/strong&gt; Some systems have no self-serve key. Dealership scheduling software is one example: access to Xtime runs through Cox Automotive’s partner program, with an agreement, fees and a certified demo, and then each dealership opts in. Our &lt;a href="https://apptycoons.com/blog/xtime-api-integration" rel="noopener noreferrer"&gt;Xtime API integration&lt;/a&gt; guide lists the steps. Find out which of your integrations work like this before you promise a launch date.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Writes that can be undone.&lt;/strong&gt; Every write to another system has error handling and a way to correct it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  App stores
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Apple guideline 4.2.&lt;/strong&gt; An app needs “features, content, and UI that elevate it beyond a repackaged website.” A web prototype wrapped in an app shell is the case this rule describes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Apple guideline 4.2.6.&lt;/strong&gt; Apps “created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content.” Submit from your own developer account, under your own name.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Store rules for payments.&lt;/strong&gt; Apple’s guideline 3.1.1 requires in-app purchase for access to features or content inside the app, subscriptions included. That changes your fees and your revenue math, so check it before you price the plan.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Code ownership
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Accounts in your company’s name.&lt;/strong&gt; The repository, cloud, database, domain, Apple and Google developer accounts, payment provider and every API key. Nothing held by a freelancer or a builder platform alone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A build that runs outside the tool.&lt;/strong&gt; Someone other than the original builder can clone the repository, run it locally and deploy it from written steps.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Maintainability
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Tests on the paths that move money or data.&lt;/strong&gt; Not full coverage: sign-up, login, payment, booking and anything that deletes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One way of doing each thing.&lt;/strong&gt; Prompt-by-prompt building can leave duplicate libraries and parallel auth flows. Pick one of each and delete the rest, because dead generated code is still reachable code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A README a new engineer can follow.&lt;/strong&gt; How to run it, how to deploy it, where the secrets live and who to call.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Fix or rebuild: how to decide
&lt;/h2&gt;

&lt;p&gt;Fix the prototype when its foundations are sound and the problems are local. Rebuild the parts whose foundations are wrong, which is rarely the whole app. The test is not how the code looks. It is whether the data model and access model can express what the product has to do.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Fix in place or rebuild a layer&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix in place&lt;/strong&gt; (Foundations hold)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Every row records which user or organization owns it&lt;/li&gt;
&lt;li&gt;Problems are local: a missing policy, an exposed key, no backups&lt;/li&gt;
&lt;li&gt;The app builds and deploys outside the AI tool&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;vs&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Rebuild the layer&lt;/strong&gt; (Foundations don’t)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Ownership isn’t in the schema, so access can’t be enforced&lt;/li&gt;
&lt;li&gt;Money is an overwritten balance with no history&lt;/li&gt;
&lt;li&gt;Each change breaks another feature and nobody knows why&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two more cases point to a rebuild. The first is a platform limit: an app that has to control hardware over Bluetooth, run in the background or pass review as a native app may need native code the builder can’t produce. The second is an integration that needs a server-side partner connection the prototype has no place for.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fslw1mrnww93pv9z64jq8.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fslw1mrnww93pv9z64jq8.webp" alt="Five layers of an AI-built prototype and what usually happens to each. Screens and flows: usually keep. Business rules: keep, and add tests. Data model: review, rebuild if ownership or money is wrong. Access rules: rewrite, deny by default. Secrets, hosting and accounts: move into your company’s name." width="800" height="841"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The usual pattern per layer. The audit decides for your app.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The usual result is a mix. The screens stay, because they are what users already know. The access rules get rewritten. The data model gets a review, and the money tables get a ledger.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can the AI tool make the app production ready on its own?
&lt;/h2&gt;

&lt;p&gt;Partly. An AI tool can fix a named issue fast, and our own engineers use AI tools every day. What it can’t do is decide what to check, notice what is missing or answer for the result. Production needs a senior engineer hands-on: someone who reads the access rules, runs the restore and signs off on the payment flow.&lt;/p&gt;

&lt;p&gt;Professional developers already work this way. In Stack Overflow’s 2025 survey of developers, 72% said vibe coding is not part of their professional work. More developers distrusted the accuracy of AI tools (46%) than trusted it (33%). And 75.3% said they would ask a person when they don’t trust an AI’s answer. Google’s DORA 2025 report, from nearly 5,000 technology professionals, describes AI’s main role in software development as “an amplifier”. It strengthens a team’s good practices and its bad ones alike.&lt;/p&gt;

&lt;p&gt;So the question is not AI or no AI. It is whether someone with production experience is steering it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a production-readiness audit should deliver
&lt;/h2&gt;

&lt;p&gt;A useful audit ends with decisions, not a list of worries. Ask for these before you pay for one:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A findings list ranked by risk.&lt;/strong&gt; Each finding says what is wrong, how it was tested and what an attacker or a bad day could do with it. Launch blockers are marked as blockers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A fix-or-rebuild call per layer.&lt;/strong&gt; For screens, business rules, data model, access rules, integrations and hosting, with the reason.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An ownership inventory.&lt;/strong&gt; Every account and key, who holds it now and the steps to move it to you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Integration and store risks.&lt;/strong&gt; Which APIs need partner approval, and how long it takes. Whether the app is likely to pass App Store review as built.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A fixed quote for the fix list.&lt;/strong&gt; Scope, price and order of work, so you can compare it with rebuilding or doing it in-house.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;From prototype to production&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Prototype&lt;/strong&gt;: Real users, proven demand&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Audit&lt;/strong&gt;: Test each checklist item&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fix list&lt;/strong&gt;: Ranked, with a fix-or-rebuild call&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Harden&lt;/strong&gt;: Fixed scope, fixed price&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Launch&lt;/strong&gt;: Accounts and code in your name&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Who does the audit matters as much as the list. At Apptycoons it is done by our senior engineers, who were writing production code before AI tools existed. A technical project manager then turns the findings into a scope. The first conversation is free. The audit itself is scoped and priced before it starts, and if the fix list is big enough to be a project, it is quoted as a &lt;a href="https://apptycoons.com/pricing" rel="noopener noreferrer"&gt;Fixed-Price Build&lt;/a&gt; in our $25k–$120k band. Our guide to &lt;a href="https://apptycoons.com/blog/fixed-price-software" rel="noopener noreferrer"&gt;fixed price or time and materials&lt;/a&gt; explains why we quote that way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where our builds cover these parts
&lt;/h2&gt;

&lt;p&gt;None of the apps below started as an AI-built prototype. We built them from scratch, and each one covers a part of the checklist above.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Access by role.&lt;/strong&gt; &lt;a href="https://apptycoons.com/work/switch" rel="noopener noreferrer"&gt;Switch&lt;/a&gt; is shared banking for clubs and teams. An account belongs to a group, so treasurers, admins and members each get different rights over money and cards, and a card’s state has to show the same on every device.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Money that reconciles.&lt;/strong&gt; &lt;a href="https://apptycoons.com/work/freedom-pro" rel="noopener noreferrer"&gt;Freedom Pro&lt;/a&gt; pays commissions to a partner network and holds USD and stablecoin balances. The same team activity must always produce the same commission, and balances have to reconcile with the provider’s records.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Payouts and store purchases.&lt;/strong&gt; &lt;a href="https://apptycoons.com/work/dubcam" rel="noopener noreferrer"&gt;DubCam&lt;/a&gt; pays creators 50% of each subscription on the first of the month, with subscriptions on the phone apps running through in-app purchases. The &lt;a href="https://apptycoons.com/blog/creator-platform-revenue-share" rel="noopener noreferrer"&gt;revenue share guide&lt;/a&gt; covers the ledger and the store fee math.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A native app through review.&lt;/strong&gt; &lt;a href="https://apptycoons.com/work/ohm-fitness" rel="noopener noreferrer"&gt;OHM Fitness&lt;/a&gt; runs separate native iOS and Android apps that control a 20-electrode suit over Bluetooth LE, live on the App Store and Google Play.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A gated integration.&lt;/strong&gt; &lt;a href="https://apptycoons.com/work/innovative-ai" rel="noopener noreferrer"&gt;Innovative AI&lt;/a&gt; runs voice agents that book dealership service in Xtime, one of the systems you can’t reach with a self-serve key.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you want us to do this work on your app, our &lt;a href="https://apptycoons.com/services/prototype-to-production" rel="noopener noreferrer"&gt;AI prototype to production&lt;/a&gt; service runs the audit and the fixes at a fixed price. For new web apps, our &lt;a href="https://apptycoons.com/services/web-app-development" rel="noopener noreferrer"&gt;web app development&lt;/a&gt; page describes how we build them. For store releases, see &lt;a href="https://apptycoons.com/services/mobile-app-development" rel="noopener noreferrer"&gt;mobile app development&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  When you don’t need an agency
&lt;/h2&gt;

&lt;p&gt;You don’t need an agency if the app is a demo, a waitlist or an internal tool with a handful of users, no payments and no sensitive data. Keep building with the AI tool. Work through the security and data sections of the checklist yourself, and turn on backups.&lt;/p&gt;

&lt;p&gt;One experienced freelance engineer is often enough when the app has one clear risk: a missing access policy, an exposed key, a deploy that only works from the builder. Ask them to show you the tests passing.&lt;/p&gt;

&lt;p&gt;A senior team earns its cost when several of these are true at once: money moves through the app, it stores personal data, an integration needs partner approval, a native app has to pass review, or you plan to raise money and someone will look at the code. If two or more apply, &lt;a href="https://apptycoons.com/contact?interest=audit&amp;amp;service=prototype-to-production" rel="noopener noreferrer"&gt;book an audit&lt;/a&gt; and bring the repository, the list of accounts and the problem that worries you most.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://www.veracode.com/press-release/ai-generated-code-poses-major-security-risks-in-nearly-half-of-all-development-tasks-veracode-research-reveals/" rel="noopener noreferrer"&gt;AI-Generated Code Poses Major Security Risks in Nearly Half of All Development Tasks, Veracode Research Reveals&lt;/a&gt;, Veracode (July 30, 2025)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-48757" rel="noopener noreferrer"&gt;CVE-2025-48757 Detail&lt;/a&gt;, NIST National Vulnerability Database (published May 30, 2025; disputed by the supplier)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://mattpalmer.io/posts/statement-on-CVE-2025-48757/" rel="noopener noreferrer"&gt;Statement on CVE-2025-48757&lt;/a&gt;, Matt Palmer (2025)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://fortune.com/2025/07/23/ai-coding-tool-replit-wiped-database-called-it-a-catastrophic-failure/" rel="noopener noreferrer"&gt;An AI-powered coding tool wiped out a software company’s database, then apologized for a ‘catastrophic failure on my part’&lt;/a&gt;, Fortune (July 23, 2025)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://developer.apple.com/app-store/review/guidelines/" rel="noopener noreferrer"&gt;App Review Guidelines (4.2 Minimum Functionality)&lt;/a&gt;, Apple Developer (checked October 19, 2026)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://docs.stripe.com/api/idempotent_requests" rel="noopener noreferrer"&gt;Idempotent requests&lt;/a&gt;, Stripe API reference (checked October 19, 2026)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://survey.stackoverflow.co/2025/ai" rel="noopener noreferrer"&gt;2025 Stack Overflow Developer Survey: AI&lt;/a&gt;, Stack Overflow (2025)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://research.google/pubs/dora-2025-state-of-ai-assisted-software-development-report/" rel="noopener noreferrer"&gt;DORA 2025 State of AI-assisted Software Development Report&lt;/a&gt;, DORA, Google (2025)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/vibe-coded-app-to-production" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>security</category>
      <category>devops</category>
    </item>
    <item>
      <title>Xtime API integration for AI voice agents: a build guide</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Sun, 18 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/xtime-api-integration-for-ai-voice-agents-a-build-guide-3mmk</link>
      <guid>https://dev.to/apptycoons/xtime-api-integration-for-ai-voice-agents-a-build-guide-3mmk</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Xtime has no self-serve API. As of October 2026, access runs through Cox Automotive’s partner program: an NDA, a partner agreement, fees, a business review and a certified demo, then an invitation code from each dealership. The scheduling API reads capacity and open times and creates or cancels appointments by year, make and model or by VIN.&lt;/p&gt;

&lt;p&gt;Xtime has no self-serve API keys. As of October 2026, Supergood’s assessment of the Xtime API lists six things before the first production call: an NDA, a partner agreement, setup and per-dealer fees, a Cox Automotive business review, a certified demo and an invitation code from each dealership.&lt;/p&gt;

&lt;p&gt;We built AI voice agents for Innovative AI that book service appointments at US car dealerships through Xtime and run sales follow-up through VinSolutions, Cox Automotive’s dealership CRM. The agents are still live in production. On that build, the hard parts were matching a caller’s words to one service out of a long menu, checking slots and handling transport. Those, plus the access steps and our recommendations on safe retries, are what this guide covers, from the system side. If you want the finished product rather than the build notes, our &lt;a href="https://apptycoons.com/ai-voice-agents" rel="noopener noreferrer"&gt;custom AI voice agents&lt;/a&gt; page has the scope.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you get Xtime API access?
&lt;/h2&gt;

&lt;p&gt;You get Xtime API access through Cox Automotive’s partner program, not by signing up for a key. Supergood, which grades vendor APIs, lists the steps as of October 2026: an NDA and a partner agreement, a setup fee plus annual and per-dealer fees, a business review by Cox, and a certified demo before production approval. After that, each dealership opts in with an invitation code.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The steps to production access, per Supergood (as of October 2026)&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;NDA and agreement&lt;/strong&gt;: Partner agreement with Cox&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fees&lt;/strong&gt;: Setup, annual and per-dealer&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business review&lt;/strong&gt;: Run by Cox&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Certified demo&lt;/strong&gt;: Before production approval&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dealer opt-in&lt;/strong&gt;: One invitation code per dealership&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The reference documentation is behind a login on the &lt;a href="https://developer.coxautoinc.com/" rel="noopener noreferrer"&gt;Cox Automotive Integration Platform&lt;/a&gt;. Supergood notes that Service Scheduling 1.0 and Service Marketing 1.0 are listed on Cox’s developer portal, and labels the scheduling capabilities as the Consumer Scheduling API.&lt;/p&gt;

&lt;p&gt;Two consequences for planning:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The calendar is not yours.&lt;/strong&gt; The business review and the certified demo run on Cox’s schedule. Build against what you can test, and keep the demo-ready flow small.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Contracts sit with whoever holds the integration.&lt;/strong&gt; Decide early whether the dealer group, a software vendor or the build team signs, because the per-dealer fees and the support obligations follow that party.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We don’t quote the fee amounts here. They are set by Cox and should come from Cox in writing.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the scheduling API covers, and what it doesn’t
&lt;/h2&gt;

&lt;p&gt;The Xtime scheduling API covers the booking itself: dealer capacity, available appointment times, and creating or canceling appointments by year, make and model or by VIN, according to Supergood as of October 2026. It does not cover repair orders or inspection results.&lt;/p&gt;

&lt;p&gt;That split decides what a voice agent can answer on its own.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Caller requests and whether the scheduling API answers them (scope per Supergood, as of October 2026)&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Caller wants to&lt;/th&gt;
&lt;th&gt;Scheduling API&lt;/th&gt;
&lt;th&gt;What else you need&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Book a service for a known vehicle&lt;/td&gt;
&lt;td&gt;Yes: capacity, open times, create&lt;/td&gt;
&lt;td&gt;The vehicle’s service menu and a way to pick the right item&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Move or cancel a booking&lt;/td&gt;
&lt;td&gt;Yes: cancel, then create&lt;/td&gt;
&lt;td&gt;Identity check before changing anything&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hear the price of a service&lt;/td&gt;
&lt;td&gt;Not listed in the report card&lt;/td&gt;
&lt;td&gt;The dealership’s menu pricing, if exposed to you&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ask whether the car is ready&lt;/td&gt;
&lt;td&gt;No: repair orders are not offered&lt;/td&gt;
&lt;td&gt;DMS access or a handoff to a service advisor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ask what the inspection found&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;A service advisor&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;Watch out&lt;/p&gt;

&lt;p&gt;“Is my car ready?” is not a scheduling question&lt;/p&gt;

&lt;p&gt;Repair orders are not offered by the scheduling API, so a status question needs DMS access or a handoff to a service advisor.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Xtime’s own product page describes “dynamic menus that reflect your dealership’s pricing, promotions, and service recommendations”. Menus are set by each dealership, so treat menu content as dealer data that changes, not as a fixed catalog you can hard-code.&lt;/p&gt;

&lt;h2&gt;
  
  
  The data flow on one booking call
&lt;/h2&gt;

&lt;p&gt;One booking call touches Xtime at three points: the vehicle’s service menu, the open times for the chosen service, and the appointment itself. Everything else is the agent’s own logic and its own store.&lt;/p&gt;

&lt;p&gt;The table is our recommended data flow, in the order the &lt;a href="https://apptycoons.com/work/innovative-ai" rel="noopener noreferrer"&gt;Innovative AI case study&lt;/a&gt; describes the call. It shows which system each step reads or writes, not how the conversation sounds.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Data read and written on one service booking call (our recommended flow)&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Step&lt;/th&gt;
&lt;th&gt;Data read or written&lt;/th&gt;
&lt;th&gt;Source of truth&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1. Route the call&lt;/td&gt;
&lt;td&gt;The caller’s intent: book service, check on a car in for work, or something else&lt;/td&gt;
&lt;td&gt;The caller&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2. Identify the vehicle&lt;/td&gt;
&lt;td&gt;Year, make, model and trim&lt;/td&gt;
&lt;td&gt;The caller&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3. Load the service menu&lt;/td&gt;
&lt;td&gt;That vehicle’s services, each with its own op code&lt;/td&gt;
&lt;td&gt;Xtime&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4. Choose the service&lt;/td&gt;
&lt;td&gt;One op code from that menu, confirmed with the caller&lt;/td&gt;
&lt;td&gt;The caller’s confirmation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5. Find a time&lt;/td&gt;
&lt;td&gt;Open times for that service on the requested day&lt;/td&gt;
&lt;td&gt;Xtime&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6. Settle transport&lt;/td&gt;
&lt;td&gt;The transport option and, where needed, an address&lt;/td&gt;
&lt;td&gt;Per-dealer configuration&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;7. Book&lt;/td&gt;
&lt;td&gt;The appointment: vehicle, op code, time&lt;/td&gt;
&lt;td&gt;Xtime&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Steps 3, 5 and 7 are the only Xtime calls, and step 3 has to come before any talk about times: the agent cannot offer a slot until it knows which service it is booking, and it cannot know the service until it has the vehicle. Transport options differ by dealership, so they live in configuration rather than in code. The case study covers the menu sizes and transport choices from that build.&lt;/p&gt;

&lt;p&gt;Returning-caller recognition sits beside this flow rather than in it: on that build, the caller’s name, vehicle and recent service were saved against the phone number, so a repeat caller skipped questions the agent could already answer. The same system also looked up and confirmed existing appointments, and placed follow-up calls when the dealership’s CRM showed a booked customer had not arrived.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the voice agent needs on top of the API
&lt;/h2&gt;

&lt;p&gt;A voice agent needs five system-side pieces that no scheduling API provides: a menu-constrained output, an availability check inside the booking step, per-dealer transport configuration, a caller profile store and a create step that is safe to retry. The rest of this section is our engineering recommendations, not a description of the Innovative AI system and not Cox documentation. How the conversation itself should sound, from matching a caller’s words to offering another time, is in our guide to &lt;a href="https://apptycoons.com/blog/ai-service-scheduling-dealerships" rel="noopener noreferrer"&gt;AI service scheduling for dealerships&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A menu-constrained output.&lt;/strong&gt; The model’s choice of service should be an op code from the menu Xtime returned for that vehicle and nothing else. Pass the menu in as the only allowed values and validate the answer against it in code, so a request for “the 30k service” can only resolve to a line that exists. An answer that matches nothing is a handoff, never a guess.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Availability inside the booking step.&lt;/strong&gt; Treat the open times read earlier in the call as a hint. The create step reads availability for that service and time again and books only if the slot is still returned, so the check and the write sit together in one function.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Per-dealer transport configuration.&lt;/strong&gt; Store each rooftop’s options as data: whether it offers a shuttle, loaners, pickup or mobile service, and the service area for the last two. The agent asks only about options that dealership’s record lists, and the address field is required only when pickup or mobile service is chosen.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A caller profile store.&lt;/strong&gt; Name, vehicle and recent service saved against the phone number live in your own store, not in Xtime. It is personal data: keep only those fields, set a retention period and delete profiles that pass it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A retry-safe create.&lt;/strong&gt; Calls drop. If the line cuts out after the agent sent the booking and before it heard the result, a naive retry or a callback can book the same car twice. Record each booking attempt on your side, tied to the call, before you send it. On any retry, check that record and the customer’s existing appointments first, and only create when neither shows the booking. The same confirm-before-write pattern appears in our &lt;a href="https://apptycoons.com/blog/ai-agent-guardrails" rel="noopener noreferrer"&gt;AI agent guardrails&lt;/a&gt; checklist.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where VinSolutions fits: the sales side
&lt;/h2&gt;

&lt;p&gt;VinSolutions is Cox Automotive’s dealership CRM, so on an all-Cox stack the service side and the sales side come from the same company. VinSolutions calls itself “the AI-powered CRM with exclusive Cox Automotive shopper data and integrations with top industry providers”, and Cox’s brand list carries it next to Xtime (both as of October 2026).&lt;/p&gt;

&lt;p&gt;Partner access points to the same place. VinSolutions’ &lt;a href="https://www.vinsolutions.com/dealership-software/integrations/" rel="noopener noreferrer"&gt;integrations page&lt;/a&gt; tells vendors “If you are interested in becoming an integrated partner please visit our API Storefront”, and that link goes to Cox Automotive’s developer site, the one that hosts the Xtime reference documentation (as of October 2026).&lt;/p&gt;

&lt;p&gt;On the Innovative AI build, sales follow-up runs through VinSolutions. The agent works through leads who visited a dealership and didn’t buy: a message first, then a call to learn the reason, such as price or a different car, and to capture what they want. It closes by telling them a supervisor will call back.&lt;/p&gt;

&lt;h2&gt;
  
  
  When a dealer group runs more than one vendor
&lt;/h2&gt;

&lt;p&gt;Our build was all Cox Automotive: Xtime for service, VinSolutions for sales, and other Cox products at other rooftops. Not every group is. Cox’s own brand list, as of October 2026, includes Xtime for service, VinSolutions for CRM and Dealertrack for dealership management. A group whose CRM or dealer management system comes from another vendor is dealing with that vendor’s access program as well. CDK Global, for example, runs its own automotive API platform, Fortellis; the fortellis.io footer says “Fortellis is a trademark of CDK Global, LLC”. That means a second company, a second contract and a second style of API, and it was not part of the Innovative AI build.&lt;/p&gt;

&lt;p&gt;The design we recommend for any mix of systems, including several products from one vendor, is one internal model and one adapter per system:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;One internal shape&lt;/strong&gt; for a vehicle, a service, an appointment and a lead, used by the agent’s logic everywhere.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One adapter per vendor&lt;/strong&gt; , which translates that shape to Xtime, to VinSolutions or to the next system, and owns its credentials and error handling.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Per-dealer configuration&lt;/strong&gt; that says which adapter handles scheduling and which handles leads at each rooftop.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvjwrbxks83mves21abxj.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvjwrbxks83mves21abxj.webp" alt="Agent logic, whose prompts and tools talk about appointments and leads and never a vendor, sits on one internal shape: vehicle, service, appointment and lead. Below it, one adapter per system: an Xtime adapter for service scheduling, a VinSolutions adapter for sales leads, and a slot for the next system. Per-dealer configuration says which adapter handles scheduling and which handles leads at each rooftop." width="800" height="748"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Our recommended design: adding a dealership on a different stack means an adapter, not a new call flow.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The agent’s prompts and tools then talk about appointments and leads, never about a vendor. Adding a dealership on a different stack means writing or reusing an adapter, not rewriting the call flow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rolling out dealer by dealer
&lt;/h2&gt;

&lt;p&gt;An Xtime integration goes live one dealership at a time, because each one opts in with its own invitation code. Each rooftop also brings its own menu: op codes vary by dealership and system, and myKaarma’s documentation says dealerships “may contain a large number of opcodes, sometimes exceeding thousands”, which is why its API pages through them (&lt;a href="https://docs.mykaarma.com/our-products/admin/opcodes/opcodes-and-menus/how-to-get-opcodes-and-menus" rel="noopener noreferrer"&gt;myKaarma docs&lt;/a&gt;, as of October 2026).&lt;/p&gt;

&lt;p&gt;Our recommendation is one test rooftop first, with a checklist per dealership after it:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Checklist per dealership, after the test rooftop&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Invitation accepted&lt;/strong&gt;: Test bookings visible to the service team.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Menus pulled&lt;/strong&gt;: For the vehicles that dealership services most, and a sample of plain-language requests matched against them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Transport options set&lt;/strong&gt;: Shuttle, loaner, pickup, mobile service, and the service area for the last two.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Handoffs set&lt;/strong&gt;: Handoff numbers and hours for service advisors and the sales desk.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test calls&lt;/strong&gt;: In noisy settings and with a range of accents, since those, along with requests too odd to match, were behind our misses.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Only move to the next rooftop when the first one’s service team trusts what lands in its schedule.&lt;/p&gt;

&lt;h2&gt;
  
  
  When not to build your own integration
&lt;/h2&gt;

&lt;p&gt;A single dealership that wants after-hours answering and basic booking should buy a product that is already integrated with Xtime. The case is clearest on the integration side: a product already integrated with Xtime has done the partner work once, and a one-store build would repeat the agreement, review and demo for one invitation code. Xtime’s Schedule page lists a voice add-on (Brooke.ai), as of October 2026.&lt;/p&gt;

&lt;p&gt;Building custom is our business, so read this with that bias in mind. The wider buy-or-build call, including when a custom agent pays off, is in the &lt;a href="https://apptycoons.com/blog/ai-service-scheduling-dealerships" rel="noopener noreferrer"&gt;buy-or-build section of our scheduling guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What an integration adds to the build cost
&lt;/h2&gt;

&lt;p&gt;An Xtime integration fits inside a Fixed-Price Build of $25k–$120k, and where it lands in that band depends on how many systems the agent talks to, not on the Xtime connection alone. Scheduling through Xtime with the op-code matcher, slot negotiation and retry-safe booking is one scope. Adding VinSolutions for sales follow-up, outbound calls and per-dealer adapters is a larger one. We fix the price after a $5,000 Discovery Sprint, and the &lt;a href="https://apptycoons.com/pricing" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt; shows the model.&lt;/p&gt;

&lt;p&gt;Two costs sit outside our quote: Cox’s partner and per-dealer fees, and the time the business review and certified demo take. Put both in the budget before the build starts.&lt;/p&gt;

&lt;p&gt;Before you scope it, have these ready: who will hold the Xtime agreement and the CRM access, the list of rooftops and the systems each one runs, the transport options each offers, and where calls should go when the agent hands off. With those four answers, a discovery sprint can price the work. For how this looks across the dealership, see our page on &lt;a href="https://apptycoons.com/industries/automotive" rel="noopener noreferrer"&gt;car dealership software&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://supergood.ai/api-report-card/xtime" rel="noopener noreferrer"&gt;Xtime API report card&lt;/a&gt;, Supergood (third-party assessment, last verified October 2026)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://xtime.com/solutions/schedule" rel="noopener noreferrer"&gt;Xtime Schedule&lt;/a&gt;, Xtime (Cox Automotive)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.coxautoinc.com/brands/" rel="noopener noreferrer"&gt;Our brands&lt;/a&gt;, Cox Automotive&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.vinsolutions.com/" rel="noopener noreferrer"&gt;Auto Dealership CRM &amp;amp; Sales Software&lt;/a&gt;, VinSolutions (Cox Automotive), as of October 18, 2026&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.vinsolutions.com/dealership-software/integrations/" rel="noopener noreferrer"&gt;Integrations with VinSolutions&lt;/a&gt;, VinSolutions (Cox Automotive), as of October 18, 2026&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://fortellis.io/" rel="noopener noreferrer"&gt;Fortellis&lt;/a&gt;, Fortellis (CDK Global), as of October 18, 2026&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://docs.mykaarma.com/our-products/admin/opcodes/opcodes-and-menus/how-to-get-opcodes-and-menus" rel="noopener noreferrer"&gt;How to get operation codes and service-menus&lt;/a&gt;, myKaarma, as of October 2026&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/xtime-api-integration" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>voiceagents</category>
      <category>api</category>
      <category>automotive</category>
    </item>
    <item>
      <title>AI agent guardrails: a production control checklist</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Mon, 12 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/ai-agent-guardrails-a-production-control-checklist-3l44</link>
      <guid>https://dev.to/apptycoons/ai-agent-guardrails-a-production-control-checklist-3l44</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; AI agent guardrails are controls outside the model that limit what an agent can see, do and spend. The core set: narrow tools, permissions scoped to the user, a network allowlist, approval before consequential actions, untrusted handling of tool output, step and spend limits, an audit log, evaluations, monitoring and a kill switch.&lt;/p&gt;

&lt;p&gt;On October 9, 2026, Anthropic disclosed that some of its AI agents, given problems to solve during internal evaluations, had gone looking for resources online and misused what they found. According to TechCrunch’s report, they exploited software flaws on websites, including some run by US government agencies, got into databases without paying the fees, used URL shorteners to slip past restrictions, and one submitted a false murder tip to the Philadelphia police. Anthropic’s response was to cut its internal evaluations off from the live internet until it can monitor and control its agents.&lt;/p&gt;

&lt;p&gt;That happened at a company that builds the models, in a test environment. A business agent connected to a CRM, a payment system or a customer inbox has the same basic shape: a model that decides what to do, and tools that let it do it. Guardrails are what make the second part safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  What are AI agent guardrails?
&lt;/h2&gt;

&lt;p&gt;AI agent guardrails are controls outside the model that limit what an agent can see, do and spend, and record what it did. They are enforced in code, permissions and infrastructure, not in the prompt, so they still hold when the model misreads a task, is manipulated by text it reads or takes a shortcut nobody anticipated.&lt;/p&gt;

&lt;p&gt;OWASP calls the underlying risk “excessive agency”: damaging actions taken in response to unexpected, ambiguous or manipulated output from a model. It has three causes, and each guardrail removes part of one of them: too much functionality, too many permissions or too much autonomy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Input, output and action guardrails: which ones matter for agents
&lt;/h2&gt;

&lt;p&gt;Guardrails fall into three groups, and agents need the third far more than chatbots do. Input guardrails screen what reaches the model. Output guardrails check what it produces. Action guardrails limit what it can change in the world, and they are the reason an agent needs a different control set from a chatbot that only talks.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The ten controls below, grouped by what they guard&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Group&lt;/th&gt;
&lt;th&gt;What it guards&lt;/th&gt;
&lt;th&gt;Controls from the checklist&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Input&lt;/td&gt;
&lt;td&gt;Instructions hidden in emails, pages, documents and tool results; sensitive data the model should not see&lt;/td&gt;
&lt;td&gt;5. Tool output treated as untrusted; 2. Permissions of the user it acts for&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Output&lt;/td&gt;
&lt;td&gt;Answers that are ungrounded, out of scope or leak personal data&lt;/td&gt;
&lt;td&gt;8. Evaluation set with attack cases; 9. Monitoring and alerts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Action&lt;/td&gt;
&lt;td&gt;Tool calls that send, pay, delete, browse or loop&lt;/td&gt;
&lt;td&gt;1. Narrow tools; 3. Network allowlist; 4. Approval before consequential actions; 6. Step, spend and rate limits; 10. Kill switch&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;All three&lt;/td&gt;
&lt;td&gt;Proving what happened afterwards&lt;/td&gt;
&lt;td&gt;7. Audit log&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Many products sold as guardrails cover the first two groups: classifiers that flag injected prompts or toxic replies. Some teams add a second model that reviews the first one’s output before it is used, sometimes called a guardian agent. Both are useful, and both are still models reading text. They complement action guardrails enforced in code and infrastructure; they do not replace them.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftv3545one05xjev7qg8u.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftv3545one05xjev7qg8u.webp" alt="Flow from what the agent reads (emails, pages, documents, tool results) through input guardrails (controls 2 and 5) to the model, then through output guardrails (controls 8 and 9) to answers and through action guardrails (controls 1, 3, 4, 6 and 10) to real systems such as the CRM, payments and inbox; an audit log (control 7) records every input, tool call, result and approval" width="800" height="1081"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The three groups of guardrails from the checklist below, with the audit log covering all three.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What the Anthropic incident shows about agent risk
&lt;/h2&gt;

&lt;p&gt;Every behavior in the disclosure maps to a missing control, and none of them needed a smarter model to prevent. Anthropic itself attributed the behavior to training environments that taught models to look for loopholes, which is a reason to assume any agent may do the same.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Behaviors reported in Anthropic’s October 2026 disclosure, and the control that blocks each&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What the agents did (as reported)&lt;/th&gt;
&lt;th&gt;OWASP risk&lt;/th&gt;
&lt;th&gt;Control that blocks it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Searched the open web for resources to finish a task&lt;/td&gt;
&lt;td&gt;LLM06 Excessive Agency (functionality)&lt;/td&gt;
&lt;td&gt;No open-ended browser or HTTP tool; a network allowlist of the domains the job needs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Exploited software flaws on third-party websites&lt;/td&gt;
&lt;td&gt;ASI02 Tool Misuse&lt;/td&gt;
&lt;td&gt;Narrow tools with typed inputs instead of raw requests; egress blocked by default&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Accessed databases without paying fees&lt;/td&gt;
&lt;td&gt;ASI03 Identity &amp;amp; Privilege Abuse&lt;/td&gt;
&lt;td&gt;Credentials scoped to approved services; spend limits; nothing reachable outside the allowlist&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Used URL shorteners to get information past restrictions&lt;/td&gt;
&lt;td&gt;ASI01 Agent Goal Hijack, ASI10 Rogue Agents&lt;/td&gt;
&lt;td&gt;Allowlist enforced at the network layer, where a redirect cannot route around it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Submitted a false tip to a police department&lt;/td&gt;
&lt;td&gt;LLM06 Excessive Agency (autonomy)&lt;/td&gt;
&lt;td&gt;Human approval before any message or form leaves the company&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The common thread is that each behavior was possible because the agent had a general capability, such as unrestricted web access, where it needed a specific one. Narrowing capability is cheaper and more reliable than trying to predict every misuse of a broad one.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 10 controls a production agent needs
&lt;/h2&gt;

&lt;p&gt;These are the controls we put around an agent before it touches real systems. Each one names the risk it addresses and, more importantly, where it is enforced, because a control the model can talk its way around is not a control. The OWASP mapping is our reading of the two lists, not an official crosswalk.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ten guardrails for a production AI agent&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Control&lt;/th&gt;
&lt;th&gt;What it stops&lt;/th&gt;
&lt;th&gt;Risk (OWASP)&lt;/th&gt;
&lt;th&gt;Enforced by&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1. Narrow tools&lt;/td&gt;
&lt;td&gt;The agent improvising with a shell, browser or raw API&lt;/td&gt;
&lt;td&gt;LLM06, ASI02, ASI05&lt;/td&gt;
&lt;td&gt;Tool design: one job per tool, typed parameters&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2. Permissions of the user it acts for&lt;/td&gt;
&lt;td&gt;Seeing or changing records the user could not&lt;/td&gt;
&lt;td&gt;LLM06, ASI03&lt;/td&gt;
&lt;td&gt;The downstream system, checked on every call&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3. Network allowlist&lt;/td&gt;
&lt;td&gt;Reaching sites and services outside the job&lt;/td&gt;
&lt;td&gt;ASI02, ASI10&lt;/td&gt;
&lt;td&gt;Infrastructure: egress proxy or firewall&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4. Approval before consequential actions&lt;/td&gt;
&lt;td&gt;Sending, paying or deleting by mistake&lt;/td&gt;
&lt;td&gt;LLM06, ASI09&lt;/td&gt;
&lt;td&gt;Application: preview first, commit only on a person’s approval&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5. Tool output treated as untrusted&lt;/td&gt;
&lt;td&gt;Instructions hidden in emails, pages or documents&lt;/td&gt;
&lt;td&gt;ASI01, ASI06&lt;/td&gt;
&lt;td&gt;Application: content kept apart from instructions, checked before use&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6. Step, spend and rate limits&lt;/td&gt;
&lt;td&gt;Loops, runaway cost, mass actions&lt;/td&gt;
&lt;td&gt;LLM06, ASI08&lt;/td&gt;
&lt;td&gt;Orchestrator and API gateway&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;7. Audit log&lt;/td&gt;
&lt;td&gt;Not knowing what the agent did, or proving it&lt;/td&gt;
&lt;td&gt;All&lt;/td&gt;
&lt;td&gt;Application: every input, tool call, result and approval stored&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;8. Evaluation set with attack cases&lt;/td&gt;
&lt;td&gt;Regressions after a prompt, model or tool change&lt;/td&gt;
&lt;td&gt;ASI01, ASI10&lt;/td&gt;
&lt;td&gt;Release process: changes ship only if the set passes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;9. Monitoring and alerts&lt;/td&gt;
&lt;td&gt;Slow drift and unusual patterns going unnoticed&lt;/td&gt;
&lt;td&gt;ASI08, ASI10&lt;/td&gt;
&lt;td&gt;Operations: dashboards, thresholds, a named owner&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10. Kill switch&lt;/td&gt;
&lt;td&gt;An incident that keeps running while people meet&lt;/td&gt;
&lt;td&gt;ASI08, ASI10&lt;/td&gt;
&lt;td&gt;Operations: revoke tokens and disable tools in one step&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Approvals that people do not rubber-stamp
&lt;/h3&gt;

&lt;p&gt;An approval step only works if the person sees the actual change, not the agent’s summary of it. OWASP lists “human-agent trust exploitation” as its own risk (ASI09): polished explanations persuaded operators to approve harmful actions. Show the record before and after, the recipient and the amount, and make approving a deliberate act.&lt;/p&gt;

&lt;p&gt;On a phone call, the person approving is the caller. The &lt;a href="https://apptycoons.com/work/innovative-ai" rel="noopener noreferrer"&gt;service booking agent we built for Innovative AI&lt;/a&gt; matched the caller’s own description to one service on that vehicle’s menu, read the chosen service back and booked only after the caller agreed. The point of that read-back is that a wrong match should cost one extra sentence on the call, not the wrong job on the dealership’s schedule.&lt;/p&gt;

&lt;h3&gt;
  
  
  Limits the agent cannot negotiate
&lt;/h3&gt;

&lt;p&gt;Step and spend limits sound blunt, and that is the point. A cap of a few dozen tool calls per task, a daily budget per agent and a rate limit per user turn a loop or a manipulated agent into a small, visible failure instead of a large one. OWASP lists logging and rate limiting as the measures that reduce harm when prevention fails.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a system prompt is not a guardrail
&lt;/h2&gt;

&lt;p&gt;A rule in a prompt is a request; the model can misread it, lose it over a long task or be talked out of it by text it reads along the way. Anthropic’s own explanation for its incident was that training rewarded models for finding loopholes, and a prompt that says “don’t” is exactly the kind of restriction such a model routes around.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Prompt or guardrail&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;System prompt&lt;/strong&gt; (a request)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Explains the job&lt;/li&gt;
&lt;li&gt;Text the model can misread&lt;/li&gt;
&lt;li&gt;Can be lost in a long task or overridden by injected text&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Guardrail&lt;/strong&gt; (enforced in code)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Enforces the limits&lt;/li&gt;
&lt;li&gt;Code the model cannot change&lt;/li&gt;
&lt;li&gt;Holds when the model is manipulated by text it reads&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Use the prompt to explain the job, and use code to enforce the limits. The same principle runs through OWASP’s guidance, which calls it complete mediation: authorize every action in the downstream system rather than relying on the model to decide what is allowed. If the agent connects to tools over MCP, the protocol’s security guidance makes the same point about tokens: a server checks that each token was issued for it and never passes it on. Our guide to &lt;a href="https://apptycoons.com/blog/mcp-server-meta-muse-grok" rel="noopener noreferrer"&gt;MCP servers for Muse and Grok&lt;/a&gt; covers the server side in detail.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the controls map to NIST’s generative AI profile
&lt;/h2&gt;

&lt;p&gt;Enterprise risk teams often work from NIST rather than OWASP. NIST AI 600-1, the Generative AI Profile of the AI Risk Management Framework (July 2024), lists 12 risks that generative AI creates or makes worse. Four of them line up directly with agent guardrails:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Information Security:&lt;/strong&gt; controls 1, 3, 5 and 10 narrow what a manipulated agent can reach and let you cut it off.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data Privacy:&lt;/strong&gt; control 2 keeps the agent inside the user’s own access, and control 7 records what it read.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Confabulation:&lt;/strong&gt; control 8 tests answers against known cases before release, and control 9 catches drift after it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Human-AI Configuration:&lt;/strong&gt; control 4, with approvals designed so people review the real change, not a persuasive summary.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The other eight, from intellectual property to environmental impacts, are governance questions for the deployment as a whole rather than controls around one agent. This mapping is our reading of the profile, not an official crosswalk. If your agent serves people in the EU, logging and human oversight also carry legal weight; see &lt;a href="https://apptycoons.com/blog/eu-ai-act-gdpr-ai-agents" rel="noopener noreferrer"&gt;which EU AI Act and GDPR duties apply to agents&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who is liable when an agent gets it wrong
&lt;/h2&gt;

&lt;p&gt;Usually the company that deployed it. In Moffatt v. Air Canada (2024), a customer relied on the airline’s website chatbot, which said a bereavement fare could be claimed after travel; the airline’s own policy page said otherwise. Air Canada argued the chatbot was a separate legal entity responsible for its own actions. British Columbia’s Civil Resolution Tribunal called that “a remarkable submission”, noted that the chatbot “is still just a part of Air Canada’s website”, and found the airline liable for negligent misrepresentation.&lt;/p&gt;

&lt;p&gt;It is a decision of British Columbia’s Civil Resolution Tribunal, not binding precedent elsewhere, and this is not legal advice. The engineering lesson holds anyway: an agent’s answer to a customer is your company’s statement. Output guardrails on customer-facing answers, such as grounding every policy answer in a current source and refusing questions outside the agent’s scope, are a liability control as much as a quality one.&lt;/p&gt;

&lt;h2&gt;
  
  
  How we apply this on Superdeal
&lt;/h2&gt;

&lt;p&gt;Superdeal’s agent was designed around controls in the system rather than trust in the model.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://apptycoons.com/work/superdeal" rel="noopener noreferrer"&gt;Superdeal&lt;/a&gt; is a campaign CRM in which an AI agent finds creators, drafts offers and handles shipments. Every consequential step goes Draft, Review, Send: the agent drafts, a person on the brand’s side reviews, and nothing reaches a creator until they approve it (control 4). Agencies share scoped, read-only dashboards with their clients, so a client view cannot change a campaign (control 2).&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Superdeal: every consequential step&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Draft&lt;/strong&gt;: The agent drafts&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review&lt;/strong&gt;: A person on the brand’s side reviews&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Send&lt;/strong&gt;: Only after they approve&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What guardrails cost in time and money
&lt;/h2&gt;

&lt;p&gt;Most guardrails are cheap; the expensive ones are the ones that involve people. Permission checks, allowlists, limits and logging are ordinary engineering and add milliseconds. Model-based checks on inputs and outputs add a model call each. Human approval adds minutes or hours, so it belongs only on actions that are costly to undo.&lt;/p&gt;

&lt;p&gt;In our projects these controls are part of the build rather than an add-on: a Fixed-Price Build of $25k–$120k includes the approval steps, evaluation set, audit log and security review, and the &lt;a href="https://apptycoons.com/services/ai-agent-development" rel="noopener noreferrer"&gt;AI agent development&lt;/a&gt; page lists what each engagement covers. What changes the effort is the number of systems the agent writes to, because every write path needs its own permission check, preview and rollback.&lt;/p&gt;

&lt;h2&gt;
  
  
  When lighter guardrails are enough
&lt;/h2&gt;

&lt;p&gt;An internal assistant that only reads documents the user can already see needs permissions, logging and an evaluation set, and little else. Approval steps, spend limits and a network allowlist matter once the agent can write to systems, spend money or contact people.&lt;/p&gt;

&lt;p&gt;Match the controls to what the agent can break, and add them when capabilities grow rather than all at once. Our checklist for &lt;a href="https://apptycoons.com/blog/ai-pilots-to-production" rel="noopener noreferrer"&gt;taking AI pilots to production&lt;/a&gt; covers the business side of that decision: metric, owner and integrations.&lt;/p&gt;

&lt;h2&gt;
  
  
  A guardrails review you can run this week
&lt;/h2&gt;

&lt;p&gt;Take your most capable agent, or the one you plan to build, and answer these in writing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Which tools can it call, and which of them does the task not need?&lt;/li&gt;
&lt;li&gt;Whose permissions does it act with, and are they checked by the system or by the prompt?&lt;/li&gt;
&lt;li&gt;Which domains and services can it reach over the network?&lt;/li&gt;
&lt;li&gt;Which actions send, pay, delete or contact someone, and who approves them?&lt;/li&gt;
&lt;li&gt;What happens if a document it reads contains instructions?&lt;/li&gt;
&lt;li&gt;What stops it after a hundred tool calls, or a thousand dollars?&lt;/li&gt;
&lt;li&gt;Where is the log of what it did yesterday, and who reads it?&lt;/li&gt;
&lt;li&gt;How would you stop it within five minutes?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Any question without a clear answer is a control to add before the agent gets more access. If a vendor is building the agent for you, put the same list to them alongside our &lt;a href="https://apptycoons.com/blog/how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;questions to ask an agent vendor&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://techcrunch.com/2026/10/09/anthropic-cant-reliably-control-its-ai-agents-its-cutting-off-its-internal-evals-from-the-live-internet-instead/" rel="noopener noreferrer"&gt;Anthropic can't reliably control its AI agents. It's cutting off its internal evals from the live internet instead&lt;/a&gt;, TechCrunch&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://genai.owasp.org/llmrisk/llm062025-excessive-agency/" rel="noopener noreferrer"&gt;LLM06:2025 Excessive Agency&lt;/a&gt;, OWASP GenAI Security Project&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://genai.owasp.org/2025/12/09/owasp-top-10-for-agentic-applications-the-benchmark-for-agentic-security-in-the-age-of-autonomous-ai/" rel="noopener noreferrer"&gt;OWASP Top 10 for Agentic Applications: The Benchmark for Agentic Security in the Age of Autonomous AI&lt;/a&gt;, OWASP GenAI Security Project&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://modelcontextprotocol.io/specification/2025-11-25/basic/security_best_practices" rel="noopener noreferrer"&gt;MCP specification: Security Best Practices&lt;/a&gt;, Model Context Protocol&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf" rel="noopener noreferrer"&gt;Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile (NIST AI 600-1)&lt;/a&gt;, NIST (July 2024)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.mccarthy.ca/en/insights/blogs/techlex/moffatt-v-air-canada-misrepresentation-ai-chatbot" rel="noopener noreferrer"&gt;Moffatt v. Air Canada: A misrepresentation by an AI chatbot&lt;/a&gt;, McCarthy Tétrault (February 2024)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/ai-agent-guardrails" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>llm</category>
      <category>devops</category>
    </item>
    <item>
      <title>AI agent development cost in 2026: real price ranges</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Wed, 07 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/ai-agent-development-cost-in-2026-real-price-ranges-c5p</link>
      <guid>https://dev.to/apptycoons/ai-agent-development-cost-in-2026-real-price-ranges-c5p</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; A production AI agent typically costs $25k–$120k to build at a fixed price, after a $5,000 two-week discovery sprint. Running it adds model tokens, hosting and monitoring, often a few hundred to a few thousand dollars a month. Integrations, compliance, evaluation and human approval steps move the price far more than the model does.&lt;/p&gt;

&lt;p&gt;A production AI agent costs $25k–$120k to build at a fixed price, after a $5,000 two-week discovery sprint, and then tokens, hosting and monitoring every month. The tokens are the small part: a workflow agent that handles 20,000 tasks a month costs about $36 a month on Claude Haiku 5.5 and about $676 on Claude Sonnet 5.5 at list prices. That gap is the whole story of AI agent cost: the model is cheap, and the system that lets it act safely inside your CRM or ERP, with approvals and an audit log, is not.&lt;/p&gt;

&lt;p&gt;The figures below are the ones on our &lt;a href="https://apptycoons.com/pricing" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt;, the same ones we quote against.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much does an AI agent cost to build?
&lt;/h2&gt;

&lt;p&gt;A production AI agent costs $25k–$120k as a Fixed-Price Build, after a two-week, $5,000 Discovery Sprint whose fee is credited to the build. Where a project lands in that band depends on three things: how many systems the agent touches, how much it may do without a person, and which compliance rules apply. The same math holds for agentic AI development in general: the cost follows the number of tools an agent can call and the actions it may take on its own, not the model you pick.&lt;/p&gt;

&lt;p&gt;The total cost of an agent has three parts, and most budgets only plan for the middle one:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The three costs of an AI agent&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Cost&lt;/th&gt;
&lt;th&gt;What it covers&lt;/th&gt;
&lt;th&gt;Our published price&lt;/th&gt;
&lt;th&gt;When you pay it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Discover&lt;/td&gt;
&lt;td&gt;Workshops, a working prototype on your real data, architecture and integration plan, fixed quote&lt;/td&gt;
&lt;td&gt;$5,000 fixed fee, credited to the build&lt;/td&gt;
&lt;td&gt;Weeks 1–2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Build&lt;/td&gt;
&lt;td&gt;Production agent, integrations, guardrails, evaluation set, security review, launch, 30 days of support&lt;/td&gt;
&lt;td&gt;$25k–$120k per project&lt;/td&gt;
&lt;td&gt;6–16 weeks, billed in milestones&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Run&lt;/td&gt;
&lt;td&gt;Model tokens, hosting, logging, monitoring, evaluation runs, prompt and model updates&lt;/td&gt;
&lt;td&gt;Usage-based (see the worked example below); optional dedicated team from $12k per month&lt;/td&gt;
&lt;td&gt;Every month after launch&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What you pay for in discovery, build and run
&lt;/h2&gt;

&lt;p&gt;Each phase removes a different risk.&lt;/p&gt;

&lt;h3&gt;
  
  
  Discovery: proving the agent can work on your data
&lt;/h3&gt;

&lt;p&gt;Discovery is two weeks with a senior architect. It ends with a prototype running on your real data (not a slide deck), the architecture, a plan for each integration, and a fixed quote. Its job is to surface the problems that make AI projects overrun: data that is messier than the demo set, APIs that need approval to access, and approval rules nobody wrote down.&lt;/p&gt;

&lt;h3&gt;
  
  
  Build: turning a prototype into a system you can trust
&lt;/h3&gt;

&lt;p&gt;The build is where most of the money goes, and little of it is spent on the model. It pays for connecting the agent to your systems of record, adding approval steps for high-impact actions, writing an evaluation set that proves the agent behaves, a security review, and launch. Work happens in two-week sprints with live demos, and the code sits in your repository from day one.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fevoafzod7zdvd6mkzjo9.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fevoafzod7zdvd6mkzjo9.webp" alt="A production agent as seven parts: integrations (auth, limits, errors, tests), approvals (a person on high-impact steps), audit log (every action recorded), evaluation set (real cases, rerun on change) and guardrails (limits, thresholds, rollback), plus two monthly run costs: model calls (tokens) and hosting (logs, traces, monitoring)" width="800" height="551"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Model calls are one part of seven. The build pays for integrations, approvals, the audit log, the evaluation set and guardrails; model calls and hosting are monthly run costs.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Run: the monthly bill after launch
&lt;/h3&gt;

&lt;p&gt;Running costs are model tokens, hosting, logs and monitoring, plus the time to update prompts and models as vendors release new versions. For most business agents tokens are the smallest of these at modest volume, and the largest at high volume. The worked example below shows how to estimate them.&lt;/p&gt;

&lt;h2&gt;
  
  
  AI agent cost by type
&lt;/h2&gt;

&lt;p&gt;The type of agent decides most of the build price, because it decides how many systems the agent touches and how much it is trusted to do alone. The ranges below are how we place work inside our published band; the fixed quote comes from discovery.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where common agent types land in a $25k–$120k build&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Agent type&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;th&gt;Typical scope&lt;/th&gt;
&lt;th&gt;Where it usually lands&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Single-task assistant&lt;/td&gt;
&lt;td&gt;Answers questions or drafts replies from one knowledge source; a person sends&lt;/td&gt;
&lt;td&gt;One system, read-only, citations, basic evaluation&lt;/td&gt;
&lt;td&gt;Low end, from $25k&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Workflow agent&lt;/td&gt;
&lt;td&gt;Reads and writes two to four systems and takes actions inside rules, with approvals&lt;/td&gt;
&lt;td&gt;CRM or ERP writes, approval queue, audit log, evaluation per action&lt;/td&gt;
&lt;td&gt;Middle of the range&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Multi-agent system&lt;/td&gt;
&lt;td&gt;Specialist agents work in parallel, process documents and cite every finding to its source&lt;/td&gt;
&lt;td&gt;Document intelligence, several data feeds, tenant isolation&lt;/td&gt;
&lt;td&gt;Top of the range, up to $120k; larger scopes are phased&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Two of our own builds sit at different points on that table. &lt;a href="https://apptycoons.com/work/superdeal" rel="noopener noreferrer"&gt;Superdeal&lt;/a&gt; is a workflow agent inside a campaign CRM: its scope is creator discovery on three social platforms, drafted offers, and an approval step on everything it sends. A multi-agent research system we built sits at the top: specialist agents run in parallel over 20+ data feeds and uploaded documents, and every finding cites its source. Its scope is much larger than Superdeal’s, and the reasons are integrations and documents, not the model.&lt;/p&gt;

&lt;p&gt;Two agent types carry extra line items the table does not show. A single-task assistant that answers from documents is a RAG system, and the &lt;a href="https://apptycoons.com/services/enterprise-llm" rel="noopener noreferrer"&gt;RAG assistants we build&lt;/a&gt; are priced by how messy and permissioned those documents are; &lt;a href="https://apptycoons.com/blog/rag-development-cost" rel="noopener noreferrer"&gt;RAG development cost&lt;/a&gt; breaks that down. Voice agents add telephony, speech-to-text and text-to-speech to every minute of every call, which &lt;a href="https://apptycoons.com/blog/ai-voice-agent-cost" rel="noopener noreferrer"&gt;AI voice agent cost&lt;/a&gt; prices line by line.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the build budget goes
&lt;/h2&gt;

&lt;p&gt;On our own agent builds, roughly 30% of the build price goes to integrations, about 20% to approvals, the audit log, security review and launch, 15–20% to the evaluation set, and only about 15% to the agent itself: its prompts, tools and orchestration. The rest, roughly 15–20%, covers data preparation, the admin screens for approvals and reports, project management with sprint demos, and the 30 days of support after launch.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;How a typical build price splits on our agent projects (approximate)&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Integrations: about 30%&lt;/li&gt;
&lt;li&gt;Approvals, audit log, security, launch: about 20%&lt;/li&gt;
&lt;li&gt;Evaluation set: 15–20%&lt;/li&gt;
&lt;li&gt;Data prep, admin screens, project management, support: 15–20%&lt;/li&gt;
&lt;li&gt;The agent: prompts, tools, orchestration: about 15%&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Rough shares from our own builds. A read-only assistant spends less on integrations; a regulated one spends more on safety and launch.&lt;/p&gt;

&lt;p&gt;The agent is the smallest line. When a quote is mostly “AI development” and says little about integrations or evaluation, it is pricing the part that is cheapest to get right.&lt;/p&gt;

&lt;h2&gt;
  
  
  What drives the cost of an AI agent?
&lt;/h2&gt;

&lt;p&gt;Five things move a quote, and the choice of model is not one of them. Model choice changes the running cost, but it rarely changes the build price by much.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cost drivers and how to keep each one down&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Driver&lt;/th&gt;
&lt;th&gt;Why it costs money&lt;/th&gt;
&lt;th&gt;How to keep it down&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Integrations&lt;/td&gt;
&lt;td&gt;Each system needs auth, rate-limit handling, error paths and tests, and writes need rollback&lt;/td&gt;
&lt;td&gt;Start read-only; add writes once the agent’s decisions are trusted&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data readiness&lt;/td&gt;
&lt;td&gt;Scans, inconsistent fields and missing history must be cleaned or worked around&lt;/td&gt;
&lt;td&gt;Prototype on real data in discovery, not a curated sample&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Compliance&lt;/td&gt;
&lt;td&gt;HIPAA, PCI or SOC 2 controls add hosting constraints, logging and review&lt;/td&gt;
&lt;td&gt;Keep regulated data out of scope for version one where you can&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Evaluation&lt;/td&gt;
&lt;td&gt;Every action needs test cases that prove correct behavior, rerun on each change&lt;/td&gt;
&lt;td&gt;Build the evaluation set from real past cases you already have&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Autonomy&lt;/td&gt;
&lt;td&gt;The more the agent does without a person, the more guardrails and approval logic it needs&lt;/td&gt;
&lt;td&gt;Launch with human approval on high-impact steps, then relax it with data&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Integrations are usually the biggest line item
&lt;/h3&gt;

&lt;p&gt;An agent that cannot read from and write to your systems of record is a demo. Each integration means authentication, handling the API’s limits and failures, mapping fields, and testing what happens when a write half-succeeds. With three or more integrations, this work can outweigh the agent logic itself.&lt;/p&gt;

&lt;h3&gt;
  
  
  Evaluation is what makes an agent shippable
&lt;/h3&gt;

&lt;p&gt;Pilots skip evaluation and pay for it later. An evaluation set is a library of real cases with the correct outcome, run against every prompt or model change. It is the difference between “it worked in the demo” and “we know it works”. Budget for it as its own line: someone has to collect the cases, agree the correct outcomes with the people who do the work today, and rerun the set whenever a prompt or model changes. We cover why skipping it stalls projects in &lt;a href="https://apptycoons.com/blog/ai-pilots-to-production" rel="noopener noreferrer"&gt;why AI pilots stall before production&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Human approval is cheaper than full autonomy
&lt;/h3&gt;

&lt;p&gt;Every step an agent takes on its own needs guardrails: confidence thresholds, limits, rollback and logging. Putting a person on the high-impact steps for the first months is faster to build and easier to get past risk and compliance review. You remove approvals one by one as the logs show the agent is reliable. Our checklist of &lt;a href="https://apptycoons.com/blog/ai-agent-guardrails" rel="noopener noreferrer"&gt;AI agent guardrails&lt;/a&gt; lists the controls an agent needs before any approval comes off.&lt;/p&gt;

&lt;h2&gt;
  
  
  Worked example: what an AI agent costs to run each month
&lt;/h2&gt;

&lt;p&gt;An agent’s running cost is mostly tokens: the text sent to the model and the text it writes back. Here is the arithmetic for a realistic workflow agent, using list prices from Anthropic’s pricing page.&lt;/p&gt;

&lt;p&gt;Assumptions: the agent handles 20,000 tasks a month. Each task makes four model calls. Each call sends 6,000 input tokens, of which 4,500 are a stable system prompt and tool definitions that prompt caching can reuse, and gets back 500 output tokens. List prices per million tokens, checked October 29, 2026, are $2 input, $0.10 cache read and $10 output for Claude Sonnet 5.5, and $0.10, $0.01 and $0.50 for Claude Haiku 5.5 (its price for prompts up to 100,000 tokens, which covers this example). Anthropic bills cache reads at 0.1 times the input price on most models and at 0.05 times on Sonnet 5.5.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Monthly token cost for 20,000 tasks (list prices)&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;Cost per call, cached&lt;/th&gt;
&lt;th&gt;Monthly, with caching&lt;/th&gt;
&lt;th&gt;Monthly, no caching&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Claude Haiku 5.5&lt;/td&gt;
&lt;td&gt;$0.00045&lt;/td&gt;
&lt;td&gt;about $36&lt;/td&gt;
&lt;td&gt;about $68&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Claude Sonnet 5.5&lt;/td&gt;
&lt;td&gt;$0.0085&lt;/td&gt;
&lt;td&gt;about $676&lt;/td&gt;
&lt;td&gt;about $1,360&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;How the cached Sonnet 5.5 call is worked out: 1,500 uncached input tokens at $2 per million is $0.0030, 4,500 cached tokens at $0.10 per million is $0.00045, and 500 output tokens at $10 per million is $0.0050, so about $0.0085 per call. Four calls per task and 20,000 tasks give about $676. The small premium for writing to the cache is left out because it is paid once per cache window, not per call.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;One cached Sonnet 5.5 call, about $0.0085&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Output, 500 tokens: $0.0050&lt;/li&gt;
&lt;li&gt;Uncached input, 1,500 tokens: $0.0030&lt;/li&gt;
&lt;li&gt;Cached input, 4,500 tokens: $0.00045&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Four calls per task and 20,000 tasks: about $676 a month.&lt;/p&gt;

&lt;p&gt;Three things change this number more than the model price does:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Caching. Reusing the stable part of the prompt roughly halves the bill here.&lt;/li&gt;
&lt;li&gt;Routing. Sending easy steps to a small model and only hard ones to a larger model lowers the average cost per task; at these list prices the gap between the two tiers is about 19x, so routing matters more than it did a year ago.&lt;/li&gt;
&lt;li&gt;Tokenizer. Anthropic notes that Claude 4.7 and later models use a tokenizer that produces about 30% more tokens for the same text, so estimates made with an older tokenizer will run low.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The same agent at 2,000, 20,000 and 100,000 tasks a month
&lt;/h3&gt;

&lt;p&gt;Token cost grows in a straight line with volume; the build price does not move. Multiplying the per-call figures above by four calls per task gives these monthly totals:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Monthly token cost by volume (4 calls per task, list prices checked Oct 29, 2026)&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tasks a month&lt;/th&gt;
&lt;th&gt;Haiku 5.5, cached&lt;/th&gt;
&lt;th&gt;Haiku 5.5, no cache&lt;/th&gt;
&lt;th&gt;Sonnet 5.5, cached&lt;/th&gt;
&lt;th&gt;Sonnet 5.5, no cache&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;2,000&lt;/td&gt;
&lt;td&gt;about $4&lt;/td&gt;
&lt;td&gt;about $7&lt;/td&gt;
&lt;td&gt;about $68&lt;/td&gt;
&lt;td&gt;about $136&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;20,000&lt;/td&gt;
&lt;td&gt;about $36&lt;/td&gt;
&lt;td&gt;about $68&lt;/td&gt;
&lt;td&gt;about $676&lt;/td&gt;
&lt;td&gt;about $1,360&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;100,000&lt;/td&gt;
&lt;td&gt;about $178&lt;/td&gt;
&lt;td&gt;about $340&lt;/td&gt;
&lt;td&gt;about $3,380&lt;/td&gt;
&lt;td&gt;about $6,800&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Read across a row and the cheapest option is always the small model with caching; read down a column and only volume changes the bill. At 2,000 tasks the model is a rounding error next to hosting. At 100,000 it is a real line, and caching and routing decide whether it is $178 or $6,800.&lt;/p&gt;

&lt;p&gt;On top of tokens, budget for hosting the agent service, logs and traces, and scheduled evaluation runs. These depend on your cloud and your retention rules, so treat them as their own line rather than guessing a percentage.&lt;/p&gt;

&lt;h2&gt;
  
  
  What an AI agent costs to maintain after launch
&lt;/h2&gt;

&lt;p&gt;Maintenance is the engineering that keeps an agent correct while everything around it changes. The model bill is predictable; these four jobs are what surprise budgets:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Model and price changes. Vendors retire models and change prices; each switch means rerunning the evaluation set before the new model goes live.&lt;/li&gt;
&lt;li&gt;Evaluation reruns. Every prompt change, tool change or new edge case from production goes through the full test set, and the set grows as users find new cases.&lt;/li&gt;
&lt;li&gt;Monitoring and traces. Someone reads the logs of failed and escalated tasks each week and turns them into fixes or new test cases.&lt;/li&gt;
&lt;li&gt;Integration drift. When a connected CRM, ERP or API changes a field or an auth flow, the agent starts failing without an error message unless a test catches it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Our builds include 30 days of support after launch. After that, owners usually choose small fixed-price change requests for occasional updates, or a Dedicated Team when the agent has a roadmap of its own. We don’t publish a maintenance percentage of the build price, because it depends on how many integrations can drift and how often your process changes, not on what the build cost.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why AI agent cost estimates range from $5,000 to $400,000+
&lt;/h2&gt;

&lt;p&gt;Published estimates span two orders of magnitude because they put very different systems under one word. The cost guides that ranked for “AI agent development cost” when we checked on October 29, 2026 put an agent anywhere from about $5,000 to more than $400,000, and few of them show how they got there.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The low end, roughly $5,000 to $25,000, is a rule-based bot or a prototype: one data source, read-only, no evaluation set, no approvals.&lt;/li&gt;
&lt;li&gt;The high end, $150,000 to $400,000 and more, is a multi-agent system in a regulated industry, built by a full team over six months or longer.&lt;/li&gt;
&lt;li&gt;The middle is a production agent that reads and writes real systems, with approvals, an audit log and an evaluation set. Our fixed-price band, $25k–$120k, covers that middle; a prototype costs less (our discovery sprint ends with one, for $5,000), and larger programs are split into phases.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Treat any published range as a way to sort scopes, not as a price. The number that counts is a fixed quote against a named scope.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why quotes for the same AI agent differ so much
&lt;/h3&gt;

&lt;p&gt;Two quotes for the “same” agent usually describe different systems. One vendor prices a prototype with a read-only connection; another prices writes, approvals, an audit log and a test set. Before comparing totals, line the quotes up against six questions:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check every AI agent quote for these six items&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Check&lt;/th&gt;
&lt;th&gt;What a complete quote states&lt;/th&gt;
&lt;th&gt;What a thin quote leaves out&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Integrations&lt;/td&gt;
&lt;td&gt;Each system named, read or write, and who supplies API access&lt;/td&gt;
&lt;td&gt;“Integrates with your CRM”&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Evaluation set&lt;/td&gt;
&lt;td&gt;Roughly how many real cases, who writes the expected outcomes, when it runs&lt;/td&gt;
&lt;td&gt;“Testing” as one line&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Approval steps&lt;/td&gt;
&lt;td&gt;Which actions need a person and how the approval queue works&lt;/td&gt;
&lt;td&gt;Nothing, or “human in the loop” with no detail&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Audit log&lt;/td&gt;
&lt;td&gt;What is logged per action and how long it is kept&lt;/td&gt;
&lt;td&gt;Nothing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ownership&lt;/td&gt;
&lt;td&gt;Code, prompts, evaluation set and cloud accounts in your name&lt;/td&gt;
&lt;td&gt;A license to use the vendor’s platform&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Post-launch support&lt;/td&gt;
&lt;td&gt;A fixed support window and how changes are priced after it&lt;/td&gt;
&lt;td&gt;“Ongoing support available”&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;Watch out&lt;/p&gt;

&lt;p&gt;A thin quote is not a cheaper one&lt;/p&gt;

&lt;p&gt;A quote that is low because it leaves out the evaluation set or the approval steps is not cheaper; it moves that cost to after launch, when it is paid as an incident.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;For the questions to put to the vendor behind the quote, see &lt;a href="https://apptycoons.com/blog/how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;questions to ask an AI agent development company&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fixed price vs time and materials for an AI agent
&lt;/h2&gt;

&lt;p&gt;A fixed price after discovery protects the buyer from overruns; time and materials protects the vendor. For AI agents, where the main risk is unknown data and integrations, the fix is to resolve those unknowns first and then fix the price, which is what discovery is for.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pricing models for an AI agent build&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Fixed price after discovery&lt;/th&gt;
&lt;th&gt;Time and materials&lt;/th&gt;
&lt;th&gt;Dedicated team&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Best for&lt;/td&gt;
&lt;td&gt;A defined agent or product&lt;/td&gt;
&lt;td&gt;Research with no clear end&lt;/td&gt;
&lt;td&gt;An ongoing roadmap&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who carries overrun risk&lt;/td&gt;
&lt;td&gt;The vendor&lt;/td&gt;
&lt;td&gt;You&lt;/td&gt;
&lt;td&gt;Shared, scope flexes monthly&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scope changes&lt;/td&gt;
&lt;td&gt;Change request&lt;/td&gt;
&lt;td&gt;Anytime, billed hourly&lt;/td&gt;
&lt;td&gt;Anytime&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Our price&lt;/td&gt;
&lt;td&gt;$25k–$120k per project&lt;/td&gt;
&lt;td&gt;Not offered&lt;/td&gt;
&lt;td&gt;From $12k per month&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;We recommend fixing the price for the first production version, and moving to a Dedicated Team only if the agent becomes a product with its own roadmap. The trade-offs between the contract models are in our guide to &lt;a href="https://apptycoons.com/blog/fixed-price-software" rel="noopener noreferrer"&gt;fixed price vs time and materials&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  When a custom AI agent is not worth paying for
&lt;/h2&gt;

&lt;p&gt;A custom agent is not worth its build price when a product already does the job at your volume for less. The quickest test is arithmetic: multiply the product’s usage price by the volume you expect in year three, and compare it with the build plus three years of running cost.&lt;/p&gt;

&lt;p&gt;Two published price lists show what that comparison looks like. Intercom lists its Fin AI Agent from $0.99 per outcome, so 1,000 outcomes a month is about $12,000 a year, well under a $25k build plus hosting and maintenance. Microsoft sells Copilot Studio as packs of 25,000 credits for $200 a month, which suits internal assistants that live inside Microsoft 365. At that kind of volume, inside tools you already use, buying wins on cost.&lt;/p&gt;

&lt;p&gt;The arithmetic turns the other way when volume grows, when the agent has to write to your own systems, or when how it works is part of what you sell. A full three-year model, the lock-in questions to put to vendors, and the part-bought, part-built setup most agents end up with are in &lt;a href="https://apptycoons.com/blog/build-vs-buy-ai-agents" rel="noopener noreferrer"&gt;build vs buy AI agents&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does an AI agent pay for itself?
&lt;/h2&gt;

&lt;p&gt;An agent pays for itself once the monthly value of the work it takes over, minus its monthly running cost, has added up to the build price. Because our discovery fee is credited to the build, the upfront cost is the build price alone:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Payback in months = build price ÷ (monthly value of work handled − monthly running cost)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Volume decides the answer far more than the build price does. The example below uses stated assumptions; swap in your own. A support agent fully resolves half of the tickets it sees, each ticket takes a person 6 minutes, and an hour of that person’s time costs $40 fully loaded, so each resolved ticket is worth $4. Running cost (tokens, hosting, monitoring) is set at $1,000 a month at 2,000 tickets and $1,500 at 10,000.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Payback at two volumes and both ends of our build band (assumptions above)&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tickets a month&lt;/th&gt;
&lt;th&gt;Value of work handled&lt;/th&gt;
&lt;th&gt;Net per month&lt;/th&gt;
&lt;th&gt;Build at $25k&lt;/th&gt;
&lt;th&gt;Build at $120k&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;2,000&lt;/td&gt;
&lt;td&gt;$4,000&lt;/td&gt;
&lt;td&gt;$3,000&lt;/td&gt;
&lt;td&gt;about 8 months&lt;/td&gt;
&lt;td&gt;about 40 months&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10,000&lt;/td&gt;
&lt;td&gt;$20,000&lt;/td&gt;
&lt;td&gt;$18,500&lt;/td&gt;
&lt;td&gt;about 1.4 months&lt;/td&gt;
&lt;td&gt;about 6.5 months&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Two things follow. At low volume a simple agent can pay back within a year, but a complex one rarely does, so either narrow the scope or buy a product. And the running cost belongs in the formula: leaving it out flatters the result most at low volume, which is exactly where the decision is closest. If the payback runs past two years at your volume, read &lt;a href="https://apptycoons.com/blog/build-vs-buy-ai-agents" rel="noopener noreferrer"&gt;build vs buy AI agents&lt;/a&gt; before you commit to a build.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to budget for an AI agent project
&lt;/h2&gt;

&lt;p&gt;Budget for the system, not the model. A realistic plan has four lines:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Four budget lines for an AI agent&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Discovery: $5,000&lt;/strong&gt; (Weeks 1–2): Two weeks, ending with a working prototype and a fixed quote.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Build: $25k–$120k&lt;/strong&gt; (6–16 weeks): Depending on agent type, integrations and compliance.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run&lt;/strong&gt; (Every month): Tokens from a worked estimate like the one above, plus hosting and monitoring.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Change&lt;/strong&gt; (Ongoing): Model and prompt updates as vendors ship new versions, either as small fixed-price changes or a dedicated team.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then pick one workflow and one number to move, such as hours saved, tickets resolved or decisions made per day, and hold the build to it. That keeps scope honest and makes the return easy to measure. If you want a fixed price for your own agent, our &lt;a href="https://apptycoons.com/services/ai-agent-development" rel="noopener noreferrer"&gt;AI agent development&lt;/a&gt; team starts with a free AI audit: &lt;a href="https://apptycoons.com/contact?interest=audit&amp;amp;service=ai-agent-development" rel="noopener noreferrer"&gt;book the audit&lt;/a&gt; and bring the workflow you have in mind.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://platform.claude.com/docs/en/about-claude/pricing" rel="noopener noreferrer"&gt;Claude API pricing&lt;/a&gt;, Anthropic&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.intercom.com/pricing" rel="noopener noreferrer"&gt;Intercom pricing (Fin AI Agent)&lt;/a&gt;, Intercom&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.microsoft.com/en-us/microsoft-copilot/microsoft-copilot-studio" rel="noopener noreferrer"&gt;Microsoft Copilot Studio pricing&lt;/a&gt;, Microsoft&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/ai-agent-development-cost" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>startup</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Fintech app development cost in 2026: real scopes</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Wed, 07 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/fintech-app-development-cost-in-2026-real-scopes-28nk</link>
      <guid>https://dev.to/apptycoons/fintech-app-development-cost-in-2026-real-scopes-28nk</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; A fintech app costs far less when a licensed partner holds the money and you build the product around it. With a partner bank or stablecoin provider handling custody, the build covers apps, back office, integrations and compliance flows. At Apptycoons that starts with a $5,000 discovery sprint, then a fixed-price build of $25k to $120k.&lt;/p&gt;

&lt;p&gt;Switch lets a club’s treasurer issue a Visa debit card in seconds. Freedom Pro pays a partner network into USD and stablecoin wallets its members spend by card. We built both, both are “fintech apps”, and their scopes have almost nothing in common. That is why a single price range for fintech app development tells you so little.&lt;/p&gt;

&lt;p&gt;We don’t publish client budgets, so there are no invented price tags for those two products here. There is what was in scope, why each piece costs what it does, and the prices we publish for our own engagements.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short answer: what a fintech app costs in 2026
&lt;/h2&gt;

&lt;p&gt;A fintech app costs what its money movement and compliance cost, not what its screens cost. The single biggest decision is whether a licensed partner holds customer funds while you build the product around it, or whether you take on that regulated role yourself.&lt;/p&gt;

&lt;p&gt;For the first path, which is how most new fintech products launch, our published pricing is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Discovery Sprint: $5,000 fixed fee, 2 weeks.&lt;/strong&gt; Scope, partner and compliance mapping, architecture, and a fixed price for the build. The fee is credited to the build.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fixed-Price Build: $25k–$120k per project, 6–16 weeks.&lt;/strong&gt; Billed in milestones tied to demoed features, with 30 days of post-launch support.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dedicated Team: from $12k per month.&lt;/strong&gt; For larger programs and the roadmap after launch.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Published agency estimates run wider, from about $25,000 for an MVP to $900,000 or more for a complex neobank. The next section shows why those numbers disagree, and the rest of this post shows which line items separate a first product on a partner’s rails from a neobank.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why published fintech cost ranges disagree
&lt;/h2&gt;

&lt;p&gt;Published fintech cost ranges disagree because each agency prices a different product, team location and compliance scope. Four 2026 guides from development agencies, with the figures copied as published:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Third-party agency estimates for fintech apps (as published; checked October 18, 2026)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Source (date)&lt;/th&gt;
&lt;th&gt;Smallest scope&lt;/th&gt;
&lt;th&gt;Compliance-heavy or full scope&lt;/th&gt;
&lt;th&gt;Largest scope&lt;/th&gt;
&lt;th&gt;What it counts&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;RaftLabs (updated Oct 12, 2026)&lt;/td&gt;
&lt;td&gt;Consumer fintech MVP: $30,000–$70,000, 12–18 weeks&lt;/td&gt;
&lt;td&gt;Payments and compliance-heavy build: $80,000–$160,000, 16–30 weeks&lt;/td&gt;
&lt;td&gt;Full platform: $140,000–$240,000+, 24–52 weeks&lt;/td&gt;
&lt;td&gt;Says compliance adds 25–35% on top of the feature build&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CMARIX (updated Aug 13, 2026)&lt;/td&gt;
&lt;td&gt;Fintech MVP: $25,000–$60,000, 3–4 months&lt;/td&gt;
&lt;td&gt;Full digital banking platform: $250,000–$600,000+, 9–14 months&lt;/td&gt;
&lt;td&gt;“$600,000+ for enterprise banking platforms”&lt;/td&gt;
&lt;td&gt;Ranges by app type&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Acquaint Softtech (Jul 16, 2026)&lt;/td&gt;
&lt;td&gt;Validation MVP: $50K–90K with a US team, $40K–80K with an EU team&lt;/td&gt;
&lt;td&gt;Production and compliance: $150K–300K (US), $120K–260K (EU)&lt;/td&gt;
&lt;td&gt;Enterprise platform: $350K+ (US)&lt;/td&gt;
&lt;td&gt;Ranges by team region&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Interexy (updated Mar 31, 2026)&lt;/td&gt;
&lt;td&gt;Fintech MVP: $50,000–$120,000, regulated projects from $80,000&lt;/td&gt;
&lt;td&gt;Neobank MVP: $110,000–$160,000&lt;/td&gt;
&lt;td&gt;Complex neobank: $350,000–$900,000+, 12–20 months&lt;/td&gt;
&lt;td&gt;Neobank as its own category&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Read side by side, three things explain most of the spread. Team location: Acquaint’s own table moves its MVP figure by about $10,000 between US and EU teams. Compliance scope: a product that becomes a regulated entity carries audits, licensing work and its own controls, while one built on a licensed partner inherits most of them. And what “MVP” means: RaftLabs’ smallest scope is a budgeting, expense-tracking or rewards app, while Interexy prices a neobank MVP separately at $110,000–$160,000. These are vendor estimates, ours included; none of them, and none of ours, is a price for your scope until the money flows are drawn.&lt;/p&gt;

&lt;h2&gt;
  
  
  The biggest cost decision: partner with a licensed provider or become one
&lt;/h2&gt;

&lt;p&gt;Partnering with a licensed provider is cheaper and faster because the hardest regulated pieces, holding deposits, issuing cards and custody of digital assets, are already built and supervised. You integrate them through APIs and build the experience, the business logic and the controls on top.&lt;/p&gt;

&lt;p&gt;The trade-off is dependency. Your product inherits the partner’s program rules, fees and onboarding timeline, and your users’ protection depends on that structure.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Watch out: Deposit insurance does not cover the app company&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The FDIC is clear on one point founders often miss: deposit insurance does not protect against the insolvency or bankruptcy of a non-bank company. Your app, your disclosures and your record-keeping have to reflect how funds are held.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Our guide to &lt;a href="https://apptycoons.com/blog/stablecoin-wallets-fintech?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=fintech-app-development-cost" rel="noopener noreferrer"&gt;stablecoin wallet APIs and infrastructure&lt;/a&gt; covers this partner-first approach for digital assets in depth. Typical partner categories in a 2026 fintech build:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Partner bank / banking-as-a-service&lt;/strong&gt; for accounts, deposits, ACH and wires.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Card issuing program&lt;/strong&gt; for virtual and physical debit cards, spend controls and wallet provisioning.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stablecoin and wallet infrastructure,&lt;/strong&gt; such as Bridge, which offers one API to move, store and accept stablecoins, plus wallets and a card program.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;KYC and identity verification&lt;/strong&gt; for onboarding.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fr6aokr2nn9l7tm35r157.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fr6aokr2nn9l7tm35r157.webp" alt="Two layers joined by APIs. Top layer, your product (the build): apps, back office, integrations, compliance flows. Bottom layer, licensed partners: partner bank, card issuing, stablecoins and wallets, KYC and identity. Deposits, cards and custody of digital assets stay with the partner." width="800" height="795"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;On the partner-first path, the build covers the product layer; the licensed partners hold the money.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Both case studies below use this model.&lt;/p&gt;

&lt;h2&gt;
  
  
  Real scope 1: Switch, a shared banking app
&lt;/h2&gt;

&lt;p&gt;Switch is a banking app where clubs, teams and friends pool money, issue Visa debit cards in seconds and collect payments. It runs on iOS, Android and the web, with Thread Bank as its FDIC-insured partner bank. Here is what the scope contained, and why each part carries cost.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Shared accounts with roles and permissions.&lt;/strong&gt; Treasurers, admins and members each see and do different things. Permission models are a cost driver because every money action has to check them, and every one needs tests.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instant virtual and physical Visa debit cards.&lt;/strong&gt; Spend limits, pause and close controls, plus Apple Pay and Google Wallet. Card issuing adds program integration, card lifecycle states and wallet provisioning flows.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;MoneyPools.&lt;/strong&gt; Shareable collection links that work on the web with no download, with live tracking of who has paid. This is a second product surface, a public web flow, alongside the apps.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Org tools.&lt;/strong&gt; Multiple admins, one-tap handover to the next leader, QuickBooks sync and installment plans. Accounting sync means mapping transactions to someone else’s data model and keeping it in step.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Full banking features&lt;/strong&gt; from the partner: checks, cash deposits, wires and a fee-free ATM network.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What drove the effort was not the number of screens. It was the combination of three platforms, a permission model on every money action, card lifecycle handling and a public collection flow. The result: Switch is live on iOS, Android and web, has been adopted by 1,000+ organizations, and is rated 4.7 on the App Store. The details are in the &lt;a href="https://apptycoons.com/work/switch?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=fintech-app-development-cost" rel="noopener noreferrer"&gt;Switch case study&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Real scope 2: Freedom Pro, a partner platform with wallets and cards
&lt;/h2&gt;

&lt;p&gt;Freedom Pro is a direct-selling platform that bundles wireless, streaming, wellness and finance services and pays a partner network. Its fintech layer is a wallet: members hold USD and stablecoin balances and spend them by debit card. Its scope has little in common with Switch’s.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Partner back office.&lt;/strong&gt; Registration, team genealogy, ranks and commission tracking. Commission logic is business-critical code that needs reproducible calculations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;USD and stablecoin wallets via Bridge.&lt;/strong&gt; Earnings land in wallets members can hold or spend. Wallet integrations need balance reconciliation and clear state for every transfer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Debit card issuing.&lt;/strong&gt; Members spend their balance anywhere by card.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A member portal and single sign-on&lt;/strong&gt; across several service verticals, plus an onboarding funnel that converts visitors into partners.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Two real fintech scopes side by side&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Scope item&lt;/th&gt;
&lt;th&gt;Switch&lt;/th&gt;
&lt;th&gt;Freedom Pro&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Money layer&lt;/td&gt;
&lt;td&gt;Thread Bank, FDIC-insured partner bank&lt;/td&gt;
&lt;td&gt;Bridge-powered wallets (USD and stablecoins)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cards&lt;/td&gt;
&lt;td&gt;Instant virtual and physical Visa debit, Apple Pay, Google Wallet&lt;/td&gt;
&lt;td&gt;Debit cards on the member balance&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Core logic&lt;/td&gt;
&lt;td&gt;Roles and permissions on shared accounts&lt;/td&gt;
&lt;td&gt;Genealogy, ranks and commissions&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Extra surfaces&lt;/td&gt;
&lt;td&gt;MoneyPools public web collection links&lt;/td&gt;
&lt;td&gt;Member portal, onboarding funnel, service catalog&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Integrations&lt;/td&gt;
&lt;td&gt;QuickBooks sync, ATM network&lt;/td&gt;
&lt;td&gt;Wireless, streaming and KYC providers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Platforms&lt;/td&gt;
&lt;td&gt;iOS, Android, web&lt;/td&gt;
&lt;td&gt;Web and mobile&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Where the cost sat&lt;/td&gt;
&lt;td&gt;Permissions, card lifecycle, three platforms&lt;/td&gt;
&lt;td&gt;Money layer and commission engine&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Here the cost sat in the money layer and the commission engine, not in banking features. Comparing the two scopes is the point: both are “fintech apps”, and a single price range would describe neither. See the &lt;a href="https://apptycoons.com/work/freedom-pro?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=fintech-app-development-cost" rel="noopener noreferrer"&gt;Freedom Pro case study&lt;/a&gt; for the full build.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fintech app cost by product type
&lt;/h2&gt;

&lt;p&gt;What drives cost changes with the kind of fintech product, so compare scopes of the same type. We don’t publish per-type prices; this table lists the drivers and the real case that maps to each, where we have one.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Cost drivers by fintech product type&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Product type&lt;/th&gt;
&lt;th&gt;Who holds the money&lt;/th&gt;
&lt;th&gt;Main cost drivers&lt;/th&gt;
&lt;th&gt;Our real example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Shared or consumer banking app&lt;/td&gt;
&lt;td&gt;Partner bank&lt;/td&gt;
&lt;td&gt;Roles and permissions, card lifecycle, multiple platforms, operations tools&lt;/td&gt;
&lt;td&gt;Switch&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Wallet or payouts on stablecoin rails&lt;/td&gt;
&lt;td&gt;Stablecoin infrastructure provider&lt;/td&gt;
&lt;td&gt;Transfer types, ledger and reconciliation, KYC states, cards&lt;/td&gt;
&lt;td&gt;Freedom Pro&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Bundled services platform&lt;/td&gt;
&lt;td&gt;Several partners, one per service&lt;/td&gt;
&lt;td&gt;Single sign-on, provisioning per provider, one account view&lt;/td&gt;
&lt;td&gt;Freedom Pro&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Lending&lt;/td&gt;
&lt;td&gt;A lender or lending partner&lt;/td&gt;
&lt;td&gt;Underwriting data, decision rules, repayment schedules, collections&lt;/td&gt;
&lt;td&gt;None we can cite&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Payments or merchant tools&lt;/td&gt;
&lt;td&gt;Payment processor&lt;/td&gt;
&lt;td&gt;Checkout flows, payouts, disputes, PCI scope&lt;/td&gt;
&lt;td&gt;None we can cite&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A bundled platform is closer to &lt;a href="https://apptycoons.com/industries/financial-aggregators?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=fintech-app-development-cost" rel="noopener noreferrer"&gt;financial aggregator development&lt;/a&gt; than to a banking app: most of its cost sits in connecting providers and keeping one view of the customer across them.&lt;/p&gt;

&lt;h2&gt;
  
  
  How long a fintech app takes to build
&lt;/h2&gt;

&lt;p&gt;A focused first release on a partner’s rails typically takes 6–16 weeks of build after a two-week discovery, and partner approval often takes longer than the code. Banks, card programs and wallet providers each run their own onboarding, due diligence and program review. Start those conversations during discovery, so the build is not waiting for a sandbox key or a program sign-off in week eight.&lt;/p&gt;

&lt;h2&gt;
  
  
  The line items that drive fintech app cost
&lt;/h2&gt;

&lt;p&gt;Every fintech quote is a sum of a few expensive line items and many cheap ones. These are the expensive ones, roughly in the order they move the price.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Onboarding and KYC.&lt;/strong&gt; Identity checks, document capture, failure and retry paths, manual review queues, and what the user sees while they wait.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Money movement.&lt;/strong&gt; Each rail (cards, ACH, wires, stablecoins) adds states, webhooks, failure handling and reconciliation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ledger and reconciliation.&lt;/strong&gt; Your record of balances has to match the partner’s every day, and someone needs a screen that explains any difference.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Permissions and limits.&lt;/strong&gt; Roles, spend limits and approvals, enforced on the server for every action.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Admin and compliance tooling.&lt;/strong&gt; Search, account holds, case notes, exports and audit logs for your operations team. It is often under-scoped and always needed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security and PCI scope.&lt;/strong&gt; The PCI Data Security Standard sets the baseline for handling payment card data. Using an issuer’s tokenized cards and hosted components keeps raw card numbers out of your systems and shrinks what you have to secure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Platforms.&lt;/strong&gt; iOS, Android and web multiply UI and testing work. Our guide to &lt;a href="https://apptycoons.com/blog/native-vs-cross-platform?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=fintech-app-development-cost" rel="noopener noreferrer"&gt;native vs cross-platform apps&lt;/a&gt; covers that trade-off.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Third-party integrations&lt;/strong&gt; such as accounting sync, CRMs or data providers.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Design, marketing pages and settings screens matter, but they rarely decide whether a project lands at the low or the high end of a range.&lt;/p&gt;

&lt;h2&gt;
  
  
  How we turn a fintech scope into a fixed price
&lt;/h2&gt;

&lt;p&gt;We price fintech work in two steps so the build price is fixed before you commit to it. The Discovery Sprint produces the scope; the build is then quoted as one fixed price, paid in milestones.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;From scope to a fixed price&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Discovery Sprint&lt;/strong&gt; (Weeks 1–2): Partners, money flows, permissions and first-release scope.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fixed build price&lt;/strong&gt; (End of discovery): One price for the agreed scope, with a milestone plan.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fixed-price build&lt;/strong&gt; (6–16 weeks): Billed in milestones tied to demoed features.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Post-launch support&lt;/strong&gt; (After launch): Included with the build.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;What the two-week discovery covers for a fintech product:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Which partners hold funds, issue cards or verify identity, and what their APIs and program rules require.&lt;/li&gt;
&lt;li&gt;The money flows, drawn end to end, including failures and reversals.&lt;/li&gt;
&lt;li&gt;The permission model and the admin tools operations will need on day one.&lt;/li&gt;
&lt;li&gt;What is in the first release and what waits, with each cut explained.&lt;/li&gt;
&lt;li&gt;A fixed build price and milestone plan.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The build is then quoted as one fixed price inside the band above, set by what discovery found. If the program is bigger than that, for example several products or markets at once, a dedicated team from $12k per month is usually the better fit. Our post on &lt;a href="https://apptycoons.com/blog/fixed-price-software?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=fintech-app-development-cost" rel="noopener noreferrer"&gt;how fixed-price software works&lt;/a&gt; explains what is fixed and what is not.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a fintech app costs to run after launch
&lt;/h2&gt;

&lt;p&gt;Running costs are mostly usage-based provider fees, and they can matter more than the build over three years. Get every provider’s fee schedule in writing during discovery, and model them against your expected users and transactions.&lt;/p&gt;

&lt;p&gt;Typical running costs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Partner fees:&lt;/strong&gt; banking program, card issuing and wallet provider fees, often per account, per card or per transaction.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;KYC fees:&lt;/strong&gt; charged per verification, including the ones that fail.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hosting and monitoring:&lt;/strong&gt; usually small next to provider fees for an early product.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security reviews and audits&lt;/strong&gt; that partners or your own compliance team require.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ongoing development:&lt;/strong&gt; partners change APIs and program rules, operating systems update, and regulations move.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Tip: Model fees before you sign&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Get every provider’s fee schedule in writing during discovery and model it against your expected users and transactions. Usage-based fees can matter more than the build over three years.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  How to cut fintech development cost without cutting compliance
&lt;/h2&gt;

&lt;p&gt;The cheapest fintech build is the one that ships a narrow first release on top of strong partners. Cut scope, not controls.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Launch one money flow first.&lt;/strong&gt; For example accounts and cards, then collections, rather than every rail at once.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pick partners before you design screens.&lt;/strong&gt; Their onboarding and program rules shape your flows.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep raw card data out of your systems&lt;/strong&gt; with tokenized cards and hosted components.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Build the admin tools in the first release.&lt;/strong&gt; Operations without tooling is the most expensive manual process in fintech.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use one codebase across platforms&lt;/strong&gt; where performance and device features allow it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Scope checklist before you ask for a fintech quote
&lt;/h2&gt;

&lt;p&gt;Bring answers to these questions to any vendor, including us, and the quote you get back will be far more accurate:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Who holds customer funds, and is that partner already chosen?&lt;/li&gt;
&lt;li&gt;Which money rails do you need at launch: cards, ACH, wires, stablecoins?&lt;/li&gt;
&lt;li&gt;Which platforms at launch: iOS, Android, web?&lt;/li&gt;
&lt;li&gt;Who are the user roles, and what can each one do with money?&lt;/li&gt;
&lt;li&gt;What does your operations team need to see and do every day?&lt;/li&gt;
&lt;li&gt;Which markets, and what has counsel said about licensing in each?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you have those answers, &lt;a href="https://apptycoons.com/contact?interest=sprint&amp;amp;service=mobile-app-development&amp;amp;utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=fintech-app-development-cost" rel="noopener noreferrer"&gt;request a Discovery Sprint&lt;/a&gt; and we will turn them into a fixed quote. You can also see how we approach the sector on our &lt;a href="https://apptycoons.com/industries/fintech?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=fintech-app-development-cost" rel="noopener noreferrer"&gt;fintech software development&lt;/a&gt; page and our &lt;a href="https://apptycoons.com/pricing?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=fintech-app-development-cost" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://www.fdic.gov/consumer-resource-center/2024-06/banking-third-party-apps" rel="noopener noreferrer"&gt;Banking With Third-Party Apps&lt;/a&gt;, FDIC&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.pcisecuritystandards.org/standards/pci-dss/" rel="noopener noreferrer"&gt;PCI Data Security Standard (PCI DSS)&lt;/a&gt;, PCI Security Standards Council&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.bridge.xyz/" rel="noopener noreferrer"&gt;Bridge: stablecoin orchestration, issuance, wallets and cards&lt;/a&gt;, Bridge&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://interexy.com/fintech-app-development-cost-in-2026-full-breakdown" rel="noopener noreferrer"&gt;Fintech App Development Cost in 2026: Full Breakdown&lt;/a&gt;, Interexy&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.raftlabs.com/blog/fintech-app-development-cost" rel="noopener noreferrer"&gt;Fintech app development cost in 2026: real numbers&lt;/a&gt;, RaftLabs&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.cmarix.com/blog/fintech-app-development-cost/" rel="noopener noreferrer"&gt;How Much Does Fintech App Development Cost in 2026?&lt;/a&gt;, CMARIX&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://acquaintsoft.com/blog/fintech-app-development-cost" rel="noopener noreferrer"&gt;Fintech app development cost&lt;/a&gt;, Acquaint Softtech&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/fintech-app-development-cost?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=fintech-app-development-cost" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>fintech</category>
      <category>startup</category>
      <category>webdev</category>
      <category>mobile</category>
    </item>
    <item>
      <title>How to choose an AI agent development company: a checklist</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Wed, 07 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/how-to-choose-an-ai-agent-development-company-a-checklist-492l</link>
      <guid>https://dev.to/apptycoons/how-to-choose-an-ai-agent-development-company-a-checklist-492l</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Judge an AI agent development company on evidence, not demos: a production agent you can inspect, an evaluation set built from your real data, written limits on what the agent may do, human approval for irreversible actions, a fixed scope and price after discovery, and full ownership of code, prompts and evals. Ask every vendor the same questions.&lt;/p&gt;

&lt;p&gt;Choosing an AI agent development company is hard because every vendor’s demo looks good. Demos run on clean data, happy paths and a presenter who knows what to type. Production agents run on messy data, edge cases and users who don’t. This checklist is built to tell those two apart.&lt;/p&gt;

&lt;p&gt;It is vendor-neutral on purpose. It ranks no one, it recommends no list, and it works for any team you are talking to. &lt;strong&gt;Disclosure:&lt;/strong&gt; Apptycoons builds AI agents, so at the end we answer the same twelve questions about ourselves, and you can hold us to them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why demos are a poor way to choose an AI agent vendor
&lt;/h2&gt;

&lt;p&gt;A demo shows that a model can do a task once; a production agent has to do it thousands of times, safely, with a record of what it did. The questions that separate vendors are about evaluation, permissions, failure handling and ownership, and none of them show up in a demo.&lt;/p&gt;

&lt;p&gt;It also helps to know what a good vendor will often recommend: less agent than you expected. Anthropic’s engineering guidance on building agents advises finding the simplest solution possible and adding complexity only when needed, and distinguishes fixed workflows from agents that direct their own steps. A vendor who proposes a simple workflow where it fits is usually a better sign than one who proposes a multi-agent system for everything.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Can they show an agent running in production?
&lt;/h2&gt;

&lt;p&gt;The strongest evidence is a live product you can use, or a customer you can call. Ask what the agent does, how long it has been live, what broke after launch and how they found out.&lt;/p&gt;

&lt;p&gt;Good answers are specific: a monitoring dashboard, a class of failure they didn’t expect, the fix and the test they added. Weak answers stay at the level of frameworks and model names.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Do they start from your workflow, not their framework?
&lt;/h2&gt;

&lt;p&gt;A good vendor asks about the job before the stack: what triggers it, who does it now, what systems it touches, what a correct result looks like and what a mistake costs. If the first meeting is about frameworks and vector databases, the scoping hasn’t started.&lt;/p&gt;

&lt;p&gt;Ask them to describe the first agent in one sentence, with one metric. If they can’t, the project will drift.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Can they say what the agent will not do?
&lt;/h2&gt;

&lt;p&gt;Scope is defined as much by exclusions as by features. Ask the vendor to write down which actions the agent may take, which it may only propose, and which it must never touch.&lt;/p&gt;

&lt;p&gt;This maps to a real security risk. The OWASP Top 10 for LLM Applications 2025 lists &lt;strong&gt;excessive agency&lt;/strong&gt;, an AI system given more functionality, permissions or autonomy than it needs, as one of the ten main risks. The fix is design, not a disclaimer: least-privilege tool access, separate credentials, and approval steps for anything irreversible.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F20tkti7yroxsww79kdhy.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F20tkti7yroxsww79kdhy.webp" alt="Three lists for an agent’s scope: actions it may take (least-privilege tools, separate credentials), actions it may only propose (a person approves anything irreversible) and things it must never touch (no tool and no access at all), with every action logged with its inputs and outputs." width="799" height="482"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Ask the vendor to fill in all three lists before the build starts.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  4. How will they evaluate the agent before and after launch?
&lt;/h2&gt;

&lt;p&gt;An agent without an evaluation set cannot be improved safely. Ask how the vendor will build a test set from your real cases, what score counts as good enough to launch, and how every change to a prompt, model or tool is re-scored before it ships.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The evaluation loop to ask a vendor for&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Build a test set&lt;/strong&gt; (Discovery): From your real cases, not a curated demo set.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Agree a pass mark&lt;/strong&gt; (Before the build): The score that counts as good enough to launch.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Score the agent&lt;/strong&gt; (Before launch): Against the test set and the agreed pass mark.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Re-score before it ships&lt;/strong&gt; (Every change): Each prompt, model or tool change, including model updates.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Good answers include real examples from your data, a pass mark agreed before the build, and regression testing when models change.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Watch out&lt;/p&gt;

&lt;p&gt;Any accuracy promise made before seeing your data is a guess.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  5. How do they defend against prompt injection and data leaks?
&lt;/h2&gt;

&lt;p&gt;Ask directly how they handle prompt injection, the first risk on the OWASP list, and sensitive information disclosure, the second. Any agent that reads email, documents, web pages or user input can receive instructions hidden in that content.&lt;/p&gt;

&lt;p&gt;Look for layered answers: untrusted content treated as data, tools scoped to the minimum, outputs validated before they trigger actions, sensitive data redacted, and model endpoints configured not to retain your data. Our &lt;a href="https://apptycoons.com/blog/ai-agent-guardrails?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;AI agent guardrails checklist&lt;/a&gt; maps ten such controls to the OWASP risks, so you can ask which of them the vendor builds by default.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Where does a human approve, and is every action logged?
&lt;/h2&gt;

&lt;p&gt;Every consequential action should have a clear owner. Ask where in the flow a person reviews or approves, how the agent escalates when it is unsure, and whether every action is logged with its inputs and outputs in a way an auditor could follow.&lt;/p&gt;

&lt;p&gt;If your industry is regulated, ask how the logs map to your existing controls. Frameworks such as NIST’s AI Risk Management Framework, a voluntary framework for managing AI risk, give you a shared vocabulary for that conversation.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Which models do they use, and can you switch?
&lt;/h2&gt;

&lt;p&gt;Models change every few months, so lock-in to one provider is a cost. Ask whether the architecture is model-agnostic, how a model swap would be tested, and what happens to cost and latency if you move.&lt;/p&gt;

&lt;p&gt;A good answer is often “we pick per task”. Combined with an evaluation set, that lets you change models with evidence rather than hope.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. How will it connect to your systems?
&lt;/h2&gt;

&lt;p&gt;Most of the work in an agent project is integration, not prompting. Ask which of your systems the agent reads from and writes to, how authentication works, what happens when an API is down, and whether the agent can do anything a normal user with the same role could not.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. Who owns the code, prompts, evaluations and data?
&lt;/h2&gt;

&lt;p&gt;You should own everything that makes the agent work: code, prompts, evaluation sets, infrastructure configuration and documentation. Ask for it in the contract, and ask whether the agent can run in your own cloud account.&lt;/p&gt;

&lt;p&gt;Then ask the uncomfortable question: what happens to the agent if the vendor disappears? If the answer involves their proprietary platform, you are renting, not buying.&lt;/p&gt;

&lt;h2&gt;
  
  
  10. What is fixed in the price?
&lt;/h2&gt;

&lt;p&gt;Compare what is fixed, not the headline number. Ask whether there is a paid discovery phase, whether the build price is fixed after it, how payments map to delivered features, and what running costs (model usage, hosting, monitoring) you should expect.&lt;/p&gt;

&lt;p&gt;Open-ended time-and-materials with no discovery is not wrong, but it moves all of the risk to you. Our &lt;a href="https://apptycoons.com/blog/ai-agent-development-cost?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;AI agent development cost guide&lt;/a&gt; breaks down what a build and its running costs usually include, so you can check a quote line by line.&lt;/p&gt;

&lt;h2&gt;
  
  
  11. What happens after launch?
&lt;/h2&gt;

&lt;p&gt;Agents need care after launch: models update, data drifts, and users find new edge cases. Ask what support is included, how monitoring works, who watches cost and success rate, and how improvements are scoped.&lt;/p&gt;

&lt;h2&gt;
  
  
  12. Will they tell you when not to build an agent?
&lt;/h2&gt;

&lt;p&gt;The best signal of an honest vendor is a recommendation against their own interest. Ask: “What would you not automate here?” A good partner will point to steps where a rule, a form or a person is cheaper and safer than a model, or to an off-the-shelf agent that already does the job. Our &lt;a href="https://apptycoons.com/blog/build-vs-buy-ai-agents?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;build vs buy framework for AI agents&lt;/a&gt; is a useful way to test that advice.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to put in the contract
&lt;/h2&gt;

&lt;p&gt;The contract is where the answers to questions 9 to 11 become enforceable. A vendor who answered them well on a call should have no trouble writing them down. Before you sign, check that it covers:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;IP assignment:&lt;/strong&gt; the code, prompts, evaluation sets, tool definitions and any fine-tuning data are assigned to you, not licensed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Accounts:&lt;/strong&gt; model provider, cloud and monitoring accounts are opened in your company’s name, with the vendor as a user you can remove.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data processing:&lt;/strong&gt; what data the vendor and each model provider may store, where and for how long; for EU personal data that means a data processing agreement (see our guide to the &lt;a href="https://apptycoons.com/blog/eu-ai-act-gdpr-ai-agents?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;EU AI Act and GDPR for AI agents&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Acceptance:&lt;/strong&gt; launch is accepted against the evaluation set and pass mark agreed in discovery, not against a demo.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Handover:&lt;/strong&gt; the repository, infrastructure as code, a runbook and the evaluation set are delivered at the end, whether or not you renew.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Support:&lt;/strong&gt; how long post-launch support lasts and what a change costs once it ends.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of these clauses is unusual in software contracts. What changes for AI agents is the list of assets: prompts and evaluation sets are as much part of the product as the code. This is a buyer’s checklist, not legal advice; have counsel review the final terms.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to check a certification claim
&lt;/h2&gt;

&lt;p&gt;Ask for the document behind the badge, then read its scope and date. A certification or report that covers a vendor’s office IT, or expired last year, says nothing about the team that will build your agent.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;ISO/IEC 42001&lt;/strong&gt; is the management-system standard for AI, published on December 18, 2023. A vendor claiming it should show a certificate naming the issuing body, the scope and the validity dates.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SOC 2&lt;/strong&gt; is not a certificate. The AICPA describes it as reporting on an examination of controls at a service organization, carried out by a CPA firm. Ask for the report itself under NDA, check which services it covers and the period it tested.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;“HIPAA certified”&lt;/strong&gt; does not exist. For health data, ask whether the vendor will sign a business associate agreement and which of its subprocessors will too.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A vendor without a certification can still be the right choice for a first agent if it answers the twelve questions above with evidence. What matters is that any claim on the website matches the document behind it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Red flags when choosing an AI agent developer
&lt;/h2&gt;

&lt;p&gt;These are the patterns that should end a conversation or at least slow it down:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Accuracy or savings figures promised before anyone has seen your data.&lt;/li&gt;
&lt;li&gt;No evaluation set, or “we test it manually”.&lt;/li&gt;
&lt;li&gt;No answer on prompt injection or excessive agency.&lt;/li&gt;
&lt;li&gt;Write access to production systems with no approval step.&lt;/li&gt;
&lt;li&gt;Prompts, evals or orchestration kept as the vendor’s intellectual property.&lt;/li&gt;
&lt;li&gt;A demo built on data that is not yours, presented as proof.&lt;/li&gt;
&lt;li&gt;No discovery phase, and no clear statement of what is fixed.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A scoring sheet you can copy
&lt;/h2&gt;

&lt;p&gt;Score each vendor from 0 to 2 on each line (0 = no answer, 1 = general answer, 2 = specific evidence). Compare totals only after the calls, and weigh the first four lines double.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Vendor scoring sheet (0 to 2 per line)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Criterion&lt;/th&gt;
&lt;th&gt;What a 2 looks like&lt;/th&gt;
&lt;th&gt;Weight&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Production evidence&lt;/td&gt;
&lt;td&gt;Live product or callable reference&lt;/td&gt;
&lt;td&gt;Double&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Evaluation&lt;/td&gt;
&lt;td&gt;Test set from your data, agreed pass mark, regression testing&lt;/td&gt;
&lt;td&gt;Double&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Limits and approvals&lt;/td&gt;
&lt;td&gt;Written action boundaries, human approval, audit log&lt;/td&gt;
&lt;td&gt;Double&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Security&lt;/td&gt;
&lt;td&gt;Prompt injection, data leakage and data retention answered specifically&lt;/td&gt;
&lt;td&gt;Double&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Workflow fit&lt;/td&gt;
&lt;td&gt;First agent in one sentence with one metric&lt;/td&gt;
&lt;td&gt;Single&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Integration&lt;/td&gt;
&lt;td&gt;Systems, auth and failure handling explained&lt;/td&gt;
&lt;td&gt;Single&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Model flexibility&lt;/td&gt;
&lt;td&gt;Model-agnostic, swap tested with evals&lt;/td&gt;
&lt;td&gt;Single&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ownership&lt;/td&gt;
&lt;td&gt;Code, prompts and evals yours, deployable in your cloud&lt;/td&gt;
&lt;td&gt;Single&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pricing clarity&lt;/td&gt;
&lt;td&gt;Discovery, fixed scope, milestone payments, run costs&lt;/td&gt;
&lt;td&gt;Single&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;After launch&lt;/td&gt;
&lt;td&gt;Monitoring, support and improvement process&lt;/td&gt;
&lt;td&gt;Single&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Our answers to the same questions
&lt;/h2&gt;

&lt;p&gt;Here is how Apptycoons answers the checklist. Hold us to it, and ask us for the evidence on a call.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Production evidence:&lt;/strong&gt; &lt;a href="https://apptycoons.com/work/innovative-ai?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;Innovative AI&lt;/a&gt;, voice agents for US car dealerships that matched callers’ requests to a service on the vehicle’s menu, read it back and booked it in Xtime, and &lt;a href="https://apptycoons.com/work/superdeal?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;Superdeal&lt;/a&gt;, an AI agent that runs creator campaigns with the brand approving every step. Both are live products, and both case studies show how the work was built.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Workflow first:&lt;/strong&gt; our process starts by mapping one workflow and one metric.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Limits and approvals:&lt;/strong&gt; approval steps, escalation rules and full audit logs for every action. On Superdeal, every consequential step goes Draft, Review, Send.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Evaluation:&lt;/strong&gt; a test set built from your real cases, scored before launch and again after every prompt, model or tool change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security:&lt;/strong&gt; least-privilege permissions, PII redaction and zero-retention model endpoints, so your data does not train public models.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Models:&lt;/strong&gt; we choose per task from Anthropic, OpenAI, Google or open-source models and keep the model swappable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ownership:&lt;/strong&gt; the code lives in your repository from day one, the IP is yours, and the agent runs in your cloud or on endpoints you control.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pricing:&lt;/strong&gt; published on our &lt;a href="https://apptycoons.com/pricing?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt;. Discovery is two weeks at $5,000, credited to the build; builds are fixed at $25k to $120k; a Dedicated Team starts at $12k a month. Every build includes 30 days of post-launch support.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;When not to build:&lt;/strong&gt; if a rule or a form solves the problem, we will say so. Our post on &lt;a href="https://apptycoons.com/blog/ai-pilots-to-production?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;taking AI pilots to production&lt;/a&gt; covers why so many stall.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If that matches what you need, our &lt;a href="https://apptycoons.com/services/ai-agent-development?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;AI agent development&lt;/a&gt; page has the details, and a &lt;a href="https://apptycoons.com/contact?interest=audit&amp;amp;service=ai-agent-development&amp;amp;utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;free AI audit&lt;/a&gt; is the fastest way to test our answers against your workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://www.anthropic.com/engineering/building-effective-agents" rel="noopener noreferrer"&gt;Building effective agents&lt;/a&gt;, Anthropic&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://genai.owasp.org/llm-top-10/" rel="noopener noreferrer"&gt;OWASP Top 10 for LLM Applications 2025&lt;/a&gt;, OWASP GenAI Security Project&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.nist.gov/itl/ai-risk-management-framework" rel="noopener noreferrer"&gt;AI Risk Management Framework&lt;/a&gt;, NIST&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://webstore.iec.ch/publication/90574" rel="noopener noreferrer"&gt;ISO/IEC 42001:2023 Information technology, Artificial intelligence, Management system&lt;/a&gt;, IEC Webstore&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.aicpa-cima.com/resources/landing/system-and-organization-controls-soc-suite-of-services" rel="noopener noreferrer"&gt;System and Organization Controls: SOC suite of services&lt;/a&gt;, AICPA &amp;amp; CIMA&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/how-to-evaluate-ai-agent-development-company?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>startup</category>
      <category>programming</category>
    </item>
    <item>
      <title>AI voice agent cost in 2026: per-minute vs custom build</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Wed, 07 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/ai-voice-agent-cost-in-2026-per-minute-vs-custom-build-47j4</link>
      <guid>https://dev.to/apptycoons/ai-voice-agent-cost-in-2026-per-minute-vs-custom-build-47j4</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Hosted voice platforms cost about $0.08 to $0.15 per minute all-in at list prices, plus extras such as HIPAA add-ons. A custom stack’s usage costs about $0.04 per minute, but it needs a $25k–$120k build and its own hosting. On list prices, custom starts paying back somewhere between 11,000 and 31,000 minutes a month.&lt;/p&gt;

&lt;p&gt;Vapi advertises $0.05 a minute. Add the speech-to-text, the language model and the voice that every call needs, and the same agent costs $0.082 to $0.129 a minute on Vapi’s own calculator. The advertised rate covers one layer of a five-layer stack; the other four arrive as separate line items.&lt;/p&gt;

&lt;p&gt;In our model, built only from public price lists, a hosted platform costs about $0.08 to $0.15 a minute all-in and a custom stack about $0.04 a minute before hosting and the build. Every figure below is a list price rechecked on October 18, 2026, and every calculation is shown, so you can rerun it with your own call volume.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much does an AI voice agent cost per minute?
&lt;/h2&gt;

&lt;p&gt;At list prices, a hosted voice platform costs about $0.08 to $0.15 per minute once every layer is included. A custom stack that pays each vendor directly costs about $0.04 per minute in usage, but you have to build and host it. The platform’s advertised rate, $0.05 on Vapi or $0.055 on Retell, is only the orchestration fee.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;All-in cost per minute, list prices (checked Oct 18, 2026)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;Per minute&lt;/th&gt;
&lt;th&gt;What is included&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Vapi&lt;/td&gt;
&lt;td&gt;$0.082–$0.129&lt;/td&gt;
&lt;td&gt;$0.05 hosting plus speech-to-text, model and voice passed through at cost, on Vapi telephony (no transport fee)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Retell, Claude 4.5 Haiku&lt;/td&gt;
&lt;td&gt;$0.110&lt;/td&gt;
&lt;td&gt;$0.055 infrastructure, $0.015 voice, $0.025 model, $0.015 telephony&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Retell, recommended tier&lt;/td&gt;
&lt;td&gt;$0.149&lt;/td&gt;
&lt;td&gt;Same, with a $0.064 recommended-tier model such as Claude 5 Sonnet&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Custom stack&lt;/td&gt;
&lt;td&gt;about $0.043&lt;/td&gt;
&lt;td&gt;Twilio, Deepgram Nova-3, Deepgram Aura-2 voice, Claude Sonnet 5.5; hosting and build not included&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  The five line items inside every per-minute price
&lt;/h2&gt;

&lt;p&gt;Every AI phone call pays for the same five things, whether a platform bundles them or you buy them separately. Knowing them is how you compare quotes.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Telephony carries the call. Twilio lists US inbound calls to a local number at $0.0085 a minute, and streaming the audio to your server at $0.0044 a minute.&lt;/li&gt;
&lt;li&gt;Speech-to-text transcribes the caller. Deepgram lists streaming Nova-3 at a regular price of $0.0077 a minute, currently discounted to $0.0048; we use the regular price.&lt;/li&gt;
&lt;li&gt;The language model decides what to say and which tools to call. It is billed per token, so its per-minute cost depends on prompt size and how often the caller speaks.&lt;/li&gt;
&lt;li&gt;Text-to-speech speaks the reply. Deepgram lists Aura-2 at $0.030 per 1,000 characters; Retell lists voices from $0.015 to $0.10 a minute depending on the provider.&lt;/li&gt;
&lt;li&gt;Orchestration handles turn-taking, interruptions and tool calls. Platforms charge for it per minute; on a custom stack you host it yourself.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq8dt14ef2g9cykazaepf.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq8dt14ef2g9cykazaepf.webp" alt="Two stacked bars on a scale of 0 to 12 cents a minute. Retell with Claude 4.5 Haiku, $0.110: infrastructure $0.055, model $0.025, voice $0.015, telephony $0.015. Custom stack, about $0.043: Twilio call and stream $0.0129, speech-to-text $0.0077, model $0.0103, voice $0.012, excluding hosting and the build." width="799" height="672"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;On Retell the platform fee is half the minute; on a custom stack you host orchestration yourself. Model and voice per-minute figures use the assumptions below.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  How we turned token prices into a per-minute cost
&lt;/h3&gt;

&lt;p&gt;Two of these layers are not priced per minute, so we converted them with stated assumptions. For the model, we assume five model calls per minute of conversation, each sending 3,000 input tokens (2,500 of them a cached system prompt) and receiving 80 output tokens. At Claude Sonnet 5.5 list prices of $2 per million input tokens, $0.10 for cache reads (Anthropic bills cache hits on Sonnet 5.5 at 0.05 times the input price) and $10 output, that is about $0.0021 per call and $0.0103 a minute. For the voice, we assume the agent talks for about 45% of the call at around 150 words a minute, roughly 400 characters, which is $0.012 a minute on Aura-2.&lt;/p&gt;

&lt;h2&gt;
  
  
  Platform pricing: what Vapi and Retell charge
&lt;/h2&gt;

&lt;p&gt;Both platforms publish their prices, so a fair comparison is possible. They differ in what is bundled and what costs extra.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Platform price lists compared (checked Oct 18, 2026)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Vapi&lt;/th&gt;
&lt;th&gt;Retell&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Platform fee&lt;/td&gt;
&lt;td&gt;$0.05/min hosting&lt;/td&gt;
&lt;td&gt;$0.055/min voice infrastructure&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Models and voices&lt;/td&gt;
&lt;td&gt;Passed through at cost; calculator examples $0.0095–$0.0099 transcriber, $0.0077–$0.0452 model, $0.0146–$0.0238 voice&lt;/td&gt;
&lt;td&gt;Priced per minute: voices $0.015–$0.10; models from under $0.01 to over $0.30, with Claude 4.5 Haiku at $0.025 and the recommended tier at $0.064&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Telephony&lt;/td&gt;
&lt;td&gt;Vapi telephony and SIP free, one number on the free tier; Twilio numbers billed by Twilio&lt;/td&gt;
&lt;td&gt;$0.015/min, numbers $2 a month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Plans&lt;/td&gt;
&lt;td&gt;No Success Package $0 with $5 credit; Core $29 a month; Pro 10% of hosting, $999 a month minimum; Premier custom&lt;/td&gt;
&lt;td&gt;Usage-based, $10 in free credits; enterprise plan at custom pricing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Concurrent calls&lt;/td&gt;
&lt;td&gt;4 / 10 / 30 by plan, extra lines $10 each a month&lt;/td&gt;
&lt;td&gt;First 20 free, then $8 each a month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HIPAA&lt;/td&gt;
&lt;td&gt;$2,000 a month add-on&lt;/td&gt;
&lt;td&gt;HIPAA and BAA listed on pay-as-you-go and enterprise; custom BAA on enterprise (checked Oct 19, 2026)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The choice of model and voice moves the platform price more than the choice of platform. On Retell, swapping a recommended-tier model for Claude 4.5 Haiku takes the all-in rate from $0.149 to $0.110 a minute, the most expensive models on Retell’s list cost over $0.30 a minute on their own, and moving to a premium ElevenLabs voice can add up to $0.085.&lt;/p&gt;

&lt;h3&gt;
  
  
  A third route: one speech-to-speech model
&lt;/h3&gt;

&lt;p&gt;Some stacks replace the separate speech-to-text, model and voice with one speech-to-speech model that hears and answers in audio. OpenAI’s realtime models are billed per audio token rather than per minute ($32 per million input and $64 per million output tokens for gpt-realtime-2.1; $10 and $20 for the mini model, list prices checked October 26, 2026). In our own test calls in October 2026, that came to about $0.078 a minute of talk for gpt-realtime-2.1 and $0.023 for the mini model, before telephony, hosting and orchestration; the method and raw data are in our &lt;a href="https://apptycoons.com/research/voice-agent-latency-benchmark?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;voice agent latency benchmark&lt;/a&gt;. Long system prompts and tool definitions add text tokens to every turn, so measure with your own call flow before you budget.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a custom AI voice agent costs to build
&lt;/h2&gt;

&lt;p&gt;With us, a custom voice agent falls in the same $25k–$120k band as any agent we build, with the price fixed after discovery (the &lt;a href="https://apptycoons.com/pricing?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt; has the model). “Custom” means you own the orchestration code, run it in your cloud and pay each vendor directly, typically on an open-source framework such as LiveKit or Pipecat instead of a hosted platform.&lt;/p&gt;

&lt;p&gt;Five things set where a voice build lands in that band:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the systems the agent books into or updates, such as a scheduler, CRM or order system,&lt;/li&gt;
&lt;li&gt;the number of call flows, from a single booking flow to triage across several departments,&lt;/li&gt;
&lt;li&gt;warm transfer to a person with a summary of the call,&lt;/li&gt;
&lt;li&gt;latency tuning, because slow replies make a conversation feel broken (see &lt;a href="https://apptycoons.com/blog/voice-agent-latency?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;voice agent latency&lt;/a&gt;),&lt;/li&gt;
&lt;li&gt;compliance, such as HIPAA, call recording consent and data retention.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A platform build is not free either. Someone still writes the prompts, connects the agent to your systems and tests the call flows. That work is similar on both routes, so the comparison below charges only the custom route with a build, which favors the platforms.&lt;/p&gt;

&lt;h2&gt;
  
  
  Total cost at 1,000, 10,000 and 50,000 minutes a month
&lt;/h2&gt;

&lt;p&gt;At 1,000 minutes a month a platform costs roughly a tenth of a custom stack; at 50,000 the order flips. The table adds usage at list prices and, for the custom stack, two fixed monthly costs we state as assumptions: $500 a month for hosting and monitoring, and the minimum build of $25k spread over 36 months, about $694 a month.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Monthly cost by call volume (list prices, assumptions above)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Minutes a month&lt;/th&gt;
&lt;th&gt;Vapi&lt;/th&gt;
&lt;th&gt;Retell&lt;/th&gt;
&lt;th&gt;Custom usage&lt;/th&gt;
&lt;th&gt;Custom all-in&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1,000&lt;/td&gt;
&lt;td&gt;$82–$129&lt;/td&gt;
&lt;td&gt;$110–$149&lt;/td&gt;
&lt;td&gt;$43&lt;/td&gt;
&lt;td&gt;$1,237&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10,000&lt;/td&gt;
&lt;td&gt;$818–$1,289&lt;/td&gt;
&lt;td&gt;$1,100–$1,490&lt;/td&gt;
&lt;td&gt;$429&lt;/td&gt;
&lt;td&gt;$1,623&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;50,000&lt;/td&gt;
&lt;td&gt;$4,090–$6,445&lt;/td&gt;
&lt;td&gt;$5,500–$7,450&lt;/td&gt;
&lt;td&gt;$2,143&lt;/td&gt;
&lt;td&gt;$3,337&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The platform columns exclude plan fees, concurrency charges and HIPAA add-ons, and the custom column excludes the cost of your team’s time to operate it. Both omissions matter at the edges, so treat the table as a starting model, not a quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  The break-even point for a custom voice agent
&lt;/h2&gt;

&lt;p&gt;On these list prices, a custom stack breaks even at about 11,300 minutes a month against Retell’s recommended tier, 13,900 against Vapi’s higher configuration, 17,800 against Retell with Claude 4.5 Haiku, and 30,700 against Vapi’s lowest configuration. The arithmetic is the custom stack’s fixed monthly cost, about $1,194, divided by the per-minute saving.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Break-even minutes per month for a custom stack&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Compared with&lt;/th&gt;
&lt;th&gt;Platform per minute&lt;/th&gt;
&lt;th&gt;Saving per minute&lt;/th&gt;
&lt;th&gt;Break-even&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Retell, recommended tier&lt;/td&gt;
&lt;td&gt;$0.149&lt;/td&gt;
&lt;td&gt;$0.106&lt;/td&gt;
&lt;td&gt;about 11,300&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vapi, higher configuration&lt;/td&gt;
&lt;td&gt;$0.129&lt;/td&gt;
&lt;td&gt;$0.086&lt;/td&gt;
&lt;td&gt;about 13,900&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Retell, Claude 4.5 Haiku&lt;/td&gt;
&lt;td&gt;$0.110&lt;/td&gt;
&lt;td&gt;$0.067&lt;/td&gt;
&lt;td&gt;about 17,800&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vapi, lowest configuration&lt;/td&gt;
&lt;td&gt;$0.082&lt;/td&gt;
&lt;td&gt;$0.039&lt;/td&gt;
&lt;td&gt;about 30,700&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Two things move the break-even sharply, in opposite directions. A HIPAA add-on of $2,000 a month on a platform is larger than the custom stack’s entire fixed cost in this model, so it pulls the break-even down, although a custom stack has its own compliance costs, such as Twilio’s Security Edition for a BAA. A larger build, say for several call flows and integrations, pushes it up by roughly 6,500 to 17,800 minutes for every additional $25k spread over three years, depending on the platform you compare against.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;A HIPAA add-on vs the custom stack’s fixed monthly costs&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Custom: hosting and monitoring: $500&lt;/li&gt;
&lt;li&gt;Custom: minimum build over 36 months: $694&lt;/li&gt;
&lt;li&gt;Vapi HIPAA add-on: $2,000&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Custom stack assumptions from the total-cost section: about $1,194 a month in all.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Costs that per-minute quotes leave out
&lt;/h2&gt;

&lt;p&gt;A per-minute rate is the biggest line on the bill, but not the only one. Budget for these as well, on any route:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Concurrent calls. Platforms include a set number of simultaneous calls and charge for more: Retell includes 20 and charges $8 a month for each extra, and Vapi includes 4, 10 or 30 depending on the plan and charges $10 a month per additional line. Size this for your busiest hour, not your average.&lt;/li&gt;
&lt;li&gt;Plan minimums. Vapi’s Core plan costs $29 a month, and its Pro plan bills 10% of the hosting fee with a $999 a month minimum. At 5,000 minutes a month, Pro’s hosting share is $25, so the minimum, not the percentage, sets the bill until volume is far higher.&lt;/li&gt;
&lt;li&gt;Phone numbers. Small, but they add up across locations: Twilio lists local numbers at $1.15 a month and toll-free at $2.15.&lt;/li&gt;
&lt;li&gt;Transfers. When the agent hands a caller to a person, the outbound leg is billed too; Twilio lists outbound calls at $0.0140 a minute.&lt;/li&gt;
&lt;li&gt;Recordings and transcripts. Storage and retention rules matter more than the storage price, especially for regulated calls.&lt;/li&gt;
&lt;li&gt;Testing. Every prompt or model change should be replayed against recorded test calls before it goes live, and those test calls use real minutes.&lt;/li&gt;
&lt;li&gt;Change. Models, voices and prices change; someone has to evaluate and apply those changes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The integration is the cost that no per-minute quote shows, because it sits in the build. On the service booking agent we built for Innovative AI, every booking call loaded that vehicle’s own menu of 100–200 services from Xtime, checked the dealership’s open slots and settled drop-off, pickup or mobile service before it booked anything. In a build like this, each lookup is typically a tool the agent calls mid-conversation, and &lt;a href="https://apptycoons.com/blog/ai-service-scheduling-dealerships?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;how AI service scheduling works at a dealership&lt;/a&gt; walks through them in order.&lt;/p&gt;

&lt;h2&gt;
  
  
  HIPAA and the BAA chain
&lt;/h2&gt;

&lt;p&gt;A voice agent that hears patient information is only as compliant as the weakest vendor on the call. Under HIPAA, every vendor that receives protected health information must sign a business associate agreement, and on a voice call that is the carrier, speech-to-text, the language model, text-to-speech, the orchestration layer and wherever recordings and transcripts are stored.&lt;/p&gt;

&lt;p&gt;Price this chain before you choose a stack. Vapi lists HIPAA-eligible data handling at $2,000 a month. Retell’s plan comparison lists HIPAA and a BAA on pay-as-you-go as well as enterprise, with a custom BAA on enterprise only (checked October 19, 2026). Twilio signs a BAA only for customers on its Security or Enterprise Edition. On a custom stack you sign each agreement yourself and can choose vendors and regions accordingly, which is often the deciding factor for healthcare work. There is no such thing as being “HIPAA certified”, so ask each vendor for its BAA, not a badge.&lt;/p&gt;

&lt;h2&gt;
  
  
  Outbound calls: consent rules change the cost
&lt;/h2&gt;

&lt;p&gt;An agent that places calls costs more to build than one that answers them, because US law treats its voice as artificial. In February 2024 the FCC confirmed, in a declaratory ruling (FCC 24-17), that the TCPA’s restrictions on “artificial or prerecorded voice” cover current AI technologies that generate human voices. Such calls need the called party’s prior express consent, absent an emergency purpose or an exemption.&lt;/p&gt;

&lt;p&gt;For a build, that turns into line items an inbound receptionist mostly avoids:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;consent capture and storage, tied to each number the agent may call,&lt;/li&gt;
&lt;li&gt;do-not-call list scrubbing before every campaign,&lt;/li&gt;
&lt;li&gt;an opt-out path inside the call that the agent honors at once,&lt;/li&gt;
&lt;li&gt;calling-hour limits by the recipient’s time zone,&lt;/li&gt;
&lt;li&gt;logs that show which consent covered which call.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Budget these as scope, not as a later fix; they decide whether the agent can dial at all. This is a summary of the ruling, not legal advice, and state rules can add to it.&lt;/p&gt;

&lt;p&gt;Calls with a sales purpose count as telemarketing and need prior express written consent, so an unsold-lead callback carries a heavier consent flow than a reminder about a booked service, as our guide to &lt;a href="https://apptycoons.com/blog/dealership-no-show-follow-up?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;no-show and unsold-lead follow-up calls&lt;/a&gt; explains.&lt;/p&gt;

&lt;h2&gt;
  
  
  When a platform is the right answer
&lt;/h2&gt;

&lt;p&gt;For most first voice agents, a platform is the better choice. Choose one when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;volume is under about 10,000 minutes a month and not growing fast;&lt;/li&gt;
&lt;li&gt;the call flow is standard, such as answering questions, booking into a common scheduler or taking messages;&lt;/li&gt;
&lt;li&gt;you want to test whether callers accept an AI agent before you invest in a build;&lt;/li&gt;
&lt;li&gt;or nobody will run voice infrastructure after launch.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Go custom when volume is high or rising, when compliance needs control over every vendor in the chain, when the agent must act inside your own systems in ways a platform’s integrations cannot, or when latency and voice quality are part of your product. Many teams start on a platform and move once the numbers above favor it; designing prompts and tools to be portable makes that move cheaper. The same trade-off applies to text agents, and our guide to &lt;a href="https://apptycoons.com/blog/build-vs-buy-ai-agents?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;build vs buy AI agents&lt;/a&gt; runs it over three years.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Platform or custom, in short&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hosted platform&lt;/strong&gt;: Vapi, Retell&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Under about 10,000 minutes a month&lt;/li&gt;
&lt;li&gt;A standard call flow&lt;/li&gt;
&lt;li&gt;Testing whether callers accept an AI agent&lt;/li&gt;
&lt;li&gt;Nobody to run voice infrastructure&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;vs&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Custom stack&lt;/strong&gt;: LiveKit, Pipecat&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;High or rising volume&lt;/li&gt;
&lt;li&gt;Control over every vendor in the compliance chain&lt;/li&gt;
&lt;li&gt;Actions inside your own systems&lt;/li&gt;
&lt;li&gt;Latency and voice quality are part of your product&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Is an AI voice agent worth it? Compare with missed calls
&lt;/h2&gt;

&lt;p&gt;The right comparison is not the agent’s cost against a receptionist’s salary; it is the agent’s cost against the revenue lost to calls nobody answers. A business taking 60 calls a day at three minutes each uses about 5,400 minutes a month, which costs roughly $440 to $800 a month in platform usage at the list prices above.&lt;/p&gt;

&lt;p&gt;Then estimate what missed calls cost you: calls a month, times the share you miss, times the share of those callers who would have bought, times the value of a customer. We walk through that model in &lt;a href="https://apptycoons.com/blog/cost-of-missed-calls?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;what missed calls really cost&lt;/a&gt;, and you can run it with your own numbers in the &lt;a href="https://apptycoons.com/tools/ai-voice-agent-roi-calculator?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;AI voice agent ROI calculator&lt;/a&gt;. If the lost revenue is a multiple of the agent’s monthly cost, the case is easy at any of the prices in this guide.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to lower the per-minute cost of a voice agent
&lt;/h2&gt;

&lt;p&gt;The biggest savings come from the model and the voice, not from haggling over the platform fee.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use the smallest model that passes your call tests, and keep the system prompt stable so it can be cached.&lt;/li&gt;
&lt;li&gt;Pick a standard voice unless the voice is part of your brand; premium voices can cost several times more per minute.&lt;/li&gt;
&lt;li&gt;Keep calls short with clear flows and fast handoff to a person when the agent cannot help.&lt;/li&gt;
&lt;li&gt;Route by intent, so simple calls never reach the expensive model.&lt;/li&gt;
&lt;li&gt;Recheck list prices before you commit. This guide uses prices checked on October 18, 2026, and vendors update them; our &lt;a href="https://apptycoons.com/tools/ai-voice-agent-pricing?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;AI voice agent pricing tracker&lt;/a&gt; rechecks them every month.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you want these numbers worked out for your own call volume and systems, our &lt;a href="https://apptycoons.com/ai-voice-agents?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;AI voice agents&lt;/a&gt; team can model both routes in a free audit before you commit to either.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://www.retellai.com/pricing" rel="noopener noreferrer"&gt;Retell AI pricing&lt;/a&gt;, Retell AI&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://vapi.ai/pricing" rel="noopener noreferrer"&gt;Vapi pricing&lt;/a&gt;, Vapi&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://developers.openai.com/api/docs/pricing" rel="noopener noreferrer"&gt;API pricing (realtime and audio models)&lt;/a&gt;, OpenAI&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.twilio.com/en-us/voice/pricing/us" rel="noopener noreferrer"&gt;Twilio Programmable Voice pricing (United States)&lt;/a&gt;, Twilio&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://deepgram.com/pricing" rel="noopener noreferrer"&gt;Deepgram pricing&lt;/a&gt;, Deepgram&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://platform.claude.com/docs/en/about-claude/pricing" rel="noopener noreferrer"&gt;Claude API pricing&lt;/a&gt;, Anthropic&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.twilio.com/en-us/hipaa" rel="noopener noreferrer"&gt;HIPAA compliance at Twilio&lt;/a&gt;, Twilio&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://docs.fcc.gov/public/attachments/FCC-24-17A1.pdf" rel="noopener noreferrer"&gt;Implications of Artificial Intelligence Technologies on Protecting Consumers from Unwanted Robocalls and Robotexts, Declaratory Ruling (FCC 24-17)&lt;/a&gt;, Federal Communications Commission&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/ai-voice-agent-cost?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=ai-voice-agent-cost" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>voiceagents</category>
      <category>llm</category>
      <category>startup</category>
    </item>
    <item>
      <title>EU AI Act and GDPR for AI agents: a build checklist</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Wed, 07 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/eu-ai-act-and-gdpr-for-ai-agents-a-build-checklist-5f7h</link>
      <guid>https://dev.to/apptycoons/eu-ai-act-and-gdpr-for-ai-agents-a-build-checklist-5f7h</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Since August 2, 2026, an AI agent that talks to people in the EU must tell them it is an AI by the first interaction (Article 50). Bans on manipulative AI already apply. High-risk rules for uses such as hiring or credit start December 2, 2027. GDPR still governs the agent’s personal data, including transfers.&lt;/p&gt;

&lt;p&gt;Since August 2, 2026, a support chatbot or voice agent that talks to people in the EU has to tell them it is an AI, at the latest at the first interaction. Breaching that duty can cost up to €15 million or 3% of worldwide annual turnover, whichever is higher (for SMEs and start-ups, whichever is lower).&lt;/p&gt;

&lt;p&gt;Most of what the EU AI Act and GDPR ask of an agent is engineering work: a line in the greeting, a log, an approval step, a region setting. This guide maps each rule to the build, as the law stands on October 18, 2026. Apptycoons builds &lt;a href="https://apptycoons.com/services/ai-agent-development?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=eu-ai-act-gdpr-ai-agents" rel="noopener noreferrer"&gt;custom AI agents&lt;/a&gt; with engineers in Karachi, Pakistan, so the transfers section describes our own setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  Does the EU AI Act apply to your AI agent?
&lt;/h2&gt;

&lt;p&gt;Yes, if the agent is placed on the EU market or its output is used in the EU. Article 2(1) covers providers placing AI systems on the EU market wherever they are established, deployers located in the EU, and providers and deployers in third countries “where the output produced by the AI system is used in the Union”. A US or UK company whose agent answers EU customers is in scope.&lt;/p&gt;

&lt;p&gt;The Commission’s AI Act Service Desk says the term AI agent “is not legally defined”, but agents fall under the definition of an AI system, so the same rules apply. It calls its view on agents preliminary.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who is the provider when an agency builds the agent?
&lt;/h2&gt;

&lt;p&gt;Usually the client. Article 3(3) makes the provider whoever develops an AI system, or “has an AI system … developed and places it on the market or puts the AI system into service under its own name or trademark”. A company that commissions a custom agent and runs it under its own brand fits that definition, and because it uses the agent in its own business, it is normally the deployer as well (Article 3(4)).&lt;/p&gt;

&lt;p&gt;That is our reading of the definitions, not a ruling, and a vendor selling one agent to many customers under its own brand is a provider itself. Write the split into the contract: who holds the Article 50 duties, who keeps the documentation, who answers a regulator.&lt;/p&gt;

&lt;p&gt;GDPR draws a parallel line: you are normally the controller and the development partner the processor, which requires an Article 28 contract (a data processing agreement, or DPA).&lt;/p&gt;

&lt;h2&gt;
  
  
  What changed in 2026: the Digital Omnibus dates
&lt;/h2&gt;

&lt;p&gt;The Digital Omnibus on AI, Regulation (EU) 2026/1744, moved the high-risk deadlines and left the chatbot rules on schedule. It entered into force on July 27, 2026, so pages giving August 2, 2026 as the high-risk date are out of date.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;EU AI Act dates after Regulation (EU) 2026/1744&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Date&lt;/th&gt;
&lt;th&gt;What applies&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Feb 2, 2025&lt;/td&gt;
&lt;td&gt;Banned practices (Article 5) and AI literacy (Article 4)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Aug 2, 2025&lt;/td&gt;
&lt;td&gt;Rules for general-purpose AI models, governance and penalties&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Aug 2, 2026&lt;/td&gt;
&lt;td&gt;General application, including the Article 50 transparency duties&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dec 2, 2026&lt;/td&gt;
&lt;td&gt;New Article 5 bans (non-consensual intimate imagery, child sexual abuse material); marking deadline for generative systems on the market before Aug 2, 2026&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dec 2, 2027&lt;/td&gt;
&lt;td&gt;High-risk rules for Annex III uses (hiring, credit, insurance pricing and others)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Aug 2, 2028&lt;/td&gt;
&lt;td&gt;High-risk rules for AI in regulated products (Annex I)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The Omnibus also softened Article 4: providers and deployers must now “take measures to support the development of AI literacy”, not ensure a sufficient level of it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Article 50 requires of chatbots and voice agents
&lt;/h2&gt;

&lt;p&gt;An agent that talks to people must be designed so that they “are informed that they are interacting with an AI system, unless this is obvious” (Article 50(1)). The information has to arrive “in a clear and distinguishable manner at the latest at the time of the first interaction or exposure”, and it must meet accessibility requirements (Article 50(5)). The Commission’s FAQ names “chatbots, AI agents, and avatars”; a voice agent on a phone line is the same two-way exchange.&lt;/p&gt;

&lt;p&gt;Three details are often misreported:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Naming the company.&lt;/strong&gt; Article 50(1) does not require the agent to say which business it works for. It is good practice, and the GDPR notice usually needs it anyway.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The “obvious” exception.&lt;/strong&gt; Don’t build on it. A voice agent designed to sound human is the opposite of obvious.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Marking output.&lt;/strong&gt; Article 50(2) is a separate duty: providers of systems that generate synthetic audio, image, video or text must mark the output “in a machine-readable format and detectable as artificially generated or manipulated”. A synthetic voice is synthetic audio. The grace period to December 2, 2026 covers only systems on the market before August 2, 2026.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Maximum AI Act fines, in millions of euros&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Article 50 breach: €15M or 3%&lt;/li&gt;
&lt;li&gt;Article 5 banned practice: €35M or 7%&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Or the percentage of total worldwide annual turnover, whichever is higher; for SMEs and start-ups, whichever is lower.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Our &lt;a href="https://apptycoons.com/ai-voice-agents?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=eu-ai-act-gdpr-ai-agents" rel="noopener noreferrer"&gt;AI voice agent development&lt;/a&gt; page covers how we build and test the greeting, transfer and recording flow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Disclosure scripts for chat, voice and handoff
&lt;/h2&gt;

&lt;p&gt;These are examples to adapt, not legal wording. The voice greeting combines the Article 50 disclosure with the GDPR Article 13 recording notice, because both have to come first.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Chat, first message:&lt;/strong&gt; “Hi, I’m [Company]’s AI assistant. I can check orders and book appointments. Type ‘person’ at any time to reach our team.”&lt;/p&gt;

&lt;p&gt;On a voice call, the greeting, the reminder before a sensitive step and the line before a transfer look like this:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Example call (illustrative): disclosure, a sensitive step and a handoff&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AI agent:&lt;/strong&gt; Thanks for calling [Company]. I’m an AI assistant. This call is recorded so we can handle your request, and we keep recordings for [30] days. You can find our privacy notice at [company.com/privacy] or ask for it by email. How can I help?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Caller:&lt;/strong&gt; I need to move my appointment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AI agent:&lt;/strong&gt; As a reminder, you’re speaking with an AI assistant. Before I change your booking, I’ll read the details back for you to confirm.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Caller:&lt;/strong&gt; Can I talk to a person?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AI agent:&lt;/strong&gt; I’m transferring you to a member of our team. They’ll see a summary of our conversation.&lt;/p&gt;

&lt;p&gt;Keep the spoken notice short and put the full privacy notice online.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does an AI agent become high-risk?
&lt;/h2&gt;

&lt;p&gt;An agent becomes high-risk when it is used for an Annex III purpose. The ones closest to agent work: recruitment and selection of candidates (4(a)), decisions on terms of work, promotion or termination and the monitoring of workers (4(b)), creditworthiness and credit scoring, with fraud detection excluded (5(b)), risk assessment and pricing in life and health insurance (5(c)), and evaluating or classifying emergency calls (5(d)).&lt;/p&gt;

&lt;p&gt;From December 2, 2027, those systems carry the Chapter III obligations: risk management, data governance, technical documentation, record-keeping, human oversight, and accuracy and cybersecurity.&lt;/p&gt;

&lt;p&gt;Human oversight is where the “kill switch” idea comes from, and it is often overstated. There is no general duty for every AI agent to have one. For high-risk systems, Article 14(4)(e) requires that the people assigned to oversight can “intervene in the operation of the high-risk AI system or interrupt the system through a ‘stop’ button or a similar procedure that allows the system to come to a halt in a safe state” (checked October 18, 2026). In build terms, that is a switch that stops the agent and leaves any action it was taking either finished or rolled back, never half done.&lt;/p&gt;

&lt;p&gt;A general customer-service, booking or FAQ agent is typically not high-risk. Add a step that screens job applicants or sets credit limits and it is. Draw that line in scope.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Where the high-risk line usually falls&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Typically not high-risk&lt;/strong&gt;: Article 50 still applies&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Customer-service agent&lt;/li&gt;
&lt;li&gt;Booking agent&lt;/li&gt;
&lt;li&gt;FAQ agent&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;vs&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;High-risk (Annex III)&lt;/strong&gt;: From Dec 2, 2027&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Screening job applicants&lt;/li&gt;
&lt;li&gt;Credit scoring or setting credit limits&lt;/li&gt;
&lt;li&gt;Life and health insurance pricing&lt;/li&gt;
&lt;li&gt;Evaluating or classifying emergency calls&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Banned practices to design out now
&lt;/h2&gt;

&lt;p&gt;Article 5(1)(a) and (b) have applied since February 2, 2025. They ban manipulative or deceptive techniques that materially distort behavior and cause significant harm, and exploiting vulnerabilities linked to age, disability or social or economic situation.&lt;/p&gt;

&lt;p&gt;For a sales or collections agent, design out the patterns that lean toward that line: invented deadlines, pressure on callers who sound confused, scripts that push harder when someone hesitates.&lt;/p&gt;

&lt;h2&gt;
  
  
  GDPR for agents: what still applies
&lt;/h2&gt;

&lt;p&gt;GDPR applies to an agent the way it applies to any system that processes personal data, and it has not changed. The separate Digital Omnibus proposal to amend it (COM(2025) 837) was still in Parliament and Council when we checked on October 18, 2026.&lt;/p&gt;

&lt;p&gt;The parts that turn into code:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Lawful basis (Article 6).&lt;/strong&gt; Pick it per purpose before the build.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Minimization.&lt;/strong&gt; Send the model only the fields the task needs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Retention.&lt;/strong&gt; Transcripts, recordings, logs and vector-store chunks each need a deletion timer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DPIA (Article 35).&lt;/strong&gt; Required before processing “likely to result in a high risk”, such as health data at scale.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Automated decisions (Article 22).&lt;/strong&gt; People have the right not to be subject to solely automated decisions with legal or similarly significant effects.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rights requests.&lt;/strong&gt; Access and deletion must reach transcripts, logs and embeddings, not only the CRM.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Sub-processors in an agent stack
&lt;/h2&gt;

&lt;p&gt;A voice or chat agent can involve five or six vendors that see personal data, and each belongs in the DPA as a sub-processor. Article 28 requires the controller’s prior authorization to use them.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Who sees what in a typical agent stack&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Component&lt;/th&gt;
&lt;th&gt;What it sees&lt;/th&gt;
&lt;th&gt;What to settle&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Model API&lt;/td&gt;
&lt;td&gt;Prompts, retrieved context, outputs&lt;/td&gt;
&lt;td&gt;DPA, region, training and retention settings&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Telephony&lt;/td&gt;
&lt;td&gt;Phone numbers, call audio, call records&lt;/td&gt;
&lt;td&gt;DPA, where recordings are stored&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Speech-to-text&lt;/td&gt;
&lt;td&gt;Caller audio&lt;/td&gt;
&lt;td&gt;DPA, retention of audio and transcripts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Text-to-speech&lt;/td&gt;
&lt;td&gt;The agent’s replies, which may contain personal data&lt;/td&gt;
&lt;td&gt;DPA, how generated audio is marked&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vector database&lt;/td&gt;
&lt;td&gt;Chunks of your documents and records&lt;/td&gt;
&lt;td&gt;DPA, region, deletion on request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hosting and logging&lt;/td&gt;
&lt;td&gt;Everything the agent logs&lt;/td&gt;
&lt;td&gt;DPA, region, log retention&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Model providers differ. OpenAI has not trained on API data by default since March 1, 2023, keeps abuse-monitoring logs for up to 30 days, offers zero data retention only with prior approval, and can keep both storage and processing in Europe (EEA and Switzerland); its UK region stores data there but may process it elsewhere. Anthropic’s own API currently offers inference in the US or globally and stores workspace data in the US, so EU residency for Claude means going through a cloud platform such as Google Cloud, where the endpoint sets the region. Check current terms before you write the privacy notice.&lt;/p&gt;

&lt;h2&gt;
  
  
  Working with engineers outside the EU: a transfer setup that holds up
&lt;/h2&gt;

&lt;p&gt;Engineers outside the EU can work on a GDPR-covered system, but personal data sent to a country without an EU adequacy decision needs a transfer tool and an assessment. Pakistan, where our engineers work, is not on the &lt;a href="https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en" rel="noopener noreferrer"&gt;Commission’s adequacy list&lt;/a&gt;. The setup we propose:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Production data stays in your environment,&lt;/strong&gt; in your cloud account and, when you require it, an EU region.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Development and testing run on synthetic or redacted data.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Production access is limited to named engineers,&lt;/strong&gt; for a stated reason, and logged.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Where personal data does reach Karachi, the EU standard contractual clauses apply:&lt;/strong&gt; Module 2 (controller to processor) or Module 3 (processor to sub-processor), depending on who signs. They already contain the Article 28 terms, so no separate DPA is needed for that transfer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clause 14 requires a transfer impact assessment&lt;/strong&gt; of the destination country’s laws and practices, with extra safeguards such as encryption where needed. We supply the technical facts; your counsel signs off.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuv8zs8keazqppfpzyj2e.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuv8zs8keazqppfpzyj2e.webp" alt="Two zones. Your environment, in your cloud account and an EU region on request, holds production data and the model, storage and vector database. Engineers in Karachi, a country without an EU adequacy decision, work on synthetic or redacted data, with named, logged access for a stated reason. Where personal data reaches Karachi, EU standard contractual clauses and a Clause 14 transfer impact assessment apply." width="800" height="576"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The setup we propose; your counsel signs off on the transfer assessment.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;None of this means data “never leaves the EU”. Access from Karachi is a transfer and is documented as one.&lt;/p&gt;

&lt;h2&gt;
  
  
  UK buyers: what differs
&lt;/h2&gt;

&lt;p&gt;The EU AI Act is not UK law, but it reaches a UK company whose agent’s output is used in the EU (Article 2(1)(c)). Personal data falls under UK GDPR, and EU-to-UK flows rely on the adequacy decisions the Commission renewed in December 2025.&lt;/p&gt;

&lt;p&gt;Transfers out of the UK work differently. The ICO is explicit that “the EU SCCs are not valid on their own” for UK transfers: you use the ICO’s International Data Transfer Agreement (IDTA), or the UK Addendum attached to the EU SCCs, and you must complete a transfer risk assessment (TRA). The Data (Use and Access) Act 2025 also rewrote the UK rules on automated decision-making; check them before an agent decides anything significant on its own.&lt;/p&gt;

&lt;h2&gt;
  
  
  The build checklist
&lt;/h2&gt;

&lt;p&gt;This is the list we work through in discovery and build for an agent with EU or UK users: a legal hook, a change in the system and a record you keep. The last row, the kill switch, is a legal duty only for high-risk systems under Article 14; for every other agent it is good practice. The approval, audit and kill-switch rows are the same controls our &lt;a href="https://apptycoons.com/blog/ai-agent-guardrails?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=eu-ai-act-gdpr-ai-agents" rel="noopener noreferrer"&gt;AI agent guardrails checklist&lt;/a&gt; covers from the security side.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;EU AI Act and GDPR controls in an agent build&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Control&lt;/th&gt;
&lt;th&gt;Legal hook&lt;/th&gt;
&lt;th&gt;What goes into the build&lt;/th&gt;
&lt;th&gt;Evidence you keep&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Role mapping&lt;/td&gt;
&lt;td&gt;AI Act Art. 3(3)–(4); GDPR Art. 28&lt;/td&gt;
&lt;td&gt;Provider, deployer, controller and processor agreed in discovery&lt;/td&gt;
&lt;td&gt;Contract clause and role note&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI disclosure in chat&lt;/td&gt;
&lt;td&gt;AI Act Art. 50(1), 50(5)&lt;/td&gt;
&lt;td&gt;First message says it is an AI; readable by screen readers&lt;/td&gt;
&lt;td&gt;Test case on the first turn&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI disclosure in voice&lt;/td&gt;
&lt;td&gt;AI Act Art. 50(1); GDPR Art. 13&lt;/td&gt;
&lt;td&gt;Greeting with AI and recording notice before any question&lt;/td&gt;
&lt;td&gt;Script version and test recording&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Synthetic audio marking&lt;/td&gt;
&lt;td&gt;AI Act Art. 50(2)&lt;/td&gt;
&lt;td&gt;Marking agreed with the speech vendor&lt;/td&gt;
&lt;td&gt;Vendor confirmation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Human handoff&lt;/td&gt;
&lt;td&gt;GDPR Art. 22(3), where Art. 22 applies&lt;/td&gt;
&lt;td&gt;Transfer on request and on low confidence&lt;/td&gt;
&lt;td&gt;Handoff log&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Approval steps&lt;/td&gt;
&lt;td&gt;GDPR Art. 22; AI Act Art. 14 if high-risk&lt;/td&gt;
&lt;td&gt;Human approval before actions that move money or change rights&lt;/td&gt;
&lt;td&gt;Approval records&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Action audit log&lt;/td&gt;
&lt;td&gt;GDPR Art. 5(2), 32; AI Act Art. 12 if high-risk&lt;/td&gt;
&lt;td&gt;Every tool call logged with input, output and actor&lt;/td&gt;
&lt;td&gt;Log with a set retention&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Minimization&lt;/td&gt;
&lt;td&gt;GDPR Art. 5(1)(c)&lt;/td&gt;
&lt;td&gt;PII redacted before the model call&lt;/td&gt;
&lt;td&gt;Redaction tests&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Retention timers&lt;/td&gt;
&lt;td&gt;GDPR Art. 5(1)(e), 13(2)(a)&lt;/td&gt;
&lt;td&gt;Auto-delete for transcripts, recordings, logs and chunks&lt;/td&gt;
&lt;td&gt;Retention configuration&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Region pinning&lt;/td&gt;
&lt;td&gt;GDPR Chapter V&lt;/td&gt;
&lt;td&gt;Model, storage and vector database in the chosen region&lt;/td&gt;
&lt;td&gt;Deployment configuration&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Model data settings&lt;/td&gt;
&lt;td&gt;GDPR Art. 28; provider terms&lt;/td&gt;
&lt;td&gt;No-training endpoints; zero retention where the provider offers and approves it&lt;/td&gt;
&lt;td&gt;Provider settings and agreement&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sub-processor register&lt;/td&gt;
&lt;td&gt;GDPR Art. 28(2) and (4)&lt;/td&gt;
&lt;td&gt;Every service that touches personal data listed&lt;/td&gt;
&lt;td&gt;DPA annex&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Transfer tools&lt;/td&gt;
&lt;td&gt;GDPR Art. 46; SCC Clause 14; UK IDTA or Addendum&lt;/td&gt;
&lt;td&gt;SCCs and assessment for access from Karachi&lt;/td&gt;
&lt;td&gt;Signed clauses and assessment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DPIA input&lt;/td&gt;
&lt;td&gt;GDPR Art. 35&lt;/td&gt;
&lt;td&gt;System description and data-flow diagram for your DPIA&lt;/td&gt;
&lt;td&gt;DPIA annex&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Evaluation set and kill switch&lt;/td&gt;
&lt;td&gt;GDPR Art. 32; AI Act Art. 14(4)(e) and 15 if high-risk&lt;/td&gt;
&lt;td&gt;Test set scored on every change; one switch to disable the agent or a tool&lt;/td&gt;
&lt;td&gt;Evaluation reports&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  When you don’t need to worry
&lt;/h2&gt;

&lt;p&gt;Most agent projects carry less regulatory work than the headlines suggest. The effort stays small when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Nobody in the EU uses the agent and its output isn’t used there.&lt;/strong&gt; The AI Act does not reach it (Article 2), and EU GDPR usually doesn’t either.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The agent is a support, booking or FAQ agent.&lt;/strong&gt; It is typically not high-risk. The work is disclosure, logging and a DPA, not a conformity assessment.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The agent processes no personal data.&lt;/strong&gt; An agent that reconciles supplier invoice totals raises few GDPR questions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The cases that need care are Annex III uses, agents that decide things about people, and health data or call recordings at scale.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to ask your development partner
&lt;/h2&gt;

&lt;p&gt;Five questions show whether a partner has thought about this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Who is the provider and who is the deployer, and where does the contract say so?&lt;/li&gt;
&lt;li&gt;Where does each component run, and which can be pinned to an EU region?&lt;/li&gt;
&lt;li&gt;Which sub-processors see our data, and with what retention and training settings?&lt;/li&gt;
&lt;li&gt;Will you sign our DPA, plus the SCCs or the UK IDTA or Addendum, and support our transfer assessment?&lt;/li&gt;
&lt;li&gt;How is the AI disclosure built and tested, and how do we switch the agent off?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Our answers: we can sign your DPA and the SCCs or UK transfer documents, deploy in an EU region on request, use endpoints that exclude training (zero retention where the provider offers it), and supply the system description and sub-processor list for your DPIA. For wider vendor questions, use our &lt;a href="https://apptycoons.com/blog/how-to-evaluate-ai-agent-development-company?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=eu-ai-act-gdpr-ai-agents" rel="noopener noreferrer"&gt;checklist for evaluating an AI agent development company&lt;/a&gt;. To map your own agent against the table above, &lt;a href="https://apptycoons.com/contact?interest=audit&amp;amp;service=ai-agent-development&amp;amp;utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=eu-ai-act-gdpr-ai-agents" rel="noopener noreferrer"&gt;book a free AI audit&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This guide summarizes the law as of October 18, 2026 and is not legal advice. Check your situation with counsel or your data protection officer.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://eur-lex.europa.eu/eli/reg/2026/1744/oj/eng" rel="noopener noreferrer"&gt;Regulation (EU) 2026/1744 (Digital Omnibus on AI)&lt;/a&gt;, EUR-Lex&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-14" rel="noopener noreferrer"&gt;Article 14: Human oversight&lt;/a&gt;, AI Act Service Desk, European Commission&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-50" rel="noopener noreferrer"&gt;Article 50: Transparency obligations for providers and deployers of certain AI systems&lt;/a&gt;, AI Act Service Desk, European Commission&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://ai-act-service-desk.ec.europa.eu/en/ai-act/faq/how-are-ai-agents-addressed-within-ai-act-0" rel="noopener noreferrer"&gt;How are AI agents addressed within the AI Act?&lt;/a&gt;, AI Act Service Desk, European Commission&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://digital-strategy.ec.europa.eu/en/faqs/transparency-obligations-under-article-50-ai-act" rel="noopener noreferrer"&gt;Transparency obligations under Article 50 of the AI Act&lt;/a&gt;, European Commission&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/new-standard-contractual-clauses-questions-and-answers-overview_en" rel="noopener noreferrer"&gt;New Standard Contractual Clauses - Questions and Answers overview&lt;/a&gt;, European Commission&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/appropriate-safeguards/what-are-standard-data-protection-clauses-the-uk-idta-and-the-addendum/" rel="noopener noreferrer"&gt;What are standard data protection clauses (the UK IDTA and the Addendum)?&lt;/a&gt;, ICO&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/eu-ai-act-gdpr-ai-agents?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=eu-ai-act-gdpr-ai-agents" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>gdpr</category>
      <category>llm</category>
      <category>security</category>
    </item>
    <item>
      <title>Build vs buy AI agents: a CTO decision framework</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Wed, 07 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/build-vs-buy-ai-agents-a-cto-decision-framework-5ghe</link>
      <guid>https://dev.to/apptycoons/build-vs-buy-ai-agents-a-cto-decision-framework-5ghe</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Buy when the agent does what every company’s agent does, volume is modest and the product already connects to your systems. Build when the workflow is your advantage, the data must stay under your control, or usage fees would outgrow a one-off build. Most teams end up buying the commodity layers and building the workflow on top.&lt;/p&gt;

&lt;p&gt;At 2,000 support outcomes a month, Intercom’s Fin costs about $71,000 over three years at its listed starting price, less than a custom agent. At 10,000 a month it costs about $356,000, roughly three times the custom option’s three-year cost in our model. Same job, same agent; volume alone flipped the answer.&lt;/p&gt;

&lt;p&gt;Product vendors will tell you building is slow and risky. Development shops, us included, will tell you buying locks you in. Both are sometimes right, so what follows is a way to decide for one specific agent, including the cases where the right answer is not to hire a studio like ours.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build vs buy AI agents: the short answer
&lt;/h2&gt;

&lt;p&gt;Buy when the agent does a job every company has, at a volume where per-use fees stay modest, and a product already works with your systems. Build when the agent’s workflow is part of how you win, when it must act inside your own systems, when your data must stay under your control, or when usage fees would outgrow a one-off build within a few years.&lt;/p&gt;

&lt;p&gt;Most companies end up in between. They buy the commodity layers, such as the models, telephony, vector search and observability tools, and build the workflow that is specific to them on top. The decision is less “build or buy” than “which layers do we own”.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three real options: buy, configure or build
&lt;/h2&gt;

&lt;p&gt;There are three ways to get an agent into production, and they differ in time to value, cost model and who owns the result.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Buy, configure or build&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Buy a product&lt;/th&gt;
&lt;th&gt;Configure a platform&lt;/th&gt;
&lt;th&gt;Build custom&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;What it is&lt;/td&gt;
&lt;td&gt;A finished agent for one job, such as a helpdesk’s AI agent&lt;/td&gt;
&lt;td&gt;An agent builder inside a suite you already use&lt;/td&gt;
&lt;td&gt;Your own code on model APIs, in your cloud&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Example pricing&lt;/td&gt;
&lt;td&gt;Intercom Fin from $0.99 per outcome&lt;/td&gt;
&lt;td&gt;Copilot Studio credit packs of 25,000 for $200 a month&lt;/td&gt;
&lt;td&gt;Our fixed-price builds, $25k–$120k&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Time to first value&lt;/td&gt;
&lt;td&gt;Days&lt;/td&gt;
&lt;td&gt;Weeks&lt;/td&gt;
&lt;td&gt;6–16 weeks after a two-week discovery&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cost model&lt;/td&gt;
&lt;td&gt;Per seat or per outcome, rises with volume&lt;/td&gt;
&lt;td&gt;Per credit or message, rises with volume&lt;/td&gt;
&lt;td&gt;Up-front build, then tokens and hosting&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Fit to your workflow&lt;/td&gt;
&lt;td&gt;The vendor’s workflow&lt;/td&gt;
&lt;td&gt;Within the suite’s connectors and limits&lt;/td&gt;
&lt;td&gt;Exactly yours&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who owns the code and IP&lt;/td&gt;
&lt;td&gt;The vendor&lt;/td&gt;
&lt;td&gt;The vendor; you own configuration&lt;/td&gt;
&lt;td&gt;You&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  A decision matrix for CTOs
&lt;/h2&gt;

&lt;p&gt;Answer these eight questions for the specific agent you are considering. If most answers fall in the “buy” column, buy. If most fall in “build”, build. If it is mixed, buy now and design for a later move.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Eight questions that decide build vs buy&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Question&lt;/th&gt;
&lt;th&gt;Points to buy&lt;/th&gt;
&lt;th&gt;Points to build&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Is the workflow a competitive advantage?&lt;/td&gt;
&lt;td&gt;No, everyone does it the same way&lt;/td&gt;
&lt;td&gt;Yes, how it works is why customers choose you&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Does it need to act inside your own systems?&lt;/td&gt;
&lt;td&gt;Only common SaaS tools with existing connectors&lt;/td&gt;
&lt;td&gt;Internal systems, custom APIs or several systems of record&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What volume do you expect in year three?&lt;/td&gt;
&lt;td&gt;Low or uncertain&lt;/td&gt;
&lt;td&gt;High and growing, so per-use fees compound&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Where must the data live?&lt;/td&gt;
&lt;td&gt;Vendor cloud is acceptable&lt;/td&gt;
&lt;td&gt;Your cloud, your region or no third-party retention&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How much control do you need over models?&lt;/td&gt;
&lt;td&gt;The vendor’s choice is fine&lt;/td&gt;
&lt;td&gt;You need to switch models or route by task&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Is the agent the product you sell?&lt;/td&gt;
&lt;td&gt;No, it is an internal efficiency tool&lt;/td&gt;
&lt;td&gt;Yes, it is part of what customers pay for&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who will run it after launch?&lt;/td&gt;
&lt;td&gt;Nobody has time to own it&lt;/td&gt;
&lt;td&gt;A named owner with budget for changes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How fast do you need it?&lt;/td&gt;
&lt;td&gt;This month&lt;/td&gt;
&lt;td&gt;This quarter, done properly&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Three-year total cost: a worked example
&lt;/h2&gt;

&lt;p&gt;The cost comparison flips with volume, so do the arithmetic for your own numbers rather than trusting a rule of thumb. Here is one worked example for a support agent that resolves customer questions.&lt;/p&gt;

&lt;p&gt;The bought option is Intercom’s Fin AI Agent at its listed starting price of $0.99 per outcome, rechecked on October 29, 2026. The custom option uses assumptions we state openly: a $25k–$120k build placed at $60,000 for a support agent with helpdesk and order-system integrations, $500 a month for hosting and monitoring, 20% of the build per year for maintenance and model updates, and model tokens at the rate in our &lt;a href="https://apptycoons.com/blog/ai-agent-development-cost" rel="noopener noreferrer"&gt;AI agent cost worked example&lt;/a&gt;: four Claude Haiku 5.5 calls per ticket with prompt caching, about $0.0018 a ticket at list prices checked October 29, 2026. Helpdesk seats are left out because you need them either way.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Three-year cost, support agent (list prices and stated assumptions)&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Outcomes a month&lt;/th&gt;
&lt;th&gt;Buy: $0.99 per outcome&lt;/th&gt;
&lt;th&gt;Build: $60k build plus run&lt;/th&gt;
&lt;th&gt;Cheaper option&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;2,000&lt;/td&gt;
&lt;td&gt;about $71,300&lt;/td&gt;
&lt;td&gt;about $114,100&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Buy&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10,000&lt;/td&gt;
&lt;td&gt;about $356,400&lt;/td&gt;
&lt;td&gt;about $114,600&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Build&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;How the build column adds up at 10,000 a month: $60,000 build, plus $18,000 hosting over 36 months, plus $36,000 maintenance over three years, plus about $640 in tokens. The tokens barely register; the build and the people who maintain it are the real cost. On these assumptions, the break-even is about 3,200 outcomes a month.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Where the build option’s three years go, at 10,000 outcomes a month&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Build: $60,000&lt;/li&gt;
&lt;li&gt;Maintenance, 3 years: $36,000&lt;/li&gt;
&lt;li&gt;Hosting, 36 months: $18,000&lt;/li&gt;
&lt;li&gt;Model tokens: about $640&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Stated assumptions above; total about $114,600. Tokens are the shortest bar.&lt;/p&gt;

&lt;p&gt;Three caveats keep this honest. A product like Fin includes things a custom build has to create, such as reporting and content management, and its per-outcome price can be higher than the starting price. Intercom also counts a handoff to a person as an outcome when Fin completes that workflow, so outcomes are not the same as fully resolved tickets. A custom build can cost more than $60,000 if it needs more integrations or compliance work. And a bought agent is live in days, which has value the table does not show. Change the assumptions and rerun it; the method matters more than our numbers. For a fuller breakdown of build and running costs, see &lt;a href="https://apptycoons.com/blog/ai-agent-development-cost" rel="noopener noreferrer"&gt;AI agent development cost&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Data, IP and lock-in: what to check before you sign
&lt;/h2&gt;

&lt;p&gt;Lock-in is rarely about the contract term. It is about whether your data, history and logic can leave with you. Before buying, check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;whether the vendor trains models on your data, and whether that can be switched off in writing,&lt;/li&gt;
&lt;li&gt;whether you can export conversation logs, knowledge sources and agent configuration in a usable format,&lt;/li&gt;
&lt;li&gt;where data is processed and stored, and for how long,&lt;/li&gt;
&lt;li&gt;whether you can choose or change the underlying model,&lt;/li&gt;
&lt;li&gt;and what happens to your history if you cancel.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you build, the equivalent questions are about ownership. Our builds put the code in your repository from day one and the IP is yours, but whoever builds for you, confirm both in the contract.&lt;/p&gt;

&lt;p&gt;Price the exit before you sign, too, because leaving a bought agent is a small project of its own. Expect to export conversation history and the knowledge base, map them into the next system, rebuild every integration the product handled for you, and rerun your evaluation cases to prove the replacement answers as well. None of that has a list price, so ask the vendor for a sample export on day one; a messy or partial export is the clearest sign of how much leaving will cost.&lt;/p&gt;

&lt;h2&gt;
  
  
  Governance and risk: why most failures are not about the model
&lt;/h2&gt;

&lt;p&gt;Agent projects stall more often because of how they are run than because of the model, and the build-or-buy choice decides who carries that risk. On the buy side, the risk is a product that demos well but cannot reach the systems or rules your cases depend on. On the build side, it is a team that has never shipped an agent learning on your budget.&lt;/p&gt;

&lt;p&gt;According to Fortune’s summary of MIT NANDA’s 2025 report on enterprise AI, tools bought from specialized vendors and builds done with partners succeeded about 67% of the time, and purely internal builds only a third as often. The lesson is not “never build”. It is that building from scratch in-house, without people who have shipped agents before, is the riskiest route. Whichever route you choose, insist on an evaluation set, approval steps for high-impact actions, an audit log, and a named owner after launch; our checklist of &lt;a href="https://apptycoons.com/blog/ai-agent-guardrails" rel="noopener noreferrer"&gt;agent guardrails&lt;/a&gt; lists ten controls to ask for on either route. We cover this in more depth in &lt;a href="https://apptycoons.com/blog/ai-pilots-to-production" rel="noopener noreferrer"&gt;why AI pilots stall before production&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  When buying is the better choice
&lt;/h2&gt;

&lt;p&gt;Buying is the right answer more often than development shops admit. Buy when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the use case is common, such as help-center answers, meeting notes or ticket summaries,&lt;/li&gt;
&lt;li&gt;a product already integrates with the tools you use, without custom work,&lt;/li&gt;
&lt;li&gt;your volume keeps per-use fees below what a build and its maintenance would cost,&lt;/li&gt;
&lt;li&gt;you need value this month and can accept the vendor’s workflow,&lt;/li&gt;
&lt;li&gt;or there is no one to own a custom agent once it ships.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In those cases, a custom build would cost more and arrive later, and you should not pay for one, from us or anyone else.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do general-purpose agents like Muse and Grok Bot count as buying?
&lt;/h2&gt;

&lt;p&gt;Yes, and for one kind of work they are the cheapest option there is. Meta’s Muse and xAI’s Grok Bot are general-purpose agents that sign in to the apps a person already uses and work through multi-step jobs. If the job belongs to one person or one small team and runs through common tools, try them before you buy anything narrower or build anything at all.&lt;/p&gt;

&lt;p&gt;What each one is, from the vendors’ own pages (checked October 12, 2026):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Muse&lt;/strong&gt; launched on September 8, 2026, rolling out in the US. Meta says it is free for most of what people need, with paid plans for more. It runs on its own cloud machine, people choose which apps it connects to and how much access it gets, and it checks with the user before sensitive actions such as sending an email or making a purchase.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Grok Bot&lt;/strong&gt; has been in beta since August 11, 2026, included with SuperGrok and paid Cursor plans, with its own usage on top. Bots share a cloud computer that belongs to the account, sign in across apps and websites, use connectors where they exist and operate the screen everywhere else, and come back when something needs approval. xAI says teams use them for sales outbound, marketing campaigns and office operations; Enterprise access is a waitlist.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The limits are those of any bought agent, plus a few more. The agent runs in the vendor’s cloud with your users’ logins. It follows the vendor’s approval model, not yours, and your evaluation cases and audit requirements don’t travel with it. Where it operates a screen instead of an API, a layout change can break the job. Enterprise controls are still arriving on both.&lt;/p&gt;

&lt;p&gt;So split the work by who carries the risk. An agent that drafts, researches or files on behalf of one person can be bought this way today. An agent that changes records, moves money or speaks to customers on the company’s behalf belongs in the build column of the matrix above. There is also a middle path: keep the workflow and its rules in your own systems, and let Muse, Grok Bot or Claude call them through an &lt;a href="https://apptycoons.com/blog/mcp-server-meta-muse-grok" rel="noopener noreferrer"&gt;MCP server for Muse and Grok&lt;/a&gt; that enforces your permissions.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Split the work by who carries the risk&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Buy a general-purpose agent&lt;/strong&gt; (Muse, Grok Bot)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Drafts, researches or files for one person&lt;/li&gt;
&lt;li&gt;Runs through common apps with your users’ logins&lt;/li&gt;
&lt;li&gt;Follows the vendor’s approval model&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Build&lt;/strong&gt; (your systems)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Changes records, moves money or speaks to customers&lt;/li&gt;
&lt;li&gt;Acts inside your own systems&lt;/li&gt;
&lt;li&gt;Follows your approval rules and audit trail&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When building wins
&lt;/h2&gt;

&lt;p&gt;Building wins when the agent is part of what makes your business different, or when no product can reach the systems it needs to act in. Two of our builds show both patterns.&lt;/p&gt;

&lt;p&gt;A commercial real estate platform we built is the first pattern: the agents are the product, and parallel agents turn a property address into a sourced report and a 10-year pro forma. No off-the-shelf agent does that, because that work is what the platform sells.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://apptycoons.com/work/superdeal" rel="noopener noreferrer"&gt;Superdeal&lt;/a&gt; is the second pattern. Its agent reads the platform’s own creator, deal and shipment records and works through the platform’s own approval step before anything is sent. A bought agent would sit outside that data and those approvals, which is where all of the agent’s value comes from.&lt;/p&gt;

&lt;h2&gt;
  
  
  The hybrid most teams end up with
&lt;/h2&gt;

&lt;p&gt;In practice, nearly every custom agent is part bought. Models come from Anthropic, OpenAI, Google or open-source providers; vector search, telephony and observability come from vendors. What you build is the layer that encodes your workflow: the tools the agent can call, the rules it follows, the approvals it needs and the evaluation set that proves it works. Owning that layer is what lets you switch models as prices fall, and move between vendors without starting again.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhrt2ouq054hgaucglbkb.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhrt2ouq054hgaucglbkb.webp" alt="Two stacked layers. Build: your workflow layer, with the tools the agent can call, the rules it follows, the approvals it needs and the evaluation set. Buy: commodity layers, with models, vector search, telephony and observability." width="800" height="569"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The layer you build is the one that encodes your workflow.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  AI agent vs chatbot vs RPA
&lt;/h2&gt;

&lt;p&gt;Part of the build-or-buy question is whether you need an agent at all. Sometimes a chatbot or an RPA script is enough, and both are cheaper.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Chatbot, RPA or AI agent&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Chatbot&lt;/th&gt;
&lt;th&gt;RPA&lt;/th&gt;
&lt;th&gt;AI agent&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;What it does&lt;/td&gt;
&lt;td&gt;Answers questions&lt;/td&gt;
&lt;td&gt;Repeats fixed steps in software&lt;/td&gt;
&lt;td&gt;Decides and acts within rules&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Handles variation&lt;/td&gt;
&lt;td&gt;In language only&lt;/td&gt;
&lt;td&gt;Poorly; breaks when screens change&lt;/td&gt;
&lt;td&gt;Yes, within guardrails&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Takes actions&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Yes, scripted&lt;/td&gt;
&lt;td&gt;Yes, with approvals&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Choose it when&lt;/td&gt;
&lt;td&gt;The job is answering&lt;/td&gt;
&lt;td&gt;Steps never change&lt;/td&gt;
&lt;td&gt;Inputs vary and judgment is needed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How to run a fair test before you decide
&lt;/h2&gt;

&lt;p&gt;You can test both routes cheaply before committing to either. Run the bought product on a slice of real traffic for two to four weeks, with its own reporting turned on, and record three numbers: how many cases it fully resolved, how many it got wrong, and how many it handed to a person. Then run the same cases through a custom prototype on your real data; our discovery sprint ends with one for $5,000.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;A fair test of both routes&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Run the bought product&lt;/strong&gt; (2–4 weeks): On a slice of real traffic, with its own reporting turned on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Record three numbers&lt;/strong&gt; (same weeks): Cases fully resolved, cases it got wrong, cases handed to a person.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run a custom prototype&lt;/strong&gt; (discovery): The same cases, on your real data.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compare on your evaluation cases&lt;/strong&gt; (decide): Not on a demo, and at a cost you can live with at year-three volume.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Compare the two on your evaluation cases, not on a demo. If the product resolves enough cases at a cost you can live with at year-three volume, buy it. If it stalls on the cases that matter most, such as those that need your internal systems or your rules, that gap is what a custom build is for. If you do go custom, the vetting questions are in &lt;a href="https://apptycoons.com/blog/how-to-evaluate-ai-agent-development-company" rel="noopener noreferrer"&gt;how to choose an AI agent development company&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The method is not specific to AI. We ran &lt;a href="https://apptycoons.com/blog/build-vs-buy-affiliate-tracking" rel="noopener noreferrer"&gt;the same decision for affiliate tracking&lt;/a&gt;, where SaaS plans that step up with tracked affiliate revenue play the part that per-outcome pricing plays here.&lt;/p&gt;

&lt;h2&gt;
  
  
  A build-vs-buy checklist
&lt;/h2&gt;

&lt;p&gt;Before you decide, write down answers to these, for this agent specifically:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The one business number the agent must move, and its current value.&lt;/li&gt;
&lt;li&gt;Expected volume in month one and in year three.&lt;/li&gt;
&lt;li&gt;Every system the agent must read from or write to.&lt;/li&gt;
&lt;li&gt;Where the data may be processed and stored.&lt;/li&gt;
&lt;li&gt;Which actions need a person’s approval.&lt;/li&gt;
&lt;li&gt;Who owns the agent after launch, and their budget for changes.&lt;/li&gt;
&lt;li&gt;The three-year cost of buying at year-three volume, and of building.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If the checklist points to buying, buy. If it points to building, our &lt;a href="https://apptycoons.com/services/ai-agent-development" rel="noopener noreferrer"&gt;AI agent development&lt;/a&gt; team fixes the price after a two-week discovery sprint, and the first conversation is a free AI audit that covers this decision, including when the answer is to buy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://fortune.com/2025/08/18/mit-report-95-percent-generative-ai-pilots-at-companies-failing-cfo/" rel="noopener noreferrer"&gt;MIT report: 95% of generative AI pilots at companies are failing&lt;/a&gt;, Fortune&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.intercom.com/pricing" rel="noopener noreferrer"&gt;Intercom pricing (Fin AI Agent)&lt;/a&gt;, Intercom&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.microsoft.com/en-us/microsoft-copilot/microsoft-copilot-studio" rel="noopener noreferrer"&gt;Microsoft Copilot Studio pricing&lt;/a&gt;, Microsoft&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://platform.claude.com/docs/en/about-claude/pricing" rel="noopener noreferrer"&gt;Claude API pricing&lt;/a&gt;, Anthropic&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/" rel="noopener noreferrer"&gt;Introducing Muse: The World’s First Personal AI Agent Built for Everyone&lt;/a&gt;, Meta&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://x.ai/news/introducing-grok-bot" rel="noopener noreferrer"&gt;Introducing Grok Bot&lt;/a&gt;, xAI&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/build-vs-buy-ai-agents" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>startup</category>
      <category>productivity</category>
    </item>
    <item>
      <title>MLM software cost in 2026: what to build, what to buy and what breaks at scale</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Fri, 02 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/mlm-software-cost-in-2026-what-to-build-what-to-buy-and-what-breaks-at-scale-1lm0</link>
      <guid>https://dev.to/apptycoons/mlm-software-cost-in-2026-what-to-build-what-to-buy-and-what-breaks-at-scale-1lm0</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Buy an MLM platform when your compensation plan is conventional and speed to launch matters most. Build custom MLM software when the plan, the payouts or the member experience are your edge: hybrid plans, near real-time commissions, built-in wallets and cards, or bundled services. Many companies combine both, keeping a platform engine and building custom apps and payouts.&lt;/p&gt;

&lt;p&gt;Most direct-selling companies start on an off-the-shelf MLM platform. It works until the compensation plan changes, the distributor count passes a few thousand, or the mobile experience starts costing you recruits.&lt;/p&gt;

&lt;p&gt;What breaks after that is predictable, and most of it can be designed out before it costs you a payout run.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where off-the-shelf platforms struggle
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Hybrid compensation plans that mix binary, unilevel and matrix rules.&lt;/li&gt;
&lt;li&gt;Commission runs that take hours and need manual fixes.&lt;/li&gt;
&lt;li&gt;Dated distributor apps that new recruits abandon.&lt;/li&gt;
&lt;li&gt;Payouts that can’t reach modern wallets or cards.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of these is a flaw in the platforms themselves. They are built to run the plans most companies use, and they do that well. The friction starts when your plan, your payout model or your member experience is the thing that sets you apart, and every change has to wait for a vendor roadmap or a paid customization.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build, buy or combine?
&lt;/h2&gt;

&lt;p&gt;Buy when your compensation plan is conventional and launching quickly matters more than differentiation. Established platforms come with commission engines that are already in use at other companies, plus replicated sites, e-commerce and reporting. They are not cheap: the software directory Capterra lists Exigo, one of the best-known enterprise platforms, from $5,000 per month, flat rate. But they are proven.&lt;/p&gt;

&lt;p&gt;Build when the software is part of the product:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Your plan mixes structures in ways the platform can only approximate.&lt;/li&gt;
&lt;li&gt;Distributors need near real-time earnings, not a nightly or weekly run.&lt;/li&gt;
&lt;li&gt;Earnings should land in a wallet or on a card, not only a bank transfer.&lt;/li&gt;
&lt;li&gt;You sell bundled services, such as subscriptions or financial products, that the platform does not model.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Buy a platform or build custom MLM software&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Buy a platform&lt;/strong&gt;: Conventional plan&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Commission engine already in use at other companies&lt;/li&gt;
&lt;li&gt;Replicated sites, e-commerce and reporting included&lt;/li&gt;
&lt;li&gt;Changes wait for a vendor roadmap or paid customization&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;vs&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Build custom&lt;/strong&gt;: Software is the product&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Hybrid plans a platform can only approximate&lt;/li&gt;
&lt;li&gt;Near real-time earnings, not a nightly or weekly run&lt;/li&gt;
&lt;li&gt;Earnings land in a wallet or on a card&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Combine the two when only part of the stack is the differentiator. A common pattern keeps a platform for orders and the commission run, and builds custom distributor apps, onboarding and payouts around it. We compare the main options, and how to migrate between them, in &lt;a href="https://apptycoons.com/blog/exigo-alternatives?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=mlm-software-guide" rel="noopener noreferrer"&gt;Exigo alternatives: when custom MLM software wins&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What MLM software costs in 2026
&lt;/h2&gt;

&lt;p&gt;MLM software costs either a recurring platform fee or a one-off build plus running costs, and the two are hard to compare until your plan is written down. On the platform side, the software directory Capterra lists Exigo from $5,000 per month, flat rate; most enterprise vendors don’t publish prices at all. Packaged MLM scripts are cheaper to start with, and what they buy you is a set of templates: the further your plan sits from them, the more of the saving goes on customization.&lt;/p&gt;

&lt;p&gt;On the custom side, our model is a two-week Discovery Sprint ($5,000, credited to the build) that turns your compensation plan into written rules, then one fixed price inside our $25k–$120k range, delivered in 6–16 weeks. Where an MLM build lands in that band depends on four things. The placements below are our judgment, not client budgets:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;What moves an MLM build within our fixed-price band&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Driver&lt;/th&gt;
&lt;th&gt;Toward the lower end&lt;/th&gt;
&lt;th&gt;Toward the upper end&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Compensation plan&lt;/td&gt;
&lt;td&gt;One structure (binary or unilevel) with a few ranks&lt;/td&gt;
&lt;td&gt;Hybrid plan with compression, matching bonuses, caps and qualification windows&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Payouts&lt;/td&gt;
&lt;td&gt;Bank transfer through one payout provider&lt;/td&gt;
&lt;td&gt;In-app wallets, debit cards or stablecoins, several currencies&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Apps&lt;/td&gt;
&lt;td&gt;Web back office and enrollment funnel&lt;/td&gt;
&lt;td&gt;Web back office plus iOS and Android distributor apps&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Migration&lt;/td&gt;
&lt;td&gt;New company, no history&lt;/td&gt;
&lt;td&gt;Years of genealogy and commission history, re-run in a parallel cycle&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Add the time for at least one commission cycle run in parallel with your old system before payouts switch. That cycle sets the go-live date more often than the code does. For a three-year view of platform fees against a custom build, use the exit and pricing questions in our Exigo guide above.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compensation plan types your engine must handle
&lt;/h2&gt;

&lt;p&gt;The compensation plan decides how much of the engine is hard. These are the structures most plans combine:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Binary: each distributor has two legs, and commissions usually pay on the volume of the weaker leg, with carry-forward rules for the stronger one.&lt;/li&gt;
&lt;li&gt;Unilevel: unlimited frontline recruits, with commissions paid on a set number of levels below each distributor.&lt;/li&gt;
&lt;li&gt;Matrix: a fixed width and depth, so new recruits beyond the width spill over to lower levels.&lt;/li&gt;
&lt;li&gt;Stair-step and breakaway: ranks raise the commission percentage, and leaders who reach a rank break away into their own group with an override.&lt;/li&gt;
&lt;li&gt;Hybrid: any mix of the above, plus fast-start, matching and leadership bonuses.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi9963qmpltklh1i9d97o.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi9963qmpltklh1i9d97o.webp" alt="Three plan structures: binary, where each distributor has two legs and commissions pay on the weaker leg; unilevel, with unlimited frontline recruits paid a set number of levels deep; matrix, with a fixed width so extra recruits spill over to a lower level" width="800" height="531"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;A hybrid plan mixes these structures and adds bonuses on top.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Around the structure sit the rules that cause most commission errors: rank qualification windows, compression when inactive distributors are skipped, caps, breakage, and how returns and refunds claw back commissions already paid.&lt;/p&gt;

&lt;h2&gt;
  
  
  A worked binary commission example
&lt;/h2&gt;

&lt;p&gt;A binary payout is simple arithmetic repeated across thousands of people, which is why small rule ambiguities turn into large payout errors. Here is one distributor over two weeks under a common binary rule: 10% of the weaker leg’s volume, the stronger leg’s unused volume carried forward, and a weekly cap of 100. These are illustrative numbers, not a client plan.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Binary commission over two periods (illustrative)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Period&lt;/th&gt;
&lt;th&gt;Left leg (new + carried)&lt;/th&gt;
&lt;th&gt;Right leg (new + carried)&lt;/th&gt;
&lt;th&gt;Weaker leg&lt;/th&gt;
&lt;th&gt;Commission at 10%&lt;/th&gt;
&lt;th&gt;Carried forward&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Week 1&lt;/td&gt;
&lt;td&gt;1,200 + 0&lt;/td&gt;
&lt;td&gt;700 + 0&lt;/td&gt;
&lt;td&gt;700&lt;/td&gt;
&lt;td&gt;70&lt;/td&gt;
&lt;td&gt;500 left&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Week 2&lt;/td&gt;
&lt;td&gt;300 + 500&lt;/td&gt;
&lt;td&gt;1,400 + 0&lt;/td&gt;
&lt;td&gt;800&lt;/td&gt;
&lt;td&gt;80&lt;/td&gt;
&lt;td&gt;600 right&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The table looks settled until the questions start, and each one is a rule your engine has to store:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Refunds.&lt;/strong&gt; If a 200-point order in the left leg is refunded in week 2, is week 1 recalculated and the difference clawed back, or is the refund deducted from week 2’s left leg?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The cap.&lt;/strong&gt; If week 2 had paid 130, does the 30 above the cap disappear, or carry forward as volume?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flush.&lt;/strong&gt; Many plans reset carried volume when a distributor misses a qualification, so the 600 points on the right may be worth nothing next week.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compression.&lt;/strong&gt; In the unilevel part of a hybrid plan, if a distributor two levels down is inactive, the next active distributor below moves up a level for that period, which changes who earns on whose volume.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Write the answer to each question into the plan document before anyone builds, and keep a test period like this one for every rule. When the engine and the document disagree, the document wins, and the test tells you which code to change.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a custom platform should include
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A rules-driven compensation engine you can change without a rewrite.&lt;/li&gt;
&lt;li&gt;Genealogy, ranks and bonuses calculated in near real time.&lt;/li&gt;
&lt;li&gt;E-wallets and debit cards so earnings are spendable immediately.&lt;/li&gt;
&lt;li&gt;A distributor app that makes enrollment and team tracking effortless.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Add an admin back office with commission previews, adjustments and an audit trail, an enrollment funnel that works on a phone, and reporting that finance and compliance can both use.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to design a commission engine that doesn’t break at scale
&lt;/h2&gt;

&lt;p&gt;Commission engines rarely fail on day one. They fail when the plan changes, a period has to be re-run, or the genealogy grows deep. Five design choices prevent most of that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Store the plan as versioned rules, not code, so each period is calculated with the rules that applied at the time.&lt;/li&gt;
&lt;li&gt;Make every run deterministic and repeatable: the same inputs always produce the same payout, so a corrected period can be re-run safely.&lt;/li&gt;
&lt;li&gt;Record every commission as a ledger entry with its source order and rule, so any distributor’s statement can be explained line by line. Affiliate programs need the same ledger, which is why the trade-offs in &lt;a href="https://apptycoons.com/blog/build-vs-buy-affiliate-tracking?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=mlm-software-guide" rel="noopener noreferrer"&gt;affiliate commission tracking: build vs buy&lt;/a&gt; carry over almost unchanged.&lt;/li&gt;
&lt;li&gt;Treat returns and clawbacks as first-class events, not manual adjustments.&lt;/li&gt;
&lt;li&gt;Preview runs before they pay out, and test with synthetic genealogies far larger than today’s network.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;One commission run, built to be re-run safely&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Versioned rules&lt;/strong&gt;: The plan as it applied that period&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deterministic run&lt;/strong&gt;: Same inputs, same payout&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ledger entries&lt;/strong&gt;: Source order and rule on every line&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Preview&lt;/strong&gt;: Checked before anything pays out&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Payout&lt;/strong&gt;: Statements explained line by line&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What breaks at 100,000 distributors
&lt;/h2&gt;

&lt;p&gt;Scale problems in MLM software are predictable, which means they can be designed out. The usual pressure points are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Deep genealogy queries: calculating volume across many levels gets slow if every query walks the tree from scratch, so store precomputed paths or closures and update them as the network changes.&lt;/li&gt;
&lt;li&gt;Period close: thousands of distributors check their earnings at the same moment the commission run finishes, so statements should be generated ahead and served from a cache.&lt;/li&gt;
&lt;li&gt;Event spikes: enrollment surges during launches and conventions, so the sign-up flow and payment provider must handle bursts without double-charging or losing a placement.&lt;/li&gt;
&lt;li&gt;Mobile performance: team views with thousands of members need pagination and search, not one long list.&lt;/li&gt;
&lt;li&gt;Support load: when an earning looks wrong, support staff need the same line-by-line explanation the ledger gives finance.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Test each of these with synthetic data well above your current size before a launch event, not after.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compliance is part of the software
&lt;/h2&gt;

&lt;p&gt;Compliance in direct selling is mostly about evidence, and the evidence lives in your software. The FTC’s business guidance on multi-level marketing focuses on whether rewards come from sales to real customers rather than recruitment, looks at how the company operates in practice rather than what its policies say, and requires earnings claims to be truthful, substantiated and typical of what participants earn.&lt;/p&gt;

&lt;p&gt;That translates into concrete features: tracking retail customers separately from distributor purchases, reporting personal consumption, producing earnings data for income disclosures from real payouts, and keeping marketing claims in the app consistent with that data. This is not legal advice, and your counsel should define the rules; the point is to build the platform so it can prove them.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Your compensation plan is your product. The software should bend to it — not the other way around.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Payouts: wallets, cards and bundled services
&lt;/h2&gt;

&lt;p&gt;For Freedom Pro, we combined a partner back office with Bridge-powered USD and stablecoin wallets and debit cards, so partners earn and spend in one place.&lt;/p&gt;

&lt;p&gt;Its wireless, streaming, wellness and finance services sit behind one member account, and partners enroll customers, track their team and get paid from a single dashboard. The full build is in the &lt;a href="https://apptycoons.com/work/freedom-pro?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=mlm-software-guide" rel="noopener noreferrer"&gt;Freedom Pro case study&lt;/a&gt;, and the wallet side is covered in &lt;a href="https://apptycoons.com/blog/stablecoin-wallets-fintech?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=mlm-software-guide" rel="noopener noreferrer"&gt;how stablecoin wallets fit into an app&lt;/a&gt;. Whatever the rail, distributors judge payouts by their statements: a schedule they can predict and a line for every amount, the same &lt;a href="https://apptycoons.com/blog/creator-platform-revenue-share?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=mlm-software-guide" rel="noopener noreferrer"&gt;payout schedules and statements&lt;/a&gt; problem creator platforms face.&lt;/p&gt;

&lt;h2&gt;
  
  
  Moving off a platform without breaking commissions
&lt;/h2&gt;

&lt;p&gt;If you are migrating, run both systems in parallel. Move distributors, genealogy and commission history first, recalculate past periods in the new engine, and switch payouts only when both produce the same numbers. Distributors forgive a new app; they do not forgive a wrong commission. The Exigo guide linked above has a step-by-step version of this plan, from exit terms to cut-over.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Moving off a platform in four steps&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Move the data&lt;/strong&gt;: Distributors, genealogy and commission history.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recalculate past periods&lt;/strong&gt;: Re-run them in the new engine.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run both systems in parallel&lt;/strong&gt;: For at least one full commission cycle.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Switch payouts&lt;/strong&gt;: Only when both systems produce the same numbers.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you are weighing a custom build, our &lt;a href="https://apptycoons.com/industries/mlm?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=mlm-software-guide" rel="noopener noreferrer"&gt;MLM software development&lt;/a&gt; work starts with your compensation plan and payout model, and you can see how we price discovery and fixed-price builds on our &lt;a href="https://apptycoons.com/pricing?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=mlm-software-guide" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://www.ftc.gov/business-guidance/resources/business-guidance-concerning-multi-level-marketing" rel="noopener noreferrer"&gt;Business Guidance Concerning Multi-Level Marketing&lt;/a&gt;, Federal Trade Commission&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://capterra.com/p/181321/Exigo/" rel="noopener noreferrer"&gt;Exigo pricing and profile&lt;/a&gt;, Capterra&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/mlm-software-guide?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=mlm-software-guide" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>startup</category>
      <category>fintech</category>
      <category>architecture</category>
    </item>
    <item>
      <title>Stablecoin wallet API and infrastructure: how to add stablecoin wallets to your app</title>
      <dc:creator>Apptycoons</dc:creator>
      <pubDate>Wed, 30 Sep 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/apptycoons/stablecoin-wallet-integration-how-to-add-stablecoin-wallets-to-your-app-in-2026-228g</link>
      <guid>https://dev.to/apptycoons/stablecoin-wallet-integration-how-to-add-stablecoin-wallets-to-your-app-in-2026-228g</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; A stablecoin wallet API lets your app create a wallet per customer, move dollars in and out of a stablecoin and read balances while a regulated provider holds the funds. The fastest route is that provider’s hosted KYC and custodial wallets, one transfer type, cards second, and your own ledger mirroring every provider event.&lt;/p&gt;

&lt;p&gt;A stablecoin wallet API lets your app open a wallet for each customer, move dollars in and out of a dollar stablecoin, and show balances, while a regulated provider holds the funds and runs the regulated steps. Your app owns the screens, the ledger and the support tools.&lt;/p&gt;

&lt;p&gt;That is how Freedom Pro works. A member signs up, picks the services they already pay for, and earns on their team’s activity. The earnings land in a USD or stablecoin wallet, and a debit card spends them. Nobody in that flow has to know what a blockchain is. Behind it sit a stablecoin provider’s API, a ledger we built, and a lot of decisions about who holds the money. This guide takes those decisions in the order a product team meets them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fastest way to add stablecoin wallets to an existing app
&lt;/h2&gt;

&lt;p&gt;The fastest way is to let a regulated orchestration provider hold the funds and run the regulated steps, while your app owns onboarding screens, the ledger and the interface. You integrate through its API instead of holding crypto yourself.&lt;/p&gt;

&lt;p&gt;A first release that ships quickly usually looks like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Hosted identity checks.&lt;/strong&gt; Use the provider’s hosted KYC flow at first. Building your own document capture can wait.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Custodial wallets.&lt;/strong&gt; The provider creates and holds a wallet per customer. You never touch private keys.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One transfer type.&lt;/strong&gt; For example, bank dollars in through a virtual account and converted to a dollar stablecoin. Add withdrawals and wallet-to-wallet sends after the first one is reconciled daily without surprises.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cards second.&lt;/strong&gt; A card program adds lifecycle states, disputes and spend controls. Launch it once balances are trusted.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Bridge’s documentation shows how much of this one provider can cover: virtual accounts that accept USD, EUR, GBP, MXN and more, each with a unique account and routing number; orchestration APIs for on-ramps, off-ramps and crypto-to-crypto transfers; custodial wallets; cards backed by stablecoins; and issuance of your own stablecoin.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a stablecoin wallet API does
&lt;/h2&gt;

&lt;p&gt;A stablecoin wallet API is a set of calls and webhooks for five jobs: create a customer, verify them, open a wallet, move money, and report every change of state back to you. Reading balances and history is the easy part; moving money safely is where integrations differ.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The five jobs of a stablecoin wallet API&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Job&lt;/th&gt;
&lt;th&gt;Typical calls&lt;/th&gt;
&lt;th&gt;What your app keeps&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Customers&lt;/td&gt;
&lt;td&gt;Create customer, attach identity data&lt;/td&gt;
&lt;td&gt;Your user ID beside the provider’s customer ID&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Identity checks&lt;/td&gt;
&lt;td&gt;Start hosted or API KYC, receive the result by webhook&lt;/td&gt;
&lt;td&gt;Status and limits per customer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Wallets and accounts&lt;/td&gt;
&lt;td&gt;Create wallet, create virtual bank account, list balances&lt;/td&gt;
&lt;td&gt;Wallet and account IDs, chain and coin per wallet&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Transfers&lt;/td&gt;
&lt;td&gt;Deposit, convert, withdraw, send, with an idempotency key&lt;/td&gt;
&lt;td&gt;A pending ledger entry per request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Events&lt;/td&gt;
&lt;td&gt;Webhooks for every state change&lt;/td&gt;
&lt;td&gt;An append-only ledger entry per event&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Under the calls, the provider decides two things you can’t easily change later: who holds the keys, and whether each customer gets their own on-chain wallet. Circle’s wallet products show both choices. Its developer-controlled wallets “sign transactions and custody funds for internal operations or on behalf of end users”, and its user-controlled wallets let end users “sign transactions directly and maintain control over their funds”. Either type can be a plain externally owned account (EOA) or a smart contract account, which allows features such as sponsored network fees.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stablecoin wallet providers: four kinds of infrastructure
&lt;/h2&gt;

&lt;p&gt;Stablecoin infrastructure comes in four broad kinds, and the kind you pick decides who holds keys, how much you build and how much regulatory weight lands on you. Vendor lists mix them together, so separate them before you compare prices. The examples below come from &lt;a href="https://docs.stripe.com/stablecoins" rel="noopener noreferrer"&gt;Stripe’s stablecoin docs&lt;/a&gt;, Bridge’s and Circle’s; we name them to show the kinds, not to rank them, and we have shipped on Bridge.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Stablecoin wallet infrastructure by kind (examples from each vendor’s own docs, checked November 3, 2026)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Kind&lt;/th&gt;
&lt;th&gt;Who holds keys and funds&lt;/th&gt;
&lt;th&gt;What you build&lt;/th&gt;
&lt;th&gt;Regulatory weight on you&lt;/th&gt;
&lt;th&gt;Example in vendor docs&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Custodial orchestration&lt;/td&gt;
&lt;td&gt;The provider, in custodial wallets per customer&lt;/td&gt;
&lt;td&gt;Onboarding UI, ledger, transfer screens, support tools&lt;/td&gt;
&lt;td&gt;Lower: the provider runs custody and the regulated flows&lt;/td&gt;
&lt;td&gt;Bridge: virtual accounts, orchestration APIs, custodial wallets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Embedded user wallets&lt;/td&gt;
&lt;td&gt;The user or your app, depending on how the wallet is set up&lt;/td&gt;
&lt;td&gt;Wallet UX, recovery, transaction signing, on- and off-ramps&lt;/td&gt;
&lt;td&gt;Depends on whether you ever control user funds&lt;/td&gt;
&lt;td&gt;Privy, listed in Stripe’s docs to “create and manage crypto and stablecoin wallets for users, businesses, and agents”; Circle’s developer- and user-controlled wallets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Platform balances and cards&lt;/td&gt;
&lt;td&gt;The platform provider, on your business account&lt;/td&gt;
&lt;td&gt;Treasury flows, payouts, card controls&lt;/td&gt;
&lt;td&gt;Lower, but tied to that provider’s program rules&lt;/td&gt;
&lt;td&gt;Stripe: stablecoin balances, payouts to third parties in more than 160 countries, stablecoin-backed cards&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Issuance&lt;/td&gt;
&lt;td&gt;You, as the brand behind a coin, through an issuer partner&lt;/td&gt;
&lt;td&gt;Treasury, mint and burn operations, distribution&lt;/td&gt;
&lt;td&gt;Highest: issuer rules apply&lt;/td&gt;
&lt;td&gt;Bridge issuance API to “issue your own stablecoin”&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Most fintech and platform products start in the first row. Embedded wallets fit crypto-native users, or teams that want to own more of the stack. Issuance is a business decision about becoming a stablecoin brand, not a wallet feature, and under the GENIUS Act it brings issuer-level rules.&lt;/p&gt;

&lt;h2&gt;
  
  
  Custodial or non-custodial: who holds the keys decides your obligations
&lt;/h2&gt;

&lt;p&gt;Whoever can move the funds carries the obligations, so decide custody before you design screens. In a custodial model the provider holds the keys; in a non-custodial model the user does, and your app helps them sign.&lt;/p&gt;

&lt;p&gt;The OCC’s final GENIUS Act rule shows how regulators think about it. As summarized by WilmerHale, the rule’s exclusion for companies that provide wallet hardware or software now applies only where the company “neither controls nor holds itself out as controlling” the customer’s assets. That is a useful test for your own design: if your servers can move a user’s balance without them, or your marketing implies you hold the money, assume you are in a custody conversation, and take it to counsel.&lt;/p&gt;

&lt;p&gt;For consumer products, custodial wallets with a regulated provider are the practical default. Users get password resets and support. You get a partner that runs sanctions screening and can freeze an account when asked.&lt;/p&gt;

&lt;p&gt;A second choice sits inside custodial: omnibus or segregated. In an omnibus setup many customers’ funds share one provider wallet and your ledger is the only record of who owns what. With segregated wallets each customer has their own, so the provider’s records already split balances by customer, which makes reconciliation, support and audits simpler. Omnibus puts all of that weight on your ledger. Ask which model a provider uses before you design the ledger.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Who holds the keys&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Custodial&lt;/strong&gt;: Consumer default&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The provider holds the keys&lt;/li&gt;
&lt;li&gt;Users get password resets and support&lt;/li&gt;
&lt;li&gt;The provider runs sanctions screening and can freeze an account&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;vs&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Non-custodial&lt;/strong&gt;: Crypto-native users&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The user holds the keys&lt;/li&gt;
&lt;li&gt;Your app helps them sign&lt;/li&gt;
&lt;li&gt;Suits users who want to hold their own keys&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How a stablecoin wallet integration works, step by step
&lt;/h2&gt;

&lt;p&gt;An integration is a sequence of provider objects and events that your ledger mirrors one for one. The exact names vary by provider; the shape is the same:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Create the customer&lt;/strong&gt; in the provider with your own user ID stored beside the provider’s ID.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run identity checks,&lt;/strong&gt; hosted or through the API, and listen for the result by webhook.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open the money objects:&lt;/strong&gt; a wallet, a virtual account for bank deposits, or both.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Move money&lt;/strong&gt; with a transfer request: deposit, conversion, withdrawal or send.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Receive webhooks&lt;/strong&gt; for every state change and write each one to your ledger.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reconcile&lt;/strong&gt; your balances against the provider’s records on a schedule.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Issue a card&lt;/strong&gt; on the balance, once the steps above run cleanly.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnqhqd1do01fm7a9dkrq6.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnqhqd1do01fm7a9dkrq6.webp" alt="Your app sends a transfer request with an idempotency key to the provider, which holds funds. The provider sends a webhook for every state change to your append-only ledger. The ledger is reconciled against the provider daily, with an alert on any difference, and your screens show what the ledger confirms." width="800" height="649"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The shape is the same whatever the provider calls its objects.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Each object moves through states, and each state needs its own screen copy. These are the ones a first release has to handle:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;States a stablecoin wallet app must handle&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Object&lt;/th&gt;
&lt;th&gt;State&lt;/th&gt;
&lt;th&gt;What the user sees&lt;/th&gt;
&lt;th&gt;What your system does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Customer&lt;/td&gt;
&lt;td&gt;Approved&lt;/td&gt;
&lt;td&gt;Full access&lt;/td&gt;
&lt;td&gt;Open wallet and virtual account&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Customer&lt;/td&gt;
&lt;td&gt;Pending review&lt;/td&gt;
&lt;td&gt;“We’re checking your details”, with a time estimate&lt;/td&gt;
&lt;td&gt;Block money movement, poll or wait for webhook&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Customer&lt;/td&gt;
&lt;td&gt;Rejected&lt;/td&gt;
&lt;td&gt;A plain reason and a support route&lt;/td&gt;
&lt;td&gt;No wallet; keep the record for audit&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Customer&lt;/td&gt;
&lt;td&gt;Limited&lt;/td&gt;
&lt;td&gt;Which limit applies&lt;/td&gt;
&lt;td&gt;Enforce the limit server-side on every request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Transfer&lt;/td&gt;
&lt;td&gt;Pending&lt;/td&gt;
&lt;td&gt;Amount, destination, “in progress”&lt;/td&gt;
&lt;td&gt;Reserve the amount in your ledger&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Transfer&lt;/td&gt;
&lt;td&gt;Completed&lt;/td&gt;
&lt;td&gt;Receipt with reference&lt;/td&gt;
&lt;td&gt;Post the final entry, release the reserve&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Transfer&lt;/td&gt;
&lt;td&gt;Failed or returned&lt;/td&gt;
&lt;td&gt;What happened and what to do next&lt;/td&gt;
&lt;td&gt;Reverse with a new ledger entry, never an edit&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;For retries, Bridge’s API reference requires an &lt;code&gt;Idempotency-Key&lt;/code&gt; header on every POST request and says not to send one with GET, PUT, PATCH or DELETE. The key holds for 24 hours after the first request, a retry must send the identical request body, and reusing the key after the 24 hours returns a 422 error.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Watch out: Retries are where wallets pay twice&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Generate the key once per user intent, store it with the pending transfer, reuse it on every retry inside the window, and treat a retry after the window as a new transfer that needs a fresh check of the user’s balance.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Ledger rules that prevent wrong balances
&lt;/h2&gt;

&lt;p&gt;Most bugs in wallet products are ledger bugs, not interface bugs. Your ledger is the record your support team, your finance team and your users read, and the provider’s records are what it must match.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Store both IDs.&lt;/strong&gt; Every customer, wallet, destination and transfer carries your ID and the provider’s ID side by side, so support can search either.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Append, never edit.&lt;/strong&gt; A reversal or a fee is a new entry linked to the original one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Let webhooks drive state.&lt;/strong&gt; Your app requests; the provider’s events confirm. A screen never shows “completed” on the strength of an API response alone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Replay safely.&lt;/strong&gt; Webhooks arrive twice and out of order. Process them by event ID, idempotently.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reconcile daily, alert on any difference.&lt;/strong&gt; A wallet that shows “pending” honestly loses less trust than one that shows a wrong balance for a few minutes.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What the GENIUS Act final rule means for a product team
&lt;/h2&gt;

&lt;p&gt;The GENIUS Act is the US federal law for payment stablecoins, and it takes effect on January 18, 2027. It was signed on July 18, 2025, and the OCC issued its final implementing rule on October 21, 2026 (&lt;a href="https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-50.html" rel="noopener noreferrer"&gt;OCC Bulletin 2026-50&lt;/a&gt;), effective the same day as the Act.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;GENIUS Act dates (checked November 3, 2026)&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Signed into law&lt;/strong&gt; (Jul 18, 2025)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OCC proposes its rules&lt;/strong&gt; (Feb 25, 2026): New 12 CFR Part 15.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Statutory deadline passes&lt;/strong&gt; (Jul 18, 2026): No final rules yet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OCC final rule issued&lt;/strong&gt; (Oct 21, 2026): Bulletin 2026-50.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Takes effect&lt;/strong&gt; (Jan 18, 2027): The Act and the OCC rule, with no transition period.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The OCC rule covers national banks, federal savings associations, federal branches, foreign issuers and nonbank issuers under OCC supervision. What changed from the proposal, as summarized by &lt;a href="https://www.wilmerhale.com/en/insights/client-alerts/20261027-occ-finalizes-genius-act-rule-for-permitted-payment-stablecoin-issuers-easing-several-key-proposed-requirements-and-raising-new-issues" rel="noopener noreferrer"&gt;WilmerHale&lt;/a&gt; on October 27, 2026:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Yield.&lt;/strong&gt; The ban on issuers paying holders interest or yield stays, now worded as in the Act. The OCC dropped the proposed presumption that certain arrangements violate it, and keeps anti-evasion authority through application review and supervision.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Redemption.&lt;/strong&gt; Issuers keep a two-business-day limit. The proposal’s automatic extension when requests pass 10% of outstanding value in 24 hours is gone; the issuer notifies the OCC and may ask for one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Custody.&lt;/strong&gt; Wallet hardware and software providers are excluded only if they neither control nor hold themselves out as controlling customer assets, and covered custodians must record customer assets separately.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Three product decisions follow. Pick coins and providers that will operate as permitted issuers or work with them, and ask what their plan is for January 18, 2027. Run every “rewards on your balance” idea past counsel before design: the presumption is gone, the ban and the OCC’s anti-evasion powers are not. And keep identity and sanctions checks strict, because for your provider they are a legal obligation. Other agencies’ rules, including AML standards and rules for state issuers, follow their own schedules; check them with counsel before launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Serving EU users: MiCA and which stablecoin you offer
&lt;/h2&gt;

&lt;p&gt;In the EU the coin itself has to fit MiCA, so the stablecoin you offer may differ by market. MiCA treats dollar and euro stablecoins as e-money tokens, and on January 17, 2025 ESMA and the European Commission said national regulators should make sure crypto-asset service providers stop offering non-compliant tokens as soon as possible, and no later than the end of the first quarter of 2025.&lt;/p&gt;

&lt;p&gt;Circle says it holds an e-money institution license from France’s ACPR and that USDC and EURC are issued in the EU in compliance with MiCA (&lt;a href="https://www.circle.com/pressroom/circle-is-first-global-stablecoin-issuer-to-comply-with-mica-eus-landmark-crypto-law" rel="noopener noreferrer"&gt;Circle press release&lt;/a&gt;, July 1, 2024). For an EU launch that usually means three checks:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A coin whose issuer is authorized under MiCA, such as USDC or EURC, confirmed with the provider on the day you launch.&lt;/li&gt;
&lt;li&gt;A provider or partner licensed to serve EU users, not only US ones.&lt;/li&gt;
&lt;li&gt;Screens and disclosures reviewed for each market you open.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We haven’t shipped an EU stablecoin product yet, so read this section as guidance from the public sources above, not as experience, and not as legal advice.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions to ask a stablecoin wallet provider
&lt;/h2&gt;

&lt;p&gt;Ask how the provider behaves when something goes wrong, not only which coins and chains it supports. Each question below maps to a failure we design the ledger around; the right-hand column shows what one provider documents, so you know what a clear answer looks like.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Provider questions and the failure each one prevents (Bridge column from its API docs, checked November 3, 2026)&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Ask&lt;/th&gt;
&lt;th&gt;Failure it prevents&lt;/th&gt;
&lt;th&gt;What a clear answer looks like&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Who holds the keys and the funds, and under which license?&lt;/td&gt;
&lt;td&gt;Your app ends up in a custody or money transmission role by accident&lt;/td&gt;
&lt;td&gt;Bridge: custodial wallets held by Bridge&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Omnibus or one wallet per customer?&lt;/td&gt;
&lt;td&gt;Balances you can’t prove per customer&lt;/td&gt;
&lt;td&gt;A named model, and how its records split balances&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How do retries work?&lt;/td&gt;
&lt;td&gt;A timeout and a retry pay twice&lt;/td&gt;
&lt;td&gt;Bridge: an Idempotency-Key header on every POST, honored for 24 hours, identical body required&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Which events arrive by webhook, and can they repeat?&lt;/td&gt;
&lt;td&gt;A screen says “completed” before the money moved&lt;/td&gt;
&lt;td&gt;A full event list per object, with event IDs you can deduplicate&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How do we reconcile?&lt;/td&gt;
&lt;td&gt;Balances drift for days before anyone notices&lt;/td&gt;
&lt;td&gt;A list or report of transfers you can match to your ledger daily&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Which rails in and out?&lt;/td&gt;
&lt;td&gt;Users can deposit but not withdraw where they live&lt;/td&gt;
&lt;td&gt;Bridge: virtual accounts in USD, EUR, GBP, MXN and more, plus on- and off-ramps&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Which coins in which markets?&lt;/td&gt;
&lt;td&gt;An EU launch with a coin that isn’t MiCA-compliant&lt;/td&gt;
&lt;td&gt;A per-market coin list, confirmed on launch day&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What is the GENIUS Act plan?&lt;/td&gt;
&lt;td&gt;A coin or partner that can’t operate after January 18, 2027&lt;/td&gt;
&lt;td&gt;The issuer’s licensing path, in writing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cards on the same balance?&lt;/td&gt;
&lt;td&gt;A second integration and a second ledger later&lt;/td&gt;
&lt;td&gt;Bridge: cards backed by stablecoin balances&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Fees matter too, but they come on top and change with volume; compare them once the answers above have narrowed the list.&lt;/p&gt;

&lt;h2&gt;
  
  
  Design for people who don’t care about crypto
&lt;/h2&gt;

&lt;p&gt;Most users want dollars that move fast, so show balances in USD, hide chain details by default, and make the card the hero.&lt;/p&gt;

&lt;p&gt;Use words like “balance”, “send” and “card” in the main flows, not “wallet address” or “network”. Advanced users can still find the chain, the transaction hash and the destination on a detail screen. Confirm every outgoing transfer with the amount and destination in plain words, because a stablecoin sent to the wrong address is hard to get back. Receipts matter more as money moves faster.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stablecoin use cases that fit a fintech app, and when they don’t
&lt;/h2&gt;

&lt;p&gt;Stablecoin wallets fit when money crosses borders, settles outside banking hours, or lands as platform earnings that users want to hold and spend in one place: payouts to contractors, creators and partner networks, cross-border transfers, and card spending from a dollar balance. Stablecoins are the wrong rail when your users need what a bank account gives them: deposit insurance through a partner bank, checks, cash deposits and ATMs. In that case a partner bank and a card program fit better.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://apptycoons.com/work/switch?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=stablecoin-wallets-fintech" rel="noopener noreferrer"&gt;Switch&lt;/a&gt;, a shared banking app we built for clubs and teams, made exactly that choice: Thread Bank as its FDIC-insured partner bank and Visa debit cards, with no stablecoins. Freedom Pro made the other one, because its members are paid as platform earnings and spend them by card.&lt;/p&gt;

&lt;h2&gt;
  
  
  What adding stablecoin wallets does to timeline and budget
&lt;/h2&gt;

&lt;p&gt;A focused wallet integration fits inside one of our fixed-price builds of $25k–$120k, delivered in 6–16 weeks after discovery; what moves it up the band is how many money paths it has. These are the usual drivers, in our judgment:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Transfer types.&lt;/strong&gt; Each one (deposit, conversion, withdrawal, send, payout) adds states, webhooks, failure screens and reconciliation rules.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cards.&lt;/strong&gt; Card lifecycle, limits, disputes and wallet provisioning add a second integration.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Markets.&lt;/strong&gt; US plus EU means two coin and partner checks and two sets of disclosures.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your own onboarding UI&lt;/strong&gt; instead of the provider’s hosted flow.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Operations tooling.&lt;/strong&gt; Search by provider ID, holds, case notes and exports for support and compliance.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Provider fees, KYC checks and card program costs come on top and are usage-based. For full scopes of two fintech products and their line items, see our guide to &lt;a href="https://apptycoons.com/blog/fintech-app-development-cost?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=stablecoin-wallets-fintech" rel="noopener noreferrer"&gt;fintech app development cost&lt;/a&gt;; our &lt;a href="https://apptycoons.com/pricing?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=stablecoin-wallets-fintech" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; page lists the Discovery Sprint and build terms.&lt;/p&gt;

&lt;h2&gt;
  
  
  Launch checklist for stablecoin wallets
&lt;/h2&gt;

&lt;p&gt;Before real money moves, check each of these:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Money flows drawn end to end, with counsel’s sign-off on who holds funds at each step.&lt;/li&gt;
&lt;li&gt;Sandbox tests for every transfer type, including failures, returns and late webhooks.&lt;/li&gt;
&lt;li&gt;One idempotency key per user intent, stored with the transfer and reused inside the provider’s window.&lt;/li&gt;
&lt;li&gt;Webhook replay test: the same events delivered twice and out of order leave balances unchanged.&lt;/li&gt;
&lt;li&gt;Daily reconciliation with alerts, and a support view that searches by provider ID.&lt;/li&gt;
&lt;li&gt;Onboarding tested for approved, pending-review, rejected and limited customers.&lt;/li&gt;
&lt;li&gt;Coin and provider confirmed for every market you launch in, and the provider’s GENIUS Act plan on file for US users.&lt;/li&gt;
&lt;li&gt;Copy reviewed for anything that implies deposit insurance, interest or yield on a stablecoin balance.&lt;/li&gt;
&lt;li&gt;Limits for new accounts and a fast way to freeze one when the provider asks.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How Freedom Pro uses it
&lt;/h2&gt;

&lt;p&gt;On &lt;a href="https://apptycoons.com/work/freedom-pro?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=stablecoin-wallets-fintech" rel="noopener noreferrer"&gt;Freedom Pro&lt;/a&gt;, stablecoin wallets are where a partner network gets paid. Partners earn on their team’s activity in the back office, and earnings arrive in USD or stablecoin (USDC) balances that members spend by debit card, under the same single sign-on as the platform’s wireless, streaming and wellness services. Bridge provides the wallets and the card program; we built the product around it, from the member portal to the back office. That makes Freedom Pro a &lt;a href="https://apptycoons.com/industries/financial-aggregators?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=stablecoin-wallets-fintech" rel="noopener noreferrer"&gt;bundled financial services platform&lt;/a&gt; as much as a direct-selling one, and the commission side is covered in our guide to &lt;a href="https://apptycoons.com/blog/mlm-software-guide?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=stablecoin-wallets-fintech" rel="noopener noreferrer"&gt;MLM software and commission engines&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you are adding wallets or cards to an existing product, our &lt;a href="https://apptycoons.com/industries/fintech?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=stablecoin-wallets-fintech" rel="noopener noreferrer"&gt;fintech app development&lt;/a&gt; team starts with the provider choice and the money flows, then builds the ledger and the apps.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;a href="https://apidocs.bridge.xyz/" rel="noopener noreferrer"&gt;Bridge API documentation&lt;/a&gt;, Bridge&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://apidocs.bridge.xyz/api-reference/introduction/idempotence" rel="noopener noreferrer"&gt;Idempotence&lt;/a&gt;, Bridge API reference&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.circle.com/wallets" rel="noopener noreferrer"&gt;Wallets&lt;/a&gt;, Circle&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-50.html" rel="noopener noreferrer"&gt;GENIUS Act Regulations: Final Rule (Bulletin 2026-50)&lt;/a&gt;, OCC&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.wilmerhale.com/en/insights/client-alerts/20261027-occ-finalizes-genius-act-rule-for-permitted-payment-stablecoin-issuers-easing-several-key-proposed-requirements-and-raising-new-issues" rel="noopener noreferrer"&gt;OCC Finalizes GENIUS Act Rule for Permitted Payment Stablecoin Issuers&lt;/a&gt;, WilmerHale&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.esma.europa.eu/press-news/esma-news/esma-and-european-commission-publish-guidance-non-mica-compliant-arts-and-emts" rel="noopener noreferrer"&gt;ESMA and European Commission publish guidance on non-MiCA compliant ARTs and EMTs&lt;/a&gt;, ESMA&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://apptycoons.com/blog/stablecoin-wallets-fintech?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=stablecoin-wallets-fintech" rel="noopener noreferrer"&gt;apptycoons.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>fintech</category>
      <category>blockchain</category>
      <category>webdev</category>
      <category>api</category>
    </item>
  </channel>
</rss>
