Background
The Stepstone Group is one of Europe's largest job platforms, helping companies fill roles and helping people find work in more than a dozen countries. Behind that simple promise sits a serious data operation: millions of jobs published every month, thousands of employer accounts to manage, and a tech team that has to keep all of it moving. n8n is part of that engine, parsing two to three million job-related data documents every month for Stepstone's marketplace, alongside the 700+ internal workflows the company now runs in production.
n8n arrived at Stepstone in 2021 the way a lot of good tools arrive at companies: through one curious engineer. Luka Pilic, Tech Lead of Marketplace Management, started using it privately, then introduced it to his team. "The adoption was gradual, but once the team understood the potential, they became highly engaged, leading to a continuous expansion of our automation capabilities." For nearly four years, that was enough. Luka's team ran on the Community Edition, building hundreds of workflows that quietly handled data routing, internal reporting, and operational fixes for other teams across the business.
By the start of 2025, the workload had outgrown what one shared Community instance could safely carry. Credentials were being shared across users, workflow ownership was getting muddled, execution monitoring was thin, and a single master account was no longer a viable model. Stepstone moved to n8n Enterprise.
Challenge
Two challenges drove the move to Enterprise and the company-wide rollout that followed.
The first was infrastructural. As Luka explained, "While the Community Edition is effective for initial use, it quickly becomes restrictive under a heavy workload. Once we surpassed a certain operational threshold, we required advanced capabilities like proper credential and workflow permissions, and dedicated execution monitoring, as relying on a single shared master account quickly became unsustainable." With 700+ active workflows and a growing user base, Stepstone needed proper credential management, role-based access, version control, and a separate environment for the IT security team, which handles GDPR-regulated employee data and shouldn't be visible to the main instance's admins.
The second challenge was cultural. Stepstone has roughly 3,000 employees and almost a thousand developers spread across the world. The company wanted to enable everyone (not just engineers) to automate parts of their own work. But without a structured rollout, an enterprise-wide n8n deployment risked turning into a graveyard of half-built workflows and frustrated users.
Solution
Stepstone's Enterprise rollout has two halves: the platform plumbing, and the human onboarding.
On the platform side, the team is wiring up the things that only become possible at Enterprise scale. SSO via Okta is going in. An external secret store means credentials don't have to be shared user by user. Role-based access lets different teams operate in their own spaces. The IT security team has spun up its own instance for sensitive workflows that the main admins shouldn't have visibility into. "The Enterprise edition provides exceptional value across numerous areas," Luka said. The point wasn't to build a business case for it. "The documented successes and rapid deployments achieved with n8n effectively justified the transition. There was a consensus across the organization that this was a necessary tool, and a formal business case for the Enterprise license was not required."
On the onboarding side, Luka's team is starting with a marketing pilot of about ten people, who are running through a structured course on data literacy and automation before getting an account. To lower the barrier even further, Luka built a chatbot that runs inside the n8n chat interface and is connected to the n8n MCP server, plus an internal MCP for Stepstone's Confluence and Jira. A user opens it, says which team they're on, describes what they want to automate in plain language, and the bot walks them through the feasibility step by step. It asks the kind of questions a senior engineer would ask. It scores how realistic the idea is. If the score is high, it draws a diagram of how the workflow should be built and lists the steps.
The next iteration uses Claude as the underlying model and the n8n MCP to scaffold the workflow itself. Not perfect, by design. "The resulting workflow is intentionally not perfect, as this requires the user to engage with and learn the underlying principles of automation, providing them with a valuable foundation to build upon."
The reason any of this gets prioritised is that the operational wins keep stacking up and selling the rollout for Luka. A customer service team came to him recently with a recurring problem: 60 to 70 contract mappings were piling up in their system every day after a large reseller restructured their data feed, and each one took two to three minutes of manual work. Luka built them a workflow over a few hours. The full daily batch now takes around 20 seconds. Soon after, the same team needed to remove a discontinued product from contract entries across 20 of their biggest customers (about 4,500 entries). "We received feedback indicating the workflow saved the team the equivalent of two full working days for five full-time employees."
The story Luka tells most often, though, is about an internal team that had spent two months chasing engineers for access to an external API. "The team had spent two months attempting to gain API access through internal channels. When they came to me, they were able to log in, provide the keys, and retrieve the necessary data instantly. That immediate success is often the 'aha moment' when users realize the efficiency they gain by having direct automation capabilities."
Results
Since moving to Enterprise at the start of 2025, Stepstone has crossed 700 active workflows, more than three times the volume from a year earlier. The IT security team is operating its own instance for sensitive work. The marketing pilot is in motion. The chatbot is in testing with the first cohort.
The operational wins are concrete: hours of daily customer-service work compressed into 20 seconds, multi-day cleanup projects reduced to half an hour, and product teams getting answers in minutes instead of weeks. "Upon logging in during our meeting, they instantly provided the API keys, and the data was immediately accessible," Luka recalled. "That's where people get their aha moments."
The bigger result is harder to put a number on, and Luka was careful about how he described it. "The tool effectively democratizes automation across the organization. However, like any self-service model, its success requires active participation and user education to realize the full benefits." He went on: "It also introduces a fundamental shift in problem-solving. As we operate under OKRs with ambitious top-level goals, integrating automation into our toolkit enables us to break down complex objectives into manageable workflows and sub-workflows. This reframing prevents the larger goal from appearing insurmountable, allowing it to be achieved through a connected series of smaller, executable tasks."
That mindset shift is what Luka wants to spread across Stepstone, and it's also how he describes the way automation actually takes hold inside a 3,000-person company. "The adoption process begins with early adopters delivering demonstrable value. As others observe these successes, they naturally become curious and ask, 'How was that accomplished? Why isn't that available to us?' This curiosity drives the demand for more comprehensive onboarding, creating a powerful, organic cycle for growth based on tangible utility."
That is what is happening at Stepstone right now. n8n started with one engineer and a private side project. Four years later, it is on its way to becoming part of how the whole company works.
"The documented successes and rapid deployments achieved with n8n effectively justified the transition from Community to Enterprise. There was a consensus across the organization that this was a necessary tool, and a formal business case for the Enterprise license was not required."