GBP 10k to GBP 30k
The kind of outcome most likely if the sale is quick, the buyer is taking on most of the future execution risk, and the package is treated primarily as promising code plus workflow groundwork.
Acquisition and asset sale
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
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.
The kind of outcome most likely if the sale is quick, the buyer is taking on most of the future execution risk, and the package is treated primarily as promising code plus workflow groundwork.
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.
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.
The buyer is not starting from a blank page. The workflow already supports one-input execution, profile-based analysis, structured bundle delivery, and deliberate cleanup of older job folders for matters that need more than a casual visual check.
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.
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.
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
Likely buyer personas
Next step
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.