Pilots by invitation · The Digital Foundry is the build studio of Digital Edge · Pricing on request

Home / Approach

approach

Scope. Prove. Run in production.

Every build follows the same path: a tight scope, a proof of value on your real workflow, then production with governance in place. Each stage ends with a decision, and a stop is a legitimate result.

how a build goes

Three stages, three gates.

01 / scope

Pick one workflow and define success

We work with the workflow owner to choose one process, map it as it really runs, and write down what success means in numbers your finance team accepts. We agree what data and systems the build may touch, and who signs off.

  • Workflow owner named
  • Success criteria in writing
  • Data, access and risk boundaries agreed

gate: do we have a measurable case worth testing?

02 / proof of value

Build it small, on real work

We build the agent or automation against your systems and run it on real cases, with a person at every checkpoint that matters. We measure against the agreed criteria and estimate the production path and run cost before the pilot ends.

  • Working system, not a demo
  • Evidence against the criteria
  • Production plan and run cost

gate: scale, change or stop, on the evidence

03 / production

Release it with governance in place

We harden the build for daily use: access control, logging, monitoring, failure handling and the human oversight POPIA requires. Your team gets a runbook and clear ownership, so the system does not depend on us to keep working.

  • Monitoring and audit trail live
  • Runbook and named owners
  • Change and support model agreed

gate: owner accepts the system into operation

before we build

What we agree in writing first.

Most stalled agent projects never agreed these. We do not start without them.

a.

The decision

What the pilot must show for you to fund production, and the date you will decide.

b.

The owner

One person on your side who owns the workflow and the outcome, and can make the call.

c.

The boundaries

Which data, systems and actions the agent may use, and which decisions stay with people.

d.

The measure

A baseline from your data today, so the result is a comparison and not an opinion.

first client

Our first client is our own house.

We run the same three stages, scope, proof of value and production, on the group’s own products first. The Digital Foundry builds the Own Your AI Studio products and the OwnID integrations, with the same gates, the same governance and the same build log a client gets.

That is where the method is tested before it is offered. We publish what ships, and we claim no results we cannot show. Client pilots are by invitation.

principles

How we build.

principle/01

Production is the standard

Integration, security, monitoring and ownership are in scope from the start, not deferred to a later phase that never gets funded.

principle/02

People at the checkpoints

Agents do the reading, drafting, checking and routing. People make the decisions that carry legal or material consequences.

principle/03

Vendor-neutral by design

We choose models, platforms and tools for the job and your environment, and design so they can be changed later.

principle/04

Redesign before automating

Automating a broken process makes it fail faster. We fix the workflow first, then automate what is left.

principle/05

Built to be owned

Documentation, runbooks and handover are part of the build, so your team can run and change what we deliver.

principle/06

Show the work

Demos at the end of every cycle, and build logs that state what a system does not do yet as clearly as what it does.

Advisory first? Digital Edge, our parent, advises on where AI can move the P&L and how to govern it before anything is built. Visit Digital Edge

next step

Have a workflow worth proving?

Tell us about one workflow. If it is a good candidate for a proof-of-value pilot, we will say so, and say why.