Skip to content
datatruth Get your Truth Score

Start here · Truth Score Read

One AI decision, tested against your own data. In writing, within 5 working days.

Send exports (spreadsheets downloaded from each system) from two or more systems behind the decision, plus the AI proposal or plan if there is one. We match the records between them and send back a signed memo: your Truth Score™, a score out of 100 for how far your data can be trusted; a Leverability read, saying whether the AI in question can be used now, after fixes, or not at all; the red flags between your systems; and a clear verdict.

Starts with a 30-minute call. Commits you to nothing.

What you send

Any two systems. Spreadsheets count.

The truth sits in the gaps between systems, so we need at least two that record the same customers, people, projects or invoices. Tell us the decision on the call and we tell you which systems matter. We never log in to anything: one person on your team runs standard exports from a field list we send first.

  • CRMAccounts, contacts, deals, owners
  • BillingCustomers, invoices, payments
  • ERP and financeLedger, customers, terms
  • HR and payrollPeople, roles, start and leave dates
  • ProjectsHours, delivery, billable work
  • Support deskTickets, contracts, service levels
  • SpreadsheetsBoard packs, trackers, the numbers nobody put in a system
  • The proposal or planOptional: the AI proposal, business case or plan under review
Field list · sent before anything else2 of 3 systems

CRM · accounts and deals

account_name
To match customers across systems
account_id, website
The strongest keys we can match on
owner, status
Who is responsible, and is it live
close_date, amount
To tie each closed deal to an invoice

Billing · customers and invoices

customer_name, billing_ref
The other side of every match
invoice_date, total
What was actually billed, and when
No passwords, no logins, nothing installed. If a system can’t export a field we need, we say so on the call, before you send anything.

What we do

The engine does the volume. A person checks every red flag.

  1. 01

    Map the fields

    Each export is mapped to the same model: who the customer is, what was sold, what was billed, who owns it. Different systems, one vocabulary.

  2. 02

    Match the records

    Our engine matches the customers, people, deals and invoices across the exports you send, by shared ID, web domain and name, including names spelt differently in each.

  3. 03

    Test the decision

    If there is a proposal or plan, each claim is mapped to the data it needs and tested against what we found. If not, we test the AI use case you name.

  4. 04

    Check, score, sign off

    Every red flag is checked by hand against sample records before sign-off. Then the Truth Score, the Leverability read and the verdict go into one memo.

The memo

One page. Signed off, so someone answers for it.

Written for the person who signs the cheque, not the data team. The verdict comes first; the evidence follows, in your own records. This one is the real sample.

  1. 1
    The verdict

    Sign, fix first, or walk away. One sentence on why.

  2. 2
    Your Truth Score™

    Each pillar shown, the cap applied if a critical pillar is weak, and any pillar the exports couldn’t support marked limited signal or not assessed.

  3. 3
    The Leverability read

    Can your data run the AI in question: Deploy now, Needs work or Blocked, requirement by requirement.

  4. 4
    Red flags between systems

    The gaps no single system shows, counted, ranked and labelled with the systems involved.

  5. 5
    A short fix list

    What to fix first, in order, with an owner and an effort estimate, ready for your team or any outside firm.

  6. 6
    The scope line

    Exactly what we looked at and what we didn’t, so the memo never claims more than the data shows.

  7. 7
    Sign-off

    Checked by hand and signed off by DataTruth, then walked through with you on a call.

How this score was reached
Truth Score Read · Sample · Example CoConfidential · Page 1 of 1
Decision
Proposed AI revenue forecasting tool
Prepared for
CEO and CFO
Compared
CRM, finance and HR exports · 72,837 records

Our verdict on the proposal

Don’t sign yet. Only 13% of deals and invoices reconcile between the CRM and finance, and 823 paying customers have no account in the CRM. A forecast trained on this would learn from deals finance can’t see. Link customers and trace deals to invoices first, then re-test.

Truth Score™

59/ 100Band C

Significant work needed

  • Accuracy22% 88
  • Completeness18% 97
  • Governance18% 69
  • Consistency16% 88
  • Connectivity14% 44
  • Lineagelimited signal12% 50

Weighted average 75. Capped at 59 because Connectivity, a critical pillar, scored 44: strong pillars can’t hide a weak foundation.

Leverability read · the AI in question

AI revenue forecasting

Blocked
  • Deals tied to invoices in finance13% reconcile
  • One customer across CRM and finance46% reconcile
  • Sales activity historyNot in exports
  • Deal close dates97% valid

Red flags between your systems

  • High

    823 customers in finance with no account in the CRM. A further 2,978 CRM accounts have no finance record; some will be prospects.

    CRM ↔ Finance

  • High

    Only 13% of deals and invoices reconcile: 4,964 deals and 21,964 invoices with no match on the other side. A traceability gap, not yet a revenue figure.

    CRM ↔ Finance

  • Medium

    3,128 matched customers where the CRM and finance disagree on the city, and 421 where the country is written differently.

    CRM ↔ Finance

  • Medium

    1,004 invalid, 845 duplicated and 870 disposable email addresses across 23,116 contacts.

    CRM

  • Medium

    521 invoices and 280 deals carry invalid dates.

    Finance · CRM

Fix first, in this order

  1. 1

    Give every customer one ID across the CRM and finance

    RevOps and finance · est. 2 to 3 weeks
  2. 2

    Trace deals to invoices, and agree which deal stages should produce one

    Finance and sales ops · est. 1 to 2 weeks
  3. 3

    Clean contact emails, and standardise city and country, then re-test

    Sales ops · est. 1 week

Scope CRM accounts, contacts and deals; finance customers, invoices and subscriptions; HR employees: 72,837 records in 7 exports. Export-based: live configuration, permissions and access logs not reviewed. Lineage scored on limited signal: the exports carry creation dates but no source-system field. Effort estimates are review judgement, not engine output.

Checked by hand · Signed off by DataTruth Ref SAMPLE-01

Sample memo. Real engine output on generated test data for a fictional B2B software company. Not a client, and no client data.

Two possible answers

The memo we most like writing says ‘sign’.

If your data can carry it, you’ll have that in writing, and no reason to buy anything else from us. Same method, same rules, same one page. Only the evidence decides which one you get.

Fix firstReal engine output, test data

Truth Score Read · Sample · Example CoConfidential · Page 1 of 1
Decision
Proposed AI revenue forecasting tool
Prepared for
CEO and CFO
Compared
CRM, finance and HR exports · 72,837 records

Our verdict on the proposal

Don’t sign yet. Only 13% of deals and invoices reconcile between the CRM and finance, and 823 paying customers have no account in the CRM. A forecast trained on this would learn from deals finance can’t see. Link customers and trace deals to invoices first, then re-test.

Truth Score™

59/ 100

Band C, significant work needed

Leverability read

AI revenue forecasting

Blocked

Deals tied to invoices in finance: 13% reconcile

Top findings between your systems

  • High

    823 customers in finance with no account in the CRM. A further 2,978 CRM accounts have no finance record; some will be prospects.

    CRM ↔ Finance

  • High

    Only 13% of deals and invoices reconcile: 4,964 deals and 21,964 invoices with no match on the other side. A traceability gap, not yet a revenue figure.

    CRM ↔ Finance

Checked by hand · Signed off by DataTruth Ref SAMPLE-01

Sample memo. Real engine output on generated test data for a fictional B2B software company. Not a client, and no client data.

SignIllustrative, a sign answer

Truth Score Read · Example CoConfidential · Page 1 of 1
Decision
AI support ticket triage from Vendor B
Prepared for
CEO and COO
Compared
Support desk, CRM and billing exports

Our verdict on the proposal

Sign. Triage needs tickets tied to customers and live contracts, and 94% are. Re-link the 41 tickets on ended contracts before go-live. Nothing in the data stands in the way of this proposal.

Truth Score™

84/ 100

Band A, ai ready

Leverability read

Support ticket triage

Deploy now

Tickets tied to a live contract: 94% linked

Top findings between your systems

  • Medium

    41 open tickets linked to contracts that ended last quarter.

    Support ↔ Billing

  • Low

    12 resolution codes used fewer than five times; worth folding into the main list.

    Support

Checked by hand · Signed off by DataTruth Ref EX-0412

Illustrative example, not a client.

Everyone in the room gains if you sign. We gain nothing either way.

We sell no AI, no software and no fixes. We take no referral fees, commissions or margin from anyone. Our fee is fixed before we start, so a ‘sign’ pays us exactly what a ‘walk away’ does.

Timeline

Day 0, day 2, day 5. The clock starts when complete exports arrive.

  1. Before day 0

    The call and the paperwork

    • A 30-minute call about the decision
    • A fixed fee, agreed
    • NDA and data processing agreement signed
    • Field list sent to your team

    Your part, about an hour

  2. Day 0

    Exports arrive

    • Standard exports from two or more systems
    • The proposal or plan, if there is one
    • Missing fields flagged straight away

    Your part, one person

  3. Day 2

    Matched across systems

    • Fields mapped, records matched
    • Close calls reviewed by a person
    • Claims mapped to the data they need

    Our part

  4. Day 5

    The memo, then a walk-through

    • Every red flag checked by hand
    • Memo signed off and sent
    • A call to take you through it

    Our part, then 30 minutes of yours

Working days. Day 5 means within 5 working days of complete exports.

With a proposal attached

Got a proposal on the table? Send it with the exports.

We take every claim the proposal makes, work out what each one needs from your data, and test it. Not whether the AI is clever, but whether your data can feed it. The verdict lands before the contract does.

Proposal · Vendor Ap. 3 of 22

AI revenue forecasting for Example Co

Our model learns from your existing pipeline and billing history. 1No data preparation is required; we connect to your CRM and billing system as they are.

Customers typically see 2forecast accuracy within 5% from month three, with 3go-live in six weeks from signature.

The claimWhat it needs, and what we found
1No data preparation required One customer across CRM and billing. 117 customers have no billing match and 86 are recorded twice.Not supported
2Accuracy within 5% from month three Closed deals that tie to invoices, to learn from. 214 closed-won deals have no matching invoice. We test the data it learns from, not the promise.At risk
3Go-live in six weeks Clean inputs on day one. The fix list estimates 3 to 5 weeks of data work before the model sees anything.At risk

Verdict

Fix first, then renegotiate. Data work before go-live, and accuracy measured from the fixed baseline.

Illustrative example, not a client or a real vendor.

Data handling

Exports in, metrics kept, records deleted.

The same rules for every engagement. The detail is on the Security page.

  • Exports only

    No logins to your systems and nothing installed. One person on your team runs standard exports from a field list we send first.

  • NDA and data processing agreement first

    Both are signed before any data moves. Your templates or ours.

  • Sub-processors disclosed

    The full list of sub-processors comes with our data processing agreement, before any data moves. Any transfer outside the EU is covered by Standard Contractual Clauses or another safeguard GDPR approves.

  • Exports deleted after the engagement

    We keep quality metrics and the memo. The memo cites a handful of sample records as evidence. How we handle your data.

What happens next

It stands on its own. Three ways it can end.

The memo is the deliverable, not a sales step. What happens next is up to you and your team.

  • If the data holds up

    Sign, with evidence

    The memo says so in writing. You go ahead on your own records, not a vendor’s word, and we tell you if you need nothing more from us.

  • If it needs work

    Fix first, then re-test

    Hand the fix list to your own team or any outside firm. We never do the work. When the fixes land, a re-test shows whether they held.

  • If the question is bigger

    Go further, if it’s worth it

    When one decision turns out to be every AI bet in the business, an AI Investment Review tests and ranks them all.

  1. Step 0A 30-minute callIs this worth testing?
  2. Step 1 · You are hereTruth Score ReadOne decision · 5 working days
  3. Step 2AI Investment ReviewEvery AI bet · about 2 weeks
  4. Step 3AI Value TrackingIs the data holding up? · quarterly

Founding clients

A founding rate for our first clients, in exchange for a private reference call once you’re happy with the work. Only with your consent: we never name a client, fund or target publicly without written consent.

Ask about founding terms

Questions

Before you send anything.

The questions to settle before the first export leaves your building. If yours isn’t here, bring it to the call.

Book the call
What does it cost?

A fixed fee, agreed before we start, that never moves with the verdict. It is a small fraction of the proposal it tests; if it wouldn’t be, we’ll tell you on the call. You get the number on the first call, once we know which systems and decisions are in scope.

You’re new. Why should we trust the verdict?

We are new, and we won’t pretend otherwise. That is why the method is published, including the cap that stops strong pillars hiding a weak one. Every finding points to records your own team can open and check, and the scope line says what we didn’t check. You can stop at the memo. Our first clients get a founding rate in exchange for a private reference call once they’re happy with the work, and only with their consent: we never name a client, fund or target publicly without written consent.

What do we need to send?

Standard exports (spreadsheets downloaded from each system) from any two or more systems the decision depends on: CRM, billing, ERP and finance, HR and payroll, projects, support. Spreadsheets count. We send the exact field list first, so one person on your team can run the exports. If there is a proposal, plan or business case, send that too.

How long does it take?

A Truth Score Read is delivered within 5 working days of complete exports. An AI Investment Review takes about 2 weeks. AI Value Tracking runs every quarter. If an export is missing fields we need, we say so straight away; the clock starts when complete exports arrive.

Do you need access to our systems?

No. One person on your team runs standard exports from the systems behind the decision and sends them under NDA. We send the exact field list first. You never log in to anything and nothing is installed.

What happens to our data?

It arrives under NDA and our data processing agreement. The full list of sub-processors comes with our data processing agreement, before any data moves. Any transfer outside the EU is covered by Standard Contractual Clauses. Raw exports are deleted after the engagement.

Do you put our data into an AI model?

The Truth Score is rule-based: the same data, scored on the same date, gives the same score, and no AI model decides it. We do use a language model (Anthropic’s Claude, through its commercial API) to read the plan or proposal you send and to help draft the memo’s wording from our findings. A person checks every line before it reaches you. If you’d rather we didn’t use it on your engagement, say so and we do that part by hand.

Can you test a specific AI proposal?

Yes. Send it with your exports. We take each claim it makes, work out the data that claim depends on, and check whether that data is there and can be trusted. Not whether the AI is clever, but whether your data can feed it. The verdict is plain: sign, fix first, or walk away.

The consultancy’s proposal already includes a data phase. Why check first?

Because by phase one you have signed. Their data phase is scoped, priced and staffed by the firm that will run the phases after it, so it is designed to lead to them. Ours comes before the signature, from a firm paid the same whatever the answer, and it tests whether the proposal’s own assumptions hold in your records. Use the memo to re-scope or negotiate the proposal.

What if our data is fine?

Then the memo says sign, in writing, and you go ahead with evidence instead of a vendor’s word. If you don’t need anything more from us, we’ll tell you that too.

What exactly does the memo stand behind?

The facts in it. Every number points to records you can open, and the scope line says what we didn’t check. The decision stays yours: the memo says what your data can and can’t support, and what closing each gap takes. If your team disputes a finding, we re-check it against the records with them.

Do we have to go further after a Truth Score Read?

No. It stands on its own. You can stop at the memo, hand the fix list to your own team, or ask for an AI Investment Review when the question becomes every AI bet in the business. You decide, and nothing is bundled.

Two systems in. One signed answer out.

The gaps between your systems, and a verdict, in writing within 5 working days of complete exports.

Starts with a 30-minute call. Commits you to nothing.

Get your Truth Score