The Studio Ahead

The Arcfluence Podcast

The Arcfluence Podcast has run for two and a half years. Seventy episodes, more than a hundred pieces of published content, and a slowly widening conversation with the architects, builders, investors, and operators who shape Central Ohio. For this one, the hosts step out of the host seats. Danny Porter, the firm’s Chief Digital Officer, interviews co-founders Nick Karakaian and Paul Fatkins about how the practice has actually been built, where emerging technologies fit, what the next stretch of work looks like, and the studio they’re about to move into.

Why the Medium

Podcasts are one of the better communication mediums of 2026, Danny argues on the show — a deep dive instead of a thirty-second snippet, an actual conversation instead of a swipe. Nick agrees, but his entry point is a different one: the episodes with people he grew up near are the ones that stick. Bill Griffith — “Mr. Griffith” to Paul for forty years — appeared on an early episode and gave the show a snapshot of architecture practiced from pencil-and-paper through the digital era. Dean Mister of Kent State did something similar from the academic side. The point of the medium, for the team, is that those conversations don’t exist on social media.

That history matters because architecture as a profession is younger than people assume. Architects didn’t exist as licensed specialists for most of the discipline’s history — there were master builders, who were part contractor, part project manager, part designer, part the person standing on site when the dome needed to be installed. Paul tells the Brunelleschi story on the show: Florence Cathedral, Brunelleschi and Ghiberti feuding over the dome, Brunelleschi calling in sick on install day so that Ghiberti would expose his incompetence in front of the commission. The next morning, Brunelleschi recovered. The team finds it useful to remember that the field has always been like that.

Designing Around Yourself

The most quoted line in the episode is Nick’s, and it lands because it’s literal. When Nick designs a corridor, he is walking down it. When he places a window, he is standing in front of it. The new generation of visualization tools haven’t changed that — they’ve made the thing in his head shareable. What used to live only in a sketchbook can be rendered for a client in an afternoon. What used to take a week of fee budget to test can now be tested in a session.

That speed changes the work the firm can take. A client who could not afford an iterative-design conversation three years ago can have one today. The visualization stack didn’t make design better — it made better design economically reachable for the kind of client who used to have to take “trust the drawing” on faith.

The Farm, and Time Gained

Paul came up through a 200-person Chicago firm. His vantage on the change in the tools is twenty years long. He describes “the farm” — the server stack the Chicago office used for distributed rendering, individual machines named after farm animals (a cow, a chicken, a goat), all chained together to render a single image that today his laptop would produce in a fraction of the time. He remembers an eight-hour Matterport scan of an eight-thousand-square-foot home in New Albany; the same job now takes an hour or two with a current-generation scanner.

The frame Paul uses for all of it is time. The biggest thing the new tools give a small firm, he says, is hours back — hours that go into thinking about how a room is entered, how the spaces stack, what the client will actually feel walking through the door. Not new ideas, in other words. Time to be thoughtful about the ones you already have.

Tools Augment Experts

On the question of where the new tools fit, the three of them converge from different directions. Paul’s frame is that they level the playing field — a small firm with the right stack can produce deliverables that used to require a much bigger firm, provided the people running the tools know what they’re looking at. Without the expertise, the tools produce a confident-looking wrong answer faster than ever before. With the expertise, they produce time.

Danny pushes a related frame about the prediction models specifically: a large language model is not an oracle. You don’t ask it a question it doesn’t already know and get truth back. What it’s good at is mapping a space — showing you the options, surfacing the shape of a problem, drawing a chart of a domain. It’s a cartographer. The judgment about which option is right still belongs to the person at the wheel.

The argument has consequences for how a firm in 2026 hires, structures itself, and competes. Power is the real constraint on these systems’ scale, Nick observes — the model itself is essentially unlimited as long as the grid is there to power it. Local models running on a laptop now match what was state of the art two years ago, which makes a small firm’s privacy and ownership posture markedly easier than it used to be. None of that changes the underlying point: tools are leverage, not substitutes.

Different Strengths

The episode spends a long stretch on the team itself. Nick and Paul have known each other for twenty years, and they describe themselves the way most long partnerships eventually do — as complements. Nick is the one who dreams first and refines second; he wants to know that a project pencils financially, socially, culturally, and aesthetically, all four, every time. He says it openly: he is the risk-taker. He throws ideas at the wall, some of which are not feasible for reasons Paul will name out loud.

Paul’s pace on the page is slow before it is fast. He takes time to think a problem through and then presents one or two carefully developed options, rather than throwing many. He is the partner most likely to flag funding constraints early. He is the one who calls the dance with consultants, contractors, and the city — what he calls the part of the job nobody teaches in school. Between them, the projects find a shape neither would have arrived at alone.

There is also a running joke on the show that they have blind spots about each other, and that the blind spots are part of the strength. Mid-conversation, Nick calls Paul one of the most well-rounded designers he has worked with. Paul interrupts: “yeah, but I have blind spots.” Nick: “of course you do, buddy.” It is the most accurate picture of the partnership on tape.

The Studio Ahead

Arcfluence is in contract on a dedicated studio — the first time the firm has had a single home base for design, client meetings, model and material reviews, and the podcast. Nick estimates the space comfortably holds fifteen to eighteen people. The team intends to fill it, supplemented by a small remote group, with a tilt toward keeping the working core in Central Ohio.

The forward agenda goes further than the office. Nick wants the firm to take on its own development work, drawing on his rental and investment portfolio so that Arcfluence can fund some of its own projects rather than only design for other people’s. Modular housing for disaster relief is on the table. Public-sector work is on the table.

The most concrete next stretch is a content series called Mapping Central Ohio — long-form pieces and podcast conversations walking through the architecture, identity, and culture of the neighborhoods most people are deciding among when they consider Columbus. German Village launched the series. Izzy, a local realtor who has worked alongside the firm on a number of projects, is the next conversation on the schedule. The thread the team keeps coming back to is that the neighborhoods Columbus already has — with their schools, their corner blocks, their organic culture — can carry most of the ambition that other cities try to manufacture from scratch.

Advice for Young People

Toward the end of the episode, Danny puts the question to both of them: what would you tell a twenty-year-old considering this field in 2026? Nick’s answer is about passion, and underneath the passion, about relationships. He recently advised a young person debating an architecture master’s to travel first, see the world, build a network of people, and come back to the question of the degree when they could feel its weight. Architecture, he points out, lets you change someone’s life by designing their house and lets you change the world on a larger scale by shaping how culture lives in space. That is not a small thing to spend a career on. If it doesn’t light you up, do something else.

Paul’s answer is about persistence and breadth. Don’t give up, he says — and remember that “architecture” is connected to a wider field than most people realize. Construction. Real estate. Planning. Development. Investment. He cites a client of the firm who studied as a planner, took a certification, and now works for a developer in an investment group. The work he does is one hundred percent connected to his field of study. He simply found his own path inside it. That, Paul argues, is the move.

Listen

The full episode is available wherever you listen to podcasts. You can find more conversations on the Arcfluence Podcast, and the team at arcfluence.com.