Try it Services Pricing Process About FAQ Insights IntelliA · live chat Versión en español Free consultation →

What someone copies today
from one screen to another.

Almost every business has someone moving data from one screen to another. That's a process, not a job. It can be automated, and what your team gains is the time that goes today into copying, pasting and double-checking.

Watch an order nobody retyped.

Monday, 06:52, nobody in the office yet: a 14-line purchase order arrives by email. It plays on its own, with the clock sped up: watch the flow read it, check it against your price list, stop at the one line that doesn't match, and wait for a person before writing anything.

Ferretería Ortiz · Purchase order 0932 Email

What the flow does, exactly as the log records it

  1. Monday, 06:52

    • Ferretería Ortiz · PurchasingPurchase order 0932 · PDF attached
    • ReadOpens the PDF, pulls out the 14 lines with quantity and price, and recognises the customer by tax ID: 30-day credit, nothing overdue.
  2. Monday, 06:52

    • ValidateChecks every line against the current price list and the stock: 13 of 14 match.
    • On holdLine 9: 40 half-inch PVC pipes at USD 3.85. The current list says 4.10. A price nobody authorised doesn't get recorded.
  3. Monday, 06:53

    • NotifyMessages Verónica, in sales, on WhatsApp:
    • Verónica, order 0932 from Ferretería Ortiz is on hold on a single line: the half-inch PVC pipe comes in at 3.85 and the current list says 4.10. Do I honour it on this order or correct it? Everything else is ready to be entered.
  4. Monday, 08:14

    • An hour and 21 minutes without writing a thing: the order waits for Verónica to get in and answer.
    • Honour the 3.85 on this order and let them know the next one goes at the current list price.
  5. Monday, 08:14

    • WriteEnters order 4471 with all 14 lines. On line 9 it notes the exception: 3.85 authorised by Verónica at 08:14, for this order only.
  6. Monday, 08:15

    • ConfirmReplies to Ferretería Ortiz in the same email thread: order 4471 received, shipping on Wednesday, and a note that from the next order the current list applies.
    • Nobody retyped the order. The flow read all 14 lines, validated the 13 that matched and stopped at the one that didn't, without making up a price. Verónica decided one thing, in one line on WhatsApp, and the log keeps every step with its time: it can be audited without taking the system's word for it.

A demonstration with an invented business: the distributor, the hardware store, the order and the people do not exist. The steps are the ones a flow like this would take; what gets held and who decides is agreed with each client. In a real project the flow first runs alongside the manual process, and the manual one is switched off only once the two have matched several times.

What it does, exactly

This isn't sold from a catalogue: every case is different, which is why it's studied before it's quoted. What does repeat is the shape:

  • Connecting systems that don't talk to each other today: CRM, ERP, spreadsheets, email, payment gateways.
  • Running the whole repetitive task, not a piece of it: read, validate, write and confirm.
  • Flagging the exception, which is the only part that genuinely needs a person.
  • Leaving a record of what was done and when, so it can be audited instead of taken on the system's word.

How it's done

The price of this doesn't come from a range: it comes from looking at the process. That's why the chat doesn't quote custom automation — it takes the case and books the consultation.

  1. The map. We follow the process as it actually is today, with the person who does it, not the person who describes it.
  2. The cut. We decide what gets automated and what stays with a person. Not everything should be automated.
  3. The build. Each system is connected through its API and tested with real data, running alongside the current process.
  4. The handover. Only once the automatic flow matches the manual one several times does the manual one get switched off.

What you need to provide

  • That the systems you want connected have an API. If one doesn't, we find another route or we tell you it can't be done.
  • The owner of the process: someone who can say “this is how it's done”.
  • Test access to the systems, with scoped permissions.

What it doesn't do

Saying it here is cheaper than finding it out in the third meeting.

  • It isn't quoted over chat or by phone: it's studied first and quoted in writing.
  • We don't promise integrations with specific brands before looking at them. Google Calendar and the WhatsApp API are included; the rest is confirmed in the consultation.
  • We don't automate a process nobody can explain. If it isn't clear by hand, automating it only makes it faster to get wrong.

What we get
asked most.

If your question isn't here, ask IntelliA: it answers at any hour.

It depends on the process, which is why there's no published range and the chat won't give you one. We look at the case in the free consultation and you get a written quote.
Yes, as long as there's a repetitive process eating hours. Company size matters less than how many times a day someone does the same thing.
We look at it. If it exposes an API, it gets connected. If it doesn't, sometimes there's another route and sometimes the honest answer is that it can't be done — and that's said in the consultation, not after invoicing.

Half an hour and
a clear map.

The consultation is free and it isn't a sales call: you leave it knowing what to automate first and what to expect. Pick a time that suits you.

Prefer to write first?