How Motif Is Rebuilding Architectural Design Software From the Ground Up — and the GTM Lessons That Almost Didn't Make It

There's a version of Motif's story where Amar Hanspal — nearly 30 years at Autodesk, deep relationships across the architecture and construction world — launches his company, calls his enterprise contacts, and lands a handful of large firms as anchor customers.

That version didn't happen.

In this recent episode of BUILDERS, Amar, CEO of Motif, walked through the real version: the wrong ICP, the premature sales hires, the pricing that slowed adoption before it could start, and six months of foundational work done before the company even had a name. It's a more useful story.

The ICP You Know Is Not Always the ICP You Need

Motif is building a browser-based, AI-native design system for architects, engineers, and general contractors. The market Amar is going after is large — building design software has been dominated by legacy desktop tools for decades — and his instinct was to start with the firms he knew best.

"Many of the architecture firms I knew were the very large ones," he explains. "They build amazing buildings everywhere, but their adoption process is a little more careful."

That carefulness has a practical cost at the enterprise level: security reviews, privacy requirements, lengthy procurement cycles. For an early-stage product, selling to those firms doesn't just consume time — it redirects your roadmap toward their requirements instead of your growth loop.

The shift was to mid-sized architecture firms. Not a consolation prize — a deliberate recalibration toward the customer who could give real signal fastest. "The iteration we had to make was to find our way to the medium sized architecture firms where they tend to be a little bit more ready to say, hey, I think this thing is still raw but great, I'll go with it."

That recalibration took roughly six months — April to October of last year. Part of what made it take that long is structural to the industry: architecture firms evaluate new tooling when they switch projects, and building projects run on two-to-three year cycles. Iteration has to be timed to when buying decisions actually happen, not when you're ready to sell.

Why "Better" Doesn't Sell in Entrenched Markets

The instinct for most founders displacing legacy software is to lead with improvement: faster, cleaner, more intuitive. Amar's view is that this framing is a trap.

When you position against an existing tool, you're asking the buyer to weigh incremental gains against real switching costs — not just the product, but the people they've trained on it, the workflows they've built around it. "Sometimes not just the product, but they've got other people they've taught how to use this product. Like it's a bigger change thing."

His alternative: find the thing they cannot do at all today, and lead with that.

"You've got to find something they're not able to do right now... when you find the net new thing they can do, that's the way to drive change."

For Motif, this took two forms. The first is AI-powered rendering — architects can generate a photorealistic building image without touching a separate tool. The second is something structurally simpler but equally significant: a shareable link.

"You and I can share a YouTube link and you can send me, hey, take a look at this TikTok video. Like, you could never do that with architectural design to say, hey, take a look at this atrium I just created. What do you think of it?"

Neither replaced an existing workflow. Both created new ones, which means there's no switching cost conversation. The mechanism matters: you enter through the net-new capability, then expand into the workflows they were previously handling elsewhere.

The PLG Commitment Problem

Motif's go-to-market is product-led growth — a deliberate fit for a market of small to medium-sized firms that discover and adopt tools the way they do Notion or Slack. But Amar is direct about not fully committing to it from the start.

"I think right from the get go I was like, hey, listen, let's just staff up the team and let's build maybe account execs a little too soon."

The downstream effect of that decision is worth understanding precisely. A sales team hired before the self-serve loop works will naturally chase the deals it can close — which at an early stage means larger accounts. Larger accounts pull product priorities toward enterprise requirements. Enterprise requirements are the opposite of what a PLG motion needs to mature.

"If you had gone PLG first right from the get go and only PLG, I think [it] would have had us accelerate."

Pricing compounded the problem. Motif launched with prices that reflected their confidence in the product — and created friction at exactly the moment they needed adoption. "We were very optimistic in the early days of high prices... we should have kept the first step really simple for someone to take."

The principle is precise: in a PLG model, entry pricing is an adoption variable, not a revenue variable. Optimizing for the wrong thing at the wrong stage costs time that doesn't come back.

Building a Team That Can Actually Execute PLG

Motif has a hard internal cap: AEC — architecture, engineering, and construction — domain experts make up no more than one-third of the company. The rest are deliberately hired from outside the industry.

"PLG is not an AEC thing. PLG got perfected in other industries. So you need to bring in people who may have worked at Figma or Notion and you know, those people really teach us."

The logic is specific, not generic. If your entire team comes from the industry you're disrupting, you default to that industry's assumptions — including its assumptions about how software gets bought and adopted. The fastest path to executing a motion you've never run before is to hire people who have already run it somewhere else, then mix that DNA with the domain knowledge you need.

The Entry Wedge Framework

Building a comprehensive design system means an enormous product surface area. The risk for any founder in that position is picking an entry point that generates early traction but sits off the critical path to the full vision — a detour that looks like progress until you have to reverse it.

Motif spent six months before founding the company working through this problem with design partners. The insight Amar surfaces about those conversations is worth holding onto: asking customers what they want doesn't work.

"They never answer the question directly like in the language that we could translate to the rest of the team."

What worked was asking where they were spending time and money, and where they had no entrenched loyalty to existing tools — the areas with "no sort of religion," as Amar puts it, about the current stack. That surfaced the zones where experimentation felt low-risk to the customer.

The output was effectively a two-by-two: customer adoption readiness on one axis, engineering feasibility on the other. The wedge had to sit at the intersection — and critically, it had to be on the road to the full product, not adjacent to it.

"The first step we took was a path to the ultimate destination... it wasn't like we're off here in the cul de sac just trying to solve this one problem and then we've got to get back on the main road."

That process concluded in 2022, before Motif was formally founded.

The long-term vision Amar is building toward is equally specific: free architects from the administrative grind of compliance documents and quality control checks, and return the creative work to the center of the profession. "Our [goal] is to free them from the drudgery and liberate them to do the creative work."

The GTM decisions made in the first two years — who to sell to, how to price, when to hire sales, where to start — will determine whether that vision is reachable. Motif's early chapters are a useful map of where those decisions go wrong, and what it takes to correct them.

Listen to the full conversation with Amar Hanspal on BUILDERS.