Where This Comes From
Three generations deep in a broken industry.
Richard Clayborn, PE, didn't stumble into the architecture and engineering world. He was born into it. The Clayborn name has been in AEC since 1951 — 75 years of his family designing, engineering, and building across Indiana and Kentucky. By the time Richard earned his Civil Engineering degree from the University of Louisville in 2001, he already understood what most young engineers take years to learn: the work is only half the job. The other half is everything else.
His career has taken him across every level of the industry. He worked inside government agencies — managing infrastructure projects for the State of Indiana, the City of Indianapolis, and the Indianapolis Airport Authority — where on a busy day he could handle over 200 emails, coordinate dozens of concurrent projects, and still be expected to produce engineering decisions by end of day. He's worked as a consulting engineer, advising firms from the outside on the same operational chaos he was navigating from within. He's built and run his own practice, Clayborn Group, to over 1,000 completed projects and more than a billion dollars in managed work. He holds Professional Engineer licenses in Indiana and Kentucky, a real estate broker license, an FAA private pilot certificate, and runs a forensic engineering practice. He has seen this problem from every seat at the table.
"I've watched this problem across every project size, every firm type, every market cycle for 25 years. The admin bottleneck isn't a small-firm problem. It's the industry's oldest unsolved problem. And nobody was fixing it because the people who felt it most weren't software engineers."
Richard has always been the person in the room asking whether there's a better way. Not in a disruptive sense — in an engineer's sense. If a process is wasting time, find the waste. If a system is creating friction, remove it. That instinct showed up early in his career, watching government agencies process hundreds of daily emails through manual routing systems that any competent developer could have automated in a weekend. It showed up in consulting, watching firms pay premium rates for coordination work that had nothing to do with the engineering. It showed up every day running Clayborn Group — answering client emails about document links, updating spreadsheets from site visits, writing proposals at 11pm for 8am meetings, following up on leads that had gone quiet while the real work piled up.
The question was never whether to fix it. The question was whether the right tools finally existed to do it properly. By 2025, they did — and Richard, who had spent a career watching this problem from every angle, knew exactly what the solution needed to look like.
The System That Should Have Existed
Three generations needed this. Now it exists.
When the Clayborn family started in AEC in 1951, the answer to the admin problem was people. At peak, Richard's grandfather had six secretaries — answering phones, typing correspondence, filing drawings, tracking invoices, scheduling site visits. Six people to hold the institutional knowledge of the firm and keep it moving. That was the system. It was expensive, it was manual, and it was the only option that existed. It worked because nothing better did.
By Richard's father's generation, margins had tightened and the workforce had shifted. One secretary. The work had grown more complex — more regulation, more documentation, more project types, more coordination — but the headcount to manage it had shrunk to a single person doing the work of six.
Richard's generation inherited both the complexity and the staffing problem. He tried hiring admins — three of them over the years. Each took months to train because the institutional knowledge of how the firm worked lived in his head, not in any system. Each eventually moved on. Each time, he started from scratch. It wasn't a people problem. It was a systems problem that people had been patching for 75 years.
Today, Archi does what six secretaries did — and more — running continuously, never needing retraining, never losing the firm's institutional knowledge when someone leaves. The tools of every prior generation have been replaced. This one replaces the last thing that hasn't changed since 1951.
"My grandfather dealt with this. My father dealt with this. I dealt with this for 25 years before I had the tools to do anything about it. Every generation just accepted it as the cost of running a firm. It isn't. It's a solvable problem that nobody in software bothered to solve — because they'd never felt it."
That's the thing about the admin problem in AEC: it's invisible to everyone who hasn't lived it. Software companies build project management tools for project managers. CRM platforms build pipelines for sales teams. AI companies build assistants for knowledge workers. Nobody builds for the principal of a small AEC firm — the person who is simultaneously the lead engineer, the business developer, the proposal writer, the client manager, the staff supervisor, and the operations director, all in the same day, often in the same hour.
Archi was built by someone who has been all of those things. Not as an experiment. Not as a side project. As the operating reality of running a multi-generational engineering practice where every system failure has a real cost — a delayed proposal, a missed follow-up, a client who didn't hear back, a staff member who couldn't get an answer without interrupting the principal mid-design.
The requirement wasn't written in a product spec. It was accumulated across 1,000 projects, three generations, and 75 years of a family that built things for a living and deserved better than spending their nights doing paperwork.
What You Don't See in the Demo
Building a product while running a firm.
Ford didn't just build a car. He built an assembly line — because he understood that solving the problem for one person was interesting, but solving it for an industry was the point. Richard had the same instinct from the beginning. He wasn't building a tool for himself. He was building the system he wished had existed for every principal who came before him.
That meant building it under real conditions — on a live firm, with real clients, real deadlines, and real consequences if something didn't work. There was no staging environment, no beta users, no tolerance for "we'll fix it in the next version." Every improvement had to work the first time it was used, because the firm was using it. That pressure produced something no software team operating from the outside ever could: a system built around how the work actually happens, not how someone imagined it does.
"The advantage I had that a software engineer wouldn't is that I already knew what the system needed to do — in granular detail, across 25 years of projects. I didn't have to figure out the problem. I just had to build the answer."
That is the difference between Richard's build and every generic "AI for AEC" product on the market. Those were built by software people who interviewed some architects. This was built by an engineer who has lived the problem across three generations and 1,000 projects — and who had the discipline to keep shipping until it was actually solved.
Every failure made the system better for the next firm that uses it. Every late-night fix to the proposal generator, every tweak to how voice memos become job cards, every iteration on how Archi briefs you in the morning — those are problems that won't happen to you, because they already happened to him.
The Morning It Worked
The first morning he didn't have to do anything.
It happened on a Wednesday. Richard woke up, opened WhatsApp, and Archi had already sent the follow-up to a client whose proposal had gone quiet, drafted the scope for the next morning's meeting from the job card, flagged a contractor invoice that was three days overdue, and distilled overnight emails into four action items — none requiring an immediate response.
He got to his desk at 8:30am. Designed until noon. No interruptions. No staff questions. No email triage. No spreadsheet updates. Just the work he became an engineer to do.
"That morning was the whole point. Not a chatbot. Not a dashboard. Not another login. A system that already handled it — so I could do what I was actually trained to do."
— Richard Clayborn, PE · Founder, Archi
Archi has run live at Clayborn Group every single day since. It has processed over 124,000 conversation and task entries. It has auto-generated more than 52,000 pages of company wiki from real firm operations — institutional knowledge that used to live only in Richard's head.
New staff ask Archi before they ask Richard. Proposals go out faster. Leads get followed up automatically. The firm handles more volume than it did with a full-time admin — and Richard works fewer evenings.
Why This Exists For You
You shouldn't have to build this yourself.
There are 200,000 small AEC and design firms in the United States. Nearly every principal is doing what Richard was doing at 11pm — running the firm and doing the work, simultaneously, at the cost of their evenings, their weekends, and the design work they started the firm to do.
The admin problem isn't going away on its own. Hiring an admin doesn't solve it — the admin still needs you as the source of truth. Generic software doesn't solve it — it creates another login nobody uses consistently. AI assistants don't solve it — they're assistants, not operators.
Archi is different because of what Richard had that no software team could replicate: 25 years of knowing exactly what needs to happen, across every project type, every client scenario, every staff dynamic — before the first line of code was written. The system isn't a best guess at what an AEC firm needs. It's the answer, refined across 393 live deployments, on a real firm, with real stakes.
"My grandfather built structures that are still standing. My father built practices that outlasted recessions. I built the system that lets the next generation of principals spend their time building — instead of administrating."
— Richard Clayborn, PE
Dyson's 5,127th prototype was the one that worked. Ford's assembly line wasn't built for one car — it was built so every car could be built right. Edison's lightbulb didn't just light his lab — it lit the world.
Archi's 393rd production deployment runs live. Every day. For a real firm. You don't get the failures. You get the system that survived them.
