Acquisition and asset sale

An early-stage specialist workflow asset for the right buyer, not yet a mature software business.

FrameAudit should currently be understood as a formed but early-stage disputed-video review workflow. It has been built around a real evidentiary problem, can already be run locally through the launcher or CLI, and produces a structured bundle, but it has not yet been validated across a wide book of outside matters or recurring commercial use.

The package has real workflow shape, but a buyer should assume current-stage risk: limited external validation, limited repeat-case proof, and strong founder dependence.

Section 1

Current early-stage sale framing.

FrameAudit should currently be framed as an early-stage specialist workflow asset, not as a mature software business. It has been built and tested around a real disputed-recording problem, but it does not yet have broad market validation, outside case history, or recurring revenue proof.

Realistic early-stage sale

GBP 30k to GBP 75k

The most realistic current range for a serious but still early-stage niche sale where the buyer values the formed workflow, local-first handling, bundle delivery, and buyer-facing positioning, while still discounting for limited external proof.

Strong aligned buyer

GBP 75k to GBP 150k

Potentially achievable only where the buyer already understands the niche, sees immediate specialist use, and is buying speed, packaging, and workflow shape rather than waiting for broader commercial validation.

Practical pricing note

Above GBP 150k is difficult to justify today without repeat buyers, broader case validation, institutional adoption, or recurring revenue. A disciplined negotiation position would usually be to open higher, target the middle band, and avoid selling too cheaply unless speed matters more than upside.

What is already real

FrameAudit already records source duration, elapsed processing time, and observed runtime ratio per run inside bundle outputs. That does not make it a mature business, but it does show that the workflow is more than a loose concept deck or mock-up.

What is still missing

Broad commercial proof

The workflow has not yet been proven across a broad set of outside client matters, paid institutional use, or recurring revenue. That is why the acquisition framing must stay in early-stage asset territory rather than mature product territory.

Why someone may still buy it

Speed, focus, and packaging

The strongest buyer argument is not scale. It is that the package already has a narrow problem focus, a local-first handling model, a structured bundle output, and a public-facing positioning layer that a buyer would otherwise have to assemble manually.

What the sale really is

Code, workflow, packaging, and positioning

This is best framed as the sale of a specialist workflow package: codebase, launcher path, CLI route, output contract, reporting pattern, early proof material, and niche buyer positioning. It is not yet best framed as a fully de-risked software company acquisition.

The practical framing is early-stage asset sale first, strategic acquisition second. A buyer who wants certainty will discount heavily; a buyer who wants a head start in this niche may still see real value.

Why a buyer may care now

The package can still be commercially interesting before scale.

  • The workflow addresses a narrow but real problem: disputed-video review with a fixed, review-ready bundle.
  • The local-first delivery model may matter in privacy-sensitive and evidentiary contexts where cloud-first handling is harder to sell.
  • The package already has buyer-language, delivery shape, and operational structure rather than raw scripts alone.
  • A buyer may value the time saved by skipping the first build-and-positioning phase.
  • That makes it more plausible as a niche asset purchase than as a conventional startup acquisition at this stage.

Likely buyer personas

The buyers most likely to see practical value in it.

  • Forensic or review-tool vendors that want a narrower disputed-video workflow without building one from zero.
  • Litigation-support or expert-service firms that want a productized review lane around contested recordings.
  • Insurer fraud or claims-review teams that need stronger single-recording review for escalated matters.
  • Oversight, regulator-tech, or inquiry-support groups handling public-body disputes and evidentiary review.
  • Specialist investigations teams that want a local-first offline review capability for sensitive matters.

Next step

Start with a buyer note, not an overclaimed platform pitch.

If someone may be a credible buyer, the right first move is a short private buyer note covering stage, package contents, valuation range, and fit. If they want to see how the workflow behaves in practice, move next into confidential review discussion or private software access.