Automated building-code compliance review for BIM
Every new IFC version checked automatically, the way software teams run tests before a release — with a provable record of which rules ran against which model. Shipping today on real project documentation; raising to open the Western market, starting with Sweden.
BIM Grade does not replace the engineer. Legal responsibility for the design stays with the chartered engineer and their firm. The platform produces findings and drafts as decision support; it never issues or signs the final documentation submitted to an authority.
Code compliance is where building projects stall
The check is manual, the codes move faster than the engineers, and the cost lands on the applicant.
Soft cost per project
What permit delay costs on a single residential project, by NAHB estimate. The applicant absorbs it — the fee was quoted before the review.
Of developers blocked
Name permit delay as a top barrier to delivery. On the Swedish side, 89% of permit applications arrive incomplete on first submission.
Per document set
Senior engineer time spent cross-checking one set against dozens of codes by hand — and codes are amended continuously.
The category just tipped. Penetration is still near zero.
Capital and regulation arrived in 2026; the installed base did not. That gap is the entry window.
Continuous integration for buildings
Two mechanisms carry the product. Both are the subject of filed U.S. provisional applications.
Coverage gate
PATENT PENDINGEach mandatory check carries its own capability, evaluation and evidence state. A “ready” verdict is structurally impossible while any required row is uncovered.
- Obligation-indexed execution records
- The tool cannot silently skip a rule
- Deterministic geometry, not LLM guesses
- Dual citation: code clause ↔ exact point in the model
Jurisdiction replay
PATENT PENDINGOne immutable project graph, replayed against another country, state or effective date. Signed manifests carry both regulatory-valid and ingestion time.
- Unaffected results provably unchanged
- Typed causal delta between rule sets
- Proof-carrying cross-domain correlation
- Post-export verification of the delivered file
Three steps, and the last one is a human
The platform fits inside the firm's existing workflow instead of replacing it.
Push a model
An IFC file lands from manual upload, an API call or a common data environment — Autodesk Construction Cloud, Trimble Connect, BIMcollab.
The engine runs
Model readiness gate, then deterministic and AI checks against the resolved jurisdiction and code edition. Findings come back as BCF issues with element identifiers.
The engineer signs
BIM Grade is decision support. The chartered engineer reviews, decides and stamps. Liability stays with the professional — which is how this market already buys.
Everyone owns one column. Nobody owns the row.
“Upload a PDF and let AI find code violations” is a crowded lane. Neutral IFC plus jurisdiction replay is not — the incumbents are vendor-locked, buyer-locked or format-locked.
| Product | IFC-native | Code corpus | Applicant-side | Cross-jurisdiction | Provable coverage | Position |
|---|---|---|---|---|---|---|
| Solibri / BIMcollab | ● | · | ● | · | · | BIM quality assurance; rules you author yourself |
| UpCodes / Helonic | · | ● | ● | · | · | Code content and AI reading of PDF drawings |
| Kestrel | · | ● | ● | · | · | Strong — but locked inside Revit |
| CodeComply / CivCheck | · | ● | · | · | · | Sold to city halls, not to design firms |
| AiTech (Sweden) | · | ● | · | · | · | Municipality-facing; applicant side left open |
| BIM Grade | ● | ● | ● | ● | ● | The row nobody else holds |
● claimed · · not claimed publicly. Assessment based on vendor-published material as of July 2026; corrections welcome.
What exists before the round
A shipped engine, a real validated project, and three filings made before raising a cent.
Validated on a real project
- 24 sections of documentation in scope, mandatory state review.
- External paying client — 1,057.8 m² public-building refurbishment.
- PDF, DWG and IFC ingest already shipped.
- Findings carry dual citation: code clause and the exact point in the document.
Filed before raising
- 64/114,878 — coverage-controlled IFC processing.
- 64/114,883 — proof-carrying correlation.
- 64/115,038 — bitemporal source-closure replay.
- All filed 19 Jul 2026 at the USPTO.
See it running
- proektologiya.ru/app — live audit module, opens in a browser.
- app.proektologiya.ru — full build, demo access on request.
- Running on paid, externally-contracted project documentation.
- Same core, different rule pack — codes are data, not code.
One engine, two regions
- Region = a rule pack: critics, code corpus, templates, language.
- The Russian deployment is the proving ground.
- The Western build is the same core plus a Swedish pack.
- Adding a jurisdiction is data work, not a rewrite.
Four founders — Sweden, Serbia, remote
Deliberately distributed. The whole point of a $200K round is that this team can actually run on it.
$200,000 pre-seed — 18 months and one jurisdiction
Not a land-grab round. Enough to prove the Western wedge with a team that already ships.
Swedish rule pack — first four check families
Means of egress, accessibility, fire separation and fixture counts, each with explicit applicability logic, required IFC fields and citations.
Design partners live
5–8 Nordic firms running their own models through the engine; findings validated against their own reviews to build the regression corpus.
First Western revenue + provisionals converted
3+ paid pilots, priority date secured to 19 Jul 2026, and a seed round raised on traction rather than on slides.
Filed before raising
Three U.S. provisional applications on the core mechanisms, all filed on 19 July 2026.
Coverage-controlled processing of IFC artifacts
Obligation-indexed execution records; a ready gate that cannot pass while a mandatory check is uncovered.
Proof-carrying correlation & exact-export verification
Typed joins over IFC entities with a provenance trail, a minimal replay witness, and verification of the delivered file.
Authenticated bitemporal source-closure replay
Replay of one project graph against another jurisdiction or date, with unaffected results provably unchanged.
The questions investors actually ask
Does the AI replace the engineer?
Why Sweden first, and not the United States?
What exactly is patent pending?
Is there a working product or just a deck?
Why only $200,000?
What does the group structure look like?
Terms and abbreviations used on this page
Investors and strategic partners
Send the form and we reply within one business day with the deck, the financial model and a live demo of the audit engine.