under<\/a> pressure, and the patterns of interaction that persist even when no one is watching.<\/p>\nIdentifying and codifying that real culture requires a different kind of work. It means spending time with people across the organisation, not to tell them what the culture should be, but to understand what they already care about. Ribreau says she has been asking fundamental questions: Why do people join Safe Software? Why do they stay after several years? What are the behaviours that people instinctively recognise as either fitting or not fitting? What are the core reasons that the organisation has been able to deliver for clients in ways that competitors cannot? The answers to these questions, she believes, form the raw material of a culture that can survive hypergrowth.<\/p>\n
The collaboration imperative<\/h3>\n
One element that Ribreau identified early in this process was collaboration. That may sound like a generic value—every company claims to value collaboration—but at Safe Software it has a specific and technical meaning. The platform’s complexity means that no single individual can own an entire solution. Problems cut across data engineering, domain expertise, customer context, and product architecture. The ability to bring people together from different functional areas and have them productively solve a problem together is not a nice-to-have; it is the central operational capability on which the business depends.<\/p>\n
The challenge of scale is that collaboration, when left to informal networks, tends to fray as headcount grows. The people who used to know whom to call for a given problem become harder to find. The trust that enabled quick, low-friction collaboration across teams gets diluted by the sheer number of new faces. Ribreau’s focus on codifying the underlying culture is, in part, an effort to preserve this collaborative capability by making it explicit—not by forcing it through process, but by articulating the behaviours that make it work and ensuring that those behaviours are recognised, modelled, and taught.<\/p>\n
What happens when culture evolves too fast<\/h2>\n
There is a well-documented pattern in hypergrowth technology companies: rapid hiring leads to a dilution of cultural norms, which leads to friction, which leads to a decline in execution speed, which leads to missed targets, which leads to leadership changes, which leads to a new set of cultural interventions. The pattern repeats because each phase of growth requires a different cultural equilibrium, and few organisations are equipped to manage those transitions deliberately. Ribreau’s approach represents an attempt to break that cycle by treating culture not as a static asset to be protected but as a living system to be guided.<\/p>\n
The distinction is subtle but important. A static view of culture assumes that the values and behaviours that worked at fifty employees will also work at five hundred. That assumption is almost always wrong. A dynamic view, by contrast, recognises that the culture must evolve as the organisation grows, but that the evolution should be intentional rather than accidental. The question is not whether the culture will change, but whether the leadership team understands what is changing and has a coherent view of what the culture needs to become.<\/p>\n
Ribreau’s emphasis on listening rather than dictating is a direct response to this reality. In many organisations, the cultural conversation is top-down: leadership decides what the values are and communicates them downward. The risk is that this approach produces values that are disconnected from the lived experience of the people doing the work, especially in a company as technically specialised as Safe Software. By spending time identifying the behaviours that people already care about, Ribreau is trying to build a cultural framework that is grounded in operational reality rather than abstract aspiration.<\/p>\n
The hiring and onboarding bottleneck<\/h3>\n
Hypergrowth places enormous pressure on hiring and onboarding processes. When a company needs to double its headcount in a short period, the temptation is to prioritise speed over cultural fit. Candidates who would previously have been passed over are brought in to fill critical gaps. The onboarding process, which might have involved weeks of immersion in the company’s way of working, gets compressed into a few days of compliance training and a Slack channel. New hires are expected to figure out the culture on their own, often by imitating the behaviours they observe in their immediate team, which may or may not reflect the broader organisational norms.<\/p>\n
The result is a fragmentation of culture. Different teams develop different subcultures, and the coherence that once made the organisation effective begins to erode. Ribreau’s focus on codifying the underlying culture is, in this context, a response to the reality that informal cultural transmission breaks down at scale. If the culture cannot be transmitted through storytelling and osmosis, it must be made explicit in a way that preserves its essential character without reducing it to a list of platitudes.<\/p>\n
This is a delicate line to walk. Codification, done poorly, can produce a bureaucracy of values that feels hollow or performative. Done well, it can provide a common language for discussing behaviour and a shared reference point for decision-making. Ribreau’s approach appears to lean heavily on the idea that the codification must emerge from the organisation itself, not from a leadership retreat, and that it must focus on behaviours rather than slogans.<\/p>\n
Why the $100 million to $250 million range is especially treacherous<\/h2>\n
The revenue range that Safe Software is navigating is notable for the specific kind of pressure it creates. At the $100 million mark, a company has typically found product-market fit, built a repeatable sales motion, and established a core team that has been together for several years. The culture at this stage is often strong and distinctive, because it has been formed by a relatively small group of people who have been through a lot together. The $250 million mark, by contrast, often requires a fundamentally different organisational structure. The founder-led, flat, informal style that worked at $100 million can become a bottleneck at $250 million. New layers of management are added. Specialised functions are created. The company becomes more process-driven, and the original culture can feel like it is being lost.<\/p>\n
Ribreau’s insight is that the transition cannot be managed by simply defending the old culture or by abandoning it entirely. The former approach leads to stagnation; the latter leads to an organisation that no longer knows what it stands for. The only viable path is to evolve the culture deliberately, preserving the core elements that drive the business while letting go of aspects that no longer serve the organisation’s scale and ambitions. That requires a clear understanding of what those core elements are, which is exactly what Ribreau has been working to identify through her listening process.<\/p>\n
The role of leadership in cultural evolution<\/h3>\n
The question of who owns culture during hypergrowth is often debated. Some argue that culture is the responsibility of every employee. Others argue that it is ultimately the CEO’s job. Ribreau’s actions suggest a more nuanced view: leadership sets the conditions for cultural evolution, but the culture itself belongs to the organisation. The role of the leader is to create the space for the underlying culture to be articulated, to provide the resources for it to be codified, and to model the behaviours that the organisation wants to preserve. But the culture cannot be imposed from the top, especially in a company where deep technical expertise and collaborative problem-solving are central to the business model. The people who do the work must recognise themselves in the cultural framework that emerges.<\/p>\n
That recognition is not automatic. It requires a process of discovery and dialogue that takes time, and time is exactly what is in shortest supply during hypergrowth. Ribreau’s willingness to slow down in order to listen is therefore a deliberate strategic choice, one that runs counter to the accelerationist logic that often dominates high-growth technology companies. It is a bet that the long-term health of the business depends on getting the cultural foundations right, even if that means sacrificing some short-term velocity.<\/p>\n
Measuring what matters in culture<\/h3>\n
One of the difficulties in managing culture during hypergrowth is that culture is notoriously difficult to measure. Revenue, headcount, customer acquisition cost, and churn rate are all quantifiable. Culture often shows up only in lagging indicators: turnover, employee engagement scores, or the difficulty of hiring. By the time those indicators deteriorate, the cultural damage has already been done. Ribreau’s emphasis on identifying and codifying the underlying culture can be understood as an attempt to create leading indicators—to understand the cultural dynamics well enough to intervene before they become problems.<\/p>\n
The specific indicators she is tracking are behavioural rather than numerical. Are new hires quickly absorbing the collaborative norms that define the organisation? Are long-tenured employees able to articulate why they stay? Do teams from different functional areas continue to solve problems together effectively as the organisation grows? These are qualitative questions, but they are also operational questions. The answers determine whether the company can continue to deliver the complex, cross-functional solutions that its clients depend on.<\/p>\n
The broader lesson for technology companies scaling rapidly<\/h2>\n
Safe Software’s experience offers a case study in the kind of cultural intentionality that is required to navigate hypergrowth successfully. The patterns Ribreau is grappling with are not unique to her organisation. Every technology company that scales past the $100 million threshold faces the same fundamental tension between the culture that made it successful and the organisational structures required to sustain that success at a larger scale. The companies that navigate this tension successfully tend to be those that treat culture as a dynamic system requiring active management, rather than a static inheritance to be protected.<\/p>\n
The specific strategies Ribreau is employing—slowing down to listen, identifying underlying behaviours rather than aspirational values, focusing on the operational importance of collaboration, and codifying the real culture in a way that can survive rapid hiring—are applicable well beyond Safe Software. They represent a philosophy of cultural management that is grounded in organisational reality rather than corporate branding. In an environment where many technology companies talk about culture but few manage it with rigour, Ribreau’s approach stands out for its willingness to engage with the complexity and ambiguity of the task.<\/p>\n
The transition from $100 million to $250 million is, for most technology companies, the moment when the original culture either becomes a foundation for sustainable growth or a constraint that holds the organisation back. Safe Software is still in the middle of that transition, and the outcome is not yet determined. But the deliberate, reflective approach that Ribreau has taken suggests a leadership team that understands what is at stake. In an industry that often celebrates speed above all else, the decision to slow down in order to preserve what matters may turn out to be the fastest path to long-term success.<\/p>\n","protected":false},"excerpt":{"rendered":"
The period when a company scales from $100 million to $250 million in revenue is often described as the most perilous transition in the lifecycle of a technology business. It is a phase in which hiring accelerates dramatically, processes that once worked at a smaller scale begin to buckle, and the informal, word-of-mouth culture that […]<\/p>\n","protected":false},"author":11,"featured_media":100736,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/100734.png","fifu_image_alt":"Safe Software\u2019s culture faces its toughest test amid hypergrowth","footnotes":""},"categories":[40791],"tags":[],"class_list":["post-100734","post","type-post","status-publish","format-standard","has-post-thumbnail","category-management"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/100734.png","fifu_image_alt":"Safe Software\u2019s culture faces its toughest test amid hypergrowth","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/100734","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=100734"}],"version-history":[{"count":1,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/100734\/revisions"}],"predecessor-version":[{"id":100735,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/100734\/revisions\/100735"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/100736"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=100734"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=100734"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=100734"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}