How an automation project runs Survey first. Then build.

Every engagement starts with a Flow Audit, so the quote you get is for work worth doing — not a guess. Four stages, one continuous flow, and you sign off before anything is built.

01 · Survey

The Flow Audit

We sit with the people who do the work, map how it really runs, and measure where time and accuracy leak.

What happens

  • Short sessions with the people who do the work — on site in Sri Lanka or over video
  • Every step, hand-off and spreadsheet mapped as it really runs, not as the manual says
  • Time, errors and waiting measured where they happen
  • Opportunities ranked by value and effort, with an honest “not worth it” where it applies

From your side

An owner for the process and an hour or two with the people who run it.

You get

Process maps · ranked opportunities · a fixed quote

02 · Design

The blueprint

Every step, owner and rule — where AI reads and where a person approves. You sign it off before we build.

What happens

  • The new flow drawn step by step: triggers, rules, AI steps, approvals, actions
  • Where it runs and which tools it uses — chosen for your size, budget and data
  • The data path documented: what each step can see and change
  • Exceptions decided up front: who is told, and what happens next

From your side

A review of the blueprint and a sign-off. Nothing is built before it.

You get

Blueprint · tool choice · security plan

03 · Build

Connect & launch

Built on the systems you already run, tested on real data, and run beside the old way until your team trusts it.

What happens

  • Built on the systems and accounts you already have
  • Tested on your real cases, including the awkward ones
  • Run alongside the old way until the results match
  • Your team trained, and every flow documented in plain language

From your side

Test cases, access to the systems involved, and people to try it.

You get

Live flows · documentation · training

04 · Steward

Flow Care

Every run monitored, fixed when other systems change, and reviewed with you monthly to find the next win.

What happens

  • Every run monitored, with failures caught before your customers notice
  • Flows kept working when WhatsApp, your bank or your software changes
  • Small changes made as your process changes
  • A monthly review: what ran, what failed, what to automate next

From your side

A monthly conversation. That’s it.

You get

Monitoring · fixes · monthly roadmap

After launch

Flow Care. Flows that keep working.

Automations don’t fail on launch day. They fail months later, when an app updates or a bank changes a format. Flow Care is how we make sure that never becomes your problem.

01

Monitoring

Every run is watched. When one fails, we know first — and fix it or tell you what needs a person.

02

Upkeep

APIs, apps and banks change. We keep each flow working when the systems around it do.

03

Small changes

A new approver, a new product, a new branch: adjustments to live flows are part of Flow Care.

04

Monthly review

What ran, what failed and what it saved, plus the next flow worth building.

Where it runs

Your data, where you want it.

We build with whatever suits the job — n8n, Make, Zapier if you already use it, and custom code in Node.js or Java when a flow needs it — and run it in one of three ways.

Run by us

The quickest start.

We host and run the flows on Flowra’s infrastructure. Your credentials stay on your accounts.

Fits · Startups and small teams

On your accounts

Your subscriptions, our work.

Built on the n8n, Make or Zapier account you own. If we part ways, everything stays with you.

Fits · Teams with tools already in place

In your cloud

Automation as infrastructure.

Self-hosted in your AWS, Azure or Google Cloud — or your own data centre — under your change control.

Fits · Enterprise and regulated work

Principles

How every flow is built.

You own everything

Every workflow, credential and document is yours. No lock-in to us or to a platform.

Least access

Each flow gets only the access it needs, and its data path is written down before we build.

People keep the decisions

Where a mistake would be costly, a person approves before anything is sent or posted.

Every AI step is logged

What it read, what it decided and how sure it was — so you can check it.

Beside the old way first

New flows run in parallel until the results match and your team trusts them.

Plain documentation

Written for the people who run the process, not just for engineers.

Pricing

No surprises. No hourly billing.

Every business is different, so we don’t publish prices. What we do publish is how pricing works — the same way for every client.

  1. Flow AuditQuoted up front

    From your size and scope, before we start.

  2. BuildA fixed quote

    For the work the audit found worth doing.

  3. Flow CareA monthly fee

    Agreed in advance. Monitoring, fixes and the monthly review.

Start with the audit: what it covers and how to book it.

FAQ

Fair questions.

Anything else? hello@techzap.co.uk

How much does it cost?

Every business is different, so we don’t publish prices. The Flow Audit is quoted up front from your size and scope. After it you get a fixed quote for the build, and Flow Care is a monthly fee agreed in advance. No open-ended hourly billing.

Do we have to replace our software?

No. Flowra connects what you already run — WhatsApp, email, spreadsheets, your accounting system, CRM or ERP. Replacing systems is rarely the cheapest way to fix a process.

What do you build with?

Whatever suits the job: n8n (hosted by us or self-hosted by you), Make, Zapier if you already use it, and custom code in Node.js or Java when a flow needs it. Every workflow, credential and document is yours.

Where does AI come in?

As a step, not the show. AI reads the messy inputs — chat orders, invoices, receipts, emails — and drafts replies. Where a mistake would be costly, a person approves before anything is sent or posted, and every AI step is logged. For bespoke AI agents and copilots, our sister company ZENTIQ does that work.

Is our data safe?

Each flow gets the least access it needs, credentials stay on your accounts, and everything can run inside your own cloud. The data path of every flow is documented before we build it.

Do you work outside Sri Lanka?

Yes. We started in Sri Lanka and work remotely with teams in the UK, Australia, the Gulf and beyond. The Flow Audit runs just as well over video calls, in your time zone.

How long does it take?

A single focused flow can be live in a few weeks. Larger programmes are delivered in phases, highest value first, so you see results early.

Bring us one process that frustrates your team.

In a Flow Audit we map how it really runs, show where it leaks, and tell you honestly what is worth automating — with a fixed quote for the work.