◆ How this works

What I touch, what I don't, and what happens if it breaks.

You're about to give a stranger access to the systems your business runs on. Here is everything I'd want to know first.

What I will never ask for

I never need your bank login, your payment processor credentials, your card details, or your customers' payment information. No system I build touches any of it. If anyone asks you for those to set up an automation, that's your signal to stop.

What I do need, and why

Read and write access to the specific systems your automation touches — usually a staff account on your store limited to products, orders and inventory, plus API access to your marketplaces. I send you the exact list before you pay, and I ask for the narrowest permissions that will do the job.

Where your data lives

Your automations run on Make, an established automation platform. Data passes through it to do its job and isn't retained beyond what the platform needs to run and log the workflow. I don't copy your catalogue, your customer list or your order history anywhere else. Where an AI model writes text — a review reply, an email draft — it sees only the content of that one item.

Who owns the automations

You do. They're built in your account where the platform allows it, or handed over in full if not. If you cancel, you get the working scenarios, the credentials and the documentation. There is no version of this where leaving means losing what you paid for. I have no interest in holding anybody hostage.

◆ When something breaks

Honest response times

📡

Monitoring

Continuous and automated. Everything I build alerts me before it alerts you.

🕐

Normal issues

Same business day, Monday to Friday. Anything that isn't costing you money by the minute waits its turn.

🚨

Urgent issues

Two hours, any day. That means a sync writing wrong stock numbers, or a phone agent down during your open hours — the two that cost you money while you wait.

And you have an off switch

Every system I build comes with a kill switch you control and know how to use. If something looks wrong at 11pm, you don't have to wait for me — you stop it yourself and we sort it in the morning. Your business should never be stuck waiting on one person to wake up.

What I will not promise

I won't quote you an uptime percentage. I don't control Amazon's API, Shopify's, or your internet connection, and any number I gave you would be marketing rather than a commitment. What I will commit to is how fast I respond and what I do when something goes wrong — because those are actually mine to control.

Still have a question?

Ask it before you spend anything. If I can't answer it plainly, don't hire me.

Book a call →