Monday.com

Monday.com's transformation story begins not with a eureka moment, but with a humbling realization. When Daniel Areya joined the company roughly 8.5 years ago as Chief Product and Technology Officer, the team was small—around 30-40 people. They were executing incredibly hard, shipping weekly updates packed with features. By their own measures, they felt fantastic about the pace of work. Then one morning, everything changed.

"I remember coming to the office and just looking at one of our competitors," Daniel recalls. Monday's core offering was its boards—essentially dynamic tables with different column types that could capture various data formats. The company had five column types, each taking roughly four months to develop. "That morning, we saw that one of our main competitors launched 30 new columns."

The initial reaction was shock and disbelief. But rather than spiral into panic, the founders and leadership—Roy, Alain, Daniel, and tech lead Tal—went outside the office to think differently. They didn't ask "how do we copy them?" Instead, they asked a more fundamental question: "What would it take to do this ourselves?"

The team could have calculated the obvious math: 30 columns × 4 months per column = 120 months of work. Impossible. Instead, they did something counterintuitive. They set an ambitious goal so audacious it forced a complete rethinking: build 25 columns in one month.

"This was the biggest favor our competitors could ask for," Daniel explains. "They showed us it's possible. Now we need to think how."

The breakthrough came from recognizing that the problem wasn't with individual developers' speed—it was architectural. The team asked: What if we stop treating each column as a custom engineering project and instead build a framework where columns are standardized, predictable building blocks?

Tal designed infrastructure that defined what every column needed: export to Excel, filtering, sorting, and other shared capabilities. Suddenly, the work shifted from "build a formula column from scratch" to "implement the formula column's unique logic within our framework."

To prove it was possible, Daniel himself coded one column in a single night. Two weeks later, the team ran a hackathon where each developer owned one column and implemented it in one day. "If you think about it, from four months to one day—it's mind-blowing," Daniel recalls. A month and a half after the hackathon started, Monday had shipped 30 columns in production.

While the article doesn't detail early customer acquisition, it reveals Monday's customer base today: 250,000 paying companies across 200+ business verticals, from aerospace engineering to real estate to finance. The platform's breadth is a testament to solving a universal problem—coordinating work.

What's striking is Monday's focus on non-technical users. Daniel emphasizes: "70% of Monday's customers are non-tech." This reveals a deliberate positioning: not a tool for engineers, but a platform for humans everywhere who need to organize, track, and collaborate on work.

The columns breakthrough unlocked a mindset shift. If the team could rethink architecture to ship 30 columns in six weeks, what else could they reimagine? The same pattern repeated with dashboards, widgets, and automations. Each time, ambitious goals forced architectural thinking instead of brute-force execution.

But the deeper lesson wasn't just about speed—it was about impact. Daniel became obsessed with a question: "What does impact mean?" The company realized they were measuring activity (features shipped, updates sent) rather than outcomes (did customers achieve their goals?).

"A great PM is someone relentless until they get this impact and validate it's in place," Daniel says. The shift was seismic. PMs stopped asking "What should we build?" and started asking "What problem are we solving, and how will we know we solved it?"

This came to a head with Monday's AI Blocks launch. The team built no-code AI actions—hugely valuable for non-technical users. Metrics showed great engagement among those who discovered the feature. But when they looked at raw adoption across all 250,000 customers, only a few thousand were using it.

Instead of celebrating the feature, the team dug deeper. They discovered the blocker: terms-of-service changes needed before rolling out to everyone. Those changes were scheduled for "next quarter."

"What? No," the team said. "This is actually what's most impactful. We need to do it now." Two weeks later, 98% of Monday's customer base had access. Impact transformed from a good metric to the transformative metric.

The most counterintuitive lesson: radical transparency. Before going public, Monday displayed real-time company metrics on dashboards—paying accounts, signups, churn—visible to everyone, including candidates interviewing for jobs. Conventional wisdom said this would demoralize teams when metrics dipped. The opposite happened. "Instead of demoralizing people," Daniel explains, "it gives them a sense of deep partnership."

Today, even as a public company, Monday maintains this culture through an internal app called Monday Morning, where employees see real-time metrics. Product managers sign 10b5 trading plans so they can view financial data without timing stock sales around news—because the numbers matter more than stock gains.

Monday.com announced it crossed $1 billion in ARR, having grown from $4 million ARR when Daniel joined. The company scaled from 30-40 people to 2,500 employees. More importantly, it transformed from a single project-management platform into a multi-product suite.

That multi-product pivot itself exemplified Monday's risk-taking philosophy. Rather than launch one new product (CRM) and test it, the company announced five simultaneously—Sales CRM, Marketing, Dev, Finance, and others. Everyone said it would confuse users, fragment go-to-market, and tank conversion. Some products (Sales CRM) exceeded original Monday's growth rate. Others were folded back into the main platform. But the move fundamentally shifted how the market perceived Monday and how the company perceived itself.

Daniel's closing insight encapsulates the journey: "Not taking bold risks, not making bold moves, is a risk in itself. Many times people want inertia and incremental value. But if you want to make leaps, you need to let go of things that were successful in the past." For a company that built itself on shipping columns in days instead of months, that philosophy isn't abstract—it's the story of how they won.