Help us make better ads
Did you recently see an ad for beehiiv in a newsletter? We’re running a short brand lift survey to understand what’s actually breaking through (and what’s not).
It takes about 20 seconds, the questions are super easy, and your feedback directly helps us improve how we show up in the newsletters you read and love.
If you’ve got a few moments, we’d really appreciate your insight.

Architectural technology keeps accelerating.
Confidence in how to adopt it does not.
This week’s discussions all circled the same underlying issue: software isn’t the hard part - decision-making is. Whether the topic was winning work, delivery efficiency, or hiring for new roles, the friction consistently showed up between tools, workflows, and ownership.
The posts below reflect that pattern. Not opinions. Not trends. Signals emerging repeatedly from conversations inside practices, founder meetings, and live delivery environments.
If you only scan one thing this week, start here. 👇
What Sparked the Most Discussion This Week
Here’s what resonated most:
We spoke to 100+ architects about technology in practice.
None of the real problems were about software.
Click here to see the full post: LinkedIn
Most architects think winning work is about better design.
It isn’t.
Click here to see the full post: LinkedIn
If you understand buildings, workflows, or delivery - these companies want you.
If you understand buildings, workflows, or delivery - these companies want you.
Click here to see the full post: LinkedIn
If you missed these during the week, this is the signal - not the noise.
Theme of the Week: Why “Time-Saving” Software Often Increases Delivery Overhead in Architecture Practices
Many architecture practices invest in software expecting it to reduce delivery time and costs. In reality, the opposite often happens - delivery overhead increases, even when the tool technically works.
This is not a software problem. It is a workflow and decision-ownership problem.
The core misconception
Time saved by software is rarely reclaimed as fee savings.
Instead, it is usually absorbed into:
-/ additional checking and coordination
-/ parallel workflows “just in case”
-/ higher design ambition without fee adjustment
The result: effort increases but it becomes harder to see.
The three patterns that cause this
1. Tools are added but workflows are not redesigned
New software is layered onto existing processes rather than replacing them.
2. No one owns the downstream risk
Once a tool affects delivery, risk becomes ambiguous:
-/ Who signs it off?
-/ Who carries liability if it fails?
-/ Who decides when it’s “good enough”?
Without clear ownership, teams default to caution.
3. Time savings convert into invisible complexity
Efficiency rarely results in fewer hours billed.
It results in:
-/ more iterations
-/ more options explored
-/ more information produced
From the outside, productivity looks unchanged but internally, complexity rises.
Why hiring staff often feels “safer” than buying software
Hiring people:
-/ increases visible capacity
-/ spreads risk across individuals
-/ fits existing mental models of delivery
Buying software:
-/ exposes how work is actually done
-/ forces decisions about responsibility
-/ makes inefficiency explicit
This is why practices will hire before they automate - even when automation is cheaper.
A simple sense-check before investing
Before approving any new tool or AI initiative, ask:
-/ What step in our current workflow disappears if this works?
-/ Who is accountable for trusting the output?
-/ What additional checking will we explicitly remove?
-/ Where will the saved time go; fee, quality, or capacity?
If these cannot be answered clearly, the tool will add overhead.
This perspective comes from ongoing work at ADDD with architecture practices assessing how technology decisions impact delivery risk, coordination and cost.
If You Sell ConTech, This Is the Room That Matters
If you build technology for architects or engineers, your biggest constraint isn’t product quality - it’s access to real decision-makers.
That’s why AEC INNOVATE (June 16–18, 2026, ARIA Resort & Casino) is different.
This is not a trade show. It’s direct access to 500+ Principals, CTOs, Innovation Leads, and Digital Directors who attend specifically to evaluate AI and workflow tools and shape their 2026 technology roadmaps.
Why exhibit
-/ Two days of high-intent conversations
-/ Senior buyers actively comparing solutions
-/ Clear pipeline, real feedback, and faster deal momentum
Exhibitor package includes
-/ Exhibit space
-/ Two passes
-/ Logo placement (website + main stage)
-/ Custom promo link offering prospects $200 off
If you want visibility with the people who actually influence buying decisions, this is one of the few events engineered for that outcome.
→ Register interest: https://www.psmj.com/innovateaddd
5 Tools Architects Are Exploring in Knowledge Management
Rather than “best tools,” these are tools I’m seeing practices actively evaluate:
Tektome: Next-Gen AI for Design. Tektome turns project data into structured knowledge, helping AEC teams find critical information, analyse documents, and design faster with intelligence and precision.
Best suited for: Architects / Engineers / Project Teams
Fits in workflow: All Project Stages
ARKI - Get more design done with less wasted effort. Architecture and engineering project design done 50% faster, by leveraging your firm’s existing data
Best suited for: Architects / Engineers
Fits in workflow: early to mid stage
Knowledge Architecture - The Intranet, LMS, and AI Search Solution for AEC. Over 150 leading AEC firms run Synthesis, our integrated Knowledge + Learning Management platform.
Best suited for: Architects and Interior Designers
Fits in workflow: early-mid-Late stages
Howie - The AI Brain for the Built World. Build a single source of truth for your construction & real estate data.
Best suited for: Architects, Engineers, Designers and Real Estate Clients
Fits in workflow: early - mid
Aane - Revolutionize Your Firm's Detail Management Process. Discover architectural details instantly with AI-powered search. Save hours of research time and create exceptional designs.
Best suited for: Architects
Fits in workflow: Early - mid
Free Resource: Explore the ConTech Landscape
If you’re scanning this space, I maintain a free ConTech database covering hundreds of tools across architecture, engineering, and construction.
I use it as a starting point before advising practices, not as an answer in itself.
→ Browse the database here: https://contechdatabase.softr.app/
What This Means for Practice Leaders
If you’re leading a practice or digital strategy, software overload directly affects:
-/ Delivery risk
-/ Team confidence
-/ Long-term competitiveness
The question isn’t whether to adopt new tools.
It’s how decisions are governed, tested, and embedded.
This is where most value is either protected, or quietly lost.
Unchecked software sprawl erodes fees, increases costs, and reduces confidence in delivery without ever showing up as a single line item.
One Role Worth Noticing This Week
Sr Product Designer - Pirros
Why this role matters:
At Pirros, this role sits where AEC software usually breaks: turning messy, real-world workflows into systems people can actually trust.
This isn’t about polishing screens. It’s about designing how decisions are made, validated, and acted on across QA/QC, collaboration, and delivery.
You shape what gets built, not just how it looks
You make complex, data-heavy workflows usable, not abstract
You ensure AI accelerates decisions without increasing risk
You replace software sprawl with clear, accountable workflows
→ View role: Sr Product Designer - Pirros
See all roles here: www.aectechjobs.com/search
One Next Step
If this issue resonated, let’s have a chat:
→ Book a short diagnostic call - https://meetings-eu1.hubspot.com/allister
No pressure, just a next step if useful.
One Question for You
When evaluating new software, what’s harder right now: deciding what to trust, who should decide, or what to remove from your existing workflow?
Hit reply, I read every response.
This newsletter exists to help architects navigate technology with confidence, not hype by focusing on workflows, decisions, and real practice constraints.
Thanks for reading!
Allister

















