KaishiftKaishift

Kaishift · Casablanca

Workflow automation agency: connect the tools you already pay for

A workflow automation agency connects the software a company already owns so work stops being re-typed from one system into another. Kaishift maps the process costing you the most hours, builds it on accounts you own, and stays to run it after launch. Your first deliverable arrives in weeks, and the first two weeks are refundable.

Most companies do not have a tools problem. They have a gap between tools, and someone paid to stand in it: copying a name out of an inbox into the CRM, then into a spreadsheet, then onto an invoice. That person is not slow. The gap is.

Workflow automation is a fixed sequence a machine runs on your behalf: when X happens, do Y, then Z. It runs the same way every time, with no judgment and no decisions outside the rules you wrote. Engines like n8n, Make and Zapier are built for exactly this, and a good share of what gets sold as AI is really this.

What does a workflow automation agency actually do?

Four things, in this order.

Write the work down. Before anything is built, the process gets described as steps: what triggers it, who touches it, which system holds the true record, where it stalls. Much of the value shows up here, because plenty of the workflows we are asked to automate contain a step nobody has needed for two years.

Connect what you already run. Your CRM, accounting tool, inbox, drive, booking platform, spreadsheets, WhatsApp. We do not replace them and we do not resell them. A record entered once should appear everywhere it belongs, without a second person typing it.

Ship something you use this month. A flow that is running, with the error cases handled and the alerts pointed at a channel your team actually reads.

Run it after launch. Automations break when a supplier changes an export format or a login expires. We monitor what we ship, fix it, and send a written note covering what ran and what changed.

Where the re-typing actually happens

The workflows that pay for themselves first are rarely the exciting ones.

  • A lead arrives from a form, an ad or WhatsApp and gets entered into the CRM by hand, hours later.
  • An invoice goes out and nobody chases it until someone remembers.
  • Two systems hold the same customer and disagree about the phone number.
  • A weekly report is assembled by copying figures out of three dashboards.
  • Every new client means creating the same record in five places.
  • A signed document lands in an inbox and a human reads the PDF to type its data into a system.

All of it needs the same two things: a rule that runs without being reminded, and someone to own it when it breaks.

Workflow automation or an AI agent?

They get sold as the same thing, and buying the wrong one is expensive. The short version:

  • A workflow runs the steps you wrote. An agent is handed a goal and picks the steps itself.
  • Workflows want structured input: a form, a webhook, a row. Agents earn their cost on messy input: an email, a voice note, a scanned invoice.
  • A workflow that breaks stops and tells you where. An agent that goes wrong carries on confidently, which is why every action it takes is logged.

Most systems we ship use both, with the one judgment step handed to an agent and handed straight back. If the whole job is judgment, you are looking at AI agent development. The full comparison, including which to buy for a given process, is in AI agents vs. workflow automation.

Who this is for, and who it is not for

This is for you if a known process runs several times a week, touches more than one system, and currently depends on a person remembering. It is also for you if an earlier automation was built by someone who has gone quiet, and you cannot see inside it.

This is not for you if the process changes every week because nobody has decided what it should be. Automating an undecided process only makes the confusion faster. It is also not for you if you want a demo to show a board, or if you would rather somebody else held the keys. We build the opposite of that.

What you own when it ships

Everything. It runs on your cloud, your repositories and your API keys, documented well enough that your own team can change it without calling us. The open-source parts we self-host, n8n, Supabase and Coolify, put no licence line on any invoice. Pay-per-use services such as model APIs and hosting are billed to your own account, at cost, with no markup. The test is one question: can you log in and read every line right now, without asking us. That is the whole argument in own your automation stack. Our terms and privacy policy are published in full, so your legal team can read them before the call.

How the engagement works

There is no price list, on purpose. No two companies hurt in the same place, so packages would be guesswork. You describe the workflow that hurts on a thirty-minute call. We map it, and a scoped, priced roadmap lands in your inbox within 48 hours, yours to keep whether you hire us or not. The first deliverable is working software in weeks, and the first two weeks are refundable if it does not convince you.

What a Casablanca base gives you

We build from Casablanca and deliver wherever the work is. Three things about that matter for automation work. We build and support in English, French, Arabic and Spanish, including right-to-left interfaces and Darija in customer-facing flows. Casablanca sits at UTC+1, which shares a working day with Europe, overlaps the Gulf, and still catches the North American East Coast, so a flow that breaks at 09:00 gets looked at at 09:00. And Morocco is the 55th state party to Convention 108, the Council of Europe convention on data protection, in force since 1 September 2019, which is the footing a European legal team usually checks first. Where your data physically sits stays your decision either way, because the hosting runs in the region you choose, on your account. The longer version of what a Casablanca base changes is on our AI automation agency in Casablanca page.

Kaishift is run by its founders, Sami Khalfi and Amine Lamfichekh, hands on keyboards. Workflow automation is how the back office floor gets built, the first of the five we run as an AI automation agency: back office, development, AI agents, infrastructure and security. You can take the tower tour to see how they stack, and more of the reasoning behind these choices sits on the blog.

Bring the workflow that hurts most. Thirty minutes on a call, and you leave with the map, whichever way you decide.

Common questions

What is workflow automation?

Workflow automation is software running a fixed sequence for you: when something happens, a set of steps you defined runs the same way every time. A form arrives, a record is created, a reminder goes out, a report is filed. No judgment is involved, which is exactly what makes it cheap to run and simple to audit.

How is workflow automation different from an AI agent?

A workflow follows the steps you wrote. An agent is given a goal and works out the steps itself, including in situations nobody scripted. Buy a workflow when the job can be written down as a fixed sequence: when X happens, do Y, then Z. Buy an agent for the one step that needs a message interpreted before anything else can happen.

Do we have to replace the tools we already use?

No. The point is the opposite. Your CRM, accounting tool, inbox, drive, booking platform and messaging apps stay where they are, and we connect them so a record entered once appears everywhere it belongs. We do not resell software, so there is nothing we gain from moving you off what already works.

How long before the first automation is running?

Weeks, not quarters. We map the workflow on a thirty-minute call, send a scoped and priced roadmap within 48 hours, and the first deliverable is something working in your hands. If it does not convince you, the first two weeks of the engagement are refundable, with no conversation needed.

Who owns the automation once it is built?

You do, from day one. It runs on your cloud, your repos and your API keys, with a written record of what runs where. Anything we self-host stays open source. If we disappeared tomorrow, nothing breaks and nothing sits behind a login you do not hold.

Start with a call

Describe where the work hurts. You leave with a written roadmap of the first three moves, whether we work together or not.

Book a call
← Kaishift