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.

Your people put your IP into software. Now other people rely on it.

Pricing logic, client methods, decision models, automations and internal applications.

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.

Your team defines the product.

Subject-matter experts decide what the software is for, what right means and which exceptions matter.

Your IT team runs the estate.

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

Stonehold operates the system.

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

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

01

Discover

Trace the business journeys people rely on, then map the software, data, dependencies and people behind them.

02

Standardise

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

03

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.

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.

  1. A named business owner and technical owner

  2. A map of code, data, models and dependencies

  3. An explicit record of intended business behaviour

  4. Acceptance tests and AI evaluations where relevant

  5. Monitoring connected to critical outcomes

  6. Controlled releases and rollback procedures

  7. Incident and escalation responsibilities

  8. Current documentation and a usable handover pack

Example: a pricing tool 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.

  1. 01

    Encode the rule

    The commercial owner confirms that quotes below 18% require approval.

  2. 02

    Test every change

    Candidate releases must handle representative pricing cases correctly.

  3. 03

    Control production

    The quote is held, routed to the right person and the exception is recorded.

Map it first. Then decide.

The work stands alone. Whatever you decide next, the map and action plan are yours.

Software Continuity Map & Action Plan

Establish what the business relies on, what must remain true and the smallest sensible response.

£3,500 one-off

  • Critical business journeys and intended outcomes
  • Software, data and dependency map
  • Operating-control and evidence assessment
  • Exact recommendation and takeover scope

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

After the map, choose who takes responsibility.

Your team takes it forward.

Use the map and defined scope with your own people or another developer.

  • Brief your internal team
  • Appoint the right developer or provider
  • Replace or retire what is not worth keeping

You keep the map, evidence and action plan.

Stonehold takes responsibility.

We productionise the software and operate it with you.

Productionisation Week

Fixed after mapping

Qualifying software enters a fixed-scope Productionisation Week.

Managed Continuity

From £4k/month

Stonehold manages monitoring, incidents, evaluations, releases, documentation and recovery.

The review fee becomes credit when you continue within 30 days. Your experts retain product decisions.

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.

Ralph Forgeon, founder of Stonehold
“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 what a £3,500 Continuity Map actually produces.

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

This prepares a request in your email app. Nothing is sent until you choose to send it.

Inside the Map

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

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 Continuity Map 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?

The call is free. We decide whether there is a meaningful continuity question. If there is, we scope the separate £3,500 Software Continuity Map & Action Plan. If there is not, the process ends there.

Find out what your company actually runs on.

The first call is free and requires no preparation. Bring your IT manager. If there is no meaningful continuity risk, we'll tell you.

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

This opens your email app with the useful details filled in. Nothing is sent until you choose to send it.