3D model of a site office: a desk, a calculator, a stack of invoices and rolled-up plans

Coming soon · Payment Protection

Payment protection for renovations

A route that releases payment to the contractor according to the agreement, the work phases and a check of the work, so both the client and the contractor are protected. Join the waiting list.

Only a launch update. No spam, unsubscribe at any time.

Barel Kaminsky, founder of RBM Solutions
Barel Kaminsky, founder of RBM SolutionsBuilt by a renovation contractor, out of real work on site.
  • Strong security
  • Hebrew, Russian and English
  • Works on computer and phone
  • Personal help getting set up

How it works

  1. Agreement and work phases

    The contractor and the client agree on milestones, amounts and release terms for each phase, before the work starts.

  2. Payment released as work progresses

    Each milestone releases its share of the payment, instead of one big sum up front or a payment that gets stuck at the end.

  3. Checking the work before release

    Before a phase is closed, both sides confirm the work was done as agreed. Peace of mind for both sides.

Why renovation payments get stuck

In most renovations in Israel, money moves on a verbal agreement: a deposit at signing, a payment "in the middle" and the balance "at the end". Each side remembers the agreement differently. The client isn't sure the phase is really finished and would rather wait, and the contractor has already paid for materials and the crew's work days and is waiting for money they're owed.

The argument doesn't start from a lack of trust but from a lack of records. There's no single list of phases and amounts, no photos of what was done before the payment request, and an extra agreed on WhatsApp doesn't appear in the payment schedule. The result: a payment delayed for weeks, a crew that stops working, and a client who feels pressured.

Payment protection is meant to close that gap: money released by a phase that was defined in advance and checked, so the client doesn't pay for a promise and the contractor doesn't work on credit.

What already works in RBM today, without us touching the money

We're still building the part that holds and releases money. The part with the agreement, the proof and the records already exists in the system, and the money in it moves directly from the client to the contractor.

Payment schedule in the quote
You build milestones as percentages of the quote total, and the editor shows how much of the 100% has been allocated before you send. The client sees the schedule before signing.
Milestones in the contract
A payment milestones clause is a fixed part of the work contract, alongside the scope of work, the schedule and the warranty.
Payment request with proof
In the client portal, a payment request arrives with the amount including VAT, the photos from the phase that was finished and the change orders approved since the previous request. If a retention was set on the project, it is shown separately.
Phase approval by the client
The client sees the phase photos and confirms it was completed. The approval is recorded with a time and a verification ID, and it is what opens the next payment request.
"I transferred" and confirming receipt
The client copies the contractor's account details, pays by bank transfer, check or cash, and reports it in the portal with a reference. The contractor confirms the money arrived, or sends the request back with a reason.
Change orders signed before the work
A change order is sent to the client with the price and the effect on the schedule. It enters the payment schedule only after the client approves it.
A payment ledger both sides see
In the portal the client sees the value of the work, how much has been paid so far, what the balance is and the status of each payment: upcoming, due, waiting for the contractor's confirmation or paid. The contractor sees the same numbers in the system, so there are no two versions of the same account.

Full transparency: RBM does not actually hold any money at this stage, and does not charge anything for the waiting list. This is early registration only. The service will launch with a proper operating model, legal terms and checking mechanism, and we'll update everyone who signed up in advance.

Who it's for

  • A client who wants to pay for real progress, not for promises
  • A contractor who wants certainty that the money is released once the work is done
  • Projects with several phases and milestones
  • Jobs where trust between the sides is worth money

Who it's less suited to

  • A small job of a day or two, paid all at once at the end
  • Anyone looking today for an escrow service that holds the money: it doesn't exist yet, and we'll let you know when it does
  • A project with no defined phases, where there's no way to check when part of the work is finished
  • Anyone who expects RBM to rule on a payment dispute today: the system records what was shown, what was approved and when, but the decision stays between the client and the contractor

An illustrative scenario: a kitchen renovation in four phases

Dana and Yossi order a kitchen renovation. The quote the contractor sends has a payment schedule: a deposit at signing, a payment after demolition and infrastructure, a payment after the cabinets are installed, and the balance at handover. They see the schedule before they sign, so there are no surprises later.

When the infrastructure is ready, the contractor photographs the pipes and wiring before they're closed up and sends a payment request. Dana opens the link, sees the photos and the amount, approves the phase and transfers the money from the bank. She marks "I transferred" and adds the transfer number, and the contractor confirms it arrived.

Halfway through the work, Yossi asks to add an electrical point to the island. The contractor sends a change order with a price and one extra work day, Yossi approves, and the change order goes into the payment schedule. At handover nobody argues about what was agreed, because it's all written in the same place.

The scenario is for illustration only and doesn't describe a real client. This is how it works today, with the money moving directly between them. Payment protection will add money that waits for a check before release, when it launches.

Frequently asked questions

Does RBM already hold the money?

No. At this stage it's a waiting list only. The service is in development and will launch with a proper operating and legal model.

When will it be available?

We're building the route. Anyone who joins the waiting list will get the first update as soon as it opens.

Does it suit every project?

The route is meant for renovation and building projects with clear work phases and milestones. We'll publish the full terms at launch.

What can I do right now to protect payments?

Build a payment schedule into the quote and the contract, send a payment request with photos of the phase, and ask the client to approve the phase in the portal before paying. The money moves directly from the client to the contractor, and RBM records who approved what, and when.

Does joining the waiting list cost money or commit me to anything?

No. You leave an email address, and we'll send an update when the service opens. There's no payment and no commitment.

What happens if the client doesn't approve a phase?

Today, in the portal, a request the client hasn't approved stays open, and they can write to the contractor or ask for a visit from inside the portal. The checking and decision rules for payment protection will be published before launch.

A renovated apartment at night, warm light in the rooms and a blue line around the floor

Want to be the first to know when it's out?

Join the waiting list and we'll update you at launch.

Only a launch update. No spam, unsubscribe at any time.

Also managing leads, quotes and projects? Meet RBM

We use cookies to improve your experience.