Skip to content

Workflow Automation · revamps Labs

Workflow automation that ends the copy, paste and chase.

revamps Labs connects the tools you already run (forms, CRM, email, WhatsApp, invoicing, spreadsheets, booking) so enquiries reach an owner, follow-ups go out on time, records stay in sync and reports build themselves. AI only where it pays. Every flow monitored, with a person on every exception.

LABS / WORKFLOW AUTOMATION
  • Every flow monitored, with a named owner
  • A person on every exception
  • Built in accounts you own
  • Colombo team · Sri Lanka and international

The problem

Your tools are connected. Through one person.

An enquiry arrives by form or WhatsApp and waits for someone to notice. Its details are typed into the CRM, a spreadsheet and an invoice, and month-end costs a day of exports. Leads cool, records disagree, and the process stops when that person is away. We connect the steps and watch them run. Now nothing waits on memory.

  1. 01

    Leads wait for a reply

    A form fills an inbox, a WhatsApp message sits unread, and the first reply depends on who noticed. By then the buyer has asked someone else.

  2. 02

    One person is the integration

    Details are copied from the form to the CRM, the sheet and the invoice. When that person is busy or away, the process stops.

  3. 03

    Records that disagree

    The CRM says one thing, the spreadsheet another, the accounts a third. Nobody trusts a number without checking all three.

  4. 04

    Reports built by hand

    Month-end means exports, pasted tables and a day of someone's time, and the figures are stale by the time anyone reads them.

  • EXAMPLE — HOW IT WORKS
  • ORANGE HIGHLIGHTS THE ACTIVE PATH OR RESULT

How a revamps automation works

Trigger. Route. Act. Record. One flow.

Every flow we build follows the same path. Something happens, rules choose the owner, data is looked up or classified, the next action fires, every system is updated and a report shows what happened. When a step fails or the AI is unsure, a person is told. Most automations skip that part.

Hover or tap a node

Illustrative system map, not client data. Which tools sit under each node is decided in the process map. AI is used at 03 only where it beats a rule; anything it cannot classify goes to a person. If your team needs a new screen to do the work, that is App Development.

The process

From the first handoff to a flow you can monitor.

Five steps, each closed by a sign-off, so the process is agreed before anything is built and you know who owns each flow on the day it goes live.

  1. 01

    Enquiry and reply

    Tell us the step someone re-types or the follow-up that slips. We reply with the questions that matter and the tools we would need access to.

    Within 2 business days

  2. 02

    Map the process

    We sit with the people doing the work and map every step, tool, owner, exception and piece of personal data, then rank the handoffs worth automating. Then a written scope.

  3. 03

    Design the flow

    Triggers, rules, exceptions, approvals and the human fallback, signed off before anything is built. Where AI would help, we say why and what it costs to run.

  4. 04

    Build and test

    Flows built in accounts you own and tested with real records and the edge cases from the map: duplicates, missing fields, a tool that is down.

  5. 05

    Go live, monitor, hand over

    Live with a named owner, a run log and a written note per flow: what triggers it, what it changes, how to pause it. Then we fix what real use shows.

What's included

You don't need more tools. You need them connected.

Six workstreams in every project. Depth changes by tier: how many flows and tools, how many exceptions and approvals, and how much AI and monitoring.

  • Process map

    Every step, tool, owner and exception in the current process, with the handoffs ranked by time lost and risk. Agreed before anything is built.

  • Integrations

    Forms, CRM, email, WhatsApp Business, invoicing, spreadsheets, booking and your CMS, connected through their APIs.

  • Rules and exceptions

    Routing, conditions, approvals and what happens when data is missing or duplicated, written down and tested with real records.

  • AI-assisted steps

    Classifying enquiries, drafting replies, qualifying leads, reading documents: only where they beat a rule, on paid accounts in your name, with a person for anything unclear.

  • Monitoring and fallback

    A run log, a named owner for every flow, retries where safe, and a manual path so work continues when a tool is down.

  • Handover and notes

    A written note per flow (trigger, changes, owner, how to pause it), access to every account, and a walkthrough for the people who own it.

Fit

Automation can't fix a broken process. It can make a clear one fast.

Automation repeats a process exactly, mistakes included. A short scoping call tells us both whether yours is ready to automate or needs mapping first.

  • A good fit if

    Someone re-types data between tools, or follow-ups depend on memory. The process runs much the same each week and someone owns it. Your tools have APIs, or you will switch.

  • Not a fit if

    You want everything automated at once. Nobody agrees on the process yet. You want messages sent to people who never opted in. You want AI to decide things nobody checks.

  • Where automation stops

    If people need a new screen to do the work, that is App Development. If you are still deciding what to automate across teams, start with Strategic Consultancy. If a product you can buy already does it, buy it.

revamps Labs · Our own flow

We automated our own enquiries first.

This is the method, shown on the flow behind the form at the bottom of this page. It is revamps' own system, a worked example and not a client result. Each rule below is one we apply to client flows. The chat in the corner is Reva, our AI step.

  • Record first, then notify

    Our form saves each enquiry to a database in one transaction before anyone is pinged, so a failed notification never loses a lead.

  • Counted without a spreadsheet

    A lead event carries the service it was for, so enquiries per service show up in analytics without anyone tallying them.

  • Only verified triggers

    Publishing a change in our CMS sends a signed webhook. The site checks the signature before refreshing the affected pages and ignores anything it cannot verify.

Reva

AI website chat and qualification. Reva answers visitor questions, qualifies the enquiry and routes it to the right person. It is running on this site now.

Questions

Ask what breaks before you automate.

Do we need custom software or an automation?

If a product you can buy already does the job, buy it; we will say so. If people need a new screen to do the work, it is App Development. If the screens exist and only the hand-offs are manual, start with Workflow Automation.

Can you automate WhatsApp messages?

Yes, through the official WhatsApp Business Platform, on a number your business owns. Meta requires opt-in before you message people and a clear path to a human in automated chats, and charges per delivered template message. We do not send bulk messages to people who have not opted in.

Do you help redesign the process before automating it?

Yes. Automating a bad process usually creates faster confusion, so process redesign is often part of the engagement.

Can we start with one team or one workflow first?

Yes. A focused pilot is often the right way to validate the automation model before expanding it across the business.

Enquire

Tell us the step someone re-types. We'll come back with the scope.

Four short fields, about a minute. Name the tools involved and who does the step today. We reply within 2 business days with the questions that set the scope and a time for a short call. No automated sales sequence: we automate the admin, not the conversation.

Prefer email? [email protected]

Fields marked * are required.

The tools involved (form, CRM, WhatsApp, sheet, invoicing), who does it today and roughly how often.