Client likes option B but wants bigger kitchen island. Concerned about cost. Wants to keep existing windows if possible. Structural engineer needs to review wall removal. MEP to confirm range hood route. Client asked about schedule. Need revised plan before next Friday. Finish direction: warm modern, not too expensive. Owner will send appliance specs.
AI for Architects · October 2026 Edition
You know you need to learn AI. Start this afternoon.
A short, plain-English guide for architects. Start with the work you already do: client emails, proposals, zoning PDFs. 80 pages, with prompts you can paste today.
- Instant PDF + EPUB download
- 80 pages, read in an afternoon
- No coding needed
From the book · Worked example 2 of 3
Messy notes in. Clear email out.
This is one example from the book, shown in full. Copy the prompt and try it on your own notes after your next client meeting.
Turn these rough meeting notes into a client follow-up email. Format: 1. Thank the client briefly. 2. Summarize decisions made. 3. List open questions. 4. List action items by responsible party. 5. End with next step and timing. Tone: clear, calm, professional. Do not invent deadlines or promises. Notes: [paste notes]
Thank you for today's meeting. Based on our discussion, we will continue developing Option B with a larger kitchen island and a warm modern finish direction. The main items still needing confirmation are the structural impact of the wall removal, the range hood routing, and whether the existing windows can remain. Action items: - Architect: revise Option B and issue an updated plan before next Friday. - Structural engineer: review the proposed wall removal. - MEP consultant: confirm range hood routing options. - Owner: send appliance specifications. Once we receive the consultant feedback, we can confirm any schedule or cost implications more clearly.
Then you edit it so it sounds like you. The book has two more worked examples (a zoning PDF and a budget conversation), a prompt library for nine everyday tasks, and a 30-day plan.
Get the Book - $19
From readers
What architects say.
[Reader quote: one or two sentences about what changed in their work.]
[Role, Firm, City]
[Reader quote: one or two sentences about what changed in their work.]
[Role, Firm, City]
[Reader quote: one or two sentences about what changed in their work.]
[Role, Firm, City]
[Reader quote: one or two sentences about what changed in their work.]
[Role, Firm, City]
The question on everyone's mind
Is it too late to start? No.
The tools changed every few months. Features moved. Prices changed. If you feel behind, you are not alone. If your work happens on a computer, AI is now part of the job. The good news: catching up is smaller than it looks.
"Am I too late?"
No. You don't need to have started early. You need a few reliable habits, and those take days to build, not years. The book is 80 pages.
"Is it just hype?"
Some of it is. The book skips the hype and shows what works today on real tasks: emails, meeting notes, zoning PDFs. You saw one example above.
"How do I even start?"
Chapter 2 is your first 30 minutes with AI. The appendix gives you a 30-day plan, one small task at a time.
This is not about AI designing buildings for you. It is about clearing the repetitive work off your desk, so you have more time to design.
Look inside
Real pages from the book.
Three pages from the October 2026 Edition, exactly as you'll get them. Tap a page to see it full size.
What's Inside
Open any chapter row for a short preview of the practical work covered in the book.
01 The Current AI Landscape A plain-English map of the tools architects should know in 2026. +
Covers general AI assistants, file upload, web search, deep research, Projects, Skills, Gemini Notebook, Workspace tools, visual AI, and the newer coding-agent category.
02 How to Choose the Right Tool Simple decision rules for matching the task to the assistant. +
Learn when to use ChatGPT, Claude, Gemini, Gemini Notebook, a workspace assistant, or a small technical helper such as Codex, Claude Code, or Antigravity.
03 Research and Feasibility Zoning PDFs, site research, constraints, and early project questions. +
Practical workflows for uploading reference documents, asking better questions, extracting constraints, and checking the model's answer against the original source.
04 Communication Work Emails, meeting notes, proposals, and client explanations. +
Shows how to move from rough notes to calm, professional drafts while keeping your judgment, tone, and responsibility in the loop.
05 Project Workflows Small repeatable routines for real architecture practice. +
Covers research folders, reusable prompts, client-facing drafts, consultant notes, and lightweight systems that do not require a large team or complicated software stack.
06 Small Technical Helpers Where agents and coding tools fit, even if you are not a programmer. +
Introduces practical uses for tools like Codex, Claude Code, and Antigravity: renaming files, cleaning CSVs, making small websites, and automating repetitive chores.
07 Building Your AI Habit A simple way to use AI regularly without overhauling your practice. +
Helps readers start with one or two repeatable tasks, build confidence, and avoid turning experimentation into another source of stress.
08 Ethics and Privacy What not to upload, what to review, and where human judgment stays central. +
A practical view of confidentiality, source checking, client trust, and the limits of AI assistance in professional work.
Appx The Library Prompt library, worked examples, and a 30-day action plan. +
Includes ready-to-adapt prompts and three longer examples: uploading a zoning PDF, turning meeting notes into a follow-up email, and explaining a budget or schedule issue.
This is for You If...
The book is written for architects who are capable with technology, but still feel that AI is scattered, noisy, or hard to bring into daily practice.
You know you should be using AI.
And you haven't really started. Or you tried it a few times and it didn't stick.
You run or work in a small practice.
You do not have a research department, automation team, or spare hours to test every new tool.
You want examples, not theory.
The focus is emails, PDFs, notes, project communication, and the kinds of tasks that repeat every week.
You want AI to stay in its lane.
This is not a book about replacing architects. It is about reducing the repetitive work around architecture.
AI for Architects
October 2026 Edition
$19
USD one-time
Less than one billable hour.
- Full PDF and EPUB files, instant download
- 80-page practical guide for architects and small studios
- Prompt library for nine everyday tasks, ready to paste
- Three worked examples: a zoning PDF, meeting notes, and a budget conversation
- Simple 30-day action plan for building the habit
- Plain guidance on client privacy and checking answers
Secure checkout by Gumroad. Your receipt and download link arrive by email.
Questions
Am I too late to start? +
No. The tools keep changing, but the useful habits are simple and few. Chapter 2 walks you through your first 30 minutes, and the 30-day plan takes it from there.
Is this just hype? +
The book is written for skeptics. It shows what AI does well today, where it fails, and what you should always check yourself. Nothing in it asks you to let AI make design or code decisions.
Can I see what's inside? +
Yes. There are three real pages and a full worked example on this page.
Can I expense it? +
Yes. Checkout is handled by Gumroad, which emails you a receipt right after purchase.
How long is it? +
80 pages. You can read it in an afternoon and use the first prompt the same day.
Is this for beginners? +
Yes. It assumes you may have tried AI a few times, but do not yet have a reliable way to use it in practice.
Do I need paid AI tools? +
No. Paid tools can help, especially for file uploads and longer documents, but the book focuses on workflows more than one subscription.
Will this help if I already use ChatGPT? +
Yes. The book is especially useful if you use AI occasionally but want clearer repeatable patterns for real project work.
What format do I receive? +
The book is delivered as digital PDF and EPUB files after purchase.
Why I
Wrote This.
I grew up in an architect's house. My father is an architect, and so are my father-in-law and my sister-in-law. I'm a programmer, not an architect, but I have watched this profession up close my whole life, and I love it.
AI has changed how I work every day. I wrote this guide for the architects in my own family: plain steps, real examples, no hype. The tools are moving fast, and I want the people who design our buildings to get the most out of them. If it helps them, I think it can help you too.
Get the Book - $19