Resources · Blog
Engineering notes, product deep-dives, research, and field reports from the team designing AI architecture for the built environment.
LATEST — WEEK 44 · 2026
Showing 1–9 of 31
Blog Oct 26, 2026
Last week took us to Paris for RELEASE [AEC] on Tuesday, and to Tokyo for Archi Future 2026 on Friday. Two very different events, nearly 10,000 kilometres apart, that ended up asking the same…
Read moreBlog Oct 2, 2026
A clean design review can still leave your firm exposed. Why a findings list misses what nobody opened, and how review coverage shows what was reviewed.
Read moreBlog Sep 23, 2026
Dubai one week, Copenhagen the next, and two markets that could hardly be more different. Here is what we took to both, who we met, and what we are bringing home. From Dubai to Copenhagen…
Read moreBlog Sep 10, 2026
Most review teams are one missed comment away from a problem they never saw coming: not because the reviewers are careless, but because the way most firms organise review work makes comprehensive…
Read moreBlog Sep 3, 2026
Every senior technical lead in AEC knows the feeling: a five-hundred-page design package lands, the programme allows four days for review, and so you triage. You sample. You sign off what you can…
Read moreBlog Sep 2, 2026
We started NEXUS because the change this industry needs will not happen one company at a time. Its second edition filled a room in Harajuku, Tokyo with 120+ people, four times last year's turnout…
Read moreBlog Aug 27, 2026
Every review process has gaps. The question is whether your reports show them, or bury them. 'Not yet checked' is not a problem. A false all-clear is. AEC teams are under constant pressure to move…
Read moreBlog Aug 20, 2026
Most reviews don't fail because the team wasn't diligent. They fail because no one ever defined what was supposed to be reviewed, and so something quietly slipped through. The sampling problem. A…
Read moreBlog Aug 13, 2026
Every major AEC project now has access to an AI checker. Upload a drawing set, wait a few seconds, get a verdict against a code reference. It looks like assurance. It isn't. When "checked" isn't the…
Read moreSUBSCRIBE
One email a week with the latest engineering notes, product deep-dives, and field reports from the Tektome team.
Step 3 of 3
Thirty minutes, and you will get a calendar invite straight away.
A calendar invite is on its way to your inbox.
Henry will bring a prepared sample project, so there is nothing for you to set up.
Need to change it? Reply to the invite and we will sort it out.
