Use cases

Five situations where the app replaces the notebook, the spreadsheet and the email thread. They describe the version launching on 9 January 2027.

Main contractor

Warehouse handover with subcontractors

Defects from the walkround go straight to the right subcontractor.

Today

The site manager writes defects in a notebook and takes photos on a phone. In the evening the list goes into a spreadsheet and out by email. The subcontractor replies that the defect wasn’t on the list.

In the app

  1. On the walkround you photograph the defect and mark the spot on the warehouse drawing.
  2. You assign it to a subcontractor and set a due date.
  3. The subcontractor sees only their own defects and adds a photo after the fix.
  4. You check the fix and close the defect, or send it back with a comment.

Result: Before handover you have a list of open defects with due dates and before and after photos.

Main contractor and client

Weekly progress report for the client

The report is built from what the team has already recorded in the app.

Today

The report is put together on Friday from emails, photos from several phones and the programme spreadsheet. Every week it looks different.

In the app

  1. You choose the project and the reporting period.
  2. The app gathers photos, completed tasks and open defects from that period.
  3. AI drafts a summary. You edit it and send the client a link to the report.
  4. The client opens the report in a browser and confirms they have read it.

Result: The client gets the report in the same layout every week, and you know they have read it.

Refurbishment firm, homeowner

Flat refurbishment or a new house

The client’s comments sit in one list, not in texts and messaging apps.

Today

The client sends comments by text, on a messaging app and in person on site. After handover nobody remembers what was reported and when.

In the app

  1. You set up one project and invite the client.
  2. The client reports an issue from their phone and adds a photo.
  3. You fix it, add an after photo and close the issue.

Result: At handover both sides see the same list of fixes. The PDF record is generated from that list.

Client, developer, main contractor

Defects after handover

Reports during the defects liability period have a date, a photo and a response deadline.

Today

After handover defects arrive by email and phone. Nobody tracks the deadlines in the contract. Disputes start with the question of when the defect was reported.

In the app

  1. The client or the building manager reports a defect with a photo.
  2. The main contractor sees the response deadline.
  3. Every status change is saved with the date and the author.

Result: Every defect has a report date, a photo and a repair history.

Property manager

Tenant requests in an office building

A tenant reports a fault and the property manager passes it to a maintenance contractor.

Today

The tenant calls reception or emails the account manager. The request reaches the maintenance contractor by email. The tenant doesn’t know where it stands.

In the app

  1. The tenant reports a fault with a photo and its location in the building.
  2. The property manager checks it and passes it to the maintenance contractor.
  3. The contractor sees only the request passed to them and closes it after the repair.

Result: The tenant can see the status of their request. The property manager has a list of requests for each building.

Do you work differently?

Tell us how it works for you today. These use cases come from conversations like that.

We use cookies to personalize your experience. By using our website you agree to our Privacy Policy