Workflows & approvals

How a project flows

Every renovation moves through the same clear phases — and every decision has one clear owner. Who accepts an offer, approves a budget change, or reviews an invoice depends entirely on how the property is set up. Here is the full flow.

The lifecycle

Five phases from the first photo to completion — each with a clear owner.

  1. 1 Phase 1

    Capture

    Resident

    The resident captures the problem with photos, a voice note, or a chat with Hopper. The AI analyzes the condition and solution options. Nothing is visible to contractors yet.

  2. 2 Phase 2

    Review & publish

    Resident · Manager

    The analysis becomes a finished listing. The resident reviews it and sends it to the marketplace. If the property has a Hausverwaltung, the request goes to them for approval first.

  3. 3 Phase 3

    Offers & selection

    Contractor · Resident

    Matched pros see the project and submit offers. The client compares them on the leaderboard, shortlists favorites, and chats — from the very first offer. Exactly one offer is accepted; all others are auto-rejected.

  4. 4 Phase 4

    Execution

    Contractor · Client

    Acceptance opens the construction workspace: the logbook and work clock, milestones with photo evidence, the execution budget plan, and invoices. The client follows along in real time — amounts stay redacted for them.

  5. 5 Phase 5

    Completion

    Everyone

    When the work is done, the contractor completes the project (once no invoice is still a draft). The client pays, books the costs to the budget, and reviews the pro.

Who approves what?

The same decisions, three configurations. How a property is set up determines who accepts, approves, and reviews.

Owner-run

Owner, no property manager

Decides: The owner decides everything directly.

  • Publish the request

    The owner sends the project straight to the marketplace — no intermediate approval.

  • Accept an offer

    The owner accepts the winning offer themselves — the project moves to execution at once.

  • Approve a budget change

    Every change order from the contractor is a request the owner approves or declines.

  • Review an invoice

    The owner accepts or disputes each invoice — a disputed one is blocked until resolved.

Managed

Property with a Hausverwaltung

Decides: The Hausverwaltung decides on the owners’ behalf — including one-click from email.

  • Publish the request

    The resident’s request lands in the manager’s approvals inbox before it enters matching.

  • Accept an offer

    Acceptance parks in “awaiting approval” until the manager confirms — in the dashboard or via a one-click link in the email.

  • Approve a budget change

    The manager approves budget changes on behalf; the owner is relieved of the task but keeps full visibility.

  • Review an invoice

    The manager accepts or disputes invoices on the owner’s behalf from the property’s transactions.

Self-managed

Contractor self-managed project

Decides: The contractor runs the project; the client confirms via a magic link — even with no app at all.

  • Open the project

    The contractor starts the project directly in execution — no marketplace, no offers.

  • Bring in the client

    Site-visit reports and status reach the client by magic link; no account required.

  • Approve a budget change

    The lead proposes change orders, the client confirms. When the contractor is also the client, the change applies at once.

  • Sign off milestones

    Both sides sign off milestones — a two-party confirmation of progress.

Four rules that always hold

Whatever the configuration, these principles protect every side.

1

Exactly one winner

Once an offer is accepted, every competing offer is automatically rejected — a project always has exactly one awarded contractor.

2

Identity only on acceptance

Chat opens from the very first offer — but the contractor sees the client’s name and contact only once their offer is accepted.

3

Prices stay protected

Clients and managers read the logbook and budget but never see the crew’s rates and amounts — they are redacted server-side.

4

Nothing happens silently

Every budget change is a traceable request with history, every invoice can be accepted or disputed — and every event arrives as a notification.