Chaos on sites
Dozens of sites, each at its own stage. Estimates, changes, contracts — in messengers and Excel.
Sites, estimates, work stages, suppliers, document workflow — all in one place.
Dozens of sites, each at its own stage. Estimates, changes, contracts — in messengers and Excel.
Estimates done manually, without current supplier prices. Margin eaten on small things.
Work deadlines slip, and the manager learns about it from the customer.
Quotes, contracts, acts — all in Word/Excel. Multiple versions, can't find the current one.
Lead came in, manager called once — and then forgot. Deal dies in a chat.
One card with all history: estimates, contracts, photos from site, correspondence, acts.
Templates with materials and works. Supplier prices auto-update via n8n.
Manager dashboard: all sites as a kanban. Auto-reminders on overdue.
Generate quotes, contracts, acts from templates with 1 click. e-Signature via Vchasno or Diia.Pidpys.
No lead is lost: auto-reminders, one-click calls, conversation history in card.
Construction does not fit a classic sales funnel: a site runs for months with several crews, subcontractors, purchases and documents, and money is counted per stage rather than per deal. So we set up site management, not a sales CRM.
Address, client, type of works, stages, estimate, contracts, photos from the site, correspondence and costs in one place. A new site opens from a template with a ready set of stages.
Every stage has an owner and a deadline. A delay is highlighted to the manager before the client reports it, not after.
Plan against fact per site: materials, works, subcontracting. You see where margin is eaten while the site is still running.
Material requests from the site, invoices, payments and costs tied to a specific stage. No more "we bought something for 40 thousand" without an address.
Crews and subcontracting tracked by scope, rate, delivered and paid, with history for each one — who to work with again and who not.
Quotes, contracts, annexes and completion acts are generated from card data. Details are filled in automatically instead of being edited out of the previous file.
The foreman sends photos from a phone and they land in the stage card with a date — both quality control and an argument in a dispute with the client.
Lead, site visit, estimate, quote, contract. Reminders so a deal does not die between "we will calculate" and "I will call back".
How many sites are running, where deadlines slipped, how much money sits in unfinished stages, margin on completed ones — on one screen.
How sites are run today, where estimates and photos live, who approves purchases, which stages are typical for your work.
We design the structure: work types, stages, mandatory fields, roles for foreman, manager and owner, agreed in writing.
Cards, document templates, estimate forms, reports. Active sites and the client base are moved over.
We train foremen on their current sites, from a phone rather than a desktop, and tune the system during the first weeks.
That is exactly why their interface is reduced to a few actions: change the stage, add a photo, request materials — all from a phone with no extra fields. Demanding ten fields from a foreman kills the system in the first week; it is the main reason implementations fail in construction.
No. Excel stays where it is strong — in calculation. The system stores the result: amount, scope, version and the link to a site and stage. You get plan-versus-fact without breaking the estimator's habits.
Yes, and that is usually the main value. Costs are recorded against a site and stage, so margin is visible while the work is running and something can still be changed.
They do not need to be. Scope, deadline and payment are tracked on your side while communication stays in the usual messenger. If needed we add a bot to receive requests and photo reports without giving system access.
Base setup with active sites migrated takes two to four weeks. The longest part is not technical work but agreeing the stages: every company has its own set and it must be fixed before configuration.