Bryan Mahoney took the long way to a simpler answer

Bryan Mahoney had a finance degree, an investment banking job waiting on Wall Street, and a small business that was becoming inconveniently interesting. He had started it with a friend at McGill University. The original ambition was modest: make some money while studying. By graduation, the side project was making a persuasive argument for becoming the main event.

He stayed. The bank would have to manage without him. The company became Dynamo, a Montreal digital studio whose clients eventually included Glossier. That decision to postpone a conventional career led him into engineering leadership, consumer brands, and the business he now runs, Chord. It also established a recurring complication: his next job would often emerge from something he was already doing.

The banking job that could wait

Mahoney’s early internet work belonged to a period when making things online involved considerable improvisation. He has described using PowerPoint to create early web experiences. A presentation program was, apparently, available for duties beyond making a meeting longer. The work developed into websites, ecommerce, and eventually a studio serving venture-backed consumer startups.

There was no single leap from student enterprise to established agency. Dynamo grew over years, finding a place where design and development belonged together. That combination mattered for companies selling directly to customers: someone had to make the experience appealing, and someone had to make the purchase work. Keeping those conversations in the same room was a business proposition.

For Mahoney, the appeal of commerce extended beyond the mechanics. He would later describe the customer’s experience as the reason the technical work stayed interesting. A store can have a perfectly adequate shopping cart and still give people very little reason to care who is selling to them.

When the client becomes the office

In 2014, Emily Weiss and Henry Davis approached Dynamo about Glossier. The relationship began with the studio building for a client. Mahoney recalls the founders coming to Montreal for a design sprint, followed by the launch of Glossier.com that October. The arrangement also included helping the young company develop its own technical team.

Eventually, that assignment acquired a personal twist. Mahoney was helping recruit an engineering leader when the conversation turned to whether he might take the position. In 2015, he moved his family from Montreal to New York. The supplier became a colleague, responsible for building the engineering organization inside a growing company.

What Glossier wanted from technology challenged the habits of an experienced ecommerce builder. Mahoney knew storefronts and order systems. Weiss and Davis were talking about a channel that would bring customers into the conversation. The technical assignment included helping preserve that relationship as the business expanded.

By December 2018, he was presenting Glossier’s technology architecture as its CTO. The presentation paired a technical discussion with an idea about brands being shaped with their customers. Shared content systems, user accounts, transaction records, and behavioral data sat beneath an experience that shoppers encountered as a coherent whole. The engineering was doing work that the customer need never name.

A brand factory with a useful basement

In 2019, Mahoney and Davis started arfa. Their plan was to build multiple consumer brands on a shared platform. Each brand could have its own character while benefiting from common technology and accumulated knowledge. The former Glossier colleagues were returning to an earlier stage of company building, where they could design the foundations themselves.

Mahoney’s remit included engineering and design, but his account of the job also concerned culture, hiring, and the everyday experience of working together. He treated the company itself as something that needed deliberate construction. Software was one part of a larger operating environment, with people expected to live inside the choices its founders made.

The platform was first built for arfa’s own brands. That distinction gives Chord’s origin a practical texture: its founders were also its early users. They were making decisions about customer experience and data while operating businesses that depended on those decisions. Other companies began expressing interest in the technology.

By 2021, they were concentrating on Chord as a standalone business. A system designed to support their own portfolio had become something they could offer to other operators. The basement, to continue the architectural metaphor, had acquired paying visitors.

The customers kept pointing downstairs

Chord initially offered headless commerce: the customer-facing storefront could be separated from the systems managing the work behind it. Mahoney preferred the term API-first. The attraction was flexibility. A brand could build the experience it wanted while connecting specialist tools for different jobs.

It was an approach he knew well. Glossier’s early architecture had separated responsibilities in similar ways. In 2021, he described the freedom this could offer brands willing to take ownership of how their systems worked together. Chord also included a data platform, designed to make sense of information arriving from those connected tools.

The difficulty was adoption. Prospective customers wanted the data capabilities without replacing their commerce setup. Chord initially required the larger commitment. Mahoney later acknowledged how unreasonable that condition had become. A buyer was asking for a useful tool; the seller was attaching a renovation.

“I got tired of hearing no.”

Bryan Mahoney, on Chord’s change of direction

Around 2023, Chord became platform agnostic. Brands could keep their existing storefront and use its data infrastructure. The shift changed who could become a customer and what adopting the product required. It also put the company’s attention on a problem that would become more urgent as businesses tried to introduce generative AI.

An AI system needs a memory

On September 30, 2025, Mahoney announced Chord AI. His argument began with familiar frustrations: disconnected systems, difficult data, and reporting that demanded too much effort before anyone could decide what to do. The new offering combined a data engine with a commerce copilot.

The ambition was to let an operator ask questions in ordinary language, understand the answer, and act through the tools the business already used. Mahoney also emphasized controls that kept people involved and made responses possible to check. An answer that arrives quickly still needs to survive contact with the business.

In April 2026, Chord announced $7 million in new funding, led by Equal Ventures, with M13, Chingona Ventures, and CEAS Investments participating. The company described a context graph that records metrics, business rules, previous decisions, and constraints. Its intended customers included commerce businesses with annual revenue between $20 million and $1 billion.

The appeal of that memory is easy to understand. A figure can be accurate and still be misleading without the circumstances around it. A business has reasons for what it did last month. Mahoney’s current proposition asks software to retain more of those reasons, so the next question does not begin with everyone explaining the company again.

He remains interested in what automation might cost a brand as well as what it might save. Reflecting on Glossier, he has worried that an enthusiasm for agents could weaken the connection between customer, product, and company. His technical career has given him plenty of reasons to appreciate efficiency. It has also given him reasons to ask what the efficient experience feels like.

Old colleagues, new microphones

Those questions now have another outlet. Mahoney hosts Brilliant Commerce, interviewing operators about the work behind consumer businesses. The conversations regularly cross the supposed boundary between brand and technology. Guests discuss the decisions that customers eventually experience as a product, a message, or a visit to a store.

With former Glossier marketing chief Ali Weiss, he revisited their introduction at Camp Glossier in 2015. Their discussion moved through customer understanding, marketing, and the challenge of measuring an experience. His interest is recognizably that of a technical colleague who remembers what happened when a marketing idea met the servers.

In September 2026, he interviewed Jenna Holcombe, a former Dynamo colleague and now a Centra co-founder. When she credited the agency’s early direction to him, he pushed credit back toward the group. They had been curious together. It is a small conversational gesture, but it gives the account of Dynamo more people than a founder biography usually allows.

He is also capable of making the sales pitch briefly ridiculous. Discussing AI with Summersalt co-founder Lori Coulter, he joked about his obligations as someone running an AI company. The humor works because the audience already knows his commercial interest. Admitting it clears a little space for a more interesting conversation.

A little room to leave the office

Mahoney’s public reflections sometimes leave the product behind. After a skiing trip to Chile with his daughter, he described the unfamiliar experience of giving his team more room while he was away. He still checked in morning and evening. The progress was in trusting colleagues to contact him when they needed him.

His daughter, he wrote, had heard enough of his calls to joke that she could sell Chord herself. That may be the least expensive sales training program a founder has devised. The trip gave his account of company building another measure: whether the business could keep moving while he was paying attention to someone beside him.

His career began by allowing a small company more time than he had planned. It has continued through clients, colleagues, and customers who changed the work in front of him. At Chord, the question remains practical: what does someone need next, and how much of the machinery can he help get out of their way?