Job management for a renovation contractor
The quote went out on WhatsApp, the change on site was said out loud, and the crew arrives in the morning without knowing which room was closed yesterday. The client asks why the price moved, and there is no line that shows the extra.
Who it is for
For a contractor with several sites at once and a crew that is not in the office. A poor fit for a one-person job on a single apartment, with no quotes and no crew.
Problems this page addresses
A quote with no version
Two quotes were sent. The client approved the first one verbally, and the crew works from the second because it is the latest message in the chat.
A site change with no extra
A wall moved or a material changed. The work was done. The price extra was never written, and it surfaces at the end as an argument.
Morning on site with no update
The site lead knows the electrician is not coming. The crew is already on the way, because the message stayed in a group nobody read.
What you get
A quote with a status
Draft, sent, approved. Only an approved version goes to the crew. An older version stays for comparison, not for the work.
An extra logged from the site
A change is recorded from the phone: what changed, who approved it, and what it adds. The client sees the line before it becomes a dispute.
Tomorrow’s site board
Which site is active, who is coming, and what is blocked. Updated from the field, not only in a morning meeting at the office.
Common questions
What does this cost a contractor with several sites?
It depends on how many sites run at once and how many people update from the field. Start with an approved quote and a site extra. The crew board joins after those two are in use on a real site.
The crew will not sit and fill forms.
Right, so the update is short and from the phone: site, what changed, a photo if needed. Not a long end-of-shift report.
Can this connect to the architect’s drawings?
The drawings stay with the architect. The contractor records what was approved to build and what changed on site. The pages stay separate because the decision and the build are not the same job.
Related pages
A CRM shaped around how you already work
An off-the-shelf CRM asks the team to adopt someone else’s stages and fields. We build the record around the approvals, statuses, and fields that already decide who the customer is and what happens next.
A mobile app on the same core as the web
The office works comfortably on a large screen, and the field stays on screenshots and group chats. We build the phone actions on the same server and the same permissions, not as an app with a database of its own.
Project management for an architecture studio
The drawing goes to the client by email, comments come back on WhatsApp, and the version sent to the contractor is not always the one that was approved. Permitting and construction drawings share the same folder.