BIMSpoke

BIM-first automation studio

If your team repeats it every week, it shouldn’t stay manual.

BIMSpoke builds custom BIM automation — Revit tools, clash dashboards and the systems around them — shaped to how your team actually works. Less manual work, fewer mistakes, better control of your project data.

Challenge me with a workflowSee what I’ve built
Built around the tools you already use
  • Revit
  • Navisworks
  • Dalux
  • Excel
  • PDFs
  • Databases
  • APIs

Most teams lose hours every week to work software should be doing.

Copying data between systems. Re-checking the same models by hand. Rebuilding the same reports. Chasing status across folders and spreadsheets with no live overview. It works — but it’s slow, it’s repetitive, and it’s exactly where mistakes creep in.

Custom tools for the work your team does every week.

01

BIM & coordination automation

Revit add-ins, clash review workflows, model QA, report automation. The repetitive modelling and coordination work, turned into buttons.

02

Data & document automation

Extracting, cleaning, structuring and reporting on project data — including AI where it actually earns its place, not for its own sake.

03

Company-branded internal tools

Dashboards and systems that live under your own ribbon, logo and language.

And when a tool needs a full system behind it — database, dashboard, deployment, the lot — BIMSpoke builds that end to end.

Real tools, not slideware.

A growing set of tools built for real project workflows. More land here as they ship.

Clash Review Dashboard

Live

Navisworks clash reports, turned into a Revit-connected review workflow.

  • Revit
  • Navisworks
  • Coordination

Pipe Insulation Plugin

Live

A Revit tool that automates pipe insulation setup and standardises a fiddly manual workflow.

  • Revit
  • MEP
  • Automation

Case study · anonymised

From scattered reports to a connected review workflow.

A coordination team was getting useful information out of Navisworks — but the workflow around it was still entirely manual.

Before

  • Exported reports and folders of screenshots
  • Element IDs copied by hand
  • Status tracked in spreadsheets
  • No shared, live overview

After

  • One structured dashboard
  • Filter, preview and read element info in place
  • Status tracked as you review
  • Jump straight back into the working environment

Impact — honest, no inflated numbers

  • Faster review
  • Less manual copying
  • Cleaner filtering before meetings
  • Clearer status
  • Fewer repeated steps
  • Adapts to the project

White-label

Your workflow. Your branding. Your tool.

BIMSpoke can deliver tools that live entirely under your company’s identity — your ribbon, your logo, your terminology. Your clients see in-house capability; your team gets a tool that feels native. Built, and quietly maintained, by BIMSpoke.

  • 01Your ribbon, logo and naming — not mine
  • 02Feels native to your team and your clients
  • 03Built, deployed and quietly maintained behind the scenes

Start here

Start with a 10-Hour Automation Sprint.

Before any big commitment, BIMSpoke takes one workflow apart in 10 focused hours: map it, test what’s actually possible, and — where the workflow allows — build a working proof of concept. You walk away with either a working demo or a clear written feasibility, spec and estimate. Either way, it’s yours to keep.

€1,500 + VAT · no long contract · a clear go/no-go after 10 hours

Start a sprint

If there’s no realistic automation worth building, I’ll tell you — and you don’t pay for the sprint.

The maths, honestly.

Build effort
≈ 80 hrs
One-off cost + VAT
≈ €12,000
Time saved
6 hrs / week
Recovered value
≈ €2,000 / mo
Pays for itself
≈ 6 months

Say a tool takes around 80 hours to build — roughly €12,000 + VAT. If it saves a team 6 hours a week at an internal cost of €80/hour, that’s about €2,000 a month, and the build pays for itself in roughly six months — before counting the mistakes it prevents and the overview it adds.

Real numbers vary by workflow. This is an example, not a promise.

Contact

What shouldn’t stay manual?

Tell me one workflow your team repeats every week. I’ll tell you, honestly, whether it’s worth automating — usually within a day.