Skip to main content

About Assurr

Building work is written down in one place, changed in another, and paid for on trust.

Most projects finish well. But when a homeowner and a contractor disagree about what was agreed, what was finished, or what a change was worth, there is rarely a shared record to settle it. Assurr exists so that there is one.

Mission

Give both sides the same record.

Make a building project legible to the people paying for it and the people doing it, so that what was agreed, what was evidenced, what was accepted and what was paid all describe the same project.

Vision

Make fulfilment a matter of record.

A system for agreements where real-world work happens over time and a decision depends on showing what was done. UK domestic building work is where we start. The underlying model is broader.

Murray East, founder of Assurr.

Why I started Assurr

The information usually existed. The structure connecting it did not.

I have spent much of my working life around the places where plans meet reality.

Designing things. Teaching people how to make them. Running building projects. Managing contractors, suppliers, customers and operational systems. Trying to work out what was supposed to happen, what had actually happened, and what needed to happen next.

The same problem kept appearing in different forms. A decision might depend on a quotation in an email, a drawing somewhere else, photographs on somebody’s phone, a conversation nobody recorded, an invoice raised weeks later and a different understanding of what had originally been agreed.

Once two people have different accounts of the same project, reconstructing what actually happened becomes difficult and expensive, and damages trust.

The money was not really the beginning of the problem. It was the point at which everything that had happened before suddenly had to become a decision.

  • Has this work been done?
  • Was this included?
  • Was that change agreed?
  • Does somebody else need to decide?
  • Is this payment now due?

I realised that making the payment mechanism better without improving the record underneath it would only solve part of the problem.

So Assurr became something broader.

It is built on a simple idea: the agreement, the work, the changes, the evidence, the decisions and the money should stay connected as a project develops.

The record should not just explain what happened afterwards. It should be useful while the work is happening, helping both sides understand what has been agreed, what has changed, what has been done and what happens next.

This creates greater clarity, better decisions and more trust throughout the project.

That is the system I wanted to exist. So I started building it.

Murray EastFounder, Assurr

What we hold to.

The principles that shape how Assurr is designed.

  • 01

    Both sides, or neither

    If a system protects only one side, it does not create trust. It creates leverage.

  • 02

    Agree before you evidence

    Progress only means something against a clear, agreed expectation.

  • 03

    Change is normal

    The record should change when the project does, without losing what came before.

  • 04

    Evidence over assertion

    Important events should be supported by evidence in context: what, who, where and when.

  • 05

    Professional judgement stays independent

    Professionals and authorities can contribute to the record without becoming subordinate to it.

  • 06

    Early queries, not late disputes

    A question raised when it arises is easier to resolve than one reconstructed months later.

  • 07

    Designed is not delivered

    Agreed, designed, built, evidenced and approved are different states. The record should keep them distinct.

  • 08

    Legible without a specialist

    The people paying for and delivering the work should be able to understand the record without translation.

Construction is the first use case

Assurr is building infrastructure for showing how agreements were performed.

Strip the trade language out of a building project and what is left is a general shape: two or more parties, an agreement that depends on work happening over time, and a decision that cannot fairly be made until somebody can show what was done. Construction is where that shape is hardest and most expensive to get wrong.

  1. Agreement
  2. Requirements
  3. Real-world activity
  4. Evidence
  5. Assurance
  6. Verified state
  7. Commercial consequence

What a verified state can be used for

  • Payment
  • Approval
  • Handover
  • Warranty
  • Finance
  • Insurance
  • Settlement

Payment is one consequence of a verified state, and the only one we are building. The rest describe what the same state could support as the infrastructure develops, not functions Assurr offers today.

Who this is being built for.

Homeowners

You are spending a large sum on work you cannot fully assess, and you would like to stop guessing.

For homeowners

Contractors and trades

You do good work, you evidence it badly because nothing has ever made that easy, and you get paid late for it.

For contractors

Partners and professionals

You are a payment provider, insurer, lender, trade body, architect or project manager with a stake in this working.

Work with Assurr

Registering is an expression of interest. It tells us which parts of this to build first.

Join the waitlist