Service 09 / 10Technology & Intelligence

Technology audits that show what to fix first and what each issue costs.

We audit websites and apps, security, data and AI for new and growing businesses and enterprises. Senior engineers check every finding by hand.

Findings register · Your company · combined audit · sample extract 37 findings Showing 8 of 37 · ranked by fix order

Severity summary for the sample register: 2 critical, 7 high, 12 medium and 16 low findings, 37 in total.

Sample findings register, scrollable sideways

An illustrative extract from a combined audit of “Your company”: eight findings with severity, estimated monthly cost, effort in engineering days and fix order. Figures are illustrative.
ID Area Finding Severity Monthly cost (est.) Effort Fix order
SEC-01 Security Admin console open to the internet with no two-step log-in Critical Rated 2 d 1
TA-03 Performance Checkout page takes 4.6 s to show on mobile (target ≤ 2.5 s) High $18,400 8 d 2
SEC-04 Security Payment service uses code with a known security flaw (CVSS 8.1) Critical Rated 1 d 3
DAT-02 Data Order records lost when the system is busy: 3.1% last month High $9,200 5 d 4
SEO-05 Search Product pages hidden from Google by a tag in an old template High $11,700 3 d 5
CLD-02 Cloud Two oversized databases sit idle for over 80% of the month Medium $4,300 2 d 6
AI-02 AI readiness Knowledge base 40% duplicated, so AI gives conflicting answers Medium Rated 6 d 7
ACC-01 Accessibility Checkout fields have no labels for screen readers (WCAG 2.2 AA) High $7,600 4 d 8

Illustrative Screens marked Illustrative are examples, not client results. Costs come from your analytics, cloud bills and staff rates. Rated means we score a risk but do not price it, such as a breach.

Typical length
2–6 weeks
Audit types
Software · search · security · data · AI
Pricing
Scoped up front

01What we check

Six audits, run alone or together.

Each audit checks one area: software, search, security, data, AI readiness or cloud waste. All 6 use one method and end in one fix list.

Two monitors of source code on a dark desk, lit keyboards in front of them

Tools check everything. People judge what matters.

Technical & performance

How your software is built, how fast it runs and how safely you can change it.

What we look at

  • System design and room for your next plans
  • Code quality, tests, outdated third-party code and licence risks
  • Google’s speed scores (Core Web Vitals) from site visits and lab tests
  • Slowest server replies and the queries behind them
  • Releases: how often, how safely and how you undo a bad one

Checks we run

  • Loads in 2.5 s, reacts in 0.2 s, stays steady, for 3 in 4 visits
  • Test at 3× your peak traffic to find what breaks first
  • Third-party code checked for known flaws and abandoned parts
  • Failed releases and recovery time over 90 days

Rated against

  • Core Web Vitals — Loading, interactivity and visual stability
  • DORA metrics — Software delivery performance
  • WCAG 2.2 AA — Web Content Accessibility Guidelines

Tools

Typical length
2–4 weeks
You get
System map, speed targets and a ranked fix list

Search & AI visibility

Whether Google can find and rank your site, and whether AI answers quote it.

What we look at

  • Pages Google can find and list, redirects and server logs
  • Hidden page labels (structured data) checked against schema.org
  • Missing topics against the searches that bring sales
  • How often ChatGPT, Perplexity and Google’s AI answers name you
  • Links between pages, unlinked pages and what JavaScript hides

Checks we run

  • Full crawl, checked against Google Search Console and logs
  • Page labels tested; each broken one listed with its fix
  • 40 test questions put to AI assistants, saved with date and model
  • What Google sees on each page versus what people see

Rated against

  • Core Web Vitals — Loading, interactivity and visual stability
  • WCAG 2.2 AA — Web Content Accessibility Guidelines

Tools

Typical length
2–3 weeks
You get
Listing report, content gaps and where AI names you

Security & compliance

What an attacker could reach, and the gaps against security standards you must meet.

What we look at

  • What outsiders can reach: open servers, ports, forgotten test sites
  • App tests against the OWASP Top 10, the standard list of security risks
  • Cloud settings checked against CIS Benchmarks (published safe settings)
  • Access: two-step log-in, admin rights and leavers’ accounts
  • Passwords left in code, third-party flaws and a list of software parts

Checks we run

  • Tests with and without a log-in, under signed test rules
  • Flaws scored on the standard CVSS scale, then for your setup
  • Containers scanned for outdated parts and critical known flaws
  • Gaps against ISO 27001 or SOC 2, security standards we prepare you for

Rated against

  • OWASP ASVS — Application Security Verification Standard
  • OWASP Top 10 — Web application security risks
  • CIS Controls v8.1 — Critical Security Controls and Benchmarks
  • ISO/IEC 27001:2022 — Information security management systems
  • SOC 2 — Trust Services Criteria

Tools

Typical length
2–4 weeks
You get
Scored list of security flaws, gaps and a fix plan

Data & analytics

Whether the numbers you decide on are right, where they come from and who sees them.

What we look at

  • Data quality: missing, duplicate, wrong, late or broken records
  • Each number’s path from source to dashboard
  • Tracking: lost or double-counted events, consent and server tracking
  • Data rules: owners, how long you keep data, who sees it, personal data
  • Data warehouse costs, and the slowest and costliest reports

Checks we run

  • Every main table checked for gaps, duplicates, odd values and age
  • A month of website tracking matched to server records
  • Consent tested against Europe’s GDPR and India’s DPDP Act 2023
  • Key numbers traced to their source and recalculated

Rated against

  • GDPR — General Data Protection Regulation (EU) 2016/679
  • DPDP Act 2023 — Digital Personal Data Protection Act, 2023
  • ISO/IEC 27001:2022 — Information security management systems

Tools

Typical length
2–4 weeks
You get
Quality scores, data map, tracking fixes and data-rule gaps

AI readiness

Whether your data, systems, rules and people are ready for AI before you invest.

What we look at

  • Data: what you have, its quality, rights to use it, freshness
  • Servers: how the AI runs, document storage, cost and speed per answer
  • AI rules: tools in use, sign-off, testing and records
  • People: who owns the AI, who checks its work, who fixes failures
  • Ideas: value, effort and risk of each job AI could do

Checks we run

  • AI answers tested on your documents: accurate and on topic
  • Repeated and conflicting articles in your knowledge base
  • Mapped to NIST AI RMF and ISO 42001, AI standards we prepare you for
  • Hidden-instruction attacks on any assistant (OWASP LLM01)

Rated against

  • NIST AI RMF 1.0 — AI Risk Management Framework
  • ISO/IEC 42001:2023 — Artificial intelligence management systems
  • OWASP Top 10 for LLM Applications — Security risks in generative AI applications
  • EU AI Act — Artificial Intelligence Act (EU) 2024/1689

Tools

Typical length
3–4 weeks
You get
Readiness scores, a groundwork list and your AI ideas, ranked

Carbon & efficiency

Where your systems waste cloud money and energy. Cutting one usually cuts the other.

What we look at

  • Your software carbon score (SCI) per visit, order or task
  • Idle or oversized servers, unused storage and costly data transfers
  • Page size, image size, add-on scripts and how well caching works
  • Running big jobs when the power grid is cleanest
  • Which AI model you use and its running cost

Checks we run

  • Cloud bill matched to each system, waste split from useful spend
  • Energy per request, converted to carbon with local grid data
  • Data sent per visit, measured on your 10 busiest pages
  • Server sizes based on typical busy use, not rare peaks

Rated against

  • SCI · ISO/IEC 21031:2024 — Software Carbon Intensity
  • ISO 14001:2015 — Environmental management systems

Tools

Typical length
1–2 weeks
You get
Carbon score, waste list and fixes with savings

02Fix-order planner

A fix order that fits your team’s time.

The planner fits 16 sample findings into one quarter. Change the days or the objective to see what fits and what it recovers.

A whiteboard ruled into columns, with orange and blue sticky notes moving from left to right
Ordered, then costedFindings go on the wall first, then into now, next and later.Photo: Paymo / Unsplash
Fix-order planner · Your company · combined audit · the 16 findings scheduled this quarter · 55 engineering days in total Plan recalculated live
30 days

One engineer working the whole quarter is roughly 60 days. Effort figures are the audit’s own estimates, not a quote.

Objective

Days committed
28 of 30
Findings in the plan
11 of 16
Value recovered Est.
$41,900 per month
Left unfixed
28% of rated risk

Plan at 30 days, balanced objective: 11 findings selected, 28 days committed, 28% of rated risk left unfixed.

Now 5

First third of capacity

  • SEC-01Crit

    Admin console open to the internet with no two-step log-in

    2 d Rated risk 20

  • SEC-04Crit

    Payment service uses code with a known security flaw (CVSS 8.1)

    1 d Rated risk 15

  • SEO-05High

    Product pages hidden from Google by a tag in an old template

    3 d $11,700/mo

  • CLD-02Med

    Two oversized databases sit idle for over 80% of the month

    2 d $4,300/mo

  • CLD-05Low

    Test servers run 24/7, including nights and weekends

    1 d $2,100/mo

Next 6

The rest of the plan

  • SEC-11High

    Activity logs switched off in 2 of 5 cloud accounts (CIS 3.1)

    2 d Rated risk 16

  • DAT-09High

    Personal data in analytics exports, kept with no time limit

    3 d Rated risk 16

  • ACC-01High

    Checkout fields have no labels for screen readers (WCAG 2.2 AA)

    4 d $7,600/mo

  • TA-11Med

    Product photos too big and in old formats, so pages load slowly

    3 d $6,100/mo

  • DAT-02High

    Order records lost when the system is busy: 3.1% last month

    5 d $9,200/mo

  • CAR-02Low

    Big jobs run when the power grid is most polluting

    2 d $900/mo

Later 5

Does not fit this quarter

  • TA-03High

    Checkout page takes 4.6 s to show on mobile (good ≤ 2.5 s)

    8 d $18,400/mo

  • TA-08High

    No way to undo a bad release, so every fault is patched live

    5 d Rated risk 12

  • SEO-09Med

    Page labels broken on 62% of product pages: rich Google listings lost

    4 d $5,400/mo

  • DAT-06Med

    Revenue reported three ways; no agreed definition or owner

    4 d Rated risk 12

  • AI-02Med

    Knowledge base 40% duplicated, so AI gives conflicting answers

    6 d Rated risk 12

Cumulative value recovered against engineering days
$65,700/mo 55 days

The sixteen findings behind the plan, sortable, scrollable sideways

Sixteen illustrative findings with severity, risk score, estimated monthly value, effort, dependencies and the lane the current plan puts them in.
Finding Severity Depends on Must fix
SEC-04 Payment service uses code with a known security flaw (CVSS 8.1)Security 15/25 Critical Rated 1 d — Now
CLD-05 Test servers run 24/7, including nights and weekendsCloud 10/25 Low $2,100 1 d — Now
SEO-05 Product pages hidden from Google by a tag in an old templateSearch 20/25 High $11,700 3 d — Now
SEC-01 Admin console open to the internet with no two-step log-inSecurity 20/25 Critical Rated 2 d — Now
CLD-02 Two oversized databases sit idle for over 80% of the monthCloud 15/25 Medium $4,300 2 d — Now
SEC-11 Activity logs switched off in 2 of 5 cloud accounts (CIS 3.1)Security 16/25 High Rated 2 d — Next
TA-11 Product photos too big and in old formats, so pages load slowlyPerformance 15/25 Medium $6,100 3 d — Next
ACC-01 Checkout fields have no labels for screen readers (WCAG 2.2 AA)Accessibility 20/25 High $7,600 4 d — Next
DAT-09 Personal data in analytics exports, kept with no time limitData 16/25 High Rated 3 d — Next
DAT-02 Order records lost when the system is busy: 3.1% last monthData 16/25 High $9,200 5 d — Next
TA-03 Checkout page takes 4.6 s to show on mobile (good ≤ 2.5 s)Performance 20/25 High $18,400 8 d TA-11 Later
CAR-02 Big jobs run when the power grid is most pollutingCarbon 8/25 Low $900 2 d CLD-02 Next
SEO-09 Page labels broken on 62% of product pages: rich Google listings lostSearch 12/25 Medium $5,400 4 d — Later
DAT-06 Revenue reported three ways; no agreed definition or ownerData 12/25 Medium Rated 4 d DAT-02 Later
TA-08 No way to undo a bad release, so every fault is patched liveDelivery 12/25 High Rated 5 d — Later
AI-02 Knowledge base 40% duplicated, so AI gives conflicting answersAI readiness 12/25 Medium Rated 6 d — Later

Illustrative The sample report holds 37 findings. The planner shows the 16 we suggest for this quarter. That is every critical and high finding, plus smaller ones that are quick or tied to planned work. Risk is severity × likelihood, each scored 1–5. Rated findings have a risk score but no price. Effort is an engineer’s estimate. Nothing is planned before the work it depends on.

03Method

Six steps from first check to a clear fix.

Scanners flag possible problems. Nothing becomes a finding until a senior engineer repeats it by hand, rates it and, where we can, prices it.

  1. 01

    Scope

    We agree systems, owners, access and the decision the audit supports. Security tests need signed rules.

    • Written scope
    • Access checklist
    • Signed test rules
  2. 02

    Collect

    Scans, speed data, logs, settings and talks with the people who run your systems.

    • Scan results
    • Log sample
    • Interview notes
  3. 03

    Verify

    We repeat each possible problem by hand. False alarms are logged and dropped.

    • Steps to repeat it
    • Trace or screenshot
    • False-alarm log
  4. 04

    Rate

    We score severity and likelihood on a published scale. Security flaws start from their standard CVSS score.

    • Severity
    • Likelihood
    • Why we rated it
  5. 05

    Cost

    We price the impact from your traffic, sales, cloud bill and staff rates. Every assumption is written down. The result is a range.

    • Your figures
    • Low–high range
    • Assumptions
  6. 06

    Recommend

    The fix, effort, owner, what it depends on and the re-test that proves it. Your team can do it without us.

    • Fix and effort
    • Owner
    • Re-test

The six steps run Scope, Collect, Verify, Rate, Cost, Recommend. A marker for finding TA-03 moves along them as the record below fills in.

TA-03 · Checkout LCP 4.6 s on mobile · evidence record Recommend
  • Scope Checkout funnel, mobile web, 28-day window
  • Field data CrUX p75 LCP 4.6 s — outside the good threshold of 2.5 s
  • Lab trace 6.1 s on a mid-range Android device over emulated 4G
  • Reproduced 5 of 5 runs on a clean profile, cache empty
  • Cause Third-party payment script loads in the head — 1.9 s of blocking time
  • Rating Severity High · Likelihood 5 · Risk 20 of 25
  • Cost model Conversion elasticity × mobile revenue — $18,400 a month, ±30%
  • Fix Defer the payment script until interaction, self-host the two web fonts, server-render the order summary
  • Effort 8 engineering days · depends on TA-11 · web platform team

Illustrative Nine evidence records back this one finding. The report files them in an appendix by finding ID. So you can trace any number in the summary back to its source.

04Tools

The tools we use in each audit.

Each audit has its own tools. They work fast, but a person decides which findings matter to your business.

A black magnifying glass beside a small notebook and a pencil on a white desk
Measured, then judgedTools read the code and the traffic. People judge what they find.Photo: Mediamodifier / Unsplash

Technical & performance

65% automated · 35% expert review

A dial: tools collect about 65 per cent of the Technical & performance audit, and people review the rest.

Speed data, load tests and code scans, all read by an engineer.

Measured

  • Google’s speed scores for 3 in 4 visits, from Chrome UX Report
  • The slowest server responses and the queries behind them
  • Tests, outdated code and known flaws
  • Failed releases and recovery time over 90 days

Estimated Modelled

  • Effort to fix, with a confidence level
  • Extra revenue from faster pages, based on how speed affects buying

AlsoWebPageTest · Chrome UX Report · Playwright traces · flame graphs

Search & AI visibility

70% automated · 30% expert review

A dial: tools collect about 70 per cent of the Search & AI visibility audit, and people review the rest.

Site crawlers, server logs and Google Search Console, plus dated questions put to AI assistants.

Measured

  • Pages Google finds and lists, checked against logs
  • Page labels tested on each page type
  • What Google sees versus the code
  • How often AI names you on fixed questions, with model and date

Estimated Modelled

  • Visits won back by a listing fix
  • More clicks from rich search results

AlsoScreaming Frog · Chrome UX Report · server log analysis

Security & compliance

55% automated · 45% expert review

A dial: tools collect about 55 per cent of the Security & compliance audit, and people review the rest.

Scanners map what is open. A tester decides what an attacker could reach and use.

Measured

  • Servers, ports and forgotten sites that anyone outside can reach
  • Known security flaws in code and containers
  • Two-step log-in, admin access and records of every action
  • Cloud settings against CIS Benchmarks

Estimated Modelled

  • How likely an attack is in your setup
  • Expected loss, modelled but not priced

AlsoOWASP ZAP · Nmap · Prowler · SBOM tooling

Data & analytics

60% automated · 40% expert review

A dial: tools collect about 60 per cent of the Data & analytics audit, and people review the rest.

Tools check every main table. Matching tracking to server records takes a person and a month.

Measured

  • Gaps, duplicates, odd values and age of each table
  • Website tracking matched to server records
  • Where each number comes from
  • Consent, and which data is personal

Estimated Modelled

  • Hours lost to rework and checks by hand
  • The cost of a decision made on a wrong number

AlsoGreat Expectations · warehouse query logs · consent-mode diagnostics

AI readiness

40% automated · 60% expert review

A dial: tools collect about 40 per cent of the AI readiness audit, and people review the rest.

The hardest audit to automate. Tools can test AI answers, but rules, skills and ideas need interviews.

Measured

  • Whether AI answers stick to your documents and stay on topic
  • Repeated and conflicting articles in your knowledge base
  • AI models in use, sign-offs and action records
  • Hidden-instruction attacks on any assistant

Estimated Modelled

  • A readiness score for each area
  • Time and groundwork before a first live AI tool

AlsoYour test examples · OWASP LLM Top 10 tests · control sheets

Carbon & efficiency

75% automated · 25% expert review

A dial: tools collect about 75 per cent of the Carbon & efficiency audit, and people review the rest.

Mostly cloud usage and billing data. Every input to the carbon score is written down.

Measured

  • Energy used by each system, from cloud data
  • Data sent per visit on your busiest pages
  • How busy servers are, idle hours and unused storage

Estimated Modelled

  • Carbon per visit or task, using local grid data
  • Carbon from making the hardware you use

AlsoCloud Carbon Footprint · grid carbon data · billing exports

Technologies we work with across audits Tool licences are ours or yours, named in the written scope before any tool runs.

  • SonarQube
  • Snyk
  • Lighthouse
  • PageSpeed Insights
  • k6
  • Google Search Console
  • Semrush
  • Burp Suite
  • Trivy
  • Datadog
  • Google Analytics
  • GitHub
  • Jira

05Scorecard

A scorecard your board can read.

We score 6 areas from 1 to 5, on a scale you see first. Each score shows what the next level needs.

Radar shows

Scores out of 5 today: security 2, speed 2, data 2, search 3, AI readiness 1, carbon 1. Targets: 4, 4, 4, 4, 3 and 3.
Today Target, 12 months
Overall today
1.8of 5
Overall at target
3.7of 5
  1. 1AbsentNothing in place, or it exists only in someone’s head.
  2. 2Ad hocIt happens when someone remembers, and differently each time.
  3. 3RepeatableDocumented, owned and repeated, but not measured.
  4. 4ManagedMeasured against a target, with alerts when it slips.
  5. 5OptimisedImproved step by step, each change confirmed by a re-test.

Security & compliance

2 4 out of 5 today, target 4 out of 5

Level 2 · Ad hoc

Two-step log-in on some admin accounts. No logs in 2 of 5 cloud accounts. Patches on request.

Level 4 · Managed requires

Two-step log-in everywhere, one log with alerts, patch times measured, cloud set to CIS Benchmarks.

Rated against
  • OWASP ASVS — Application Security Verification Standard
  • NIST CSF 2.0 — Cybersecurity Framework

Performance & accessibility

2 4 out of 5 today, target 4 out of 5

Level 2 · Ad hoc

Speed tested in the lab only. Checkout takes 4.6 s to show on mobile. Accessibility never tested.

Level 4 · Managed requires

Google’s speed scores good for 3 in 4 visits (LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1). Speed and WCAG 2.2 AA checked on every release.

Rated against
  • Core Web Vitals — Loading, interactivity and visual stability
  • WCAG 2.2 AA — Web Content Accessibility Guidelines

Data & analytics

2 4 out of 5 today, target 4 out of 5

Level 2 · Ad hoc

Revenue reported 3 ways. Key numbers have no owner. No rule on how long data is kept. Personal data in exports.

Level 4 · Managed requires

Each key number has one definition and an owner. Quality tests run automatically. Consent and deletion rules enforced, with proof.

Rated against
  • DPDP Act 2023 — Digital Personal Data Protection Act, 2023
  • GDPR — General Data Protection Regulation (EU) 2016/679

Search & AI visibility

3 4 out of 5 today, target 4 out of 5

Level 3 · Repeatable

Google lists the main pages. Page labels missing or broken on product pages. No record of how often AI names you.

Level 4 · Managed requires

Complete page labels, checked on every release. AI mentions tracked on a fixed, dated set of questions.

Rated against schema.org · Google Search Essentials

AI readiness

1 3 out of 5 today, target 3 out of 5

Level 1 · Absent

No list of AI models in use, no test examples, knowledge base 40% duplicated, no owner for AI output.

Level 3 · Repeatable requires

Every AI model listed and signed off. Test examples for each AI job. A clean knowledge base with an owner. Decisions on record.

Rated against
  • ISO/IEC 42001:2023 — Artificial intelligence management systems
  • NIST AI RMF 1.0 — AI Risk Management Framework

Carbon & efficiency

1 3 out of 5 today, target 3 out of 5

Level 1 · Absent

No record of energy or carbon. Two databases idle for over 80% of the month. No limit on page size.

Level 3 · Repeatable requires

A carbon score (SCI) for each visit or task. Server sizes reviewed monthly against typical busy use. A page-size limit enforced.

Rated against
  • SCI · ISO/IEC 21031:2024 — Software Carbon Intensity

Illustrative Scores show your systems on one date, not a certificate. Certificates for ISO 27001 or ISO 42001, and SOC 2 reports, come from an accredited body. We get you ready. Re-tests score the same 6 areas, the same way.

06Cost of waiting

The monthly cost of unfixed issues.

A risk rating alone rarely wins a budget, so we price every finding we can. Each figure shows its formula and your inputs.

Monthly online sales
$1.24Meach loss is a share of this
Monthly cloud bill
$96,0009.6% pays for capacity nobody uses
Effort to fix
31 eng. daysbehind these 5 lines, of 55 across the whole plan

The chart stacks five monthly loss lines into a recoverable total of $61,200. Lost online sales are the largest at $18,400. Then manual rework at $14,600, lost search visibility at $11,700, cloud waste at $9,200 and modelled risk exposure at $7,300. Select any bar for its formula and inputs.

Illustrative Monthly, in US dollars, for a made-up company. Select a bar, or move across them with the arrow keys, to open the calculation.

Lost online sales

Slow mobile checkout

$18,400per month

Formula

monthly loss = checkout sessions × Δ conversion rate × average order value 214,000 × 0.29% × $29.60 = $18,369
Inputs to the lost online sales calculation, with the source of each one.
InputValueSource
Mobile checkout sessions 214,000 / month Analytics, 28 days
Conversion, LCP ≤ 2.5 s 1.71% Analytics cohort, field LCP
Conversion, LCP 4.6 s 1.42% Analytics cohort, field LCP
Average order value $29.60 Order data, 90 days

We compare fast and slow visits using real load times from the Chrome UX Report, not lab tests. Google calls a page good when its main content shows in 2.5 s, it reacts in 0.2 s and stays steady, for 3 in 4 visits.

  • Measured inputs · modelled gain
  • TA-03

Manual rework

Matching order and event data by hand

$14,600per month

Formula

monthly cost = rework hours × blended loaded hourly rate 380 h × $38.40 = $14,592
Inputs to the manual rework calculation, with the source of each one.
InputValueSource
Rework hours 380 / month Time log, three teams, 4 weeks
Blended loaded rate $38.40 / hour Your finance team
Largest single task Order reconciliation, 190 h Time log
Event loss driving it 3.1% of order events Queue metrics vs server truth

Rework is the cost of doing a task twice, not the cost of the team. Hours were logged by the people doing the work rather than estimated in a workshop.

  • Estimated from a four-week time log
  • DAT-02
  • AI-02

Cloud waste

Idle servers, unused storage, data transfer

$9,200per month

Formula

monthly waste = Σ (unused capacity × unit rate × hours) $5,690 + $2,288 + $1,220 = $9,198
Inputs to the cloud waste calculation, with the source of each one.
InputValueSource
Oversized instances 9, mean 61% unused p95 utilisation, 30 days
Blended instance rate $1.42 / hour × 730 h Cloud bill
Unattached block storage 26 TB at $0.088 / GB-month Cloud bill
Cross-region transfer 61 TB at $0.02 / GB Cloud bill

That is 9.6% of the monthly cloud bill, spent on servers nobody used. Sizing servers for typical busy use, not rare peaks, also cuts the carbon score (SCI). So the cost line and the carbon line fall together.

  • Measured from the bill and server use
  • CLD-02

Risk exposure

Expected loss, not a price

$7,300per month · modelled

Formula

expected monthly loss = (annual likelihood × modelled impact) ÷ 12 (14% × $625,000) ÷ 12 = $7,292
Inputs to the risk exposure calculation, with the source of each one.
InputValueSource
Critical findings open 2 Findings register
Modelled annual likelihood 14% Exposure, exploit maturity, controls
Modelled impact $625,000 Response, notification, downtime, penalty exposure
Rating method CVSS v3.1, re-rated for context Security assessment

This line is here only so risk can be weighed against revenue in one fix order. A breach is a chance, not a monthly bill. The findings register still rates security flaws with CVSS and does not price them. Possible fines are modelled on India’s DPDP Act 2023.

  • Modelled · rated, not priced
  • SEC-01
  • SEC-04

Recoverable value

The five lines together

$61,200per month

Formula

recoverable value = Σ (the five lines above) $18,400 + $11,700 + $14,600 + $9,200 + $7,300 = $61,200
Inputs to the recoverable value calculation, with the source of each one.
InputValueSource
Recoverable per month $61,200 Modelled
Recoverable per year ≈ $734,400 Modelled, at a steady run rate
Share of monthly online sales 4.9% Against $1.24M / month
Total effort to fix 31 engineering days Engineering estimates, ±30%

The planner above orders the full 55-day plan, these five lines included. The biggest gains come first, and nothing starts before the work it depends on. Every figure here is an example for a made-up company.

  • Sum of the lines above

These 5 lines group losses by where the money goes, and add a modelled figure for rated risks. So $61,200 here and $65,700 in the planner are one audit, counted two ways. Measured was counted in your systems. Estimated was sized by a person. Modelled uses a probability.

07AI readiness

AI readiness, scored before you invest.

AI projects often stall on data, rules or unclear owners. We score 6 areas and list the work to close each gap.

The gap to your first live AI tool

Each area is scored 1–5. Solid shows today’s score, pale shows the gap and the dashed mark shows the target. We size each gap in engineering days.

Groundwork, by area 35 engineering days
  • Data foundations 12 d
  • AI rules 8 d
  • Security & privacy 6 d
  • Skills & ways of working 5 d
  • Servers & cloud 4 d

A strip shows the 35 engineering days of groundwork by area. Data foundations 12 days, AI rules 8, security and privacy 6. Skills and ways of working 5, servers and cloud 4, AI ideas none.

  1. 01

    Data foundations

    24 scores 2 of 5 today against a target of 4 of 5 12 eng. days

    EvidenceMain data is written up. 40% of the knowledge base is duplicated. Nobody checks it is current.

    Next actionClear duplicates from the knowledge base. Then add checks for missing and old data.

    Data engineering DPDP Act 2023 — Digital Personal Data Protection Act, 2023
  2. 02

    AI rules

    13 scores 1 of 5 today against a target of 3 of 5 8 eng. days

    EvidenceNo list of AI models, no sign-off step, no test record. AI use is found out after the fact.

    Next actionList every AI model and add a sign-off step before the next trial leaves a developer’s laptop.

    CTO office ISO/IEC 42001:2023 — Artificial intelligence management systems
  3. 03

    Security & privacy

    34 scores 3 of 5 today against a target of 4 of 5 6 eng. days

    EvidenceOne company log-in and central logs. No attack tests on prompts and no limit on keeping them.

    Next actionTest for hidden-instruction attacks (OWASP Top 10 for LLM Applications). Set how long prompts are kept.

    Security OWASP Top 10 for LLM Applications — Security risks in generative AI applications
  4. 04

    Skills & ways of working

    24 scores 2 of 5 today against a target of 4 of 5 5 eng. days

    EvidenceTwo engineers trying things. No owner for the AI, no review rota, nobody on call for failures.

    Next actionName an AI owner, review its answers weekly and add AI failures to the on-call guide.

    Platform NIST AI RMF 1.0 — AI Risk Management Framework
  5. 05

    Servers & cloud

    34 scores 3 of 5 today against a target of 4 of 5 4 eng. days

    EvidenceServers and an AI search database run. No cost limit per answer, no speed target.

    Next actionSet a cost limit and a speed target per answer before the first live AI tool.

    Platform
  6. 06

    AI ideas

    44 scores 4 of 5 today against a target of 4 of 5 At target

    EvidenceThree ideas with measured starting points. One has an owner and a budget. Already at target.

    Next actionNothing to close. Keep the starting figures current, so the first AI tool is judged fairly.

    Product

Illustrative 35 engineering days of groundwork in 5 areas before a first live AI tool is worth funding. Only the AI ideas are ready. The basics under them are not.

Profiling run · agent 04 · warehouse.analytics Complete 6.1M rows · 9 min
Data profiling output for five columns: null rate, duplicate rate, freshness and the flag raised. The bars share one scale from 0 to 45%.
Column Null rate Duplicate rate Freshness Flag
orders.order_id 0.0% 0.0% 2 min clean
orders.channel 12.8% 0.0% 2 min nulls
customers.email 0.4% 6.1% 2 min duplicates
events.session_id 3.1% 0.2% 5 min event loss
kb_articles.body 1.1% 40.2% 31 days duplicates · stale

Illustrative AI tools check the data, group log errors and draft possible findings in the first days. Here the AI drafted 14 possible findings. An analyst confirmed 9 and rejected 5 as false alarms. Only those 9 reached the findings register.

08Sample report

What the audit report looks like.

Five pages from a sample report. Leaders read the short summary. Engineers get the detail each fix needs.

  1. Combined technology auditConfidential

    Audit report · v1.0

    Combined technology audit

    Technical & performance · Security · Data & analytics · Search & AI visibility · AI readiness

    Prepared for
    Your company
    Prepared by
    Xterra Edze
    Period
    Kick-off to results
    Classification
    Named recipients only
    The corner of a glass office building against a deep sky, its lines converging upward
    Findings register · 37 findingsPage 01 of 42
  2. 1. Executive summaryConfidential

    Executive summary

    • 37 findings
    • Critical2
    • High7
    • Medium12
    • Low16
    • Two findings need fixing this week. An admin console is open to the internet without two-step log-in. The payment service uses code with a known security flaw.
    • Checkout earns the most revenue. On mobile it takes 4.6 s to show, against a good 2.5 s. Slower visits end in a sale 0.29 points less often.
    • Modelled value to win back: $61,200 a month, 4.9% of monthly online sales, for 31 engineering days of fixes.
    • AI readiness is held back by missing rules, not technology. There is no AI model list and no sign-off step. The AI ideas themselves are sound.

    Recommendation. Take the Now lane, 11 engineering days, before the next release. It closes both critical findings and recovers $20,900 a month without touching checkout code.

    Severity counts on results dayPage 03 of 42
  3. 3.2 Findings · PerformanceTA-03

    TA-03 Checkout LCP is 4.6 s on mobile at the 75th percentile

    Severity
    High
    Component
    web / checkout
    Owner
    Web platform
    Effort
    8 eng. days
    Fix order
    02

    Evidence

    • Field data, 28-day window: LCP p75 4.6 s, INP p75 240 ms, CLS 0.04 (mobile)
    • Lab trace: 1.9 s blocked on a third-party payment script loaded in the head
    • Analytics cohort: 1.42% conversion above 4 s against 1.71% below 2.5 s
    • Filmstrip captured at 2.0 s, 3.0 s and 4.6 s (appendix E-014, E-015)

    Reproduction

    1. Throttle to Slow 4G on a mid-range Android profile
    2. Load /checkout cold, cache disabled, from a cold CDN edge
    3. Record LCP — the element is the order-summary card

    Why we rated it. High, not critical: it costs sales every day, but no data is at risk and the site stays up. Google’s speed scores need LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1. This journey fails one of the three.

    Recommendation. Defer the payment script until interaction, self-host the two web fonts and server-render the order summary. Re-test against field data after two weeks of collection, not against a lab score.

    Every finding carries evidence, reproduction, rationale and an ownerPage 14 of 42
  4. 5. 90-day planConfidential

    Fix plan: 30, 60 and 90 days

    NowDays 0–30

    • SEC-01Admin console: two-step log-in, known networks only
    • SEC-04Patch the payment-service dependency, then re-scan
    • SEO-05Remove the old tag that hides product pages from Google
    • CLD-02Shrink 2 oversized databases to the size you use

    11 eng. daysRisk closed + $20,900 / month

    NextDays 31–60

    • TA-03Faster checkout: load the payment script last, pre-build the summary
    • DAT-02Stop losing order records when the system is busy
    • ACC-01Label every checkout form field (WCAG 2.2 AA, 1.3.1)

    13 eng. days$33,000 / month

    LaterDays 61–90

    • AI-02Clear duplicates from the knowledge base and keep it current
    • GOV-01AI model list and sign-off step before the next trial

    7 eng. daysGroundwork for the AI project

    Order matters. The payment code is patched before checkout work touches the same service. The knowledge base is cleaned before any AI search is built. Totals: 31 engineering days, $61,200 a month recovered on the model.

    Ordered by value per engineering day, dependencies respectedPage 28 of 42
  5. Appendix E · EvidenceConfidential

    Evidence appendix

    Evidence artefacts retained for the audit, with the instrument that produced each one, the day it was captured and the finding it supports.
    RefArtefactInstrumentCapturedFinding
    E-014 28-day field export, mobile Chrome UX Report Day 04 TA-03
    E-015 Lab trace and filmstrip Lighthouse Day 04 TA-03
    E-022 Authenticated scan report Burp Suite Day 09 SEC-01
    E-023 SBOM with CVE match, CVSS v3.1 Trivy Day 09 SEC-04
    E-031 Coverage export vs full crawl Search Console Day 11 SEO-05
    E-040 Profiling notebook, null and duplicate rates Python · Jupyter Day 12 AI-02

    Every evidence file comes with the report and is kept for the agreed time. Unchecked scan output never becomes a finding: a person repeated each line above by hand.

    6 of 148 artefacts shownPage 35 of 42

The five pages sit in a stack, the current one in front. You can also open any page from the list above.

Illustrative A sample for a made-up company. The full report is about 40 pages. About 6 are the summary and the plan.

09How it works

Four weeks from kick-off to a fix plan.

A lead auditor runs the audit with your team. AI tools scan every system first, then senior engineers dig deeper.

Wk 01 → Wk 04 · 4 phases · 3 checks · results in week 4

Audit schedule · combined audit · four working weeks Evidence log open from day one Checks · 3

Schedule diagram: Scope runs in Wk 01; Investigate runs in Wk 01–03; Quantify runs in Wk 03–04; Report runs in Wk 04. An evidence log stays open across all four weeks. Three checks sit on the timeline — Access confirmed at the end of week 1. Draft review at the end of week 3. Results meeting at the end of week 4.

  • End of week 1 Access confirmed Scope signed, log-ins tested and test rules agreed before any scan runs.
  • End of week 3 Draft review We check each finding with your engineers before we write it up, and drop false alarms.
  • End of week 4 Results meeting 90 minutes with your leaders and team leads. It ends with owners and dates for each fix.
  1. 01Wk 01

    Scope

    Goals, systems, access, the people involved and the decisions the audit supports.

    You get

    • Written scope
    • Access checklist
    Run by
    Lead auditor · your lead
    Moves on only when
    Read-only access works everywhere
  2. 02Wk 01–03

    Investigate

    Scans, checks by hand, interviews and data analysis. We save evidence for every finding.

    You get

    • Evidence log
    • Interview notes
    • Scan results
    Run by
    AI tools · 2 senior engineers
    Moves on only when
    Every finding is repeated by hand
  3. 03Wk 03–04

    Quantify

    We rate each finding, price what waiting costs, size the effort to fix and rank the list.

    You get

    • Findings register
    • Cost model
    • Ranked fix list
    Run by
    Lead auditor · your finance lead
    Moves on only when
    You confirm the cost inputs
  4. 04Wk 04

    Report

    A summary, full findings and a plan for 30, 60 and 90 days, talked through with your leaders and engineers.

    You get

    • Results meeting
    • Detailed report
    • 90-day fix plan
    Run by
    Lead auditor · area leads
    Moves on only when
    Top findings have owners and dates

What we need from you

  • Read-only access Code, cloud, analytics, search and monitoring tools. We change nothing, except in security tests you agree to.
  • 4–6 hours Short interviews with the people who build and run your systems, spread over weeks 1 and 2.
  • Signed test rules A signed scope and test window, agreed before any security test starts.

10What you get

Six handover files, each written for its reader.

Leaders get what needs their decision. Finance gets the cost model. Engineers get the evidence and a fix list for their tracker.

Handover · audits/your-company/2026-Q4/ 6 files Shared folder · your ownership
  1. 01

    Executive summary

    01_executive-summary.pdf

    The findings that need your decision, each with its cost and effort to fix.

    Deck · 2 pages Written for: Board, owner
  2. 02

    Detailed findings with evidence

    02_findings-detail.pdf

    Every finding with steps to repeat it, evidence, why we rated it and an owner.

    Report Written for: Engineering leads
  3. 03

    Scorecard by audit area

    03_scorecard.xlsx

    Six areas scored 1 to 5, each with its standard and the reason for the score.

    Dashboard Written for: Owner, audit lead
  4. 04

    Ranked fix list

    04_ranked-fix-list.csv

    Rows ready for Jira or Linear: title, severity, days of effort, what it depends on and a test.

    Sheet · Jira Written for: Engineering teams
  5. 05

    Cost-of-waiting estimates

    05_cost-model.xlsx

    Open formulas on your own figures. Change an input and every number updates.

    Model · Sheet Written for: Finance, owner
  6. 06

    90-day fix plan

    06_30-60-90-plan.pdf

    The fix order fitted to your team’s time, with owners and the re-test date.

    Plan Written for: Owner, team leads

Sample paths File names are examples. The findings register also exports as CSV, ready for your tracker.

Also in the handover

  • Session · 90 min

    Results meeting

    Your leaders and engineers question the findings together and leave with an agreed fix order.

  • Archive · raw

    Evidence appendix

    Scan results, logs, screenshots and interview notes, filed by finding, so you can check any rating.

  • Report · comparison

    Re-test

    An optional re-run of the same checks after the fixes, compared with the first audit.

We scope the re-test separately from the audit.

Formats you own
Sheets, CSV and PDF. No portal, licence or expiry date.
Evidence kept
We keep raw evidence for the agreed time, then destroy it when you ask.
Reusable register
A later audit can use the same register and compare line by line.

11What changes

Fixes, re-tested at 90 days.

At the results meeting we agree measures and targets with you. The re-test shows what the fixes changed.

Re-test comparison · Your company · first audit, then re-test at 90 days Same instruments, same sample Targets

Showing

Each bar is scaled inside its own row — the units differ by measure.

  1. High-severity findings open count At audit 7 Re-test target 1 −6
  2. Findings with a named owner and a date share of all findings At audit 18% Re-test target 100% +82 pts
  3. Key journeys passing Core Web Vitals of 6, for 3 in 4 visits At audit 2 / 6 Re-test target 6 / 6 +4 journeys
  4. Modelled monthly value recovered of the value identified At audit $0 Re-test target $31,600 +$31,600 / month
  5. Cloud spend classified as waste share of the bill At audit 9.6% Re-test target 3% −6.6 pts

Illustrative Figures are targets for a combined audit of a mid-sized online business, not a named client’s results. Starting figures are measured in week one. Targets are agreed at the results meeting.

  1. 01

    A ranked list of fixes

    Findings ranked by impact and effort, so you know what to fix first.

  2. 02

    Numbers your leaders can use

    The cost of waiting and the effort to fix, so old code becomes a budget decision.

  3. 03

    Independent starting point

    Scores to measure progress against, re-run in 6 or 12 months.

Same method as the first audit
We re-run each measure the same way, so the comparison is fair.
Owned by your team
The re-test shows which findings your team fixed, without blame.
Value checked against the cost model
We use the same cost model and your inputs. Any wrong assumption is fixed in both columns.

Offers & plans

Audits and assessments for software, security, search, data, AI and cloud.

Independent audits that find what is wrong, show what it costs and rank the fixes. Run one or several together.

Categories
04
Offers
14
Plans
03
Not sure what you need? Tell us the problem

How to buy

  1. 01Pick offers. Ask about one, or add several to one enquiry.
  2. 02Choose a plan. A small job, a fixed project or ongoing help.
  3. 03Send your enquiry. We reply within one working day.

Browse by category

Timelines are typical. We write the scope before we quote.

01Software audits

4 offers
Typical timeline: 2–4 weeks

Technical & code audit

An independent review of your code and system design: quality, security, tests, third-party code and room to grow.

What’s included

  • Code quality and ease of change
  • System design and room to grow
  • Third-party code & licences
  • Tests and how releases go live
  • Ranked fix list
  • Code quality
  • System design
  • Tech debt

Best forBefore funding, a sale, a rebuild or a change of supplier.

Typical timeline: 1–3 weeks

Speed audit

Find out why your site or app is slow and what each fix is worth. We use visit data and load tests.

What’s included

  • Google speed scores from actual visits
  • Slow server and database steps
  • Load test to find the limits
  • Ranked fixes, each with its gain
  • Core Web Vitals
  • Load testing
  • Slow spots

Best forSites and apps that are slow or struggle when busy.

Typical timeline: 2–3 weeks

Release process assessment

Measure how fast and safely your team releases software. Then find what slows it down.

What’s included

  • Release speed and failure rates (DORA)
  • How code gets tested and released
  • Test servers and tools review
  • A plan to improve
  • DORA metrics
  • Automation
  • Release process

Best forTech leaders whose releases feel slow or risky.

Typical timeline: 2–4 weeks

Technical due diligence

An independent tech check of a company, product or supplier before you invest, buy or rely on it.

What’s included

  • System design, code and security
  • Interviews with the team
  • Growth, cost and key-person risks
  • Report for investors or your board
  • Due diligence
  • Mergers
  • Investment

Best forInvestors, company buyers and teams choosing key software.

02Security, compliance & accessibility

3 offers
Typical timeline: 2–3 weeks

Security assessment

A check of your apps, cloud and log-ins for security flaws and weak settings, ranked by risk. We only run attack tests under a signed scope.

What’s included

  • Security flaw check
  • Cloud and log-in settings review
  • Attack paths to key systems
  • Risk-ranked findings and fixes
  • Security flaws
  • Cloud settings
  • Risk-ranked

Best forCompanies that have never had an independent security review.

Typical timeline: 2–4 weeks

Compliance gap assessment

See how far you are from ISO/IEC 27001:2022, SOC 2 or India’s DPDP Act 2023. We get you ready for the audit. We do not certify.

What’s included

  • Each required safeguard checked
  • Review of existing evidence
  • Effort to close each gap
  • Audit-ready plan
  • ISO/IEC 27001:2022
  • SOC 2
  • DPDP Act 2023

Best forCompanies asked for compliance evidence by customers or regulators.

Typical timeline: 1–3 weeks

Accessibility audit (WCAG 2.2 AA)

Check that your site or app works for people with disabilities. We test with tools, screen readers and keyboards.

What’s included

  • Tool scans of key page types
  • Hands-on tests with screen readers
  • Issues matched to WCAG rules
  • Fixes in priority order
  • WCAG 2.2 AA
  • Hands-on tests
  • Screen readers
  • Playwright

Best forAnyone serving the public, or with a legal duty to be accessible.

03Search, data & analytics audits

3 offers
Typical timeline: 1 week

Website health check

A quick check of one website’s speed, search, accessibility and security basics. You get the few fixes that matter most.

What’s included

  • Page speed check
  • Google search basics
  • Accessibility spot checks
  • Basic security settings check
  • Top fixes in priority order
  • Quick start
  • Speed · search · accessibility
  • Security basics

Best forSmall and mid-size businesses wanting a quick, low-risk first look.

Typical timeline: 2–3 weeks

Search & AI visibility audit

Find out why your site is not ranking or named in AI answers, and what to fix first.

What’s included

  • Pages Google can find and list
  • Missing topics and search terms
  • Page labels for search and AI
  • How often AI names you today
  • Ranked fix list
  • SEO
  • AI answers
  • First scores
  • Ahrefs

Best forSites losing Google visits, or before a redesign.

Typical timeline: 2–4 weeks

Data & analytics audit

Check whether you can trust your data and reports, from tracking to consent.

What’s included

  • Website tracking review
  • Data quality and source checks
  • Key number definitions
  • Consent and privacy check
  • Data quality
  • Tracking
  • Consent
  • dbt

Best forTeams making decisions on numbers they do not fully trust.

04AI & cloud assessments

4 offers
Typical timeline: 2–4 weeks

AI readiness assessment

Score how ready your data, systems, skills and rules are for AI. Then list what to fix before you build.

What’s included

  • Readiness score for 6 areas
  • Which AI ideas are ready
  • Risk and compliance check
  • Groundwork plan
  • Readiness score
  • Groundwork

Best forCompanies planning their first AI project.

Typical timeline: 2–3 weeks

AI system review

An independent check of an AI tool you already use: answer quality, safety, cost and who oversees it.

What’s included

  • Tests on your own examples
  • Hidden-instruction and data-leak tests
  • Cost and speed review
  • AI rules and human checks
  • Answer tests
  • OWASP LLM Top 10
  • Cost
  • OpenAI

Best forTeams with AI already live, unsure how well it works.

Typical timeline: 1–3 weeks

Cloud cost audit

Find where your cloud bill goes and how much you can save. Each saving is sized and rated for risk.

What’s included

  • Spend by system and team
  • Idle and oversized servers
  • Long-term discount options
  • Savings plan with estimates
  • Cloud bills
  • Savings plan
  • AWS
  • Microsoft Azure

Best forCompanies with a cloud bill growing faster than usage.

Typical timeline: 2–3 weeks

Cloud reliability & recovery assessment

Review how your cloud is built to stay up, stay safe and recover. We also test that your backups restore.

What’s included

  • Cloud design review
  • Single points of failure
  • Backup restore test
  • Recovery time and data-loss goals
  • Reliability
  • Restore goals
  • Restore test
  • AWS
  • Microsoft Azure

Best forBusinesses where an outage would be costly.

Your enquiry

Tick “Add to enquiry” on any offer, choose a plan, then continue. Or enquire about one offer.

How we work with you

Ways to start, from a question to a quote.

Ask a quick question, send your project details or request a quote. The person who will lead the work reads each one in full. Services in your enquiry go with it.

Or book a 30-minute call

What are you sending?

  1. 01

    About 2 minutes3 short answers

    For a first chat, a press request or anything not ready to plan yet.

    You get A reply from a named lead

  2. 02Recommended

    About 8 minutes5 short steps

    Goals, who it is for, budget and timing, so our first reply can outline the work.

    You get Options and prices after one call

  3. 03

    About 15 minutesYour documents attached

    Your documents, deadlines and the purchasing and security rules to meet.

    You get Confirmation and a named lead

How it is priced

Each plan shows how it is priced. Work starts once we agree a written scope and price.

  • Typical length
    1–3 weeks
    Pricing
    Fixed fee
  • Typical length
    4–12 weeks
    Pricing
    Fixed price
  • Typical length
    6–18 months
    Pricing
    Priced per written scope
Compare what each plan includes
What each plan includes and who it suits
PlanWhat you getBest for
SprintA short, fixed job that answers one clear question.
  • Scope and result agreed before we start
  • A senior lead and the right specialists
  • A weekly review with you
  • A clear answer or a test version
An audit, a brand check or a test version of an app
ProjectOne clear job for one fixed price.
  • A written scope: what you get and how we agree it is done
  • A named project lead and a fixed team
  • A shared plan with checkpoint dates
  • Source files, yours once paid for
A brand identity, a website, a simple app or a set of tools
EnterpriseA large, long project with its own team and agreed response times.
  • A project director and a decision group
  • A team for each part of the work
  • Response times, reports and a list of risks
  • Security, legal and purchasing checks in the plan
Large companies making changes across markets, brands or business units

12Questions

Audit questions we hear on first calls.

Short answers on our method, access, safety, security tests, costs and what happens next.

  • 01

    How is this different from an automated scan?

    Method

    A scan lists problems. An audit tells you which ones matter. We add senior review, your team’s context, the cost of each finding and a ranked plan.

  • 02

    What access do you need?

    Access

    Read-only access to your code, cloud, analytics and tools. We also need a few hours with the people who run your systems. Security tests need a signed scope and test rules.

  • 03

    Will it disrupt live systems?

    Safety

    No. We only read your data. We slow our scans so your systems stay fast. Load and security tests run on a test copy, or live at a time agreed in writing. Nothing risky runs until your named contact approves it.

  • 04

    Will you tell us things we do not want to hear?

    Independence

    Yes. An audit is only useful if it is independent. We check findings with your team first, but we do not soften them.

  • 05

    Is a penetration test included?

    Security tests

    Not a formal one. We test your apps and cloud against the OWASP Top 10, under signed rules. A formal security test is a separate service we offer. Letters and certificates for insurers or customers come from accredited bodies, never from us.

  • 06

    Can you audit a system another supplier built?

    Suppliers

    Yes. We need read access and any documents. Findings blame no one. Each has steps to repeat it and a test, ready to hand to that supplier.

  • 07

    How do you put a price on a finding?

    Costs

    With your own figures, where a cost can be worked out. Lost sales come from your analytics, waste from your bills. Risks are rated, not priced. You can change every input.

  • 08

    Can you fix what you find?

    After the audit

    Yes, or your team can. Anyone can work from the fix list. If we do the work, we scope it separately, so the audit stays independent.

  • 09

    Which audit should we start with?

    Scope

    Start with the one closest to your next decision. That might be a rebuild, an AI project, funding, a compliance deadline or falling search traffic. Several audits can share one fix list.

Tell us what you need built.

You will talk to the lead who would run your work.

Book a call

Three ways to start

We always agree a written scope and price before work begins.

Choose one of the three ways above