Workflow mapping
The real path from pitch to strike, walked and documented with the people who run it.
← All work
Case 04 — Experiential × AI
AI workflows for the team that builds experiences.
For the exhibit design-build firm, we brought the Foundation playbook to a creative production business: connected tools, documented process, and Claude working alongside the team.
World-class builds. Hand-carried process.
A design-build firm runs on coordination: designers, fabricators, project managers, and client teams all moving against hard show dates. The craft was never in question — the connective tissue was.
Project knowledge lived in people and threads. Every show meant re-answering questions the organization had already answered.
The brief: connect the tools, get the process out of heads, and give the team an AI layer that actually helps against a deadline.
Build the system around the show date.
-
Decision 01
Map the real workflow before touching tools.
Pitch to strike, walked with the people who run it. The tools get wired around that path, not the other way around.
-
Decision 02
Let show dates drive the workflows.
Deadlines don’t move, so the system keys off them. Real project milestones trigger the work, and the AI reads the same record as the team.
-
Decision 03
Set AI up around real jobs, not a generic chatbot.
Proposals, project recaps, and client comms, mapped to each role. The goal: an AI layer that actually helps against a deadline.
The Foundation playbook, tuned for a creative shop.
Connected tooling
Project, design, and client systems wired together so status lives in one place.
Claude workspace
AI set up around the team’s actual jobs — proposals, project recaps, client comms — not a generic chatbot.
SOP library
The recurring 80% of show production written down where software and new hires can run it.
Adoption & training
Real use cases per role, so the AI layer gets used after we leave the room.
Deadlines don’t move. So the system has to.
Everything is built around show dates: the workflows fire off real project milestones, and the AI layer reads from the same connected record the team already keeps.
The result is a production organization where the repeatable work runs itself, and the humans spend their hours on the part clients actually buy — the experience.
Practice
Experiential
Focus
Workflows · Adoption
Status
In progress
Where the work stands today.
In progress
This engagement is still underway. The current focus: workflows and adoption.
Status in one place
Project, design, and client systems wired together, so status lives in one place.
80%
The recurring 80% of show production, written down where software and new hires can run it.
Craft up front. System underneath.
The shows always shipped. Now the two weeks before a show don’t eat the whole company to make that true.Production team — Exhibitus
Other engagements in this neighborhood of work.
Skip the slides. Have the conversation.
Thirty minutes, no deck pitch. We walk your top three bottlenecks and what it would take to fix the first one.