You have looked at four products that do most of what you need, and none of them do the part that matters. The demo skips it, the sales engineer calls it a roadmap item, and meanwhile the work still happens in a spreadsheet, an email thread, and one person's head.
So you start pricing a build, and the quotes come back with no shape to them. Custom application development gets sold as an open question, which makes it hard to tell what you would be buying. This post is what a build actually contains. I run a firm that does this work, so read the pricing section as an argument for hiring us. The rest holds whoever you hire.
Three jobs a custom application does
Almost every build is some mix of three jobs. Naming which ones you need is most of the scoping work.
A screen for work people do: the intake form, the review queue, the approval, the dispatch board. Right now that is a spreadsheet with color coding and a set of rules nobody wrote down.
A connection between systems that cannot see each other: the accounting file on a server in your office, an operational database written in 2004 with no API, a supplier portal with a login and no export. The application reads and writes both sides, maps the fields, checks the values, and logs every record it moved.
A place the records actually live: when the real record of a job is split across a spreadsheet, a shared drive, and an inbox, the first thing to build is one place that holds the current version, with a history of what changed and who changed it.
Decide what it must not do
The fastest way to make a build expensive is to let it grow into a replacement for software you already pay for. A custom application should sit next to your accounting system and your CRM, not instead of them. Those products solve the general problem — a ledger, a contact record, a pipeline — and they solve it better than a build for one company ever will.
What you build is the part no vendor sells: your rules, your steps, your exceptions, and the connections between the systems you are keeping. Write down the list of systems that stay. That list is the boundary of the project, and it is what a fixed price can be written against.
The first version should run one process end to end
A build that covers one process completely gets used the day it ships. A build that covers 40 percent of six processes gets abandoned, because all six still need the old spreadsheet for the rest.
Pick the process you would take off someone's desk first. Count the hours a week it eats and the number of times a month it goes wrong. Build that one, put it in production, and let it run for a month before you scope the next. The narrow first version is also the only honest way to price the rest, because it is where both sides find out where your exceptions actually are.
What gets built, in order
The process map: we walk the real steps with the person who does them, including the steps that are not in anyone's documentation. Everything after this is wrong if this part is wrong.
The data model: what a job, an order, a slip, or a load is in your business. Which fields are required, which values are allowed, and what makes two records the same record.
The integrations: middleware against each system that stays, with field mapping, validation rules, and a log of every read and write. No cloud migration, and no asking you to replace a system that works.
The screens: only for the steps where a person decides something. If a step needs no judgment, it should need no screen.
The agents: the steps nobody should be doing by hand.
The audit trail: every record carries where it came from, which rules it matched, and when it posted, so you can sample the automatic ones and see exactly why each one went through.
The agents that run the repetitive steps
The screens and the connections are the frame. The agents do the work inside it.
The data-entry agent reads PDFs, spreadsheets, web forms, and email attachments, checks every field against rules you set, posts clean records to your CRM, your ERP, a spreadsheet, or an internal database, and sends anything that fails a rule to your team for review. We ran that job for a delivery company in Dallas-Fort Worth: about 2,000 handwritten slips, about twenty fields each, into more than 1,900 checked rows in about 30 minutes.
The bookkeeping agent reads transactions from bank feeds, invoices, and operating records, checks each one against your chart of accounts and your classification rules, posts what passes, and routes exceptions to a review queue with the reason it stopped.
The voice agent is one system doing two jobs. It answers your inbound calls as a receptionist and places your outbound ones as a cold caller. It holds a real two-way conversation, handles interruptions, and responds in under a second. It transfers a live call to a person, books on your calendar, sends the invite, takes a message, and writes the note. On outbound it qualifies, books, follows up by email, and writes the activity back to your CRM. It answers every call at once, so there is no queue and no capacity limit. It has placed more than 30,000 outbound calls since December 2025.
Our proven deployment is outbound qualification and meeting setting in oil and gas. Other industries are a fit rather than a proof, and I will tell you on the call which one yours is.
Who is responsible for it the Tuesday after launch
Software wired into daily operations breaks on the days you are busiest. A vendor changes a form. An upstream system renames a field. A caller says something in an order nobody tested.
We build it, put it in production, and stay responsible for it while it runs. We watch it, fix what breaks, and make the changes you ask for. You are not handed a repository and a login. That is the part most of this market does not sell, and it is the reason the system still works in month six.
What it costs and how long it takes
Custom software and one-off jobs are priced per project, from $10,000. The agents have a build fee and then a monthly fee: the AI receptionist and answering service from $2,500, then from $500 a month, and on the receptionist a busy month costs the same as a quiet one; the cold caller and appointment setter from $5,000, then from $2,500 a month; the bookkeeping and data-entry agents from $5,000, then from $500 a month.
The monthly fee covers AI model usage, monitoring, fixes, and the changes you ask for, plus the phone line and call minutes on the voice agents. More systems to connect, more volume, more complicated rules, and more agents or phone lines raise a quote. The pricing section of our FAQ covers the rest.
Timeline follows scope. A simple build can be ready in a few days. A complicated one can take 90 days to design, build, and test.
The call
Bring two things: the process you would take off someone's desk first, and the list of systems that are staying. We will walk the real steps, say what we would build against each one, and put a number on that scope.
If that is the conversation you want, book a call and we will scope the first version with you on the call.