About BRCKS
BRCKS was built by James Shorter, a founder with 20+ years in UK construction — from trainee to running his own AV installation company. After years of watching brilliant teams lose hours to WhatsApp groups, email chains and disconnected apps, he built what he wished had existed.
What we believe
- If it's not simple, it won't get used. Your team is busy; complicated tools drive people straight back to WhatsApp.
- Built for builders, not boardrooms. Every feature is tested with real tradespeople on real sites.
- We actually listen. Feature requests go to the founder directly.
Company details
BRCKS IO LTD, 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ. Contact: [email protected].
Quick facts
- 100+ UK construction teams running on BRCKS
- 2+ hours saved per day, per project lead
- £40 per seat per month — subcontractors and clients free
How BRCKS got built
James ran an AV and fit-out business with a small team and too many live jobs. Every evening ended the same way: scrolling WhatsApp to work out what had actually happened that day, then rebuilding a site diary from memory. The tools that promised to fix it all asked the same impossible thing — that every subcontractor download an app, create an account and change how they work. None of them ever did.
So BRCKS started from the opposite end. Keep the WhatsApp behaviour exactly as it is, and put the software behind it. The first version simply turned messages into a dated project record. Snagging, variations, RFIs, plots, the client portal and 360° tours were added as real customers hit real gaps.
What we're building next
We ship weekly and publish every release publicly on the changelog. Priorities come from customer calls, not a roadmap written in a boardroom — which is why features like bulk plot creation, WhatsApp-filed plots and "Ask BRCKS" natural-language project questions exist. If you use BRCKS and something is slow or missing, tell the founder and it usually lands inside a few weeks.
Want the fuller story? Read why BRCKS exists, see customer case studies, or talk to us with the team.
How we work with customers
BRCKS is small on purpose. When you email support you are talking to the people who write the software, not a ticket queue, and when you ask for something we can tell you honestly whether it will be built or not. Most of what shipped in the last year came from a customer describing a bad afternoon on site.
We also try to be straight about fit. If a call makes it clear you need estimating, takeoff, BIM coordination or a full ERP, we say so and point you elsewhere rather than sell a seat that gets cancelled in month three. That costs us the odd sale and saves everybody time.
What BRCKS is not
It is not an estimating or tender-pricing package. It is not a BIM or clash-detection tool. It is not accounting software, though it captures the costs your accountant needs. And it is not a compliance platform that only works if every operative is trained — the whole design assumption is that they will not be. See the honest comparisons for where other tools do a specific job better.
Where we are
BRCKS is built and supported in the UK, and the product assumes UK construction practice throughout — NHBC and LABC evidence trails, retention and final accounts, Part P, and the Building Safety Act golden thread. That shows up in small ways that matter on site: dates in the right order, VAT handled properly, and support answered in your working day rather than overnight from another timezone.
Your data, plainly
Project data belongs to you. You can export it, and you can ask us to delete it. We do not sell it, and we do not use your project content to train our own models. Full detail is in the privacy policy and the terms of service; if you have a specific question about where data sits or who can see it, email [email protected] and you will get a direct answer rather than a policy link.
Start your 14-day free trial · View pricing · Watch the demo · Talk to us