The software your people built is too important to lose.

Your experts decide what right means. Stonehold keeps the system tested, monitored and safe to change.

Book a 20-minute Continuity Check

No preparation. Bring your IT manager.

See an illustrative review

YOUR PEOPLE PUT YOUR IP INTO SOFTWARE

Pricing logic
Client methods
Decision models
Automations
Integrations
Internal applications

Now other people rely on it.AI made building easier. Ownership did not.

The ownership gap

02 / 08

Building became easier. Ownership did not.

Once other people depend on the software, somebody must own its tests, monitoring, changes, incidents and recovery. That job often sits between the people who understand the business and the team that runs the technology estate.

01 — YOUR EXPERTS

Define the product.

They decide what the software is for, what right means and which exceptions matter.

02 — IT

Runs the estate.

Identity, devices, networks, cloud accounts and the policies that keep the company connected.

03 — STONEHOLD

Operates the system.

We turn product decisions into controls, then test, monitor, change and recover the technology.

The Stonehold operating system

03 / 08

The software can be one of a kind. Looking after it shouldn't be.

Discover

Inventory the software, dependencies, business rules and people who currently know what correct means.

Standardise

Install the operating contract: ownership, tests, AI evaluations, monitoring, release controls and recovery.

Operate and adapt

Handle changes, incidents, dependencies, security and production behaviour as the business evolves.

One accountable operator. Software the business can depend on—even when the person who built it is gone.

The Stonehold Managed Standard

04 / 08

What “managed by Stonehold” means.

A visible, auditable condition for every system—not a promise that a capable person will remember what to do.When AI is part of the product, ordinary tests are no longer enough. Stonehold adds evaluations, model monitoring and human approval where judgement still matters.

01
A named business owner and technical owner
02
A map of code, data, models and dependencies
03
An explicit record of intended business behaviour
04
Acceptance tests and AI evaluations where relevant
05
Monitoring connected to critical outcomes
06
Controlled releases and rollback procedures
07
Incident and escalation responsibilities
08
Current documentation and a usable handover pack

Illustrative scenario — a pricing tool

Imagine the system produces a quote below the company's approved margin.

Nothing appears broken: the application is online, the API responds and a quote is produced. But its 14.2% margin breaches the company's 18% policy. Here is what ordinary monitoring sees, and what Stonehold adds.

WHAT ORDINARY MONITORING SEES HEALTHY

API response: 200 OK
Deployment: PASSED
Quote produced: YES

Everything appears to be working.

WHAT STONEHOLD ADDSINTERVENTION

Quote margin: 14.2%
Policy minimum: 18.0%
Required action: HOLD FOR APPROVAL

The output is technically valid, but the business has not authorised it.

01
Encode the rule
The commercial owner confirms that quotes below 18% require approval.
02
Test every change
Candidate releases must handle representative pricing cases correctly.
03
Control production
The quote is held, routed to the right person and the exception is recorded.

A clear commercial path

05 / 08

Review. Standardise. Operate.

01 — DISCOVER£3,500

Software Continuity Review

Find out what you run on, where company knowledge lives and what the smallest sensible response is.

System and dependency map
Knowledge and ownership map
Control and continuity gaps
90-day recommendation

The fee becomes credit if Stonehold takes responsibility within 30 days.

02 — STANDARDISESCOPED

Takeover and stabilisation

Install the controls required before Stonehold can responsibly operate the system.

Recover missing knowledge
Add tests and AI evaluations
Set up monitoring and access
Establish release and recovery

Bounded and separately priced only where the Review shows it is needed.

03 — OPERATE£4k/mo

Managed Continuity

Stonehold becomes the named technical operator while your experts retain product decisions.

Monitoring and incidents
Tests and evaluations
Safe changes and releases
Documentation and recovery

From £4,000 per month. Cancel any month.

Designed for scrutiny

06 / 08

You gain an operator. You do not surrender control.

Product purpose, business policy and risk appetite stay inside your company. Stonehold operates under explicit authority and keeps the arrangement reversible.

Your systems

Code, data and infrastructure remain in accounts you control.

Your decisions

Your experts approve policy and consequential exceptions.

Revocable access

Stonehold receives only the access required to perform the agreed job.

IT in the room

We define the application and estate boundary with your IT team.

Visible evidence

Changes, incidents, controls and operating decisions remain inspectable.

Clean handover

Current documentation makes transfer or retirement a normal operation.

“Great software was being built with AI. Nobody was set up to look after it.”

I started Stonehold so companies could keep their experts in charge of the product while giving the technology a proper, accountable operator.

Ralph Forgeon · Founder

See the output before you buy

07 / 08

See what a £3,500 Review actually produces.

A worked example of the evidence, decisions and 90-day actions Stonehold gives leadership and IT.

Inside the review

01 Executive continuity rating
02 Ownership and dependency map
03 Operating-control assessment
04 Business-facing risk register
05 30-60-90 day action plan
06 Hire, hand over, retire or Stonehold

Questions sensible people ask

Before you invite us in.

Does the software have to use AI?

No. AI made the problem more common, but continuity matters whenever important company knowledge lives in code that too few people understand.

Is this too important to outsource?

Product purpose, policy and risk appetite stay with you. Stonehold operates the technology under explicit approvals, inside systems you control, with a current handover pack.

Shouldn't we just hire a developer?

Sometimes. The Review defines the actual operating job first, then recommends whether to hire, hand over, retire the system or give Stonehold responsibility.

What happens after the twenty-minute call?

We decide whether there is a meaningful continuity question. If there is, we scope the £3,500 Review. If there is not, the process ends there.

Start with twenty minutes

08 / 08

Find out what your company actually runs on.

No preparation. Bring your IT manager. If there is no meaningful continuity risk, we'll tell you.

01 Tell us what the software does.
02 Tell us who depends on it.
03 Suggest a time that works.