Contact

Work that runs itself, and knows when to ask.

ADK Creatives builds AI automation for businesses doing the same work by hand every day. Assistants that answer in your voice, work that sorts and routes itself, and a back office that stops needing anyone to retype anything.

Start a build The menu

01 Brief the problem, in your words

The automation pipeline: a paper courier walks a rail past seven paper stations, Brief, Router, Build, Audit, Docs, Gate and Handoff, the seven steps of an automation build. A1 A2 A3 A4 A5 A6 A7 Brief Router Build Audit Docs Gate Handoff
One build

Four steps, one of them yours.

Every automation the studio ships has the same shape. It arrives, it finds its way, someone decides, and the rest follows. Three of those four run without you. The one that does not is the reason the work is worth doing, so it stays with you. The studio's own systems are built on that shape too. The website assistant on this page is one of them, drawn out step by step.

ADK / build / AI AutomationIdle
One build, four stepsOnly the Decision step needs a person
IntakeRoutingDecisionHandoffYour accounts
  1. An automation takes shape
  2. Start with the problem you want to solve
  3. shape: intake, routing, decision, handoff
  4. connecting your inbox and your site, in your accounts
  5. decision step: anything unsure goes to a person
  6. Give the assistant the information it can answer from
  7. dry run: sample messages routed, the unsure ones handed over
  8. handoff: keys, accounts and the written notes in your name
  9. build ready for a person to sign off
Build walkthrough
An automation, step by stepThe log is scripted as an illustration; the two counted tiles are real
How it works

How a build runs, and what you walk away with.

You need nothing before starting: no brief written, no files gathered, no budget worked out. Turn up with the problem and the call works out what it actually needs.

Timeline
One to four weeks, depending on scope. Typical rather than promised; the real timeline comes with the written proposal.
Ownership
The accounts and the keys belong to you from day one. The studio works with delegated access, so nothing sits inside its accounts and nothing has to be transferred later.
Payment
Scope sets the number. Every build is priced personally, in a written proposal, and there is a written agreement on every build.
After handover
If something is broken or is not what was agreed, the studio puts it right, and that is not chargeable. Ongoing care is available for changes as they come up.

A personal reply arrives within a day or two of the form, then a call, then the proposal, then the build. How the studio works.

Fair questions

The questions people actually ask.

You are deciding whether to put your customers and your data in the studio's hands. These deserve straight answers.

01Is my data used to train AI models?

No. Client data is not used to train AI models. If you want the technical detail of how that is set up, it comes from Kobby on the call.

02Where does the data live?

In your own accounts. The same rule the studio follows for domains and hosting applies to automations: the accounts and the keys belong to you from day one, and the studio works with delegated access. No part of your business sits inside the studio's accounts, so nothing has to be transferred later, because it was never held.

03What does it cost to run?

The AI usage and any tool subscriptions run on your own accounts, so you hold the billing and can see exactly what is being used. What that comes to depends on the build, and it is worked through with you before anything runs.

04What happens when the assistant gets something wrong?

It will, sometimes, and nobody should tell you otherwise. An assistant the studio builds is given a defined body of knowledge and answers from it, and hands anything outside that to a person rather than guess. Only the Decision step needs a human, and anything the assistant is unsure about becomes a decision.

The assistant on this page works exactly that way. Ask it something it cannot know and watch what it does.

05Which AI do you use?

Whichever fits the job. The studio is not tied to one provider. If you have a preference, or a company you will not use, say so and it is covered on the call.

06Can it hand over to a person?

Every automation the studio builds has a route to a human, designed in rather than bolted on. It is the same four step shape every time, Intake, Routing, Decision, Handoff, and only the Decision step needs a person.

07What if a provider changes, breaks, or raises its prices?

Builds are made to keep working, and ongoing care is available if you want the studio to keep an eye on things and make changes as they come up. The arrangement exists; the details come from Kobby personally.

08Will it replace my staff?

No, and the studio will not sell it that way. We automate the work, not the judgment: the repeatable part runs on its own, and the part that needs a person stays with a person.

09How many rounds of changes do I get?

That depends on the scope of the build, and the written proposal sets it out rather than a number promised here. Telling the studio a system is not behaving the way you need it to is the process working, not a complaint. Work moves through feedback rather than landing right first time.

10What don't you take on for an automation build?

Mobile apps: the studio builds for the web, not app stores. Paid ads and media buying. Online stores with carts and checkout. If one of those is the real problem, say so in the first message and you will hear straight away rather than three emails in.

Turn up with the problem, not a brief.

A personal reply within a day or two, then a call, then a written proposal. Nothing to prepare first.

Start a build

ADK / start a buildIdle
Open for builds

Start an automation build.

Tell us what is eating the week. We will tell you the shortest path to a system that takes it off you.

0 / 2000

Prefer email? kobby@adk-creatives.com