The Hidden Ledgers: Three Software Businesses Hiding Inside Broken Evidence Chains

Idea 1: RightsMesh, the Contract Rights Evidence Ledger

Problem

At 4:47 on a Friday afternoon in Manchester, Daniel receives a call from a lender.

The question sounds harmless: “Do we hold every warranty required for this project?”

Daniel expects an answer before five.

Instead, fourteen PDFs appear from four different folders. One names an old company. Another has no visible signature. A third may have been superseded. Someone remembers a notice being sent, although nobody can find the email.

The company may possess every right it needs. Its immediate problem is simpler and more expensive: nobody can prove that quickly.

For lenders, property owners and businesses managing large contractual relationships, important rights often survive as disconnected documents. The warranty sits in one folder, the underlying contract somewhere else, and evidence of execution or notice in somebody's inbox.

Solution Approach

Build RightsMesh, a private ledger connecting contractual rights to the evidence supporting them.

Daniel uploads warranties, contracts, notices and amendments. The software extracts parties, dates, document types and references, then creates a structured rights map.

Each statement remains traceable to its source document. A checklist can show that a warranty is expected, that a document has been uploaded, that a signature appears present and that a required evidence field remains empty.

The product should avoid declaring that a document is legally valid. Its job is evidence management.

MVP

Start with UK commercial property lenders or developers and one document category, such as collateral warranties.

The MVP needs secure document storage, document classification, configurable requirements, party matching, version control, evidence links, audit history and red, amber and green completeness reporting.

A user should be able to answer the Friday afternoon question in thirty seconds and open the document supporting every answer.

Why Software Alone Can Solve Much of It

The raw ingredients already exist electronically.

The difficulty lies in connecting parties, contracts, dates, versions and evidence. No new physical infrastructure is required. Software can continuously maintain the relationship between a fact and the document that supports it.

Why a Founder Can Build It Independently

An ordinary private document and evidence-management service does not require approval from a UK ministry, court or professional body before launch.

UK law recognises that electronic signatures can execute documents where the signer intends to authenticate them and applicable execution formalities are satisfied. Electronic signatures are also admissible as evidence.

The product should leave legal conclusions and reserved legal activities to customers and qualified advisers. Where personal data is stored, UK data-protection rules require lawful, fair and transparent processing, together with principles including purpose limitation, minimisation, security and accountability.

A founder can therefore build RightsMesh as ordinary UK SaaS without government integration or privileged access.

Idea 2: TitleKeep, the Asset Chain-of-Proof Platform

Problem

On Monday morning, a manufacturing company collapses.

A supplier named Rebecca calls the insolvency team.

“We retained title to £420,000 of equipment.”

The next question causes the room to go quiet.

“Which equipment?”

The terms exist. So do invoices and delivery records. The machines have serial numbers, although those numbers live in another spreadsheet. Several units have moved warehouses. Payments cover some invoices but apparently not others.

Rebecca believes the machines remain hers.

Belief is now competing with an evidence problem.

Solution Approach

Build TitleKeep, software that creates a continuous evidence chain around identifiable commercial assets. For every item, the system links contractual terms, purchase order, shipment, delivery note, invoice, payment status, serial number and current recorded location.

When something changes, the history remains visible.

Instead of reconstructing the transaction after insolvency occurs, the supplier maintains the evidence chain while ordinary business is happening.

MVP

Begin with UK business-to-business suppliers selling identifiable machinery or equipment under retention-of-title terms.

The MVP needs asset records, serial-number capture, invoice matching, document storage, location history, payment-status fields and an exportable evidence pack.

It should flag missing links without deciding whether title legally remains with the supplier.

Why Software Alone Can Solve Much of It

The core problem is reconciliation.

A contract has to connect to an invoice. The invoice must connect to goods. The goods must remain identifiable. Payments and movements must remain traceable. Those relationships belong naturally in a database.

Why a Founder Can Build It Independently

The Insolvency Service confirms that the Sale of Goods Act 1979 continues to apply to UK business-to-business sales and that ownership passes according to the parties' intention. Its retention-of-title guidance specifically emphasises contractual documentation, invoices and identification of goods, noting serial numbers as a particularly strong method of identification.

More ambitious retention clauses can raise separate questions, including whether an arrangement amounts to a registrable charge. TitleKeep should therefore organise evidence rather than pronounce upon ownership or draft bespoke legal clauses.

No government licence is required merely to build the record system.

Idea 3: CompetenceClock, the Forward Workforce Coverage Ledger

Problem

Sofia manages seven maintenance sites across Europe.

On Friday, every rota looks complete.

By Monday morning, two people are unavailable. Another worker's certification expired on Sunday. A fourth has been allocated to a different site.

The spreadsheet discovers the problem at 7:12 a.m., eleven minutes after the first shift was supposed to begin.

The failure began weeks earlier. Nobody was looking forward.

Solution Approach

Build CompetenceClock, a workforce coverage ledger that continuously compares future requirements with recorded availability and competencies.

Employers define which competencies each site requires. Employees receive records for qualifications, expiry dates and availability. The software searches future schedules and flags approaching gaps.

The safest early product remains deliberately mechanical. It reports that Tuesday requires three qualified people and only two are presently scheduled. A manager decides what happens next.

MVP

Start with one operational sector and companies running multiple sites.

The MVP needs employee records, employer-defined competencies, qualification expiry dates, site requirements, availability, forward calendars and coverage alerts.

Store “unavailable” where possible rather than collecting unnecessary medical explanations.

Why Software Alone Can Solve Much of It

Coverage is largely a structured-data problem.

The variables are people, locations, dates, qualifications, expiries and minimum coverage. Deterministic software can calculate future gaps continuously instead of waiting for a spreadsheet review.

Why a Founder Can Build It Independently

A private workforce-planning application can be built and sold in the EU without obtaining general approval from the European Commission or a national government.

GDPR still governs the processing of employee personal data and requires lawfulness, purpose limitation, minimisation, accuracy and appropriate protection.

Product design matters if AI is introduced. EU rules treat certain AI uses involving employment, worker management, monitoring and task allocation as potentially high-risk. Under the current implementation timetable, the relevant Annex III high-risk rules apply from 2 December 2027.

A founder can keep the first product much simpler: deterministic coverage calculations, employer-entered requirements, no worker ranking, no automated employment decisions and minimal sensitive data.

Across all three businesses, the opportunity comes from the same quiet failure. Companies possess the facts, yet the facts live apart from the evidence that proves them.

Software can close that distance.

References:

1. Law Commission, Electronic Execution of Documents

   
   

   Confirms the legal capability of electronic signatures in England and Wales where authentication intent and applicable formalities are satisfied, and confirms admissibility in evidence.

   
   

2. UK Information Commissioner's Office, Data Protection Principles

   
   

   Sets out the UK GDPR principles including lawfulness, fairness, transparency, purpose limitation, data minimisation and security.

   
   

3. UK Insolvency Service, Retention of Title Guidance, updated April 2026

   
   

   Explains retention-of-title claims, the continuing application of the Sale of Goods Act 1979 to business-to-business sales, and the importance of contractual records and identifiable goods.

   
   

4. EU General Data Protection Regulation, Article 5

   
   

   Establishes the core principles governing personal-data processing within the EU.

   
   

5. EU Artificial Intelligence Act, Annex III

   
   

   Identifies certain employment and worker-management AI systems as high-risk use cases.

   
   

6. European Commission, AI Act Implementation Timeline, August 2026

   
   

   Confirms that rules for Annex III high-risk AI systems are scheduled to apply from 2 December 2027 under the current framework.

   
   

P.S. Drafted with assistance from OpenAI. The image has been produced using OpenAI as well. The names, companies, characters and circumstances used in this article are fictional and are included solely to illustrate the underlying business and administrative problems.