Everything you would ask us on the call.

Before the audit

What do I actually get back?

A written report by email: your score out of 100, the band it falls in, your three biggest leaks ranked, the hours and dollars each one costs, and a roadmap for closing them. A PDF copy comes attached.

How long does it take?

About 4 to 6 minutes to fill in. 15 questions, most of them tick boxes. The report comes back by email.

What does it cost?

Nothing. The audit is free and no call is needed to get it.

Do I have to give you access to my accounts?

No. The report is built from the form alone. No ad account, CRM or analytics access is needed to get it.

Is this a sales call in disguise?

No. You get the report first. A call is yours to book, not ours to push.

What if I already have someone doing this?

Then the audit finds work to hand them. It measures the leak, it does not assume you have nobody.

Before buying

What does an implementation cost, and can I start small?

You can start with one workflow, not a system. Most first builds are a single automation, the narrowest one that costs you the most time, and the free audit tells you which one that is. We scope it and quote after that, not before. It is a one-time build, not a monthly retainer.

How long until it is live and running on its own?

Two stages, and the clock starts at the second one. First the blueprint: a written map of what changes, what it connects to and what you approve. Then the build runs inside your stack. You get the build date with the blueprint, once the scope is fixed, so the date you are given is one we can keep.

Who owns what you build?

You do. The workflow stays your property, and handover includes the documentation and the training to run it without us.

Do you replace my team?

No. It removes the manual work, not the people. The handover step exists so your team can run it without us.

What if it does not work?

"Working" is defined in writing before we start. You approve a written blueprint first, so what the build should do is agreed on both sides before any of it exists. If a step does not do what the blueprint says, we fix it. Then a check-in about 30 days after handover, with your own numbers, while support is still open.

About the build

Is this no-code or code?

Both, depending on what the job needs. Most of what we build runs on workflow tooling you can open, read and edit yourself.

What happens when a platform changes its API?

The automation lives in your stack, so when a step breaks it is visible in your own tooling rather than inside a black box. That is also why the handover matters: the person who can fix it is already on your team.

Can you work with what we already run?

Usually yes, and that is the point. The build happens inside the tools you already pay for rather than replacing them. Anything outside the core list is scoped first.

What if my stack is not on your list?

If it has an API, it can join the workflow. Meta, Google, TikTok, Klaviyo, Shopify, GA4, Looker Studio, Slack, Notion and Sheets are covered with no extra work. Anything outside that list joins through its API or webhook. If a tool has neither, we tell you before you pay, not after.

Where does my data live?

In your accounts, not ours. Implementations run on your credentials inside your own tools, and nothing is copied into a system we own. The audit form is the one exception: your answers are stored in our Google Workspace so we can build and send your report.