SOAR AI

What working together looks like

Four stages, and the first two cost nothing and commit you to nothing.

1

Process diagnosis

Thirty minutes (free).

We walk through the whole process from start to finish, meaning where enquiries come in, what happens to them next, who owns which stage and how long should pass between one and the next. Separately I ask what happens in the isolated cases, because the rule usually works well enough and only the exceptions to it show where the process actually jams.

You leave that call with a list of two or three things that can be automated at your company fastest, and the list stays yours regardless of what you decide next.

On your side: half an hour and someone who knows the process from the inside.

2

Planning

A few days after the call (still no commitment).

Once I know what can be automated at your company I write up how to do it and you get the scope, the order of work and a date. If you would rather not do everything at once we split it into stages so that each one ends with something usable straight away, rather than only once the whole thing closes.

In the same document I list what I will need from you, meaning which accounts and tools I need access to, which keys have to be generated and who on the team needs to be reachable to answer questions while I build. You get all of it before we sign anything, so nothing surfaces halfway through the project.

On your side: reading the plan and saying what does not add up.

3

Delivery

Usually two to four weeks for the first process.

I build the solution on your accounts and with your keys, so nothing sits on my side and you are not dependent on me now or later.

I test on your real data, anonymised beforehand, rather than on made up examples. Only there do those exceptions to the rule show up that I asked about at the start, meaning an invoice in an unusual layout, a client who sends everything as an attachment or an order missing half its fields, and those are exactly the things no demonstration ever shows. Along the way I show you working pieces so you can say something is off before I build the rest on top of it.

On your side: the access agreed earlier in the plan and one person who answers questions along the way.

4

Handover and growth

A few days after launch.

You get documentation and we go through together what to do when something breaks, and you are left with a working system that you develop yourself, with your team or further with me. If in a year you wanted to move all of it elsewhere you will move it, because nothing is tied to me.

On your side: nothing at this stage, the handover is on me.

What I do not do

I do not sell a subscription for something that can be closed once and I do not build on platforms you cannot later leave. I also do not start from building if after the call I can see that setting up properly what you already have is enough, because then it is a waste of your money on a rollout you do not need.

Start with a call

Thirty minutes with no commitment, after which you leave with a list of processes to automate even if nothing further comes of it.

Book a call