Question 1

What exactly is the free consultation?

Accepted Answer

We sit with the people who run one of your processes and map it as it actually works today. You get a mapped view of the workflow, an estimate of the hours and cost it consumes, a prioritised list of what could be automated, and an expected ROI range with our assumptions shown. It is free, it takes a few sessions, and it commits you to nothing.

Question 2

Is the consultation really free, or is it a sales meeting?

Accepted Answer

It is genuinely free and you keep the output. We do it because it is the only honest way to scope automation work — quoting before understanding the process would mean guessing. Sometimes the consultation concludes that a process is not worth automating, and we say so.

Question 3

Which process should we start with?

Accepted Answer

The one that is repetitive, follows the same rules every time, and irritates your team the most. High volume and clear rules beat high complexity. If you are unsure, that is what the consultation is for.

Question 4

How small is too small to work with OTMO?

Accepted Answer

There is no minimum headcount. What matters is whether you have a process that repeats often enough for automation to pay for itself. A ten-person company with a daily invoicing routine is a better fit than a large organisation with a quarterly one.

Question 5

How long does a typical project take?

Accepted Answer

A first workflow usually runs eight weeks from consultation to live: roughly a week to consult, two to design, three to build, and two to integrate and hand over. Scope drives it more than anything, and we tell you the range before you commit.

Question 6

How much of our team's time will this take?

Accepted Answer

Most of the demand is in the first two weeks — we need real access to the people who run the process, because they know the workarounds nobody wrote down. After that it is a review session each cycle, usually an hour.

Question 7

What happens if the automation gets something wrong?

Accepted Answer

Every workflow we build has defined error handling and an escalation path to a person — that is designed in from the start, not added after an incident. Before anything goes live it runs in parallel with your existing manual process until the outputs agree.

Question 8

Do we have to replace our current systems?

Accepted Answer

No. We build on top of what you already run — your CRM, accounting system, spreadsheets, whatever it is. If a project requires you to migrate everything first, it is a migration project, not an automation one, and we will tell you that.

Question 9

What can you integrate with?

Accepted Answer

Anything with an API, and a good deal that does not have one. In practice that covers WhatsApp, Google Workspace, Microsoft 365, Salesforce, HubSpot, SAP, Shopify, Slack, Notion and most industry-specific systems. We confirm the specifics during the consultation rather than promising in advance.

Question 10

What happens to our data?

Accepted Answer

Your data stays yours. We work to the access you grant us and no more, we scope where data is processed and stored during design so you approve it before anything is built, and assistants follow your existing permission model rather than working around it.

Question 11

Do your chatbots and assistants work in Arabic?

Accepted Answer

Yes, natively. Arabic is not a translation layer we add at the end — it is designed in from the first sketch, including right-to-left layout and the way people actually phrase questions in Arabic versus English.

Question 12

Who owns what you build?

Accepted Answer

You do. The workflows, the code, the documentation and the data belong to you. We do not build architecture that makes leaving expensive.

Question 13

How do you price engagements?

Accepted Answer

Per project, scoped after the consultation, with the number agreed before work starts. We do not quote before understanding the process, because a quote made without that is a guess you would end up paying for.

Question 14

What happens after a workflow goes live?

Accepted Answer

We measure what it actually returns against the baseline the consultation established, tune it against real usage, and — if it earns it — move on to the next process. Ongoing support is agreed explicitly rather than assumed.

Questions, answered directly

Getting started

How we work

Technical & data

Commercial

Still have a question?