Barbour ABI gives you an API. Then it says: find a developer.
Their own integration page is clear about it — a software developer needs to use the Barbour ABI APIs to get project data into your CRM. Most UK teams never get that developer, so the data stays in the portal and the pipeline gets built by hand. We build connectors around the construction databases our clients already licence.
We can provide Barbour ABI project data into your CRM.
An API is not an integration. Someone still has to decide what a project becomes in your CRM, which stakeholders get linked to it, how records update as a scheme moves, and what happens when a project is merged or dropped. That mapping work is what we do — and it is the same work behind the construction-data connector we already run in production in another market.
Stakeholders arrive pre-linked
Every project would come with the architect, main contractor, developer and consultants attached as companies and contacts, with their roles labelled — not a list of names your reps copy out of a portal.
Mapped to your objects, not dumped in a field
Projects become deals, stakeholders become companies and contacts, and the relationships between them come across too. Your reps work native CRM records, not an embedded dashboard.
Records that keep pace
As a scheme moves from planning to tender to contract awarded, the record in your CRM moves with it. No stale pipeline, no daily CSV, no weekly re-import.
What a Barbour ABI connector puts in front of your team
The same approach we use to build CRM connectors, mapped to Barbour ABI's data model.
Your search, on autopilot
Set the filters once — region, sector, development stage, value. Only the projects that match come through. Everything else stays out of the pipeline.
Filters or tags — both routes covered
Barbour ABI supports pulling by search criteria and by the tags your team applies in the platform. A connector should honour whichever way your researchers already work, not force a new habit.
The developer you were told to find
We already run a construction-data connector in production, against a different provider, today. Nobody on your team has to learn an ETL pipeline or own it afterwards.
Built for how UK teams sell
Regions, sectors and development stages scoped around your patch — so what lands in the CRM is the work you'd actually bid, not the whole country.
How we build it
The same process behind our live construction-data connector, scoped to Barbour ABI and your CRM.
You keep your licence — we build within it
The connector would work under the Barbour ABI subscription you already hold. Your licence, your data, your relationship with Barbour ABI — we never resell any of it.
We map your CRM and search profile
Your objects, your sales process, your regions and sectors, and whether you pull by filter or by tag — scoped around how your team actually sells.
We build it around your setup
Your feedback shapes the mapping as we build — so what ships fits how your team works, not a generic template you have to bend to.
FAQ
Barbour ABI connector — common questions
What UK construction BD leaders ask about a Barbour ABI integration.
Do you connect to Barbour ABI today?
expand_more
Not yet. We build CRM connectors around the construction databases our clients licence, and Barbour ABI is one we're actively scoping. Tell us about your setup and the CRM you run, and we'll walk you through exactly what it would look like for your team.
Barbour ABI already lists CRM integrations. Why would I need you?
expand_more
Because what they list are APIs, not connectors. Their own integration page says a software developer will need to use the Barbour ABI APIs, and the CRM logos are examples of what those APIs can reach — not products you can switch on. The build is still yours to commission. We're the team that does that build, and then keeps it running.
Do I need my own Barbour ABI subscription?
expand_more
Yes. You hold the data licence and the relationship with Barbour ABI; the connector would move what you're already licensed to see into your CRM, within your licence terms. We don't resell Barbour ABI data.
We're weighing up Barbour ABI against Glenigan — does that change anything?
expand_more
Not for us. Pick the database that covers your patch best; that's a decision about data, not about plumbing. We build connectors around whichever one you licence — we cover Glenigan too — and the CRM mapping work is much the same either way.
Could our own developer just build this?
expand_more
They could. The APIs are documented and the extract is the easy part. What takes the time is the mapping and the maintenance — deciding what a project becomes in your CRM, linking stakeholders with their roles, handling schemes that move stage, merge or drop off, and keeping all of it working as both the API and your CRM change. That's the part teams underestimate, and it's the part that lands back on someone every month.
Which CRMs would it support?
expand_more
HubSpot first, and we'll scope from there based on what you tell us. Let us know what you run — the more we hear, the more precisely we can prioritise your CRM.
Where’s the Barbour ABI API documentation?
expand_more
Barbour ABI publishes its API for customers, and their own integrations page is straight about what that means: a software developer needs to use the APIs to get project data into your CRM. If you’ve gone looking for the documentation, you’ve already found the wall — an API is raw material, not a working pipeline. Tell us what your licence includes and we’ll tell you plainly what’s buildable on it.
What does Barbour ABI cost?
expand_more
We can’t quote it — that’s Barbour ABI’s to give, and it’s priced per team and dataset rather than published. The cost worth adding to the comparison is the one after the subscription: the developer time their own integration page tells you to go and find.
Is Barbour ABI worth it?
expand_more
That’s a question about the data, and not ours to answer for you. What we’d say is that the licence is worth what your reps act on — and the usual reason these subscriptions get cancelled isn’t data quality, it’s that the data never made it into the CRM where the work happens.
We’re thinking about switching away from Barbour ABI — can you help?
expand_more
Not if you’re after a cheaper database — we don’t sell one and we don’t rank them. If you’re switching because the data never reaches your CRM, that’s the problem we actually solve, and it’s worth checking whether you need to switch at all.
Talk to us about your Barbour ABI connector.
Tell us about your Barbour ABI licence and the CRM you run, and we'll scope exactly what this looks like for your team — no cost, no commitment.
Book a discovery call
Tell us about your Barbour ABI licence and the CRM you run. We'll walk you through what a connector would look like for your team — and what it wouldn't do.
- check_circle30-minute discovery
- check_circleNo obligation
- check_circleClear next-steps