What is project management software: opening the project when the quote is accepted

Example scenario: Picture a pool builder in Antalya. A villa job starts with a site survey, followed by drawings, excavation, tiling, the plant room, and handover. Each step has an owner, a start, and an end. Project management software writes this sequence down and shows who is waiting on what.

Writing the plan is the easy part; the software's real job is to show everyone when the plan breaks. If the tiling crew is a day late, the plant room's start slips too. The software shows the slip and tells the owners affected. The survey photos, the approved drawing, and the materials list sit next to the work as well; when documents live in a separate folder, the field crew may work from an old drawing.

These tools present the work in different views. A board view (kanban) shows steps as cards in columns such as to do, in progress, and done. A timeline (Gantt) lays steps out as bars on a calendar and shows which ones slip when one is late. Whatever the view, the same record sits underneath.

A task list answers the question of what needs doing. A project asks more: in what order, by whom, by when, and for which customer. In the pool example, the plant room cannot start before the tiling is finished; a task list does not know that, a project plan does.

Small teams often start with a task list, and that can be enough. When jobs for more than one customer run at the same time, when steps depend on each other, and when the delivery date is written in a contract, a project record becomes necessary. One sign helps: if the same job has its own calendar in a spreadsheet, its own WhatsApp group, and its own email thread, task tracking has reached its limit. At that point, what brings the work together is the project record.

The salesperson meets the customer several times and notes the tile colour, the delivery month, and the condition that access is only through the garden gate. The quote is accepted. If the project team opens the job in another tool and sees only the quote PDF, the garden gate note stays in the salesperson's email, and on day one the excavator may not get through the gate. The note is well written; it simply sits in the wrong place, where the project team never looks.

There is no bad intent behind the break; the two records simply do not know each other. Everything sales knows should be in the project on its first day.

The break has a finance side as well. If the quote sets out a deposit and interim payments, those terms should match the project steps. The excavation is finished, but if accounting never hears of it, the interim invoice is never raised. The same break happens the other way: when the project team does work outside the scope and that news never reaches sales, the extra work is never billed.

• The accepted quote is tied to a contract; scope and line items are read from there.
• The project opens from the same customer record; contacts and address are not retyped.
• Sales notes and correspondence sit where the project team can see them.
• Steps, owners, and delivery dates are put on the calendar on day one.
• Field reports and photos are tied to the relevant step.

The plan written on day one does not have to be right in every detail; it will change. What matters is that changes are made on the same record and everyone sees the same plan. If the plan is updated in a separate file, the team soon starts working to two different plans. When the scope comes from the accepted quote without being copied, no gap is left between the scope agreed with the customer and the scope the team works to.

If the question "where are we" is asked project by project in the Monday meeting, the meeting runs long and the answers come from memory. If steps are closed on the record, the answer is already on the screen, and the meeting is left for the matters that need a decision.

The questions a manager wants answered on the project screen are clear: which step is late, which is waiting for approval, which project has no report from the field. As steps close on the record, the answers form by themselves. The Monday meeting stays, with a new agenda; instead of reading out status, it focuses on why a step is late and what to decide.

Reports from the field are part of this screen too. If the photo report is tied to the project step, the manager sees where the work stands without calling the site; if no report has come in, that is a signal as well.

In Corex360 the manager's day starts with the morning briefing. X AI reads the customer, contract, invoice, staff, and project records in the core and ranks pending approvals and risks by the manager's own rules. You can follow how this briefing is used in a manager's day on the manager's morning briefing page.

On the customer card, quotes, contracts, projects, finance, and files sit side by side as tabs; when a project opens, the customer and contacts are not retyped. The field team enters its report and photos from the phone, and the report is tied to the project and the customer card. What this flow looks like on a building site is covered in quotes and site records in construction.

So what sales knows is not copied into the project; it is already there. Because the garden gate note sits on the same customer card as the quote correspondence, the project team sees it on day one.

Project and finance records open from the Projects and Finance tabs of the customer card. Short answers about projects and accounting are on the projects and accounting questions page.

Start the demo with your own quote: let us turn an accepted quote into a project and write the first steps, owners, and delivery dates together.