Revit add-in + Rubiq dashboard · WBS & BOQ automation
One model.
Every element
coded.
One-click BOQ.
Qubiq classifies every model element with a structured Bill-of-Quantities code and sends the take-off to Rubiq, the office dashboard that turns it into the final bill.
The problem
01 / 10Take-off shouldn’t be manual —
or different on every job.
Stale by lunchtime
A take-off done by hand is out of date the moment someone moves a wall. The model changes; the schedule doesn’t.
Everyone codes differently
Without a shared structure, the same element is classified three ways across three jobs. Nothing reconciles.
Errors surface too late
A missing Type Mark or a misplaced door only shows up when the BOQ won’t add up — always under deadline.
How it works
02 / 10From model to bill in five steps.
The ribbon reads left to right in the order the work happens. Each card plays the tooltips of its own buttons.
Set up once
Pick what gets counted, and let the codes follow the model as it changes. The office template comes down from the cloud by itself.
Build the keys
Each category’s BOQ key is put together part by part from Revit parameters, and chapters can carry a classification standard.
Tag it
One run assigns every WBS parameter from each element’s zone, level, workset and Type Mark — on a selection, the active view or the whole model.
Check
Problems show up before the bill leaves Revit, each with its reason and its elements one click away.
Send to Rubiq
One click sends the model’s bill to the office, with a preview of every row. Rubiq takes it from there.
Anatomy of a WBS code
03 / 10Eight segments. One string per element.
WBS0 · Location
Project
The project code, carried by every element.
Read from: Setup, once per project
Back in the model
04 / 10Quantities, schedules and legends, inside Revit.
Rubiq — the office dashboard
05 / 10The BOQ doesn’t stop at export.
Every bill lands in your office’s private cloud, where Rubiq — the Windows dashboard installed with the add-in — turns model lines into the final bill of quantities.
Rubiq ships with every Qubiq install, identifies the seat by its licence key — nothing to log into — updates itself, and imports the office’s Excel item catalog and existing computi in one go.
For BIM coordinators & managers
06 / 10Standardise take-off across every project and team.
The office team, their roles, and who receives the daily WBS audit.
One method, every project
Shared parameters, one cloud catalog and one office template mean every model is classified the same way — regardless of who runs it.
Numbers you can defend
Each export is traceable to the model, template and engine version that produced it, with warnings and unmapped items flagged.
Nothing drifts silently
Type Marks, Keynotes and Materials lock once assigned, drift is detected, and a daily audit keeps a record — hand edits can’t quietly poison the BOQ.
Deployment without drama
One installer covers Revit 2022–2027 and Rubiq; the updater runs outside Revit and keeps every seat on the office’s current build — no licence server, no manual reinstalls.
Office rules
07 / 10The rulebook the whole team can see — and react to.
Every office has a way things are “supposed” to be done — usually it lives in someone’s head, or a PDF nobody reopens. Office Rules puts it inside Qubiq instead: a living, firm-wide rulebook the coordinator owns, that the whole team can react to and help shape.
The coordinator sets the standard
The coordinator writes and publishes the office’s workflow rules — the same rulebook every project inherits.
Owned by the coordinatorThe team reacts, anonymously
Anyone can like or dislike a rule. Reactions are anonymous, so feedback reflects what people actually think about the workflow — not what’s safe to say to the person who wrote it.
Anonymous reactionsAnyone can propose a rule
Team members can propose changes or new rules of their own, choosing whether to sign the proposal or submit it anonymously. The same reaction system applies, so the coordinator sees where a proposal actually stands.
Sign it — or don’tVisibility, not silence
The only signal a coordinator usually gets that a workflow isn’t working is inconsistent models three weeks later. Office Rules surfaces disagreement early, in one place, before it becomes a quiet workaround nobody mentions.
Still one rulebook
Office Rules doesn’t turn the standard into a vote — the coordinator still decides what’s published. It just means that decision is made with real signal, instead of in the dark.
Licensing & deployment
08 / 10One key for the office.
No licence server.
Qubiq is licensed per organisation against a private cloud — built for offices, not dongles.
Seats, not dongles
One licence key activates the whole office, up to your seat limit. Each machine registers its own seat, and the team roster — Coordinator, Project Manager, Specialist — says who’s on it and what they may change.
Works offline
The key is entered once, in Rubiq. Each seat holds a signed token, encrypted per machine, that keeps working for 14 days without a connection before it asks to see the network again.
Stays current
One installer for Revit 2022–2027 and Rubiq; the updater runs outside Revit and keeps every seat on the office’s current build — no reinstalls, ever.
FAQ
09 / 10Questions BIM teams ask first.
Does it modify my Revit model?
Qubiq writes shared parameters (with fixed GUIDs) onto elements and keeps an offline copy of the office catalog in the project; it never moves, deletes or alters geometry. Setup ▸ On / Off turns it off for a project entirely.
Which Revit versions are supported?
Autodesk Revit 2022 through 2027 on Windows. Qubiq is a standalone add-in built natively against each Revit version — no pyRevit or other frameworks required.
How is it installed and deployed?
One installer, QubiqSetup, detects the Revit versions on the machine and installs the add-in for each of them, plus Rubiq. From then on the updater — which runs outside Revit — keeps every seat on the office’s current build; nobody reinstalls anything.
What is Rubiq?
The Windows dashboard installed next to the add-in. It receives every export, holds the office template and catalog, and is where the office assembles the final bill of quantities — sub-voices, manual lines, proposals — before it goes out as CSV. It identifies the seat by its licence; there is nothing to log into.
Does the AI touch my model or my bill?
No. When a bill needs a sub-voice the catalog can’t answer, or a chapter needs grouping into super-voices, Rubiq asks a hosted model for a proposal, grounded on your own catalog entries and earlier decisions. The proposal waits in a queue until someone accepts, edits or rejects it — the model never writes to the catalog, the bill or the Revit model, and every decision teaches the next proposal.
Will it cope with large models?
Yes. Tag it is built for 80k+ element models, and Count it gives you live totals on any selection without leaving the model.
How does licensing work?
One key per organisation, covering an agreed number of seats. The key is entered once, in Rubiq; each machine registers its own seat and holds a signed token, encrypted per machine, that keeps working for 14 days without a connection — a brief outage never stops take-off.
Can I reuse a setup across projects?
You don’t have to. The office template — scope, tailor marks, lot-line convention, chapter catalog — lives in the cloud and reaches every project and every seat on its own. Every change is a version the coordinator can restore.
Private beta
10 / 10Want to try Qubiq?
Qubiq is in private beta. Leave your email and we’ll let you in as spots open.
Rather talk first? a.dildabayev@gmail.com