Case Study
Case Study: Construction Bid & Subcontractor Automation
We built a connected set of automations for a mid-sized general contractor: an opportunity pipeline in a CRM, bid package summaries with subcontractor invitations and chasers, subcontractor compliance tracking and monthly pay application collection with notice deadlines. Estimators and the commercial team now work from clear lists, and every pricing, safety and payment decision stays with them.
- Firm type
- General contractor working on commercial and residential projects
- Team involved
- Directors, estimators, buyer, quantity surveyor, project managers, compliance coordinator
- Systems connected
- CRM, bidding platform, project management system, accounting system, email, n8n
- Delivery
- Scrum, 1-week sprints, about 7 weeks to full launch
The challenge
Where the practice started
Opportunities lived in a spreadsheet and the estimators' inboxes. Bid due dates were sometimes spotted late, and nobody followed up on submitted bids in a consistent way.
Each bid package took the estimators days to read, and the buyer sent and chased subcontractor invitations by hand, tracking replies in another spreadsheet.
Subcontractor insurance certificates and safety documents were stored as email attachments. Expiry dates were checked when someone remembered.
Monthly subcontractor applications arrived late and in mixed formats, and payment notice dates were tracked in personal calendars.
Goals
What the project had to change
- Every opportunity sits in one pipeline with dates, an owner and a follow-up.
- Estimators get a first-read summary of each bid package within hours of receipt.
- Subcontractor invitations and chasers run themselves once the buyer approves the list.
- Subcontractor documents are current before anyone reaches site.
- Applications are collected on time and no payment notice deadline is missed.
What we built
What we built, as one connected system.
Opportunity pipeline
We parsed website enquiries, emails and bid invitations into one CRM pipeline with go or no-go stages, due date reminders, follow-ups after submission and a monthly win and loss report.
Service detailsBid management
New packages produce a first-read summary with page references; the buyer approves bidders per trade package, invitations and chasers go out, and returns are lined up with exclusions highlighted.
Service detailsSubcontractor compliance
One onboarding link per project, expiry dates read for the coordinator to confirm, automatic chasers and a site readiness list before each start date.
Service detailsPay applications
Requests go out before each cut-off, applications are checked against last month, payment notice dates are tracked per contract and approved figures go to accounting as draft bills.
Service detailsArchitecture
How the contractor's workflows connect
- Input
- Logic and services
- AI step
- Data
- People
- Output
How it flows
- 1 Enquiries, invitations to bid and subcontractor documents, quotes and applications feed one n8n instance.
- 2 Four workflows update the CRM pipeline and trackers, with AI steps summarising packages and reading dates.
- 3 Estimators decide bids and prices; the QS and project managers approve documents, valuations and notices.
- 4 Approved figures go to accounting, and every step is logged for the directors.
How it behaves
How the system behaves day to day
What clients and subcontractors see
- Follow-ups after each bid and on the decision date
- Clear invitations and reminders before the internal deadline
- One upload link for compliance documents
- Application requests before every cut-off
What staff see
- One pipeline and one bid board per package
- A site readiness list before each start
- An assessment pack and notice deadlines each month
What the automation does
- Parses, summarises, invites, chases and reminds
- Reads dates for people to confirm
- Logs every step and alerts a director if anything fails
Edge cases and fallbacks
- A bid package is mostly scanned drawings
- The summary flags unread pages for the estimator.
- A subcontractor's insurance lapses mid-project
- The PM is alerted and decides whether work continues.
- An application arrives after the cut-off
- Logged as late for the QS to decide under the contract.
- A bidder asks a question
- Logged and answered to all bidders on the package.
- n8n or email outage
- Work queues and retries, and staff can send invitations and reminders by hand.
Integrations
What we connected
Procore
Project managementProjects, directory, daily logs, RFIs, commitments and documents.
Procore REST API with OAuth 2.0, through an app in the Procore Developer Portal.
BuildingConnected
Bid managementBid packages, invitations and opportunities.
BuildingConnected API on Autodesk Platform Services (needs the Pro subscriptions Autodesk requires).
HubSpot
CRMOpportunities, contacts and follow-up tasks.
HubSpot CRM REST API.
QuickBooks Online
AccountingDraft bills and vendor records from approved applications.
QuickBooks Online Accounting API.
Xero
AccountingDraft bills and contacts, including UK CIS-registered firms.
Xero Accounting API.
Microsoft 365
Email, Teams and SharePointInvitations, chasers, document storage and the AI assistant in Teams.
Microsoft Graph API.
n8n
Automation platformRuns the workflows, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 7 weeks, then support
-
01
Discovery
Week 1
We sat with estimators, the buyer, the QS and the compliance coordinator, mapped the bid, onboarding and valuation steps and agreed data flows.
-
02
Design and access
Week 2
Pipeline stages, summary template, document rules, deadline rules per contract and API access to the CRM, bidding platform and accounting.
-
03
Sprint 1: compliance
Week 3
Built the onboarding link, tracker and chasers, and loaded existing subcontractor documents; demo and sign-off.
-
04
Sprint 2: bids
Week 4
Compliance went live. Built package summaries, invitations, chasers and the quote line-up, shadow-run on a live bid.
-
05
Sprint 3: pipeline
Week 5
Bid management went live. Built the CRM pipeline, reminders and follow-ups.
-
06
Sprint 4: pay applications
Week 6
The pipeline went live. Built application requests, checks, the deadline tracker and accounting hand-off, shadow-run on one cycle.
-
07
UAT and handover
Week 7
The team ran acceptance testing on every workflow, then we switched everything on, handed over the run book and trained staff.
-
08
Support
Ongoing
Weekly check-ins during stabilisation, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Parses enquiries and invitations into the CRM
- Summarises bid packages with page references
- Sends approved invitations and chases quotes
- Collects subcontractor documents and chases expiries
- Requests applications and tracks notice deadlines
The team does
- Check summaries and approve bidder lists
- Check and approve subcontractor documents
- Value applications and prepare notices
- Follow up clients and record bid outcomes
Site manager or director decides
- Decides whether to bid and the final price
- Decides who may start on site
- Signs payment notices and approves payments
- Owns safety and contractual decisions
Compliance handled
Privacy, consent and safety, built in.
No automated contractual or safety decisions
Summaries, trackers and reminders support people; they never decide a bid, a valuation, a notice or safety.
CIS verification
New subcontractors are verified with HMRC by an authorised person before the first payment.
Source: www.gov.ukConstruction Act deadlines
Payment notice and pay less notice dates are tracked from each contract's payment terms.
Source: www.legislation.gov.ukCDM 2015 safety documents
Safety documents are collected for competent review, never approved automatically.
Source: www.hse.gov.ukData minimisation
Subcontractor personal data is kept only where the workflows need it.
Source: gdpr-info.euOutcomes
What changed for the practice
- Every opportunity now sits in one pipeline with an owner, dates and a follow-up.
- Estimators start each bid from a summary with page references instead of a blank page.
- The buyer approves bidder lists and the invitations and chasers run themselves.
- Subcontractor documents are checked and current before start dates, with an audit trail.
- Monthly applications arrive in one place, and notice deadlines are visible to the whole commercial team.
What we track
The measures the practice watches.
Bid readiness
Hours from package receipt to estimator summary and bids submitted on time.
Bidder response
Share of invited subcontractors who return a quote per package.
Win rate
Bids submitted and won by sector and client.
Compliance
Subcontractors with expired or missing documents at start date.
Payment paperwork
Applications received on time and notices issued before deadline.
Cost estimate
What a project like this costs
-
Discovery and design
Process mapping, data flows, templates and the backlog for all four workflows.
$800 – $1,600
-
CRM pipeline module
Parsing, stages, reminders and follow-ups.
$700 – $1,600
-
Bid management module
Summaries, invitations, chasers and quote line-up.
$800 – $2,000
-
Subcontractor compliance module
Onboarding link, tracker and chasers.
$800 – $2,000
-
Pay application module
Requests, checks, deadline tracker and accounting hand-off.
$800 – $2,000
-
Integrations
CRM, bidding platform, project system and accounting connections.
$300 – $700
-
Testing, UAT and launch
QA, user acceptance testing, launch and training.
$300 – $1,100
-
Total project estimate
$4,500 – $11,000
Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: four workflows at our fixed per-workflow range. Every contractor gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- AI usage: Pay-per-use model fees, mainly for bid package summaries.
- Software subscriptions: Each vendor's own plan (CRM, bidding platform, project system, accounting).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- Website Security Scan FreeSSL, security headers, cookies and exposed file checks
- Email Deliverability Check FreeMX, SPF, DKIM, DMARC, MTA-STS and BIMI with ready DNS fixes
- Website Monitoring Scheduled re-scans, score emails and 5-minute uptime alerts
- SEO Audit FreeTitles, meta, headings, indexability, sitemaps and schema
Free website tools for practices
Services in this case study
Construction CRM & opportunity pipeline automation
Track every enquiry, invitation to bid and repeat client in one construction CRM, with follow-ups after each bid, reminders for estimators and a report on where profitable work comes from.
From $1,000 · About 4 weeks Details
Bid & tender management automation
Read new bid packages into a summary, send invitations to the right subcontractors and suppliers, chase quotes before the deadline and line up returns for the estimator to compare.
From $1,000 · About 4 to 5 weeks Details
Subcontractor compliance & COI tracking
Collect and track subcontractor insurance certificates, licences, safety documents and tax checks, chase anything expiring and stop unapproved firms reaching site.
From $1,000 · About 4 weeks Details
Pay applications, payment notices & lien waivers
Collect subcontractor pay applications on time, prepare your own applications and the paperwork around them, track payment notice deadlines and chase lien waivers before money moves.
From $1,000 · About 4 to 5 weeks Details
Site manager or director decides
-
AI in Construction: Practical Uses for UK Contractors (With People Signing Off Safety)Automation · 9 min read
-
Subcontractor Onboarding: A Document Compliance Workflow That Keeps Sites MovingAutomation · 11 min read
-
RFQ to Quote Process: A Step-by-Step Workflow for ManufacturersAutomation · 8 min read
-
Quote Request to Booked Job: A Workflow for Local Service BusinessesAutomation · 11 min read
-
Client Document Collection Automation for Accounting FirmsAutomation · 8 min read
-
What Are AI Agents? A Plain-English Guide for Small BusinessesAutomation · 10 min read
Free 20-minute call
Want this built for your construction firm?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- GOV.UK: Verify subcontractors as a CIS contractor
- Housing Grants, Construction and Regeneration Act 1996, section 110A
- HSE: Summary of duties under CDM 2015
- OSHA: Recordkeeping
- 47 CFR 64.1200 (TCPA rules)
- UK PECR regulation 22
- EU AI Act, Article 50
- GDPR Article 5
- Procore developer documentation
- BuildingConnected and TradeTapp APIs (Autodesk Platform Services)
- Fieldwire Developer Hub
- CompanyCam API documentation
- JobNimbus open API
- Buildertrend: software integrations
- HubSpot API overview
- QuickBooks Online Accounting API
- Xero Accounting API
- Sage Intacct developer documentation
- DocuSign eSignature REST API
- Microsoft Graph API
- n8n pricing
- Google autocomplete checked for keywords (construction crm, crm for contractors, construction bid management software, subcontractor compliance, certificate of insurance tracking, construction daily report app, pay application construction, construction ai assistant)