We use cookies

We use essential cookies to keep the site working, and optional cookies for analytics and advertising. Non-essential cookies are off by default. You can accept all, reject all, or choose by category. Read our Cookie Policy for full details.

For finance directors and IT leads

How we work inside your systems

We make AI work inside your business, not beside it. That means working in your tools, under your accounts, with access you can see and remove. Here is exactly how.

The principle

Most AI agencies want you on their platform. We do the opposite. Everything we build lives in the systems you already own, so there is nothing to migrate, nothing to keep paying for, and nothing that stops working if we part ways.

That only works if access is handled properly. These are the rules we work to on every engagement, and they are written into every contract.

Six rules we work to

Named user access, never shared passwords

Each of us who works on your account has their own named login in your tools, with the lowest permissions that do the job. Every action is attributable to a person.

Credentials in a secure shared vault

API keys and any credentials you issue are held in a vault set up per client, with access limited to your account team. Never in documents, email, chat or code.

Everything built in your accounts

Workflows, assistants, Projects and integrations are created inside your CRM, Workspace or Microsoft 365, website and automation platform. You own them from day one.

Always-on automations run in your platform

Routine steps run in your own automation platform under your account. We configure and maintain them; they do not depend on our infrastructure.

A data processing agreement and access schedule in every contract

What we process, why, where, for how long, and exactly which systems we can access at what level. Reviewed whenever the scope changes.

Clean offboarding

When an engagement ends we remove our access, confirm it in writing and leave documentation in your accounts. Everything keeps working without us.

What this means in practice

Before we start, your IT lead receives the access schedule: which systems, which accounts, what level and why. During the engagement, anything a customer would see is drafted by AI and approved by a person on your side, at approval points we agree with you. At the end, you receive written confirmation that our access has been removed.

We hold ourselves to the same standard internally. Our own agency runs on the same systems and rules we set up for clients, and we have published how that was built, including the mistakes.

Questions IT and finance teams ask

Want to see the access schedule before you commit?

Book a short call and we will walk your IT or finance lead through exactly what we would need, and what we would not.

Book a scoping call

Read how we built our own systems: our CRM case study.