Skip to main content

We understand your needs before preparing a scoped quote. Future proposals are in USD; scope, deliverables, timing and terms are agreed separately. An enquiry is non-binding, not a purchase or booking.

AI opportunity audit

Compare the documented process with how work happens.

A documented process can miss exceptions and hand-offs. A scoped assessment compares both, then weighs buying, configuring, integrating, selectively building or stopping.

Quote after discovery
Scoped quote

Quote after discovery

Embedded with your team
2–4 wks

Embedded with your team

Scope per audit
1 dept

Scope per audit

Terms agreed separately
Agreed

Terms agreed separately

What we do

Six things happen inside the audit.

Interview and shadow

The people who do the work, live, on real cases — not the managers who describe it.

Access the systems

Read access to the tools of record so we trace data, not opinions about data.

Map reality

Documented versus actual, with every hand-off and exception visible.

Rank opportunities

Hours, effort, risk and the right autonomy level — assisted, enabled or agent-run.

Roadmap

What to build first, what to buy, what to leave alone, in order.

Business case

A baseline and a target you can hold us to, with a stop rule agreed in advance.

Sample deliverable

What you get, shown on an invented finance team.

Click through the four parts of the report. Names and numbers are illustrative, not a client.

Illustrative sample · not a real client

Week 1

Kickoff and shadowing

  • · Scope with the executive sponsor
  • · Shadow the main workflows live
  • · Get read access to systems of record

Week 2

Systems and data

  • · Trace data across every tool
  • · Interview the people who handle exceptions
  • · Time-allocation sampling

Week 3

Reality map

  • · Build the as-is process map
  • · Compare documented vs real
  • · Categorise every exception

Week 4

Roadmap and case

  • · Rank opportunities
  • · Model cost and return
  • · Present, defend, hand over

Who it suits

Good fit, bad fit.

Good fit

  • · A department of 5–100 people doing repeatable work
  • · Leadership asking "where should we use AI?" with no clear answer
  • · PE or roll-up portfolios running the same process in several companies
  • · A sponsor who will give us access to people and systems

Not a fit

  • · You need one chatbot, not a process change — discuss a review scope instead
  • · No one can give us system access
  • · The answer is already decided and you need it validated

Request an opportunity audit

Name, email and a brief description are required. The other details are optional. Please do not include credentials, sensitive customer records or regulated documents.

Scope and availability require agreement. A non-binding enquiry only; future proposals are in USD after understanding your needs.

Workflow context (optional)

Showcase inquiries concern in-house engineering directions, not a SaaS purchase. Architecture walkthrough availability requires confirmation; no live demo is offered here.

We use submitted details to assess and respond to your request. Hosting and communication providers may process them on our behalf. Do not send sensitive material; any secure channel and access must be agreed separately.

What each person receives

User

Department head / COO

Needs: A system that matches how the team actually works, not how the vendor imagined it.

Doubt: Custom software sounds slow, risky and hard to maintain.

Proposed deliverables · agreed in scope

  • • A mapped real-vs-documented process
  • • A running system for one department
  • • Runbooks the team can follow

Buyer

CFO / finance lead

Needs: A cost case that holds against current seat spend and manual hours.

Doubt: The return will be asserted, not measured.

Proposed deliverables · agreed in scope

  • • A baseline agreed before work starts
  • • A 3-year rent-vs-own comparison
  • • A measured result against that baseline

Approver

IT / security lead

Needs: Something supportable that does not add shadow IT.

Doubt: Another system the IT team will be left holding.

Proposed deliverables · agreed in scope

  • • Architecture and data model documentation
  • • Access control and audit design
  • • A named handover plan

Affected

The team doing the work

Needs: Less re-keying and fewer workarounds.

Doubt: Automation will be imposed without asking them.

Proposed deliverables · agreed in scope

  • • Shadowing time where their workarounds are recorded
  • • Clear lines on what stays human

Access we ask for — and how you take it back

  • • Read access to the department's tools and exports
  • • Shadowing time with named team members
  • • No production write access during the audit

Access is limited to the department in scope and logged.

Initial inquiry: non-sensitive summary only. Later assessment: authorised redacted samples or read-only access. Sandbox and production write access require separate approval, minimisation, access expiry and retention agreement.

Agree revocation, working-copy handling, retention exceptions and confirmation responsibilities before access.

Not ready for an audit?

Start by discussing your review scope.

One decision, examined properly, with a written summary. If an audit is the right next step, you'll know.