Not sure where AI would pay off? Take the 3-minute opportunity check →
Architecture firms · Internal knowledge assistant

Your firm's standards and lessons learned, searchable in plain language

Every architecture firm has a knowledge problem that grows with each hire. The office standards manual, typical wall details, master spec sections, code research memos and lessons learned from past projects exist, but they live on a file server with folder names only the original author understands. Junior staff ask the senior project architect, who loses an hour a day answering.

How it often works today
  • Junior designers interrupt senior staff with standards questions several times a day, pulling the most experienced people away from billable production work.
  • Typical details get redrawn from scratch because nobody can find the version the firm already refined after a leak or a contractor question.
  • Lessons learned meetings happen at project closeout, but the notes are filed and forgotten, so the same coordination mistakes repeat on the next job.
  • Code research memos for jurisdictions such as Denver or Boulder County are rewritten for each project instead of being reused and updated.

An internal knowledge assistant indexes the documents you approve and answers questions such as which parapet detail we use with TPO roofing or what we learned about elevator pit waterproofing on the last mid-rise. Every answer links to the source so staff can check it. It does not replace code research or professional judgment.

The improved workflow

Choose and clean the source documents

Start with a limited set: office standards, CAD and Revit standards, master spec sections, typical details index and recent lessons learned. Outdated versions are archived so the assistant does not quote superseded guidance.

Index inside your own environment

Set up the assistant within Microsoft 365 or another approved platform so documents stay under your existing permissions. Staff only see answers drawn from files they already have access to.

Answer with links to the source

Staff ask questions in Teams or a browser. Each answer quotes and links the relevant standard, detail or memo, so the person checks the original rather than trusting a summary.

Capture new knowledge as it happens

When a project architect resolves a recurring question, a short form adds the answer to the knowledge base for review, so the library grows from real problems instead of annual cleanups.

How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.

What we would measure

Questions answered without senior staff

The main goal is giving experienced architects back their time. Tracking this shows whether the assistant is trusted.

Answer accuracy on a test set

A list of 30 or 40 real questions with known answers, checked monthly, catches drift when documents change.

Time for new hires to work independently

Faster onboarding is one of the clearest benefits for firms hiring designers and project architects.

Where people stay in control

  • The assistant answers from firm documents only. Code interpretation for a specific project is still confirmed by a licensed architect against the adopted code.
  • Client project files stay under existing folder permissions. Confidential projects can be excluded from the index entirely.
  • A named standards owner reviews new entries before they become part of the knowledge base, so one person's workaround does not become firm policy.
Example

Illustrative example: a new project architect on a multifamily job

For example, a project architect joins a 40-person firm and is placed on a podium apartment project. In the first week she asks the assistant about the firm's standard corridor wall assembly for the required fire rating and which window flashing detail was revised after a past water issue. Each answer links to the standard detail and the lessons learned memo. She checks both, then asks the senior PA one focused question instead of ten. This is illustrative, not a measured outcome.

Tools typically involved

Microsoft CopilotSharePointMicrosoft TeamsAutodesk RevitBluebeam Revu

What the first 30 days look like

In the first 30 days we would collect 40 real questions your senior staff answer repeatedly, map where the answers live, and flag outdated documents. Then we would agree which sources to include, set an accuracy target and choose the platform for a pilot.

Common questions

Can it search inside Revit models or drawing sets?

Mostly no, at least not reliably. Assistants work best on text documents such as standards manuals, spec sections, memos and meeting notes. Details can be found through a well-named index or a PDF detail book. We would be honest about this limit rather than promise model search that produces wrong answers.

What if our standards manual is out of date?

That is common, and it is worth fixing first. An assistant that confidently quotes old standards does more harm than none. A typical first step is a short cleanup of the most-used sections. That work pays back even if you decide not to build the assistant.

Is Microsoft Copilot enough, or do we need something custom?

For many firms already on Microsoft 365, Copilot or a SharePoint-based agent is a reasonable starting point because it respects existing permissions. A custom setup makes sense when you need tighter control over sources or answers. We would test with your real questions before you commit to licenses.

The business case

Does it pay for itself?

Illustrative defaults for an architecture firm. Replace them with your numbers.

What this workflow costs today

a month in staff time, before any lost sales

Monthly fee + assumed tools +
Break-even: new clients a month (at first-year value)
Or: staff hours recovered and redeployed
Break-even additional revenue
Value of +1 point of win rate
First 90 days, service fee

Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.

Next step

Bring one expensive workflow. Leave with a clear next step.

In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.

Book a 30-minute workflow review Not ready to talk? Take the 3-minute check

30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.

Book a 30-minute review