Renovation under control
Estimate, stages, payments and a chat with the crew in one app. Payment is tied to a signed-off stage.
Prototype
Built: the estimate, stages with sign-off, chats and an offline mode; the payment flow is built; live payments are not connected. The receipt and self-employed status check via the Federal Tax Service is so far worked out on a simulation; the live check goes on once access is granted. Full scope of work: section 07.
Summary
- The estimate drifts from actual costs, and overspend surfaces only at the end.
- The contractor’s status goes unchecked, and no one is accountable for the result.
- Renova pulls everything into one flow: a gap between estimate, actuals and payment shows at the moment it appears.
01 — The problem
Renovations run on chat threads, and no one is accountable
The economics of a renovation are never in one place: the estimate in a file, the conversation in a messenger, the receipts in a pile.
-
The estimate drifts from actual costs
The estimate lives in a file; purchasing and payments sit elsewhere. Every small difference piles up unseen until it becomes an overspend.
-
Payment is not tied to results
Payment follows a verbal agreement rather than a signed-off stage. What exactly was paid for cannot be checked later.
-
The contractor’s legal status is unconfirmed
Self-employed or sole-trader status is taken on trust and, as a rule, not checked at the time of payment.
-
Whether a stage is finished is a matter of trust, not fact
The crew and the client mean different things by “done”, and there is no shared confirmation. Photos, if any, stay in a phone gallery, not linked to a stage or date.
Outcome: the client learns the real cost of the renovation only after the money has been spent.
02 — The principle
Every action recalculates the figures
-
The estimate is a state, not a document
Every change to the estimate is saved as a new version. You can see what changed, when, and why the plan departed from actual costs.
-
Payment is tied to sign-off
A stage payment is confirmed only after sign-off, with photo evidence and confirmation from both sides.
-
Checks go to official sources
In the intended flow, receipts and self-employed status are matched against Federal Tax Service data rather than accepted on the contractor’s word, and the result decides whether this contractor can be paid. For now this is worked out on a simulation.
03 — System class
A place between the group chat and the contractor’s accounting system
Private renovations are usually run in one of these ways: a spreadsheet with receipts, a group chat with no single version of the estimate, or the contractor’s own accounting system (1C, a site manager’s software), closed to the client. None of them shows the client the full economics of the project.
The Renova column shows the intended scope; readiness is described in section 07. None of the usual methods checks the receipt or the contractor’s status.
04 — Scope
From estimate to signed-off result
The system holds the order of steps: until a stage is signed off, its payment cannot be confirmed, and every change to the estimate leaves a trace.
- Estimate
- Version approval
- Work on the stage
- Photo evidence
- Sign-off
- Payment
- Next stage
05 — Roles
Client and contractor each get their own screens
The client and the contractor see the same site, but each sees their own part.
-
Client
Sees the whole estimate, its versions and deviations, stage status and payment history. Signs off a stage or rejects it with a comment.
-
Contractor or crew
Runs their own area: photographs the stage, requests sign-off and confirms receipt of payment.
-
Renovation company
Runs several sites at once and sees the estimate, stages and payments for each.
06 — Interface
The app on screen
A video and screens of the prototype: estimate, work stages, payments. The app can already be shown in use, not just described. Phone first: a renovation is run on site, not at a desk.
Tap a screenshot to open it full screen and swipe through the others. The frames were taken in the demo on illustrative data.
07 — Stage
The prototype is built; a closed test is next
08 — Involvement
Ways to get involved
I show how the system is built and the roadmap in person.
09 — FAQ
Frequently asked questions
- How does this differ from a spreadsheet and a messenger chat?
- The estimate, stage and payment are connected: the crew requests sign-off from the app, the client signs off the stage from the photos, and only then does payment go through. In a spreadsheet or a chat, that chain rests on a verbal agreement.
- How is the contractor’s legal status checked?
- By the system, not by the client: the contractor sends nothing, and the check runs before payment. The key scenario is worked through; I will switch on the live check once I have access to the Federal Tax Service.
- Do I have to move the whole renovation into the app at once?
- No. Start with one stage or one estimate and run the rest as you usually do.
- What happens if the connection is lost on site?
- Actions go into a queue and are sent once the connection returns; stage sign-off and stage photos, among others, work this way. Protection against duplicates after a dropped connection is still being finished.
- Who pays for the app, the client or the contractor?
- I will set the payment model after the pilots: the side that gains more on site should pay.
- Can the client change the estimate alone, without the contractor’s agreement?
- Once a contractor is appointed, the estimate is locked on the contractor’s proposal with the client’s confirmation. After that, changes are raised as variation orders that both sides agree; every version is visible to both.
- Can I see a demo?
- Yes, on the working version.
Contact
Tell me who you are: a client, a contractor or crew, or a renovation company. I reply personally.