How Dmitry Kushnikov Scaled Manychat by Treating Operations Like Software Architecture

A profile in Business Insider Africa traces how Dmitry Kushnikov climbed from backend engineer to COO at Manychat — the customer engagement platform now serving more than a million businesses across 170 countries, running over a billion customer conversations a year, and employing more than 400 people. The piece is less a founder origin story and more a case study in how one operator learned to design systems instead of write code. For builders scaling past their first hundred people, that distinction is where everything gets harder.

The promotion arc is actually an architecture arc

Kushnikov joined in the fall of 2016 as a backend engineer, when the permanent team was the two co-founders and a small group of developers. Over the next several years he stepped into backend team lead, Head of Engineering, CTO, and eventually COO — a path that looks like a ladder but functions like a widening of scope. His own framing is blunt: "My job is building systems. A company is a system as well."

That reframe is the through-line. Early on, the systems were code, architecture, and product components. As the company expanded, the same craft had to cover engineering teams, executive leadership, and company-wide operations. The skill didn't switch tracks; the object being engineered just grew.

What "managing the system" actually looks like

Kushnikov's early signature at Manychat was Flow Builder, the visual tool that lets businesses design automated messaging workflows without writing code. The idea came from the founders; he ran project management and the first implementation. Since launch, businesses have built more than 270 million automations in it — and the platform now spans Instagram, WhatsApp, Facebook Messenger, Telegram, and TikTok.

Look at how he describes his role on the Instagram and WhatsApp integrations, which by 2026 had more than a million Instagram accounts connected to the platform: "My job was to figure out how to organize work around it and ensure that it happens." Notice what's missing. He wasn't writing the integration. He was the person accountable for the team that did. He told the publication he manages the system around people — goals, constraints, decision rights — and that the one thing you can't delegate is responsibility for the people themselves.

That distinction matters for your org chart. If your senior people are still doing tasks rather than designing the conditions under which tasks get done well, you don't have a leadership bench. You have a bottleneck wearing a better title.

The $140M moment and what it actually bought

In April 2025, Manychat raised $140 million from Summit Partners to expand internationally and accelerate AI-powered product development. On paper that's a funding story. In practice it's a stress test of exactly the system Kushnikov describes — whether the org can absorb capital and grow into a different shape without the seams showing. Watch whether their headcount discipline, decision rights, and cross-functional handoffs hold up as the 400-plus team expands into new markets.

So here's the question worth sitting with tonight: are you still doing the work yourself, or are you already designing the conditions under which the work gets done? Your answer tells you whether you're leading a company or running a very expensive to-do list.