Both, connected — which is the point. Construction loses money at the seam between winning work (leads) and delivering it (projects). Keeping them in one system means an enquiry becomes a project without the handover falling through a crack.

Yes — a document and approval vault per project replaces the scatter across drives and chats, so the current drawing and the pending sign-off are where everyone expects them, not in an email thread.

Whichever genuinely fits. Construction workflows often don't map cleanly onto generic tools, which is why this sits under custom software — but if a good existing tool covers most of it, we'll configure that rather than build from scratch, and say so.

One dashboard for pipeline, spend and project stage means the owner stops finding out about a problem after it has cost money. Visibility is the difference between managing a project and discovering it went wrong.