DIGIFORMINDEX

Most AI spend never reaches EBITDA. We only build what does.

SECTIONS01 / 10
01Overview→02The gap→03Clients→04Problem & fix→05The standard→06Proof→07Engagements→08Questions→09AI Value Map→10Contact→
HomeAICommerceGovernanceBack officeROIInsightsWork
BOOK A CALL →

24H REPLY · FROM A PRINCIPAL

WE BUILD IT AND WE RUN IT
01
01 — AI Transformation · For any company putting AI to work

Most AI spend never reaches EBITDA.We only build what does.

Fluency, governance and value mapping first — then the two or three things worth building, run by a sitting CTO.

From pilots that stallTo systems in daily use
From vendor promisesTo a ranked, costed plan
From risk nobody ownsTo a board that decides
0202 / 10
The gap

Nearly everyone feels AI working. Almost nobody can show it.

That distance — between the feeling and the number — is where budgets quietly disappear. Closing it is the whole job.

Of executives say they're benefiting from AIReported97%
See significant organisational ROIEvidenced29%

68 points of spend nobody can evidence

Source: State of Enterprise AI, Global AI Forum, 2026.0 — 100% of surveyed executives
0303 / 10
Clients
Trusted by operators, from growth brands to the Fortune 500.

A selection of past and present clients.

Nili Lotan
NOYZ
Frère NY
Fleur du Mal
DKMS
Alta Cycling Group
Lake Pajamas
Tevine Teas
Blackbeard Spice
Fortune 500Several engagements, under NDA
0404 / 10
The problem and the fix

Why AI spend fails, and what we do about it.

Start with a value map →
Problem 01

You bought it off a demo.

Nobody in the room could separate a real capability from a rehearsed one, so it got approved on confidence.

Our fix — stage 01
Fluency

Your leadership gets hands on the tools and judges the next pitch themselves.

  • Executive working sessions
  • Hands on the tools, not slideware
  • Function-by-function walkthroughs
  • A shared vocabulary for the board
Problem 02

No one put a number on it.

There was no baseline, so there is nothing to measure the invoice against. Renewal becomes a matter of opinion.

Our fix — stage 02
Map

Every opportunity gets a baseline and a payback figure before anything is built.

  • AI value mapping
  • Baseline and payback per use case
  • Sequenced build order
  • An explicit “not yet” list
Problem 03

Approvals went to committee.

Legal worries, IT hesitates, the sponsor moves on. Good use cases die queuing behind bad ones.

Our fix — stage 03
Govern

One body says yes, no or not yet — and logs why. Approvals take a week, not a quarter.

  • AI governance board
  • Written policy staff and auditors can read
  • Risk register
  • EU AI Act obligations mapped
Problem 04

The tool works. Nobody uses it.

Adoption was treated as training, not a change to the work. Six weeks on, the team is back in the spreadsheet.

Our fix — stage 04
Build & adopt

We change how the work is done, and stay until your team does it that way.

  • Scoped, sequenced delivery
  • Built into the systems you already run
  • Adoption measured, not assumed
  • Fractional CTO advisory

Every month this runs, the licences renew and the baseline you never took gets harder to reconstruct. We don’t resell platforms or take vendor commissions — if nothing here pays back yet, that is what the value map will say.

0505 / 10
The standard

Governance isn’t the brake. It’s what lets you go faster.

Most firms sell governance as compliance — a cost you accept to stay out of trouble. That’s backwards. A board that can approve a use case in a week is the difference between three builds a year and none, and the register is what tells you which ones paid.

  • A body that can say yes, no, or not yet — and logs the reason.
  • A policy your staff, your customers and your auditors can all read.
  • A register that tracks the risk and the payback side by side.
  • EU AI Act obligations mapped to what is actually in force today.
0606 / 10
Proof

What we can actually show you.

Operating facts, not a maturity-model diagram. The AI practice is led personally — you are buying a named person’s time, not a methodology.

Ask for references →
CPG brand · anonymised

Supplier invoices read by AI, written into the ERP.

Order entry, per day
3 hrs → <1
Time to live
4 weeks from kickoff
Volume
About 200 invoices a month
Read the case study →
NOYZ · Beach House Group

Executive fluency first. The build followed from it.

Time to first automation live
2 weeks
Started as
Executive AI fluency
Relationship
Still running it
AI governance

Boards built, and then actually chaired.

Chaired by
A sitting CTO
Output
Policy & risk register
Decisions
Logged, with reasons
2–3
Builds we recommend, out of dozens mapped
1 day
To a reply from a principal
Zero
Vendor commissions or resale margin
Current
The CTO seat is held today, not in 2019
0707 / 10
Engagements

How to work with us.

Engagement 01
3 weeks · fixed fee

AI Value Map

We walk your operation and come back with every opportunity ranked by payback — scoped, sequenced, with a baseline against each. Including the ones not worth building.

Best if the pressure to “do something with AI” is real and the business case isn’t.

Engagement 02
6–8 weeks · project

Fluency & governance

Executive working sessions, then the board, policy and risk register stood up behind them — chaired with you until it runs on its own.

Best if approvals are the bottleneck, or the board has started asking about the EU AI Act.

Engagement 03
Retained · monthly

Fractional CTO

A sitting CTO in your leadership meetings a day or two a month — owning the AI roadmap, chairing the board, and accountable for whether the builds land.

Best if you need the seniority without the search and the salary.

0808 / 10
Questions

Before you get in touch.

How do you measure whether AI actually improved EBITDA?

By baselining before we build. Every use case in the value map carries a current cost — hours, error rate, cycle time, headcount avoided — and a payback estimate against it. After the build we measure the same line. If a use case can't be baselined, that's usually a sign it shouldn't be first.

Why do most AI pilots fail to deliver ROI?

Three reasons, in our experience: the pilot was approved on plausibility rather than payback, no single body owned the decision to scale it, and adoption was treated as training instead of a change to how the work gets done. None of those are technology problems, which is why buying better technology doesn't fix them.

What is an AI governance board, and do we need one?

A standing body that decides which AI use cases are approved, which are off-limits, and how each decision gets logged. You need one once more than one team is experimenting, or once a customer, auditor or regulator might ask what you approved and why. It speeds approvals up rather than slowing them down.

Does the EU AI Act apply to us if we're a US company?

It can — the obligations follow the market, not your head office. But the timeline changed: the Digital Omnibus (Regulation (EU) 2026/1744) entered force on 27 July 2026 and deferred the high-risk regime to December 2027 for standalone systems and August 2028 for AI embedded in regulated products. Article 50 transparency and labelling duties, GPAI provider obligations and the prohibited-practices rules are all live now. We map which of those you actually touch rather than guessing.

How is this different from an AI consultancy?

The person advising you currently holds a CTO seat, so the accountability is present tense rather than a story about a role someone left. We also take no vendor commissions and resell no platforms, which means the value map can honestly conclude that nothing is worth building yet.

We've already tried AI and it didn't stick. Why would this be different?

Because we'd start by finding out why it didn't. Usually the use case was chosen for visibility rather than payback, or nobody changed the process the tool was supposed to replace. We only recommend two or three builds out of dozens mapped, and we stay until your team uses them daily.

Do we need clean data or an in-house tech team first?

No. We design around the systems and data you already have, and the value map accounts for the state they're in — a use case that needs six months of data cleanup gets ranked accordingly rather than quietly failing later. Where a data foundation genuinely is the first job, we'll say so.

How much of our team's time will this take?

For a value map, a few hours per function — we come to your people rather than asking them to prepare for us. The fluency sessions are the exception and are meant to be: leadership has to have hands on the tools, or they can't tell a real opportunity from a vendor pitch afterwards.

0909 / 10
Start here

The AI Value Map.

Three weeks, fixed fee. Every opportunity ranked by payback, with a baseline against each — and an honest list of what not to build. Yours whether or not we build any of it.

Request a value mapReply within one business day, from a principal
1010 / 10
Contact us

Tell us what you run.

One call with a principal, and a straight answer about where AI would pay in your operation — including when the answer is “not yet”.

Email
hello@digiform.io
Response
Within one business day, from a principal.
Practice
AI Transformation

Tell us what you run

Two minutes. It reaches a principal directly — not a queue.

Where are you with AI?

Or email hello@digiform.io directly.

01 / 10Overview02 / 10The gap03 / 10Clients04 / 10Problem & fix05 / 10The standard06 / 10Proof07 / 10Engagements08 / 10Questions09 / 10AI Value Map10 / 10ContactIndex
On this pageClose ✕
01Overview02The gap03Clients04Problem & fix05The standard06Proof07Engagements08Questions09AI Value Map10Contact
HomeCommerce & DigitalAI TransformationAI governance advisoryBack-office automationROI LabInsightsCPG case studyNOYZ case studyNOYZ · Only HumanNili Lotan case study
SITE INDEX — 12 PAGES · 86 SECTIONSCLOSE ✕
AOperating partnerHome01Commerce & Digital02AI Transformation03Why us04The work05Clients06Start
BPractice 01Commerce & Digital01Overview02Clients03What we do04Proof05Engagements06Questions07Storefront Review08Contact
CPractice 02 · you are hereAI Transformation01Overview02The gap03Clients04Problem & fix05The standard06Proof07Engagements08Questions09AI Value Map10Contact11Request an AI Value Map
DServiceAI governance advisory01Overview02In plain terms03The problem04What you get05How it runs06Why us07How you buy it08Questions09Start here10Regulated industries
EServiceBack-office automation01Overview02What we automate03Cost of waiting04Before & after05Clients06Case07How we deploy08Get an estimate09After you send10Honest answers11Methodology12Operator-led
FToolROI Lab01Overview02The lab03Method04Sources05Questions
GThe Digiform ReviewInsights01Feature Nº 1402In this issue03Topics & newsletter
HEssayInsight detail01The essay02The reading03Read next
IWorkCPG case study01Overview02Spec sheet03The problem04What we built05The stack06When it fails07The result08What it is worth09Get in touch
JWorkNOYZ case study01Overview02Spec sheet03The challenge04What we built05Build vs buy06What happened next07The speed work08Get in touch
KWorkNOYZ · Only Human01Overview02Spec sheet03What we built04Keep reading
LWorkNili Lotan case study01Overview02The store03Spec sheet04The brief05How we worked06What we shipped07Get in touch
Ask ClAIr

I answer from what’s published on this site — nothing else. If I don’t know, I’ll say so.

An AI assistant, not a person. It can be wrong.