Use Cases
Relationship Memory for Architects
Architects carry relationships across long projects — clients, engineers, contractors, officials. Relationship memory keeps every one warm for years.
Architecture is a relationship business disguised as a design business. A single project can run two or three years, involve a dozen consultants, and depend on a planning official remembering you favorably. Yet most of that relational knowledge lives only in your head — and it leaks the moment a project closes out.
Your drawing software remembers the building. Your project management tool remembers the schedule. Neither remembers that the structural engineer prefers email to calls, or that a former client just bought a second lot.
Why an architect’s relationships are easy to lose
Projects are intense and then they end. For eighteen months you talk to a client’s whole family, learn the way a contractor likes to sequence work, and build real trust with a consulting engineer. Then the building opens, the team disperses, and within a year the specifics fade. The next time that client wants an addition — or refers a friend — you are reconstructing a relationship you already built.
The same thing happens across the supply side. You work with a brilliant civil engineer on one job, then do not have a project that needs them for two years. When you finally do, you barely remember why you trusted them.
What architects should remember
- Clients: their taste, their tolerance for risk, family details, future plans, how they like to be communicated with
- Consulting engineers — structural, civil, MEP — and how each one works, communicates, and bills
- Contractors and subs: who delivers, who is worth the premium, who you would never use again
- Planning and building officials: names, what each jurisdiction cares about, past variance history
- Past-project relationships: the people from every job who might become the next referral
- Promised follow-ups that fall between projects — the drawing you said you would send, the introduction you offered
A note that helps before a kickoff call
Reconnecting with the Hartwells about the lakehouse addition. Original 2024 project — they loved the cantilever, hated the change-order surprises, so over-communicate budget early. Daughter Mia is an architecture student now; she’ll be on calls. Use Dale at Meridian Structural again — they liked him. Planning here cares most about lake setback; pull the old variance file.
Specific, human, and tied to a person — the kind of memory that makes a returning client feel known.
Build a network you can actually recall
Your competitive edge is not just design talent; it is the team you can assemble on short notice. That edge depends on remembering who is good and how they work.
| Relationship | What to capture |
|---|---|
| Consulting engineer | Discipline, communication style, reliability, rate |
| Contractor / sub | Quality, schedule honesty, last project together |
| Planning official | Jurisdiction, priorities, variance history |
| Past client | Project, what they loved, future plans, referrals given |
When a new project lands, a relationship memory layer turns “who did we use for that?” into an answer you have in seconds.
How Intriq fits an architecture practice
Intriq is relationship memory, not a heavy CRM or a project tool. After a client meeting or a call with a consultant, you write a quick note in plain English and the details organize themselves around each person. You get reminders that carry context, and before a kickoff or a re-engagement you can ask for a grounded briefing drawn only from notes you actually saved — it tells you when it does not know.
It is private by default and iPhone-first, so you can capture a thought on a job site walk-through before it disappears. It complements your design and project-management stack rather than competing with it.
For more on the approach, see what a personal CRM is, why relationship memory is not contact management, and how to take better contact notes.
Key takeaway: Buildings outlast projects, but so do relationships — and the practices that remember their clients, consultants, and officials win the repeat work and referrals that fill the pipeline. A private relationship memory layer keeps that network warm across the long gaps between jobs.
FAQ
Does this replace my project management software?
No. Project management handles schedules, drawings, and deliverables. Relationship memory handles the people context — client preferences, consultant reliability, and planning-official history — that those tools were never designed to hold.
How does it help with repeat clients?
Returning clients want to feel remembered. A grounded briefing before a re-engagement call surfaces what they loved, what frustrated them, and what they were planning — so the conversation picks up where it left off.
Can it help me staff a project team faster?
Yes. By capturing how each engineer, contractor, and sub actually performed, you can recall the right team for a new job instead of guessing from a stale memory.
Final recommendation
Treat your network as the asset it is. After each meaningful conversation — with a client, a consultant, or an official — capture one short note. Across the long arcs of architectural projects, that habit is what turns a one-time job into a returning client and a scattered set of contacts into a team you can assemble on demand.