Software Costs
How to Hire an AI Agent Development Company: What to Ask
How to hire an AI agent development company to build and run your office software: the brief, ten questions, a paid trial, contract terms and exit rights.
In this article
- Who you are actually hiring: three kinds of firm
- Before you contact anyone: the one-page brief
- Ten questions to send in writing, and the answers that should worry you
- Reference calls: six questions that work
- Run a paid trial instead of a demo
- What the software is allowed to do
- Contract terms to settle before the statement of work
- Red flags, and how to check instead of trust
- When not to hire an outside firm at all
- What good looks like, and what to do next
- Frequently asked questions
- Sources
Short answer: how to hire an AI agent development company comes down to five moves, and only one of them involves a sales call. Write a one-page brief before you contact anyone. Screen on written answers instead of decks. Pay for a small trial or audit on your own numbers. Settle who owns what, and how you leave, before you sign. Then ask who answers the phone when it breaks, because that question separates a builder from a firm that will run your software.
The usual order fails. Most owners collect a few impressive-looking firms, sit through demos, pick the most confident one, and discover in month four that nobody agreed what "working" meant, or what happens to the dispatch board when the contract ends.
This guide is written for the owner or general manager of a contracting business with 8 or more trucks and an office team, who is thinking about paying someone to build software and run it. It gives you:
- the three kinds of firm you can hire, and when each is the right one;
- a one-page brief that makes quotes comparable;
- ten questions to send in writing, with the answers that should worry you;
- how to use a paid trial instead of a demo;
- the contract terms that matter, including export, escrow and exit;
- the red flags, and when the right answer is not to hire anyone.
"AI agent development company" is the phrase people search for, and it covers firms that build and run software for you. If your problem is that your tools do not talk to each other, that is a smaller job than replacing them; both are covered below.
Who you are actually hiring: three kinds of firm
Before you compare vendors, decide which kind of vendor fits the problem. They carry very different risks.
| Kind of firm | Good for | The risk |
|---|---|---|
| A freelancer or small agency | A prototype, a report, a one-off integration | When they move on, nobody maintains it |
| A firm that builds and hands over | A custom system your own IT person will run | You inherit the maintenance, which is usually the biggest line in a three-year cost |
| A firm that builds and operates | Replacing subscriptions with software built for how you work | You depend on them, so exit terms are everything |
The third model is what Fleurant AI does, and it is the one where the contract matters most, because you are trusting a company with the system your office runs on. That is why most of this article is about terms rather than technology.
Key takeaway: The more of your operation a vendor runs, the more the questions about export, ownership and exit matter. Ask them first, not last.
Before you contact anyone: the one-page brief
A vendor can only quote what you have described. One page, written by you, is enough, and it makes every proposal comparable.
- The problem in your words. "Our dispatcher re-types every job into the invoicing tool" is better than "we want automation".
- Your systems. Every subscription, with seats and monthly cost. If you do not have this list, it is the first thing to build. The Stack Audit produces it for $2,500, credited in full against a build started within 90 days.
- What stays. Accounting, payroll and payment processing normally stay as they are. Naming that up front shows the vendor what you are not asking for.
- The size of the business. Employees, trucks, trades, residential or commercial.
- A named decision maker. One person who can say yes.
- The date it must not break. Your peak week. Ask every vendor how they would protect it.
Ten questions to send in writing, and the answers that should worry you
Send these as an email, not a call, and compare the written answers side by side. A vendor who replies with a deck has told you something.
| # | Question | Answer that should worry you |
|---|---|---|
| 1 | What do you run in production today for a business like mine? | "Our clients are confidential" with nothing else |
| 2 | Who exactly will build my system, and who will operate it afterwards? | "A team", with no names or roles |
| 3 | What do I own when this ends: data, software instance, source code? | A long answer that never says "your data" |
| 4 | Can I export everything, in standard formats, whenever I want? | "Yes, for a fee", or "on request after 30 days" |
| 5 | What happens if I cancel? | No mention of read-only access or a final export |
| 6 | Is the price per seat, per job or by company size? | Per seat. It rises with every technician you hire |
| 7 | When can the price change? | Mid-term, or on a notice shorter than a renewal cycle |
| 8 | What is your support commitment, in hours? | "24/7" from a small team, or no number at all |
| 9 | What will you never touch? | "Everything", including payroll and accounting |
| 10 | What would make you tell me not to buy this? | Nothing |
A few of these deserve more than a table cell.
Question 3, ownership. The safest answer separates two things. You own your data and your instance of the software. The vendor rents you the agent fleet that operates it. That is a fair split if the contract also guarantees a full export, read-only access after you leave, and source code escrow on request. A vendor who answers "you own everything" without those protections is promising more than a contract can deliver, and one who answers "we own the platform" without them is describing a lock-in.
Question 6, price. Per-seat pricing is what most contractors are escaping. Fleurant AI sets the monthly fee by company size band instead: $2,000 up to 30 employees, $2,750 for 31 to 60, $3,500 for 61 to 100. The band is reviewed once a year at renewal, never mid-term, so a new hire never changes the invoice. Whatever model you are offered, ask what happens to the bill when you hire five technicians.
Question 8, support. Fleurant AI's commitment is next business day for normal issues and four hours for urgent ones, with no overnight coverage. A written number you can hold a vendor to beats an impressive-sounding promise.
Question 10, the honest one. The best vendors answer this readily. Spending under about $1,500 a month on software is a typical one: below that, replacement does not pay back in a sensible time, and a vendor should say so.
Reference calls: six questions that work
Ask for two references, and ask for a contractor in your trade and of your size if there is one. A company that cannot provide any should say why, and if it is new, it should say that plainly. Do not accept testimonials written by the vendor in place of a call.
- What did you buy, and what was supposed to change?
- How long did it take, against what you were told?
- What broke in the first 90 days, and how fast was it fixed?
- Who do you call when something is wrong, and how long does a reply take?
- What did it cost beyond the original quote?
- Would you buy it again, and what would you change about the contract?
Listen for specifics, and for how long the answer to question 4 takes. Fleurant AI has no client yet to put on that list, so the Stack Audit exists for a reason: you see your own numbers instead of someone else's story.
Run a paid trial instead of a demo
Demos are chosen by the vendor, built on tidy data and rehearsed. A trial on your own records is the nearest thing to evidence.
The cheapest version is an audit. A Stack Audit takes one to two weeks and delivers four things: every subscription with seats, cost and contract end date; a workflow map of how a job travels from call to cash; the overlap list of what two tools both do; and a costed replacement plan with the payback period in months. You pay $2,500, and it is credited in full against a build started within 90 days. Even if you never build anything, you keep the document.
Whoever you hire, a good trial has the same shape:
- Real data. Your customers, your jobs, your price book, not a sample set.
- A defined pass mark. Agreed in writing before work starts, not chosen afterward to match the result.
- A cost. Paid, so both sides take it seriously and you own what comes out of it.
- One workflow. Narrow enough to judge in two weeks.
If a vendor will not run anything on your data until you sign a long contract, treat that as the answer to question 1.
What the software is allowed to do
Hiring someone to build software that acts, instead of one that only reads, adds a category of risk most owners have not met. Anthropic's engineering team advises finding the simplest solution possible and adding complexity only when needed, which is a useful test of any proposal: ask why each step needs a model at all. Chasing an unpaid invoice on a schedule does not.
Where the software does act, ask for the limits in writing. The OWASP Gen AI Security Project publishes a Top 10 for Agentic Applications, released on December 9, 2025, as a reference list of the most critical risks. You do not need to read it, but a serious vendor will have. In plain terms the limits are:
- the software that raises invoices cannot delete a customer;
- a message from a customer cannot change a price;
- anything that moves money or changes the schedule needs a person's approval until it has earned its freedom;
- every action is logged, so you can see what it did and undo it.
Also ask where your data lives and who can see it. A vendor that hosts your records should be able to show an independent assurance report. The AICPA describes its SOC reports as assurance reports that help users assess the risks of outsourcing services; a SOC 2 report covers controls relating to security, availability, processing integrity, confidentiality or privacy. Read the scope and the exceptions, and check that the systems covered are the ones your project will use. A new firm may not have one yet, and the honest answer is to say so and explain what it does instead.
Contract terms to settle before the statement of work
The contract is where a good relationship is protected and a bad one is survivable. These are the terms that matter for a firm that builds and operates your software.
| Term | What to require |
|---|---|
| Ownership | Your data and your instance are yours, in writing. The agent fleet is rented, and the contract says so |
| Export | Standard formats, free, any time, with no waiting period |
| Exit | 60 days of read-only access and a full export on cancellation |
| Escrow | Source code escrow on request |
| Exclusions | Accounting, payroll, payment processing and anything with a regulatory filing are never replaced, and the contract names them |
| Price | By company size or a fixed fee, never by seat. Reviewed at renewal, not mid-term |
| Included | What the monthly covers: hosting, backups, operation, monitoring, fixes, storage and hours of changes. Rates for anything beyond |
| Support | Written response times, and an honest statement of what is not covered, such as overnight |
| Acceptance | What "live" means for each module, agreed before work starts |
| Rollback | A defined way back for every cutover |
Fleurant AI's own terms, for comparison, are: a monthly fee that includes hosting, backups, operation, monitoring, fixes, 2 TB of storage and four hours of changes a month; past that, $175 an hour and $20 per terabyte a month; and a Stack Operator tier from year two at an extra $1,500 a month for 10 hours of development instead of four. Compare them line by line with whatever else you are offered, and make every vendor price the same scope. A quote that leaves a line out is not cheaper.
The forward-deployed trap
Some firms sell "forward-deployed engineering": their engineers embed in your team and build the solution on your site or in your systems. Gartner warned in September 2026 that many providers use the label for ordinary implementation or consulting, and predicted that by 2028, 70% of enterprises will abandon agentic AI built this way because of rising costs and an inability to evolve it themselves. The lesson for a contractor is smaller and sharper: if you pay a person to be inside your business, make sure you can run and change the result without them, and that your data and instance are yours when they leave.
Red flags, and how to check instead of trust
A fixed price before anyone has looked at your systems. It means a guess, or change orders later. The cure is the paid audit or trial.
A demo video instead of a live run. Ask to see it work on your records, with the logs visible.
"AI" on everything. Gartner's 2025 release on agent projects says many vendors are "agent washing", relabelling chatbots and older automation, and that only about 130 of the thousands of agentic AI vendors are real. The FTC said in September 2024 that there is no AI exemption from the laws on the books when companies use AI claims to mislead. A vendor's claims about what its software does should be ones it can show you.
A savings promise. Any percentage quoted before the vendor has seen your invoices is a marketing number. Fleurant AI does not quote one and has no client results to point to yet; the audit shows you your own numbers instead. Treat a vendor who quotes you a percentage with caution.
No answer on exit. If the cancellation terms are vague, they are not in your favor.
Vague support. "24/7" with a small team is a promise nobody can keep. Ask for response times in hours, in writing.
Pressure around your busy season. A vendor who wants a signature before the peak, so the go-live lands in your worst week, is working to its calendar, not yours. Our guide to how long a build really takes covers why season matters.
When not to hire an outside firm at all
Hiring is not always the answer.
You spend less than about $1,500 a month on software. Below that, replacing it does not pay back, and the guide to what software can take off a small office team covers cheaper routes.
Your tools just need to share data. A Connector keeps what you have and makes it work as one system: $7,500 to build, $750 a month, live in two to four weeks. It is a smaller commitment than a replacement.
You already have a capable developer. If you employ someone who can run the system, building in-house can be right, as long as you budget for maintenance, which is usually the largest line over three years.
Your records are in spreadsheets and people's heads. That is a data project first. See when to replace spreadsheets with custom software.
What good looks like, and what to do next
A good hire looks like this: a brief you wrote, written answers from three vendors, a paid audit or trial on your own numbers, ownership and exit terms you can explain to your office manager in two minutes, and a start date that is not the first hot week of the summer.
Do three things this week. Write the one-page brief, starting with the list of everything you pay for. Send the ten questions to two or three firms. And decide who on your side signs off.
If you want the list and the numbers done for you, the Stack Audit is built for exactly that, and the Operations Stack page sets out the full terms. Or talk to a specialist first.
If you'd like one clear, practical take on the software that runs your business each month, subscribe to the Fleurant AI Briefing: one email a month, unsubscribe any time.
Frequently asked questions
What should I ask an AI agent development company before signing?
Ask for one system they run in production today for a business like yours, and what it costs per month. Ask who exactly will build it and who answers when it breaks. Ask what you own at the end, whether your data exports in standard formats, and what happens to the software if you cancel. Get the answers in writing, not in a deck.
Should I hire a freelancer, a general web agency or a specialist firm?
Match the vendor to the risk. A freelancer is fine for a prototype or a report that only reads your data. A specialist firm earns its fee when the software writes to dispatch, invoices or customer records, because someone has to be on the hook when it fails. A general web agency with nobody who has run office software for a service business is the most common expensive mistake.
Who owns the software, the data and the prompts?
You should own your data and your instance of the software, and the contract has to say so in plain words. Some vendors rent the agent fleet that operates it and keep that part, which can be reasonable if the contract also guarantees a full export, read-only access after you leave and source code escrow on request. The thing to refuse is silence on the question.
How long should it take to choose a vendor?
About four to five weeks if you do it properly: one week for the brief, one for written answers, one for calls and references, and one to two for a paid trial or audit on your own numbers. Under two weeks usually means you are buying a presentation. Do not let the process run into your busy season, when nobody has time to answer the vendor's questions.
What is forward-deployed engineering, and should I pay extra for it?
It is a delivery model where the vendor's engineers work inside your team to build and deploy a solution. Gartner warned in September 2026 that many providers now use the label for ordinary implementation work, and predicted that by 2028 70% of enterprises will abandon agentic AI built this way because of rising costs and an inability to evolve it themselves. Pay for it only with ownership, knowledge transfer and an exit plan in the contract.
How much does it cost to hire someone to build and run office software?
It depends on the model. Building it yourself is a project cost plus an engineer's time every month for years, which our cost guide works through. Fleurant AI's published prices are a $2,500 Stack Audit credited against a build, then $18,000 for three modules or $32,000 for five or more, plus $2,000, $2,750 or $3,500 a month depending on whether you have up to 30, 31 to 60 or 61 to 100 employees. Ask every vendor to price the same scope.
What is the single biggest red flag?
A fixed price offered before anyone has looked at your systems or your data. It means the vendor is guessing, or planning to recover the difference through change orders. The second biggest is a demo video in place of a live run on your own records.
Sources
- Gartner Predicts Over 40% of Agentic AI Projects Will Be Canceled by End of 2027, Gartner
- Gartner Predicts 70% of Enterprises Will Abandon Agentic AI Built by Vendor Forward-Deployed Engineering by 2028, Gartner
- FTC Announces Crackdown on Deceptive AI Claims and Schemes, Federal Trade Commission
- System and Organization Controls: SOC Suite of Services, AICPA & CIMA
- OWASP Top 10 for Agentic Applications, OWASP Gen AI Security Project
- Building Effective AI Agents, Anthropic
- Software Developers, Quality Assurance Analysts, and Testers, U.S. Bureau of Labor Statistics