Workflow automation

The steps you do by hand every day run in the background on their own.

A proposal is approved, the invoice is raised, the client gets an email and the record is updated, with nobody doing it by hand. Every workflow sits on one dashboard, so you see which one is running from the same screen. If a step fails, you hear about it.

The tools we use

  • n8n
  • Make
  • Zapier
  • Airtable
  • Supabase
  • GitHub
  • Docker
How it works

First we work out how the job runs today,then we choose the tool.

We write down how many steps a job takes today and whose hands it passes through. The choice of tool is made from that table. Once the workflow is built, every run is followed on the dashboard.

We list the steps of the jobWhich step is done by hand, and which one can follow a rule?

The tool is chosen and the workflow builtHow long each step takes by hand and in the workflow sits side by side.

Workflows are followed from one dashboardWhen each workflow ran, and how often, shows on the same screen.

The parts of a workflow

The workflow takes on the repeated step,and asks you where approval is needed.

Every workflow is built from the same parts: the event that starts it, the steps, what happens on a failure and the approval point. Because the rule is written down, the result is the same whoever builds it.

A workflow starts with an event

A new record in the CRM, a WhatsApp message, an email in the inbox or a set time of day can start a workflow. Which event starts what is written down.

Every run is logged

When the workflow ran, with which record and with what result goes into the log. Every past run can be followed from the same place.

Failures do not stay quiet

A failed run is reported to its owner, its cause is written down and it is retried. If the retry fails too, the workflow stops and you hear about it.

Hard-to-reverse steps wait for approval

Steps such as a payment, a bulk send or deleting records get an approval point. The workflow stops there and waits for a person to approve.

Start with one workflow, then grow

The first set-up takes on the single workflow that costs the most time. Once it is measured and settled, the next one is added.

Every workflow shows on one dashboard

Each workflow we build appears on the same dashboard: how often it ran, how long it took and whether a failure is waiting. Other systems we build connect to the same dashboard too.

Monthly report

How much work your workflows didreaches you at the end of every month.

The report shows how often each workflow ran, the share of runs without error and any failures waiting. We decide together from this report which workflow to grow or change.

  • Every workflow sits on one dashboard
  • Every run is logged
  • You hear about every failure
Request a sample workflow report
Frequently asked

Workflow automation Frequently asked questions

Any job done in the same order every time can be automated. Examples are raising the invoice once a proposal is approved, adding a new client to the CRM, sending the weekly report and filing a document in the right folder. A step that needs judgement stays in the workflow as an approval point.

It depends on the job. If data must stay on your own server, n8n; for a visual, mid-sized workflow, Make; for a simple link between common programs, Zapier. The reasoning is written into the discovery report.

A failed run is reported to its owner, its cause is written down and it is retried. If the retry fails too, the workflow stops and you hear about it; no workflow stops quietly.

n8n runs on your own server, so data does not leave. If Make or Zapier is chosen, which information goes to that service is written down at set-up; sensitive information never enters a cloud workflow.

Yes. The workflows sit in your account or on your server and are handed over with their documentation. When you want to take them over, we walk your team through them.

Steps such as payments, bulk sends and record deletion get an approval point. The workflow stops there and waits for a person; it does not go on without approval.

We start with the single workflow that takes the most time. A wide scope on day one delays the first workflow; the second is added once the first is measured and settled.

Discovery takes a week. In that week we list the steps, the exceptions and the programs to connect, and choose the tool with its reasoning. The first live workflow opens within 4-8 weeks, depending on the number of steps, the systems to connect and the approval points. The exact timeline for you is written in the discovery report.

Two things are measured during discovery: how long a step takes by hand and how often it repeats each week. Both are measured again once the workflow is running, next to the share of runs without error.

The tools we use

We do not pick the tool first,we pick it once we understand the work.

n8n runs on your own server and keeps data in. Make is quick to build for visual flows, and Zapier stands out for its number of ready connections. Why a tool was chosen is written in the discovery report.

n8n

Runs on your own server, so data does not leave. Chosen for workflows with many steps or sensitive information.

Make

Visual flows in the cloud; quick to build for mid-sized jobs with many steps.

Zapier

A wide list of ready connections; chosen for simple flows between common programs.

Our own code

Where no tool is enough, written on your own infrastructure to fit your work.

Airtable

A light data layer for small tables and approval lists; your team edits it directly.

Scheduled jobs

Overnight batches and reports; large data is processed on your own server.

Where this is used

Mert Can Gundogdu
The founder takes the call, not a sales team
Next step

We write the proposal after we have found the problem together

In a thirty-minute call we listen to how you work and talk through where time and customers are slipping away. If you do not need a digital fix, we will tell you that too.

30 minutes · no preparation needed

Chat on WhatsApp