I’m seventy-four years old. I started drafting on a board in 1974, watched the industry move to CAD in the late 1980s, lived through the BIM transition in the 2000s, and I’m now in the middle of the third major tooling shift of my career.

The AI one.

I want to write this piece carefully, because there is a lot of bad writing about AI in architecture right now—and most of it is being done by people who have never stamped a drawing in their lives. So instead of another think-piece, here is an honest inventory: the AI tools that actually sit on my desk today, what they do, where they fail, and what I’ve concluded about the shift after building inside it for the last two years.

The Three Tools I Actually Use

- AECLogix Proof — a Revit plug-in for keynote checking. This is one I’m building. It does one specific thing: it checks the tagged keynotes in a Revit model against the actual project specifications and flags every mismatch. A keynote pointing to a spec section that doesn’t exist. A spec section that nothing in the drawings actually references. Every gap between what the drawings say and what the spec book says. Why does this exist? Because every architect reading this knows that keynote-to-spec coordination on a typical project is held together by hope, the project architect’s memory, and a Friday-afternoon spot check. The errors are real, they’re embarrassing in CA, and the cost of finding them by hand is too high to do it consistently. Proof finds them in seconds. The honest part: it doesn’t fix anything. It tells you what’s broken. The architect still has to decide what to do about it. That’s the right division of labor.

- COI Autopilot — subcontractor certificate-of-insurance verification. Also something I’m building, on the AECLogix side. This one is for general contractors more than for architects, but I include it here because it’s the clearest example I know of where AI does a job no human wants—and no software has previously done well. A mid-size GC tracks hundreds of subcontractors, each of whom needs to maintain current certificates of insurance with the right limits, the right additional insureds, the right endorsements. The current process is a part-time staffer with a spreadsheet, chasing PDFs, calling brokers, and missing things. COI Autopilot reads the COIs, extracts the data, compares it to the project requirements, and flags what’s wrong. The lesson from building it is this: AI is at its best when you point it at a job that already exists, that everyone hates, and that no one is doing well. It is at its worst when you point it at a job that doesn’t exist and try to invent a use for it.

- The Ghostwriter Desktop — my drafting partner for everything that isn’t a drawing. This is the one I use personally, every day. Client letters. Spec language. The first draft of this newsletter, which I then mark up the way I’d mark up a junior architect’s writing. Email responses to owners that I can’t bring myself to write at 7 p.m. on a Thursday. The mistake people make with this category of tool is treating it as a writer. It isn’t. It’s a draftsman. It produces a draft. The architect’s job is to redline it—the same way I redlined drawings for forty years. The output is only as good as the redline. I’d estimate it saves me four to six hours a week on writing tasks that used to eat my evenings.

What It Doesn’t Do

Now let me be clear about the boundaries—because this is the part the marketing people leave out.

AI does not design. It produces options, sometimes good ones, but it has no judgment about which option is right for this owner, this site, this code climate, this budget. The architect still designs.

AI does not understand the project. It understands the document in front of it. The architect still has to hold the whole project in their head.

AI does not replace the cheap part of practice—the drawing, the typing, the formatting. That part has already been getting cheaper for thirty years. What AI replaces is the medium-cost coordination work that used to sit awkwardly between the cheap tasks and the expensive judgment. Keynote coordination. COI tracking. First-draft writing. Schedule cross-checks. That entire layer is collapsing fast.

The expensive part—judgment, taste, the ability to look an owner in the eye and tell them what’s wrong with their idea—is not collapsing. If anything, it is getting more valuable. Because every architect now has a coordination layer that runs ten times faster than it used to, the constraint on the practice moves up to judgment.

---

Below the paywall: my prediction for which architects win the next ten years, the bet I’m making with AECLogix, and The AI Tools I Actually Use — the one-page Redline that lists every tool currently on my drafting table, the prompts I run them with, and the workflows that produced the four-to-six-hour weekly time savings I mentioned above. Steal the ones that fit your practice. Skip the ones that don’t.

If you’re on the free tier and this Field Note has earned its way into your week, the paid tier ($8/month, $80/year) is what makes the Redline series possible. Every Tuesday Field Note ships with a printable working tool like this one.

What I Think Comes Next

A prediction, with the caveat that I have been wrong about technology transitions before.

The architects who win the next ten years will not be the ones who learn the most AI tools. They will be the ones who understand the practice deeply enough to know which tasks should be delegated to AI—and which absolutely should not.

Put another way: AI in AEC is going to be won by people who understand the practice, not by people who understand the tools. The tools change every eighteen months. The practice doesn’t.

This is also, frankly, the bet I’m making with AECLogix. I’m not building AI products for the AI-curious. I’m building them for working architects and working contractors who already know exactly which parts of their day are wasted on coordination they shouldn’t be doing. The product is the time it gives them back.

The Honest Part, Again

I am not an AI evangelist. I am an architect who has watched three tooling transitions and has opinions about how this one is going to play out.

Here is what I would tell a thirty-year-old architect today: don’t ignore this, don’t worship it, and don’t let anyone tell you it’s a substitute for understanding the work. Pick up the tools that solve the problems you already have. Put down the ones that don’t.

Stay close to the practice.

That, I think, is what every previous tooling shift has rewarded. I don’t see any reason this one is different.

---

📄 Redline — The AI Tools I Actually Use

A one-page inventory of every AI tool currently on my drafting table, what each one does, the specific prompts I run them with, and the workflows that pulled four-to-six hours back into my week. Three tools you’ve probably heard of, three you haven’t, and a candid section on the tools I tried and abandoned.

→ Download the Redline (PDF)

Steal the ones that fit your practice. Skip the ones that don’t. Update it as the tools change — I will.

— Randy

Subscribe now

There’s a project I took in 2012 that I should have walked away from.

A quick-service restaurant in Arkansas. The owner had hired a contractor who turned out to be a disaster—wrong materials, missed inspections, a punch list that grew faster than it got resolved. By the end of it, we were in arbitration. The job consumed eighteen months of my life and a meaningful chunk of my staff’s, and the fee—the fee I fought to get paid—didn’t begin to cover what it had cost me.

I’d love to tell you the lesson was about contractors. It wasn’t. The lesson was about me. The warning signs had all been there in the first three conversations with the owner, and I had ignored every one of them—because I wanted the work.

This is the piece I wish someone had handed me at thirty-five.

The Fee That Costs the Most

Here’s the math younger architects don’t run.

When you take on a bad project, you’re not just earning a smaller margin on that one project. You’re losing every other project you couldn’t pursue because you were drowning in the bad one. You’re losing the attention you couldn’t give to your better clients, who quietly notice and start drifting. You’re losing the goodwill of your staff, who burn out a little on every problem job. You’re losing nights and weekends that you’ll never get back—and at fifty, those nights and weekends turn out to have been more valuable than the fee.

I’ve done the back-of-the-envelope on this a few times over the years. My honest estimate: a bad project costs you somewhere between two and four times the fee, once you count opportunity loss and staff damage. A great project, by contrast, often *generates* more revenue than the fee—through referrals, repeat work, and reputation.

So the fee you don’t earn from the wrong client is the cheapest money you’ll ever make.

The trouble is that “the fee you don’t earn” never shows up on any income statement—but the fee you *do* earn from a bad project does. And so architects keep taking the bad ones.

The Warning Signs You Already Know

Let me be honest: when I look back at the worst projects of my career, none of the warning signs were subtle. Every single one was visible in the first three conversations. I just talked myself out of seeing them.

Here is the short list, in the order I now pay attention to them.

• The previous architect. The way an owner talks about the architect they fired is the way they’re going to talk about you. If they describe the previous architect as incompetent, arrogant, slow, expensive, or “didn’t understand our vision”—pause. Sometimes the previous architect actually was bad. But more often, what you’re hearing is the owner narrating how they treat the professionals they hire. Listen carefully. That’s the script you’re about to be cast in.

• The decision-maker isn’t in the room. If the person across the table can’t clearly tell you who else has to sign off on decisions, this project is going to be re-litigated at every milestone. I once had a healthcare project where the “owner representative” turned out to be one of seven people who could veto a decision—and they weren’t even the most senior of the seven. Every drawing got reviewed three times by three different factions. I still have the gray hairs.

• The personal attachment. This one is rarer, but devastating when it shows up. I had a project years ago where the owner’s representative had developed a strong personal attachment to the previous project manager on our team. When he had to step away from the practice for medical reasons and I assigned a different PM, the representative could not—would not—accept anyone else. Every decision the new PM made was wrong by definition. Every meeting became an exercise in re-litigating a substitution she hadn’t approved. The project never recovered, because the issue had nothing to do with the project. The lesson isn’t to avoid clients with strong feelings about your team. It’s that when a client’s reaction to a routine business decision is disproportionate, you are seeing how they’re going to react to every other decision down the road. Trust what they’re showing you.

• The fee fight in the first conversation. There’s a difference between an owner who has a budget and an owner who has a grievance. The first one will tell you their number, ask intelligent questions about what they’re getting, and let you negotiate. The second one will treat your fee as something to be reduced on principle, with no curiosity about what’s in it. That second owner is going to grind you on every invoice for the life of the project.

• The schedule that doesn’t add up. If the owner’s schedule requires you to compress design, skip review cycles, or sign off on things you haven’t reviewed, the answer is no. Not “we’ll do our best.” No. The schedule is the first stress test of whether this owner is going to give you the room to do the job. If the answer is no in the first conversation, it will be no in every conversation that follows.

Below the paywall: the harder part — how to actually act on the warning signs when you need the work, the three rules I tell every younger architect now, and *The 5 Warning Signs Worksheet*, the one-page Redline I built from this Field Note. Score it honestly on your next questionable client. Three or more, walk.

If you’re on the free tier and you’ve gotten value from this so far, the paid tier ($8/month, $80/year) is what makes the Redline series possible. Every Tuesday Field Note ships with a printable tool like this one.

The Harder Discipline

Knowing the warning signs is the easy part. Acting on them is the hard part—especially when you’re early in your career, or in a slow year, and the work in front of you is the work in front of you.

I am not going to pretend I’ve always been good at this. I haven’t. The 2012 restaurant was one of at least a dozen times I saw the signs and took the work anyway. Most of those projects didn’t end in arbitration, but most of them ended in a slow grind that taught me the same lesson the arbitration did, just more politely.

What helped me, eventually, was reframing the question.

I stopped asking, ”Can I afford to walk away from this fee?” and started asking, ”Can I afford to take this project—and lose the next three months of attention to my best clients?” Almost always, the answer to the second question was no. And the project I’d been about to take didn’t survive the comparison.

The walk-away is never as expensive as it feels in the moment. The take is always more expensive than it looks on paper.

What I Tell Younger Architects Now

Three things.

Trust the first three conversations. They’re not preliminary. They are the project, compressed.

The way an owner talks about the people he hired before you is the way he’s going to talk about you. Listen the first time.

The fee you don’t earn from the wrong client is the cheapest money you’ll ever make. Write it on a sticky note and put it on your monitor.

I should have.

---

📄 Redline — The 5 Warning Signs Worksheet

A one-page printable scoring sheet for the next questionable client. Each of the five warning signs gets a yes/no honest score. Tally at the bottom — three or more, walk. Carry it into the meeting; fill it out in the parking lot afterward.

[→ Download the Redline (PDF)]

*The cheapest fee is the one you never had to chase.*

Randy

Here’s something I’ve started telling every younger architect who will listen: by the time you’ve had three meetings with an owner, the project is already mostly won—or mostly lost. Everything that comes after is just execution on a decision you’ve already made, whether you realized you were making it or not.

I’m not talking about the formal milestones. Schematic Design, Design Development, Construction Documents—those are deliverables. They show up on the contract. They have fees attached. They don’t decide anything.

The three meetings I’m talking about happen before any of that. And in fifty-two years of practice, I’ve watched every good project I’ve ever done pass cleanly through them, and every bad project I’ve ever done quietly fail one of them.

Meeting One: The Intake

The first meeting is where the owner tells you what they think they want—and where you find out who they actually are.

What I’m listening for has almost nothing to do with the building. I’m listening for the things they don’t realize they’re telling me.

• How they talk about money. Do they tell me a number, or do they want to “see what we come back with”? The first answer means they’ve done this before. The second usually means they haven’t—and that we’re going to spend the next six months re-litigating the budget.

• How they talk about the architect they fired. Almost every owner who has built before carries around a previous architect they couldn’t stand. The way they tell that story is exactly the way they’re going to tell mine, eighteen months from now, to the next architect.

• Who else is in the room. If the spouse is sitting in on the first meeting and contradicting half of what the owner says, that’s the project. If a controller is there with a spreadsheet, that’s a different project. If nobody else is there, and the owner can’t even tell me who else needs to sign off—that’s a third project, and the worst of the three.

I don’t say any of this out loud in that first meeting. I just take notes.

Meeting Two: The Walk-Through

The second meeting is the program walk-through. Whether you’re walking a site or walking a list of rooms, what you’re really doing is testing whether the owner’s vision survives contact with reality.

Here’s where I push. Hard, but politely. I ask questions I already know the answer to, because I want to see how the owner responds when their first instinct doesn’t survive ten seconds of examination.

On a senior living project—and I’ve done a lot of these—the owner almost always says they want a “warm, residential feel.” I’ll lean in and say: “Good. So you want carpet in the corridors?” Half of them say yes. Then I quietly explain what carpet costs to maintain over twenty years in a facility where every resident is a fall risk—and I watch what they do with the new information.

If they listen, adjust, and ask the next question, this is a project I can do. If they get defensive or go quiet, this is going to be a project where every decision gets re-fought three times. I price accordingly. Sometimes I walk away.

The walk-through is the cheapest test you’ll ever run on an owner. Use it.

Meeting Three: The Fee Conversation

The third meeting is the one most architects flinch through.

This is where the owner has decided they want to work with you, and you have to tell them what it costs. Younger architects treat this like a job interview where they’re terrified of being told no. I treat it like a marriage counselor’s first session: if we can’t have a clear, adult conversation about money right now, we are absolutely going to have a terrible one eighteen months from now when there’s a change order on the table.

Here’s what I do in this meeting:

• State the fee plainly. Not “around” the fee. Not “it depends.” A number.

• Tell them what’s in it. And what isn’t. The owners who push back on fee are almost never really pushing on the number—they’re trying to figure out what they’re getting for it.

• Tell them what changes the fee. Scope creep, owner-driven redesign, regulatory surprises. Name them in the first conversation, not in a change order ten months later.

• Watch how they react. This is the second-cheapest test. An owner who pushes back hard on a fair fee in meeting three will push back harder on every invoice for the next two years. An owner who accepts the number and asks intelligent questions about what’s in it is the owner you want.

Two Projects, Told Quickly

San Jacinto Center. The intake was clean. The owner had built before, knew their budget, and knew their decision-makers. The walk-through went well—they listened, they adjusted, they pushed back where they should have. The fee conversation was finished in twenty minutes. That project ran like it was on rails for years. Not because we were geniuses. Because the first three meetings had been clean.

StoneCreek Senior Living, Colorado Springs. Currently in delivery. Same pattern. An owner with real experience, a walk-through where the program survived contact with reality, and a fee conversation that took an hour and was the last hard conversation we’ve had about money. Going well. Will keep going well, almost certainly—because the foundation was set in those first three meetings.

Now compare that to the projects where the intake was muddy, the walk-through showed an owner who wouldn’t take input, or the fee conversation never quite happened. Those are the projects that show up in your nightmares ten years later.

Below the paywall: the discipline that turns this from a story you read into a tool you use on Monday — plus The Three-Meeting Intake Checklist, the one-page Redline I built from this exact framework. Print it, take it to your next first meeting, mark it up.

If you’re on the free tier and you’ve gotten value from this so far, the paid tier ($8/month, $80/year) is what makes the Redline series possible. Every Tuesday Field Note comes with a printable Redline like this one.

The Discipline

Here’s the part I want younger architects to take from this: you can do this. You don’t need fifty-two years of experience to run a good intake. The questions I’m asking in those three meetings aren’t secret. The discipline is noticing what you’re noticing—and being willing to act on it.

The most expensive lesson in practice is the one where you saw the warning sign in the first meeting and took the project anyway. I’ve learned that lesson at least a dozen times.

I want fewer of you to have to.

📄 Redline — The Three-Meeting Intake Checklist

A one-page printable that walks the intake, walk-through, and fee conversation as a single field tool. Twelve checkpoints, the warning signs to listen for at each, and the score-it-honestly section at the bottom.

→ Download the Redline (PDF)

Print one per first-meeting. Pencil in the margins. Save the marked-up sheets — they become the cheapest underwriting record you’ll ever build.

— Randy

Subscribe now

That’s fifty-two years of stamping drawings, sitting across the table from hopeful owners and hardened contractors, and watching projects rise from the dirt. I’ve seen buildings come in beautifully clean, and I’ve watched others go spectacularly sideways. Over half a century, I’ve had a hand in building roughly $300 million worth of senior living, healthcare, restaurants, industrial, and Class-A office spaces.

I’m seventy-three now. Most architects my age have either retired or are pretending they have. I haven’t. But for the first time in five decades, I’m no longer running a practice in the relentless, daily-grind sense—chasing payroll, juggling a dozen projects, and fighting fires before my morning coffee. I’ve intentionally stepped back from that.

Instead, I’m doing what I probably should have started doing twenty years ago: I’m writing it all down.

The Reason I Waited

If you had asked me at fifty whether I had anything useful to share with younger architects, I would have laughed at you. I was too busy just surviving as one.

This profession consumes you. There’s rarely slack in the schedule for reflection—hell, there’s barely enough slack for lunch. The lessons you learn on one site get immediately poured into the foundation of the next before you’ve even had a chance to process them.

That’s the great trap of our practice. The people with the most valuable lessons to teach are usually the ones who can least afford the hours to teach them. And by the time they finally have the hours, many have lost the energy, the interest, or the thread altogether.

I refuse to lose the thread.

What This Newsletter Is

The Practicing Architect will be my weekly Field Notes to you. Expect short, plain-spoken pieces from someone who has actually done the work, rather than just theorized about it.

Here is what we’ll cover:

- The Reality of Practice: How the job actually works, bridging the gap between school, the AIA, and the real world.

- The Crucial Early Calls: The quiet, make-or-break decisions that determine a project’s fate—which almost always happen in the first three meetings.

- The Business of Architecture: The unglamorous essentials of contracts, fees, scope creep, and how to actually get paid.

- The AI Evolution: The massive shift happening right now as AI transitions from a novelty to a foundational tool inside AEC firms.

- Building for the Future: Real-time lessons from building AECLogix, the AI automation company I currently run for our industry.

- War Stories: The projects that went perfectly, and the ones that kept me up at night.

I’ll name names where it helps and stay anonymous where it doesn’t. But I will never write about anyone I’d be ashamed to look in the eye.

Who It’s For

This is for practicing architects—from eager interns to seasoned principals—who crave field perspective over academic theory. But it’s also for the contractors, owners, and developers sitting across the table from us. Because the truth is, the more clearly we understand how the other side thinks, the better our buildings become.

What I’m Not Going to Do

I’m not going to write design think-pieces. There are plenty of those, and most are written by people far more qualified for that conversation than I am.

I’m not going to chase the news cycle. If something genuinely affects practice—a code change, a tool that actually works, a court ruling that matters—I’ll write about it. Otherwise, I’m staying out of the noise.

I’m not going to pretend I have everything figured out. I’ve made every mistake an architect can make, and some of the best pieces in this newsletter will be about projects that went sideways and what I’d do differently the second time around.

And I’m not going to pretend AI is either a passing fad or an existential threat. It’s a tool. A good architect has always known how to pick up the right tool and put down the wrong one. What’s changing now is the size of the toolbox.

The Honest Reason

The real reason I’m writing this—the one underneath all the others—is that I have the time now, and I won’t always.

There are five more decades of architects coming up behind me who will run into the same problems I ran into. The lessons are simple enough to be useful, if someone bothers to write them down. Most of those lessons aren’t in any book. They live in the heads of people my age who don’t have the hours to put them on paper. With the daily grind off my plate, I finally do.

If you’ve been practicing a while and you want to push back on what I write here, even better. Comments are open. I read everyone. The whole point of Field Notes is that practice is a conversation, not a lecture.

One issue a week. Sometimes two.

Subscribe if any of that sounds like your kind of thing.

Randy Kopplin

Subscribe now

You just subscribed, which means I owe you something useful.

You should have received your Bonus Unlock in a separate email — Owner Intake: 12 Questions a 50-Year Architect Asks First. It’s the question set I’ve spent fifty-two years assembling, condensed onto four pages you can print and mark up. If you don’t see it, check your spam folder or download it directly here. If it doesn’t save you on a project at least once, I’ll be surprised.

This is The Practicing Architect. It is what I wish someone had handed me at thirty, forty, and fifty.

Here is what I believe about practice, in one paragraph: most of the architects I’ve watched succeed quietly thrive on the unglamorous parts — the intake conversation, the contract clause, the redline at the right moment — and most of the ones who struggle are losing in those same places. The schools don’t teach this. The AIA doesn’t quite put it in writing. So I’m writing it down here, while I still can.

2. Who This Is For

You’re in the right place if you are:

• A practicing architect — intern through principal — who wants field perspective instead of theory.

• A general contractor who’d rather understand how the architect across the table is thinking than guess.

• An owner or developer who wants a clearer view of the people you’re trusting with the building.

• A young architect who’d like to skip ten years of avoidable mistakes.

You’re not in the right place if you want design think-pieces, hot takes on starchitects, software reviews, or news-cycle commentary. I don’t write about any of that.

3. The Biggest Problems This Newsletter Exists to Solve

After fifty-two years, here is what I’ve watched eat practicing architects alive:

• The first three meetings. Most projects are quietly won or lost in the intake, the walk-through, and the fee conversation. Almost nobody is taught how to run them.

• Contracts and getting paid. The unglamorous business of practice — fees, scope, change orders, the legal language that protects you or doesn’t. School never covers this. You learn it the hard way or you don’t learn it at all.

• The wrong client. Every architect I know has at least one project that should never have been signed. The warning signs were visible in conversation one. Nobody trained us to see them.

• The AI shift. A real tooling transition is underway in AEC, and the conversation is dominated by people who have never stamped a drawing. The practicing architect needs a sober, working-architect’s view of what AI does, what it doesn’t, and where it actually belongs.

These four are the rails this newsletter runs on.

4. What You Get, Every Week

This is the part most newsletters skip. Here is exactly what arrives in your inbox:

Every Tuesday: one Field Note + one Redline.

• The Field Note is a 1,000–1,500 word essay — a specific lesson, decision, or mistake from my fifty-two years on the boards. Always grounded in a real project, a real conversation, a real number.

• The Redline is a one-page deliverable that comes with each Field Note — a checklist, template, contract clause, intake question set, or AI prompt. Something you can use Monday morning.

Free subscribers get the Field Note in full and a preview of the Redline.
Paid subscribers get the Redline as a downloadable PDF and the searchable archive of every past Redline.

That’s the deal. No filler. No “support my writing.” A tool every week.

5. Who I Am

Randy Kopplin, RA. Licensed in 1974. Fifty-two years stamping drawings on roughly $300 million of built work across senior living, healthcare, restaurants, industrial, and Class-A office.

I have worked at HKS, run delivery at Haskell, built senior living for Marshall Erdman, developed Class-A office with StoneCreek, and owned my own practice. I have sat on every side of the table an architect can sit on — design lead, project architect, owner’s rep, developer, principal. I have signed the drawings, the checks, and the lien releases.

I also run AECLogix, an AI automation company for the construction industry. I will write here about what I am learning while building it.

I am seventy-three years old. Most architects my age have either retired or are pretending they have. I haven’t. I’m writing this down because the lessons live mostly in the heads of people who don’t have the hours to put them on paper. With the daily grind off my plate, I finally do.

6. Where to Start

If you want a sense of the work before the first Tuesday lands, start here:

• Why I’m Finally Writing This Down — the manifesto.

• Three Meetings to Win the Job — how every project is decided before you draw a line. (Publishes Jun 9.)

• The Cheapest Money You’ll Ever Make — a lesson from the wrong client. (Publishes Jun 16.)

(Links update as articles publish.)

7. What I’d Like You to Do Next

Two small asks:

1. Reply to this email and tell me what you’re stuck on in your practice right now. One sentence is plenty. I read every reply, and the best questions become future Field Notes.

2. If a Redline is the kind of thing you’d want every week, upgrade to paid. It’s $8/month or $80/year, and it pays for the time I spend turning each essay into a usable tool. Founding members ($200/year) also get a quarterly small-group Zoom and my direct email.

Either way — welcome. Comments are open on every post. Push back hard when you disagree. Field Notes is a conversation, not a lecture.

See you Tuesday.

Randy Kopplin, RA