TL;DR: The first meeting with an AI agency in Abu Dhabi should be about one workflow, not about AI. A good meeting maps that workflow end to end with the people who do it, names every system it touches, agrees what will be measured, and ends with a written scope and a fixed price to follow. If you leave with a demo and a number, you have been sold to rather than scoped.
What should the first meeting with an AI agency cover?
The first meeting with an AI agency should cover one specific workflow in your business: where the work arrives, who touches it, which systems it passes through, where it stalls, and what "done" looks like. It should also cover the boundaries you need (what the system may never do on its own), how success will be measured, and who will own the result. It should not be a product demonstration, and it should not end with a price.
This is written for an owner or operations lead in Abu Dhabi who has been approached by, or is about to approach, an AI agency. It explains what a useful first meeting looks like, what to bring, what the agency should be asking you, and how to recognise a meeting that is going badly while you are still in it.
Why the first meeting matters more than the proposal
Most AI projects that disappoint were scoped badly rather than built badly. The workflow chosen was the one that sounded impressive rather than the one that hurt; the people who actually do the work were not in the room; a system that "everyone uses" turned out to have no usable export; and nobody agreed what number would move. All of those are decided, or left undecided, in the first meeting.
An agency that runs a good first meeting will save you from most of that. An agency that runs a bad one will still send a polished proposal, and you will not find out until the build is under way.
What should you bring?
You do not need a brief, a requirements document or a budget figure. You need four things.
- One workflow that hurts. Quotation requests that sit overnight, tenant complaints that arrive on WhatsApp and get lost, supplier invoices that someone re-types into the accounting system, tender documents assembled by hand every month. Pick the one your team complains about most.
- The people who do it. Not their manager. The person who answers the WhatsApp number, the accountant who re-types the invoices, the coordinator who chases the drivers. They know where it actually breaks.
- Real examples. A handful of actual messages, documents or emails, with anything sensitive removed. The agency needs to see the Arabic and English mix, the photos of handwritten delivery notes, the PDFs that are really scans, and the voice notes.
- A list of systems. Which CRM, ERP or accounting software, which WhatsApp number and whether it is on the app or the Business API, where documents are stored, and who administers each. If you do not know, say so; that is useful information too.
Which workflow should you talk about first?
The right first workflow is the one where the work is repetitive, the inputs already arrive in a digital form (a WhatsApp message, an email, a PDF), the outcome is easy to check, and a mistake is recoverable. Answering enquiries, reading documents into a system, and chasing follow-ups all qualify. Redesigning your whole customer journey does not.
Be suspicious if the agency steers you toward something broader than what you brought. "Let's start with a full AI transformation roadmap" is a way of selling consulting days. A serious engineering studio would rather ship one working thing, measure it, and earn the second project.
What questions should the agency be asking you?
The quality of the meeting is in the questions the agency asks, not the slides it shows. Listen for these.
- Where does this work arrive, and in what form? WhatsApp, email, a portal, a phone call, a paper document?
- Who handles it now, and what do they do step by step? What do they look up, and where?
- What happens when the input is wrong, incomplete or in a language the handler does not read?
- Which decisions in this workflow commit money, make a promise to a customer, or have legal weight? Those are the steps that will need human approval.
- What would you look at in a month to know whether this worked?
- Who administers the systems involved, and can we get access to test with real data?
- Are there data residency, confidentiality or sector rules we need to design around?
If the agency asks none of these and instead opens a laptop to show a chatbot, you are watching a sales process, not a scoping one. Our earlier piece on questions to ask an AI agency before signing covers the questions you should be asking back.
What does the Abu Dhabi context change?
Working in Abu Dhabi shapes the scope in ways an agency from elsewhere may not anticipate, and a good first meeting surfaces them early.
WhatsApp is the channel. For most businesses here, customers, tenants, suppliers and drivers communicate on WhatsApp first and email second, if at all. The first question about almost any workflow is whether it starts on a WhatsApp number, and whether that number is on the consumer app or the Business API. The answer changes what can be automated.
Arabic and English arrive together. A single enquiry may open in English, switch to Arabic, and include a voice note. The agency should ask to see real examples rather than assume "bilingual" means two clean languages.
Approvals are structured. Many Abu Dhabi businesses serve government-linked entities, semi-government groups or free-zone companies, and their own internal approvals reflect that. A system that sends a quotation without the right sign-off will not survive its first week. The meeting should identify who approves what.
Data has a place it needs to stay. If you work in healthcare, finance, legal or government supply, in-country or in-region hosting may be expected. Ask the agency how their design changes when data must stay in the UAE, and check the current data protection guidance for your sector alongside their answer.
The Abu Dhabi page describes how we approach these constraints locally.
What should you leave the meeting with?
A useful first meeting produces a short written summary soon after, not a proposal. It should name the workflow, list the systems, state what is in and out of scope, list the steps that need human approval, name the metric that will be watched, and say what the agency needs from you before it can price the work. The fixed price comes after the agency has seen your systems and data, because that is what the price depends on.
You should also leave knowing who will do the work, where your data will live, and what you will own at the end: code, prompts, knowledge base, the WhatsApp Business Account, and every account the system depends on.
A good first meeting versus a weak one
| What happens | Good first meeting | Weak first meeting |
|---|---|---|
| Opening | Questions about your workflow | Slides about the agency |
| Who is in the room | The people who do the work | Decision-makers only |
| Examples | Real messages and documents on the table | Hypotheticals |
| Scope | One workflow, boundaries named | "Transformation roadmap" |
| Money | Drivers of price explained; number to follow | A price quoted on the spot |
| Outcomes | A metric and a baseline agreed | A promised percentage |
| Ownership | Code, accounts and data in your name | Not discussed |
| Close | Written summary and next steps | A signature request |
Red flags you can spot in the room
A demo before any questions means the agency has a product to place rather than a problem to solve. A price on the first call means the number was decided before you spoke. A promised saving or percentage means the figure came from marketing rather than from your operation. Vagueness about ownership of code, accounts and data means leaving will be expensive. Any one of these is a reason to slow down; two together are a reason to stop.
How Soluvide runs a first meeting
We are an engineering studio in Abu Dhabi, and the first conversation is free and unscripted. We ask you to bring one painful workflow and the person who does it. We walk it end to end, ask to see real examples, name the systems and the approval points, and agree what we would measure. We then send a written scope and a fixed price. Anything that commits money or makes a promise to a customer is gated behind human approval in every system we build, and the client owns the code, the accounts and the data from the first day.
If you want a structured way to start, the free automation audit is that first meeting in a repeatable form: we look at your workflows and come back with a ranked list of what is worth automating and what is not. Our AI integration and consulting page describes what happens after that.
If you would rather just talk, message us on WhatsApp with the workflow that hurts most and we will take it from there.
Questions
Frequently asked.
Bring one workflow that costs your team the most time, the people who actually do it, examples of the real messages or documents involved, and a list of the systems it touches (CRM, ERP, accounting, WhatsApp number). You do not need a brief or a budget figure. A good agency will do the rest of the work in the room.
Where this applies