Request the auditRequest audit

Trust and data

Ask for less. Hand back more.

You share a description, never a login. What we build is documented as it is built and stays with you. The rules behind that, in one place.

Request the auditRead the privacy notice

Data minimisation

The audit runs on the picture you describe.

Nothing in the audit needs a login, an integration or access to your systems, so you can request it without asking anyone for permission.

What the audit asks for

What leaves your business during the free audit, and what never doesOn the left, your business, holding five things the audit asks for, described in your own words: your system and spend list, two or three workflows end to end, who owns each step, where the flow stalls, the reporting you rely on. A description crosses the audit boundary to ScalePass. A written read comes back: current-state summary, friction and gap read, areas worth examining, recommended next path. What never crosses at the audit stage: Passwords or credentials for any of your systems. Finance documents or unnecessary sensitive client data. A login, an integration or direct access to your systems at the audit stage. Anything the audit does not need in order to answer the question you asked.YOUR BUSINESSFive things, described in your own words. No login, no export, no integration.Your system and spend listTwo or three workflows end to endWho owns each stepWhere the flow stallsThe reporting you rely onApproximate figures and plain descriptions are enough.THE AUDIT BOUNDARYA description crossesA written read comes backSCALEPASSOne of the two people who build environments reads it and writes back.Current-state summaryFriction and gap readAreas worth examiningRecommended next pathHigh level, written, and honest about whether a paid Blueprintis worth it, including when it is not.NEVER CROSSES AT THE AUDIT STAGEPasswords or credentialsFinance documents or sensitive client dataA login, an integration or system accessAnything the question does not need

What the audit never asks for, in full

  • Passwords or credentials for any of your systems.
  • Finance documents or unnecessary sensitive client data.
  • A login, an integration or direct access to your systems at the audit stage.
  • Anything the audit does not need in order to answer the question you asked.

Implementation is a separate stage. Where an accepted scope needs access to a system in order to configure, connect or migrate it, that access is requested, agreed and limited to the work in that scope. The audit itself never needs it.

Protect your information. Do not submit passwords, credentials or unnecessary sensitive client data.

How each phase is agreed

Nothing starts before the phase before it is signed off.

You always know what has been agreed, what is being built and what you can stop.

See the six phases and what each one needs

  1. The free audit comes first. Where it makes sense, the paid Blueprint defines the implementation scope rather than a pre-set package.

  2. Implementation runs in accepted phases: only the agreed scope is configured, connected, documented or migrated.

  3. New requirements are assessed and scoped, never quietly absorbed into work already agreed.

  4. Where implementation is not warranted, we say so and recommend no deployment.

  5. Scheduling and invoicing follow a scope you have accepted in writing, on the terms set out in that accepted proposal or contract.

Ownership and handover

What handover leaves you with.

This is the delivery approach we work to. What is built, documented and handed over on an engagement is set by the scope, deliverables and terms of the proposal or contract you accept.

The systems that earn their place stay yours
Where the accepted scope keeps a specialist system you already rely on, it stays in use and stays the system of record for its own work.
What gets built is documented as it is built
The operating reality and the handover instructions are recorded as part of the work in scope, not reconstructed afterwards.
The operating layer is built to be handed over
Components we build where no suitable system exists are documented and handed to your team, on the terms set out in the accepted scope.
Control, not dependency
The aim is an operating backbone your own team can understand, run and change. How far that reaches depends on the scope you accept and the components it covers.

Legal record

Who you are dealing with.

Lawful bases, recipients, retention and your rights sit in the privacy notice. Consent and measurement are covered by the cookie notice, and use of this website by the website terms.

Controller
TECHOPS ONLINE LIMITED
Company number
13014658
Registered office
71–75 Shelton Street, Covent Garden, London, WC2H 9JQ
Parent company
Campbell Bryan Limited
Notices effective
14 August 2026

Start

Ask for the read before you ask anyone for access.

The free audit needs no access to your systems. You get a written read of what is worth examining, and the description you wrote stays yours.

Request the audit