You're running five projects at once. One team is waiting for materials, another is in the finishing stage, the third just passed handover, and the fourth is still at the quote stage because the client never replied. The whiteboard in your office has phone numbers and dates, but you can't keep it updated. When you ask "what about that bathroom in Mokotów?" — it turns out they paid the deposit three days ago and you didn't know. The whiteboard stopped being enough the moment you had more than three projects.
In this article you'll find: why renovation companies start using CRM systems, which project stages to track and what to record at each transition, when AI can help prepare a quote and when human verification is necessary, and how to build a simple mechanism that shows which projects have stalled.
Why renovation companies adopt CRM
These figures don't specifically relate to the renovation industry, but they show the general direction: managing client relationships and project stages is becoming a standard, not an exception.
In a renovation company, it's about more than just client relationships. The client calls, asks about timing, wants to know when the team will be on site. Without a system, you answer from scratch each time, flipping through your notes. The system shows the current project stage in seconds — no searching through papers and messenger groups.
Project stages as a funnel: from quote to handover
A typical renovation project goes through four main stages:
Quote is when the client receives the estimate. In the system you record: the date the quote was sent, the proposed price, the scope of work, and the delivery date. If the client doesn't respond for seven days — the system can send a reminder.
Accepted quote means a signed contract or deposit paid. Here you enter: the acceptance date, the contract amount, the planned start date, client contact details, and the contract or invoice number.
Materials ordering is the stage where you often lose time. You record: the material list with the supplier, expected delivery date, the person responsible for ordering, and the materials budget. When materials arrive — you mark it in the system and move forward.
Work is the longest stage. In the system you see: current progress (e.g., "walls ready, waiting for paint"), schedule, the person responsible for that section, and client notes.
Handover is the final transition. You record: the handover date, any remarks for correction, handover confirmation, and final payment.
This division lets you answer the client's "where are we?" in seconds instead of calling the foreman and checking on site.
What to record at each stage transition
Quote to accepted quote transition: deposit payment date, contract number, planned start date. This is the moment from which you count deadlines.
Accepted quote to materials ordering transition: material list with delivery schedule. Without this, the team arrives on site and waits for tiles.
Materials ordering to work transition: confirmation that all materials are on site. One missing item can stop the entire job.
Work to handover transition: protocol with remarks, list of corrections to make. This document protects both you and the client.
AI in quote preparation: the human must verify
AI-powered tools can prepare an initial quote draft based on your previous projects. You enter the square footage, finish standard, and location — AI generates an estimate. Sounds convenient, but there's a catch.
OpenAI's safety documentation recommends having a human review model outputs before they're used in practice wherever possible OpenAI, Safety best practices. This is especially critical in high-stakes domains where errors can cost significant money or time. In renovation quoting, a mistake in material costs or area measurement means either a loss for you or a surprise for the client. AI doesn't know current material prices at your local market, doesn't know the team needs three days for given work in winter season, and doesn't account for the specifics of a particular apartment. So AI's draft is a starting point — you verify, correct, and only then send it to the client.
Content quality on your company website: Who, How and Why
If you run a company website and post photos of completed projects, pay attention to Google's "people-first" content guidelines Google Search Central, Creating helpful content. Google's guidance says content should be evaluated with "Who, How and Why" questions — who created the content, how it was created, and why. For a renovation portfolio, this means: who performed the specific project (your company, a specific team), how the photo was created (e.g., "photo from handover three months after work completion"), and why you're publishing it (to show a specific type of work, like loft conversion).
Don't publish photos "from the internet" — Google sees that and treats it as low-quality content. Don't write "our client from Mokotów" — that looks like a fabricated example. Write specifically: "loft conversion 85 m², Warsaw Mokotów, completion 2025" — that's content that builds trust.
What doesn't go into the system: quality assessment of work
There's one thing no system should do for you: assessing the quality of completed work at handover. It's a decision that requires being on site, touching surfaces, checking whether grout is even or if paint comes off when touched. The system can remind about handover, collect client notes, record the protocol — but quality is assessed by a human: you, the foreman, or the client. Record in the system that handover occurred and what notes were made, but don't try to automate the assessment itself.
Reporting automation: numbers you actually look at
If you run several projects at once, you know how hard it is to keep all numbers in your head. Reporting automation in CRM lets you see: how many projects are in progress, how many are waiting for client decision, how many materials ordered versus delivered. Instead of collecting data manually from each spreadsheet — the system shows them on one screen. Read more about how reporting automation helps business owners see the numbers they actually care about.
Client access to the system: only their project
The client doesn't need to see what you're working on for others. In a good CRM system, each client sees only their project: current stage, schedule, and communication history. They don't see that another project has delays, that another client is behind on payment, or that you're running five projects in parallel. This builds professionalism and trust. The system shows the client the stage their project is at and the history — what was done, what's planned, and what requires their decision.
This division is also important from GDPR and data protection perspective. You don't share one client's business information with another, even by accident. Read more about how automation and GDPR affects customer data storage.
Where to start: process automation in your company
Before implementing a full CRM, it's worth looking at the processes in your company. The article How much does process automation cost in a company? shows what costs are involved with introducing systems and what affects the price. If you're wondering which system layers you need, read CRM or ERP: which system layer will you add next — this article explains the difference between simple relationship management and full resource planning.
Do it yourself: project list with stages and last movement dates
You don't need a full CRM system right away to see which projects have stalled. Make a simple spreadsheet:
Columns: Project name / Client / Current stage / Last movement date / Days since last movement.
Enter all active projects. In the last column use a formula that counts days from the "last movement" date. Sort descending by this column — the projects where nothing has happened longest will appear at the top.
Example on placeholder numbers — substitute your own: you have eight projects. Five are in progress with last movement today or yesterday. Three projects have last movement dates of seven, twelve, and nineteen days ago. Those three projects are your "backlog" — projects where something got stuck: client isn't responding to the quote, materials are delayed, waiting for client decision on paint color. You see this in seconds instead of flipping through all your notes.
This list is the first step before implementing a full system. When you see that you have more projects than you can manage in a spreadsheet — it's time for CRM.
How it looks with a system
When you implement CRM in a renovation company, the mechanism works like this:
The foreman changes the stage in the system: from "work" to "waiting for handover." CRM automatically updates the project card and sends the client a brief notification: "Work stage completed. Please schedule a handover date."
Once a week, the system generates a report with projects that haven't changed stage in seven days. This isn't monitoring — it's a tool that shows where things got stuck. You can call the client, check material delivery, or remind the foreman about an unfinished section.
The client can themselves enter their project via link and see what stage you're at, without calling you. This saves your time and builds trust.
See how this mechanism works in practice: CRM and automations help run projects through all stages, Dashboards show numbers on one screen, and Automatic messages send stage change notifications without your involvement. If you need to connect CRM with other tools, check out Integrations, and for tracking tasks within projects, the Tasks module will come in handy.
When CRM is unnecessary
If you run one team and do two, maybe three projects a year, and clients call you directly — you don't need CRM. You know all clients by name, know what stage each project is at, and don't lose track in the numbers. In this situation, a spreadsheet or even a notepad on your desk is enough. A system makes sense when you have more than three or four projects at once, or when you run more than one team. That's when the whiteboard stops being sufficient, and the time spent searching for information costs more than implementing a system.
Frequently asked questions
Do I need to enter all projects into the system from day one?
No. Start with active projects — the ones you're currently running. Older completions can be added later as history. Consistent entry of current project stages is more important than a perfect database from day one.
Can AI prepare a complete quote without my involvement?
Not fully. AI can generate a draft based on your previous quotes and templates, but you always need to verify material prices, team availability for the date, and the specifics of the particular apartment. OpenAI recommends human verification in high-stakes domains, and renovation definitely belongs to them.
What to enter at the "work" stage?
At the work stage, record what lets you answer the client's "where are we?": the specific section (e.g., "painting walls in the living room"), the responsible person, the planned completion date for that section, and any client notes. You don't need to enter something every day — just the moment of transition from one sub-stage to another.
Does the client see that I run other projects?
No, if the system is configured correctly. Each client sees only their project and its history. They don't see what you're working on for others, how many projects you have, or what delays you have. It's a matter of professionalism and GDPR.
How often should the "stuck projects" report appear?
Once a week is optimal. Daily — too much, because projects don't change that fast. Monthly — too rare, because you lose touch with projects that got stuck. In the system, set an automatic reminder every seven days.
What to do when a quote-stage project stalls for more than two weeks?
That's a signal to call the client. Maybe they need more information, don't understand the estimate, or are considering another company. Mark such a project as "needs attention" in the system and write a note from the last conversation — then a month later you'll know what it was about instead of asking "what was that about?"