Operating-layer AI practice

Use expensive AI only where it earns its keep.

Trueform helps senior operators decide where expensive AI is worth using, then rebuild the workflow around it: context, permissions, routing, review, memory, measurement, and spend discipline.

f.01

Different models need different jobs.

Cheap, specialist, open, and frontier models now have different economics. The operating layer decides which work deserves which level of intelligence.

Trueform starts with the route from tokens to value, not with a model demo.

f.02

Find the point where AI starts breaking the work.

The first useful move is deliberately small: one workflow, one conversation, and one point where capability is moving faster than the business can control or measure.

If we cannot find a meaningful boundary to improve, we say so. The output is a plain decision, not a maturity score or a decorative dashboard.

f.03

Build the operating layer around the value.

i.

Diagnose the work and the spend

Find where capability is already moving faster than the business can govern or measure.

ii.

Name the value path

Separate the work that deserves frontier reasoning from the work that needs cheaper machinery.

iii.

Rebuild the workflow

Put context, permissions, model routing, review gates, and handoffs into the operating flow.

iv.

Embed measurement

Track time, throughput, quality, risk, spend, and decision speed before scaling the system.

f.04

Proof before scale, with named local seniors.

Trueform is a named senior practice, not a vendor bench. The senior people named in the work stay close from diagnosis through adoption.

The work is based in the UAE and built for operators who need control, continuity, and a method that survives the next model release.

About the practice

f.05

Capturing value at the point of work.

Current Work

Clinical capture, at the point of delivery

An active engagement restoring clinical capture into the vet's hand, voice-first and offline-capable. Linked from the home page at f.04.

Discuss a workflow like this

f.06

Services

See the service ladder

Start with the smallest honest proof. Move into build, recovery, or ongoing senior support only when the boundary holds.

30-45 min call

Readiness Diagnostic

A conversation-only pass over one workflow. We place the work, expose the production risk, and decide whether there is a real next move.

1-2 weeks

AI Readiness Sprint

A written assessment, 100% credited against a Foothold within 60 days. No maturity score, no fake dashboard.

4-6 weeks

Foothold Engagement

The core proof engagement: one working operating change, weekly artefacts, and a weekly decision gate.

Monthly, 3-month minimum

Strategist Retainer

Continuous senior access and a standing cadence of outcomes after the first proof has landed.

f.07

What we will not do

Generic chatbot bolted onto broken work.

Vendor lock-in disguised as transformation.

Slide-only strategy without a working operating change.

Unmanaged AI spend with no value measurement.

Fake dashboards, fake logos, or invented metrics.

f.08

Field Notes

Vol 1, no. 1 · Mark Bunce · 12 June 2026

From Building to Bounding

The building is getting cheaper by the month, so the bounding has become the work: judgement, constraint, and accountability around systems that now act faster than people can check.

Read the note

f.09

Bring one workflow, one spend line, or one fragile AI pilot.

The first conversation is simple: place the work, name the boundary, and decide whether a Readiness Diagnostic or Sprint is the right next step.