Platform
© 2026 ConstructionCRM. All rights reserved.
United Kingdom · United States · United Arab Emirates
ConstructionCRM ships with a construction data model already built in. But no two businesses work identically. Every field, dropdown, pipeline stage, and module can be configured to match the exact language and workflow of your team.
Most configuration in ConstructionCRM requires no developer and no support request. Your administrators handle it directly. For anything more bespoke, our team will work with you to build exactly what your business needs.
The Field Manager, App Manager, User Manager, Dashboard Designer, and Workflow Manager are all point-and-click tools built for non-technical administrators. If you can use a spreadsheet, you can configure ConstructionCRM.
When your requirements go beyond what administrators can configure, our team steps in. We have built bespoke modules, conditional validation logic, automated workflows, custom quote templates, and integrations with ERP systems, SharePoint, Barbour ABI, and marketing platforms for construction businesses across the UK, North America, and UAE.
The Field Manager exposes the complete database schema as an editable interface. Rename any label, add custom fields to any entity, make fields mandatory at a specific pipeline stage, and control visibility per user group - all without code. Changes take effect instantly across the entire UI including the mobile app.
Every dropdown across the system, including pipeline stages, company types, project sectors, action classes, and opportunity types, can be fully customised. The pipeline stage set uses a lettered prefix system to ensure correct sort order across all list views and reports, regardless of how you label each stage.
Field visibility can be made conditional on another field's value, configured through the Field Manager without code. Selecting "Sub Contractor" as the company type can reveal Construction Line, insurance, and specialisation fields that are hidden for every other type. Project sector can trigger entirely different field sets.
The User Manager organises accounts in a hierarchical tree by User Group. Each record has granular access control over modules, records, and actions, plus a Quotation Approval Role tab for multi-step quote workflows. Vehicles are modelled as user accounts so they appear in the Dispatch Board alongside people.
The App Manager controls exactly what each mobile user sees on iPhone or Android, independently from the desktop. A three-level configuration lets you choose which modules appear, which tabs are visible, and which fields show within each tab, giving field reps a clean, fast interface while back-office users retain the full experience.
The Workflow Manager fires automated actions based on events in the CRM. Create and Update triggers work across all core entities. A "Only apply if the field has changed" checkbox prevents repeated firing. Actions include Database Update and Email Alert, both fully configurable without a developer.
The List Manager lets you build InfoSearch lists: live, dynamic queries using a visual relational criteria builder with full access to the data model including related entities. Any saved list can have a Schedule Alert set to deliver email reports daily, weekly, or monthly to any list of recipients.
The Dashboard Designer is a full embedded BI authoring tool. Drag and drop from 14 visualisation types: bar, line, KPI cards, gauges, treemaps, choropleth maps by UK region, and geo point maps. Define calculated fields, set date range filters across all panels, and publish to all users instantly on save.
Multiple quotation templates can be stored and selected at the point of issue. The same quote data renders through a standard house-style template for routine quotes, and a fully bespoke client-branded layout for key accounts. Templates include product line items, scope of work text, and branded cover pages.
The Generic Entity is a flexible record type linkable to any combination of Company, Contact, Project, Opportunity, and Quotation records. By assigning an Entity Type ID it becomes a specific custom record: a Certification, Risk Assessment, Sample Request, or a Phase sub-entity beneath a Project with its own status and purchase order tab.
Multiple named price lists run simultaneously: a standard rate card, client-specific agreements, and time-limited promotional rates. Each product carries a cost price, unit list price, and a Max Discount field to prevent unauthorised margin erosion. Composite products allow complex service packages to be quoted as single line items.
Three dedicated GDPR entities exist as first-class data model components: PII management for subject access requests, Record Consent with date, method, and scope per contact, and a Rights to Be Forgotten workflow with a full audit trail. Every major record type has an Auditing tab logging every field change and access.
When your requirements go beyond what administrators can configure in the Field Manager, our team works directly with you to build what you need. Here is the kind of work we regularly deliver.
Every construction business has its own data structure, its own language, and its own workflows. The examples below are drawn from real builds for businesses across the UK and represent the range of what is possible when self-managed configuration is not quite enough.
Opening any field in the Field Manager reveals a five-tab dialog. Each tab adds a different layer of control without any code.
The Description field is the only element that changes what users see. Renaming "Company Name" to "Account Name" here updates the label everywhere instantly: list views, record dialogs, reports, and the mobile app. The underlying database column is shown read-only for developer reference.
Controls global field behaviour including searchability and system-wide required status. Setting a field as required here means no user on any platform (desktop, web, or mobile) can save a record without it populated. The blunt instrument for enforcing data quality across the whole organisation.
Controls field behaviour per division. A field can be required in the Commercial division but optional in Infrastructure, or visible to one business unit and hidden from another, using a single field definition across the database while presenting a different experience to each team.
Controls field behaviour per user group. A "Contract Value" field can be visible and editable for a Sales Manager, read-only for a Sales Executive, and hidden entirely from a Field Operative, all from the same Edit Field dialog. Different defaults can be set per group so new records are pre-populated correctly.
Bring your current CRM setup, your field structure, your pipeline stages, and your data quality problems. We will show you exactly how ConstructionCRM would be configured for your specific business.
Bring your questions about pipeline stages, custom fields, and integrations. We will show you exactly how it would be set up for your team.