Databases, Automation and Other Fun Things for Architecture Project Management
Me
Licensed Architect
Web designer
Love reducing admin drag & finding better ways to do things
Practitioner, not vendor
Software-neutral; a practicing architect who's tested dozens of systems and built tools specifically for architecture/interiors workflows.
Systems brain, born in practice
The same instinct for finding better ways to build applies to how firms run; tools designed from inside real project delivery, not from a software company's guess at it.
"Custom is king"
There's a reason no all-in-one platform ever stuck across architecture firms: it's impossible. The workflows are too niche, every firm runs projects differently, and architects want things done their way. Off-the-shelf software forces you into someone else's process whereas custom systems are built around yours.
Invest once, save ongoing
Custom infrastructure can cost a little more up front but replaces stacked per-seat subscriptions, cutting long-term software spend.
Current Systems:
Server folders, project drawings, human memory
Small firms don't have the bandwidth to solve these problems
Building smart databases allows you to scale your project work.
I use Airtable or Teable as the foundation to for this
Database structures:
Your Team Base
one base, all firm wide information
customize for your firm's needs
Your Project Base
project based information
I build as many project bases as you need
Your Business Base
leadership focused business base
organize proposals, invoices & expenses
A single source of truth
One place for:
materials
specs
details
RFIs
FORs
presentations
decisions
Connected data (not files)
Single database of materials links to all projects
Update once, syncs everywhere
Link all sorts of data together
Decisions are tracked and not buried
Automated Outputs
PDFs generate automatically
Spec books build themselves
Client presentations auto-generate
Why?
Save
Time
Reduce
Errors & Risk
Improve
Client Experience
