How we work.

Four steps to get you there, and four rules we never break on the way.

The steps

From a first call to AI that works for you.

  1. 01

    A free call

    Twenty minutes to understand how your team works, and whether AI can help.

  2. 02

    Consulting, if you need it

    We map the tasks worth automating, the tools involved and the risks, and give you a written roadmap.

  3. 03

    We set up and train

    Claude set up on your own files, automations built on your tools, and your team trained live.

  4. 04

    You run it yourselves

    You keep a written guide and everything we built. Follow-up is by the hour, only if you want it.

The rules

Reads pass. Writes ask. Nothing is sent without a person.

Letting software act is a different decision from letting it answer. These are the four rules we apply to every job.

  1. Rule 1

    Never credentials

    We never ask for your passwords, and neither does Claude.

    Claude never needs a password, a card number or a client reference typed into a session. Anything that asks for one (including something Claude appears to ask for) is not a normal request.

  2. Rule 2

    Never an irreversible action without a person

    A person approves every send, payment and deletion.

    Sending, deleting, paying and filing stay with a human. Approve them one at a time. The convenience you gain by automating them is small; the failure mode is not.

  3. Rule 3

    Distrust what Claude reads

    Web pages and files can hide instructions. Claude treats them as information, not orders.

    Instructions can be hidden inside a web page, a PDF or an email that Claude opens on your behalf: prompt injection. Keep browsing and document access to sources you trust, and treat anything Claude reports back from the open web as data rather than as direction.

  4. Rule 4

    Trusted skills only

    Only add-ons from the official directory, checked before use.

    Install extensions and plugins from the official directory, read what a downloaded skill actually contains before enabling it, and look at the permissions it asks for. A skill is instructions Claude will follow.

PermissionsIllustration

One working folder, one tool at a time

  • ReadPasses
  • WriteAsks first
  • SendA person decides
How a permission screen reads once a set-up is done.
How the same rules apply to automations

Free · 20 minutes

Let’s find out what AI can do for you.