Platform
© 2026 ConstructionCRM. All rights reserved.
United Kingdom · United States · United Arab Emirates
Your tender packs, drawings and contracts live in SharePoint. Your companies, contacts, projects and quotes live in ConstructionCRM. Our team builds a bespoke SharePoint integration, scoped through a Change Request Document, so your CRM records and your document library work together the way your business does.
Every business organises SharePoint differently. So there is no off-the-shelf connector here. Each integration is designed around your folder structure, your permissions and the way your teams actually work with documents.
We review how your SharePoint library is organised and agree which CRM records it needs to connect with.
Your IT team provides the access and permissions the integration needs, agreed in the CRD before work begins.
The integration is built and tested against your setup, exactly as specified in the signed-off CRD.
Our team reviews the finished integration end to end before anyone on your side is given access.
You confirm the deliverable works as agreed, the CRD is closed, and your team starts using it day to day.
When the CRM and the document library don't talk to each other, the same problems come up on every project.
The account history and project pipeline are in the CRM. The tender pack, drawings and contract are in SharePoint. Anyone preparing for a meeting has to piece the story together from both.
Quotes, proposals and specifications get saved to personal folders, email attachments and shared drives. When a client asks for the latest version, someone has to go looking.
When a project moves from sales to delivery, or an account changes hands, the documents don't always follow. The new owner inherits the record but not the files behind it.
Without a link to the CRM, folder names and structures drift. Finding everything for one project or one customer depends on who saved it and where.
Every integration is bespoke. These are the areas clients most often want connected; your CRD defines exactly what is built for your business.
Tender packs, drawings and specifications connected to the right project record, so everyone working on a bid can find what they need from one place.
Contracts, framework agreements and compliance paperwork connected to the company record, so the commercial history of a customer sits alongside its relationship history.
The proposals your team produces in ConstructionCRM kept with the rest of the project's documents, so the version the client received is never hard to find.
A consistent way of organising documents by customer and project, agreed with you during scoping, so files are filed the same way every time.
SharePoint is one part of how ConstructionCRM works with the Microsoft tools your team uses every day. Outlook Connect logs emails and keeps calendars in sync, Power BI runs inside the CRM, and SharePoint can be connected to your documents through a bespoke integration.
All bespoke work, from a new field to a full SharePoint integration, is governed by a Change Request Document (CRD). Nothing goes into development until the scope is written down, estimated, and signed off by both parties.
Each CRD includes a numbered development task list, deployment prerequisites the client must provide, a full list of deliverables, chargeability and estimated development time, and a formal sign-off block. The CRD supersedes all prior conversations and becomes the master document for delivery. Up to five revisions are included in the scoping process.
Every CRD passes through five stages before close: Scoping, where tasks and estimates are agreed; Waiting, for client prerequisites; In Development, where work is built and tested; Internal Demo, where the team reviews before client access; and Client Sign Off, where the deliverable is confirmed and the CRD is closed.
The range is wide. A CRD can cover new fields and validation rules, automated email alerts, custom quote templates, entirely new modules built on the Generic Entity engine, and integrations with ERP systems, SharePoint and marketing platforms.
A SharePoint integration is scoped through the CRD process at a published rate, so you always know what the work will cost before it starts.
Tasks, deliverables and estimated development time are agreed in the CRD and signed off before any work begins.
Bespoke development is invoiced at 70% upfront and 30% on deployment. Where a client deploys themselves, the 30% balance is due on handover. Out-of-hours work is charged at a premium rate.
Where a support bundle is in place, CRD hours are deducted from the bundle rather than invoiced separately. Deployment into the client environment is also drawn from the support bundle unless otherwise stated.
Book a 30-minute call. We'll look at how your SharePoint library is organised today, talk through what you'd like connected, and tell you honestly how the integration would work.