Skip to main content

Service

Business automation

Any process you do by hand twice a day is a process you can stop doing.

Automation does not start with software - it starts with asking where your time actually goes. An order read out loud to the kitchen, a work order living in WhatsApp, a price list recalculated in Excel after every change - each of these is a system we have already built for someone. We map the process as it really is, build the system that replaces the manual part, and connect it to what you already have.

Let's Talk

Prefer to write? Send an enquiry through the form

What it gives you

  • A process with no double entry - the data goes in once and reaches everywhere it needs to
  • One picture of what is happening now, instead of calling to ask
  • A documented history - recorded work can be measured and improved
  • Integration with the systems you already run instead of replacing them

Who this is for

  • A process that repeats several times a day and passes through a person whose only job in it is moving a figure from one place to another.
  • The same figure typed in twice - once into a spreadsheet, once into a system - with the two copies no longer matching.
  • There is no single picture of what is open right now, so anyone who wants to know has to call and ask.
  • Systems that already exist and work, with no connection whatsoever between them.

How the work runs, stage by stage

  1. Mapping the process as it is

    Not as it is supposed to be. Who types what, where it goes next, who waits on whom, and where someone has already built a workaround in a spreadsheet.

  2. Choosing the first piece

    One, not everything. We pick the stretch that returns the most hours relative to the work it takes, even when it is not the one you called about.

  3. Building in stages

    At the end of every stage there is something usable. That way the system meets the real process before it is finished, instead of the direction turning out to be wrong at the end.

  4. Connecting to what exists

    The existing systems stay. We connect to them, so a figure goes in once and reaches everywhere it needs to - as with the two-way ERP sync we built for the J-Cafe store.

  5. Parallel run and switchover

    The manual process keeps running until the system has proved itself on real work. A switchover done in one day with no fallback is how internal systems die.

What moves the price

Automation is priced by the process rather than by the number of screens. A project usually starts in the low thousands of shekels, and a system with integrations costs more; the range arrives in a written proposal once the process is mapped. These are the things that move it:

  • How many stages the process has and how many different people touch it.
  • Whether there is an integration, and whether the system on the other side has a documented API. Documented is days of work; absent is weeks.
  • Whether the existing data needs importing and cleaning before the system can start from it.
  • Permissions and roles: who sees what, and who is allowed to approve.
  • Whether it is internal or customer-facing. An interface a customer sees needs work an internal tool does not.
  • The timeline: a system with automations takes 4-6 weeks.

Common questions

I have several processes stuck - where do we start?

With one. On the scoping call we look at all of them and pick the one that returns the most hours relative to the work it takes. One system running in the first week is worth more than three halfway built.

Will the automation connect to the systems I already have?

That is the default. Connecting to an existing system is almost always better than replacing it - a replacement is a project of its own that adds risk without adding returned hours. If the system has a documented API, it is days of work.

How long does it take?

A system with automations: 4-6 weeks. The work is staged, so there is something usable at the end of the first stage rather than six weeks of waiting and then one release.

What if the process changes in six months?

It will change, and that is fine. This is why the code is yours and not locked into a vendor tool: a change is work on a system you own rather than a request to whoever holds it. Some changes are configuration rather than code, and the mapping stage tries to decide which up front.

Do I have to replace my current system to start?

No, and in most cases you should not. The existing system is usually not the problem - the problem is the gap between systems, where somebody types by hand. That is where we start.