Whether it’s a quick question or a detailed brief — we’d love to hear about it.
AI Hub 030 · Guide
Do you need an AI team, or one tool?
You have one thing you want AI to do: a chatbot for customers, a review that eats hours, a document nobody wants to write. Do you need a whole team for that, or just the one tool built? It depends on what happens after it goes live. One tool is the right purchase when the job is settled, you can write it down, and someone will look after it. A team is the right purchase when there is a list of work behind the first tool, or the tool will keep changing.
If you cannot tell yet, you do not have to guess. Start with one process, measure it, and let the result decide whether a dedicated AI development team is worth having.
One tool or a team, side by side
| One tool, built once | A team that stays | |
|---|---|---|
| Fits when | One process, settled rules, a scope you can write down | Several processes, or one that keeps changing |
| What you buy | A defined build at an agreed price | People, paid month by month |
| Who decides what gets built | You, up front, in the brief | You, as you go, every sprint |
| Who keeps it working | You, or whoever you pay afterwards | The people who built it |
| The risk | A tool nobody looks after | Paying for people without enough work |
| How it ends | Handover | When the work runs out |
Five questions that settle it
1. How many processes are on your list?
One process: buy one tool. Three or more: a team earns its place, because the people who built the first tool already know your systems, your data and your staff, so the second starts further along. Two: treat it as one, and see what the first teaches you.
2. Can you write down exactly what it should do?
If the brief fits on two pages and nobody argues with it, a fixed build works. If you expect to find out what you need by using it, a fixed scope will fight you, because every change becomes a new negotiation.
3. Will the rules or the inputs change?
A tool that checks documents against rules is only as good as this month’s rules. If your guidelines, forms or suppliers change a few times a year, someone has to keep the tool in step with them.
4. Who will keep it working after it goes live?
An AI tool is not finished the day it goes live. OpenAI, Anthropic and Google each publish a list of the AI models they are retiring, with dates, and a retired model stops answering. A tool built on one has to be moved to its replacement and checked again. If nobody in your business can do that, either the handover includes someone who will, or the tool has a shelf life.
5. Does the saving carry a monthly cost?
A team is a monthly cost, so the work has to pay for it every month. Put a number on the process first with the AI ROI calculator, and see how much AI development costs by each route. If the process runs a few times a month, the savings will not add up for a team or a tool.
Reading your answers: one process, a brief you can write down, stable rules and someone to look after it point to one tool. A list of processes, a brief you expect to change, moving rules and nobody in-house point to a team.
When one tool is the right answer
More often than a firm that sells teams will usually admit. One settled process needs one build, and sometimes it does not need AI at all.
Fixed rules, clean data: a straightforward automation is cheaper to build and run. If that’s all the process needs, that’s what we recommend.
We say the same on our own Teams page: if you need one fixed piece of work built and handed over, a dedicated team is probably not the right fit.
With a single build, ask for three things in writing: the code, the documentation and the accounts in your name; which AI model it runs on; and what it costs to have someone look after it. The full list of what to ask is in choosing an AI development partner. For how one build works with us, see automating one process.
When a team is the right answer
A team fits when:
- You have high-volume manual work, or an AI product roadmap, that you can put a cost on
- You want capability that lasts and grows, not a one-off project
- You have tried to hire for this, or a vendor has not delivered
- Someone senior in the business will own the outcome
A team does not have to mean a big one.
Most teams start with one or two AI developers and add roles as the roadmap grows.
If you cannot tell yet, start with one process
A US mortgage lender started with three developers and one target: a document review that took credentialed staff 45 to 50 minutes a file. The first tool cut that review to 15 minutes. At the lender’s volume it saved more than $40,000 a month and paid for the whole engagement. As the tools proved themselves, the team grew to more than ten people. In under nine months more than 12 AI tools were in production, saving $175,000+ a month across three core workflows.
The spend followed the results, not a contract signed up front.
The lender’s Executive Vice President describes what came out of it as “not a series of projects, but an operating model”. Read the case study.
That is the safe answer when you are unsure: one tool first, measured against the old way of working, and a team only if the number says so.
How we handle either
The first two steps are the same whichever way it goes: a free consultation, then a proof of concept at a fixed price, quoted before it starts.
After that, a dedicated team or a fixed-price build, whichever the roadmap needs, costed before each stage.
A dedicated team is from $4,500 per team member per month and runs month to month: there is no premium for stopping and no discount for promising a year. A fixed-price build ends with the code, the documentation and the accounts in your hands. Everything we charge is on our pricing page.
Bring the one process
Tell us the one process that costs you most. We will tell you whether it needs a team, one tool, or nothing: if there isn’t one worth automating, we’ll say so. See how a dedicated AI development team works, or book the free consultation.
Offshorly is a UK-led AI development company that builds dedicated AI development teams in the Philippines, trading since 2014.