Recent success stories of free software adoption across companies of all sizes

Intro

Free and open-source software (FOSS) is no longer the preserve of eclectic IT specialists: from the very small business right up to the multinational giant, more and more companies are adopting open-source solutions to gain efficiency and autonomy. Here we present three concrete success stories (between 2020 and 2022) of open-source software adoption, each illustrating a type of company in Quebec, Canada or elsewhere: a micro-business (very small enterprise), a small or medium-sized enterprise (SME), and a very large enterprise. For each case, we detail the company's name and sector, the open-source software adopted, the reasons behind that choice, the benefits obtained, as well as the challenges encountered and overcome. Finally, we will analyze the similarities and differences according to company size and sector of activity, before concluding with the lessons to be drawn.

Case no. 1: StepEarly – A micro-business that optimizes online furniture sales (very small enterprise)

Company profile: StepEarly is a very small enterprise founded in 2020, specializing in the online sale of office furniturefrappe.io. It is a young e-commerce startup that launched with the ambition of "revolutionizing online furniture buying" and eliminating the common pain points for customersfrappe.io. Its founder, with 10 years of experience in the furniture sector, wanted to offer quality products while guaranteeing fair prices and excellent customer service.

Open-source software adopted: To manage its operations, StepEarly chose an open-source enterprise resource planning suite, ERPNext (a free ERP system), including CRM and inventory management modules. The company preferred this open-source solution over a proprietary ERP such as SAP Business One or Oracle, because ERPNext is "100% FOSS" (fully open source), highly customizable and "future-ready," in the project's own wordsfrappe.io. This choice allowed StepEarly to keep control of its management tool without paying costly licenses, while tailoring it precisely to its needs.

Reasons for choosing open source: From its very first year of operation, StepEarly ran into the limits of its initial tools (such as the Tally accounting software). Several operational bottlenecks pushed it toward a more integrated open-source solution. For instance, lead and sales tracking lacked visibility; customer orders were getting lost for want of traceability in the sales pipeline; and there was no unified system to track each order from confirmation through to delivery, which hurt the customer experiencefrappe.iofrappe.io. In short, the young company struggled to track each salesperson's performance and to coordinate sales and purchasing, and the "lack of traceability at the point of order confirmation" led to errors and customer dissatisfactionfrappe.io. Rather than invest in expensive proprietary software, StepEarly therefore opted for an open-source ERP to centralize and automate its management, while avoiding proprietary lock-in. The ability to easily integrate third-party services (e.g., the IndiaMART lead platform) and to automate communications also motivated this choicefrappe.io.

Results and observed benefits: Adopting ERPNext transformed StepEarly's operations in barely six weeks. Thanks to a customized implementation, every sales order is now linked to its corresponding supplier purchases, providing end-to-end visibility and reducing discrepanciesfrappe.io. The system automatically captures online leads, eliminating manual data entry and speeding up follow-upsfrappe.io. All departments (sales, design, procurement) now work on a single, real-time platform, which improves collaboration and transparencyfrappe.io. Concretely, StepEarly observed an improvement in order accuracy (fewer errors or "misplaced" orders) thanks to better traceabilityfrappe.iofrappe.io. Customer responses are faster, which increases the sales conversion ratefrappe.io. Task processing has been accelerated, reducing delays and making operations smoother for the teamfrappe.io. As soon as a customer places an order, they now receive an automatic acknowledgment of receipt, establishing greater transparency and trust right from the startfrappe.io. The system keeps a history of all quote and order changes, preventing later misunderstandings and improving internal communicationfrappe.io. Finally, each team member can see at a glance the status of a project or order and identify where and who needs to act, which has removed many obstacles and made it possible to resolve problems fasterfrappe.io. All these gains translated into a noticeable rise in customer satisfaction and a strengthening of trust in the young StepEarly brandfrappe.io.

Challenges encountered and solutions: For such a small organization, the main challenge was to implement a complete ERP without disrupting operations. StepEarly called on a specialized integrator to configure ERPNext for its specific needs (for example, integrating the IndiaMART lead source or automating emails)frappe.io. Training the team on the new tool was made easier by close collaboration with the experts: founder Shashikant Tapre points out that going live was achieved "in six weeks, with a friendly and professional (implementation) team that made the experience smooth"frappe.io. In other words, the micro-business overcame the deployment challenge thanks to external support and the flexibility of open-source software, which allowed it to quickly reap the benefits without enduring long months of transition.

Case no. 2: Van Dyk Trucks – A service SME that unifies its processes (SME)

Company profile: Van Dyk Trucks is a North American SME specializing in the repair and maintenance of heavy trucks (truck fleets). It is a mechanical service provider that has built a reputation for fast, quality repairs on its customers' trucksfrappe.io. Its size places it in the SME range, with several dozen employees (mechanics, parts managers, administrative staff).

Open-source software adopted: Faced with management difficulties, Van Dyk Trucks decided to migrate to ERPNext, the same open-source ERP used by StepEarly, in order to manage its entire repair cycle within an integrated systemfrappe.io. The open-source modules deployed include customer relationship management (CRM), spare-parts inventory management, sales/quote management, and even a project module to track each repair orderfrappe.io. In other words, the SME adopted a 100% open-source management system to replace its patchwork of disparate tools.

Reasons for choosing open source: Before this change, Van Dyk Trucks used a combination of disparate tools: lots of Excel spreadsheets, emails, QuickBooks for accounting, Word for purchase orders, and so onfrappe.io. This reliance on separate, non-integrated software led to numerous errors and slowdowns. Customer data, truck maintenance histories and costs were "scattered across several systems," making it difficult to track repairs and profitabilityfrappe.io. Coordination between mechanics, the parts manager and accounting was done manually, generating bottlenecks in job assignment, approvals and invoicingfrappe.io. Moreover, real-time tracking was lacking: it was impossible to easily know where a repair stood, which part was out of stock, or whether a deadline would be met, which caused delays and inventory inconsistenciesfrappe.io. Finally, a problem specific to the trade was the management of core charges (used parts returned for a refund): without a suitable system, credits were poorly tracked, causing financial discrepanciesfrappe.io. Faced with these challenges, the SME chose open-source software for several reasons: first, an open-source ERP like ERPNext makes it possible to unify all functions in a single application (avoiding data fragmentation). Second, it is modifiable to fit particular business processes (for example, integrating the notion of part core charges). Finally, cost no doubt weighed in: adopting an open-source solution spared it the purchase of a costly proprietary ERP suite, while benefiting from a community and partners able to implement it.

Results and observed benefits: The implementation of ERPNext literally centralized all of Van Dyk Trucks' operations on a single platform covering "the entire truck repair cycle, from opening the customer file through to invoicing"frappe.io. The benefits were immediate. First, automation and centralization drastically reduced manual data entry and duplicate data, which "saves time and reduces errors"frappe.io. Next, real-time visibility took a major leap forward: the manager now sees instantly the progress of jobs, the state of inventory and financial indicators through the unified dashboardfrappe.io. Collaboration between teams improved, since mechanics, parts managers and accountants all work in the same system, with instant updates rather than scattered email exchangesfrappe.io. Concretely, Van Dyk observed better internal coordination and a reduction in delays and misunderstandings: each task (from the initial quote to the parts order and the invoice) follows a predefined flow in the ERP, eliminating oversights. Invoicing is more accurate thanks to automated tracking of labour hours and the quick generation of quotes/orders from data entered by the mechanicsfrappe.iofrappe.io. The well-known core charges are now managed automatically in the ERP, which tracks which used parts have been returned and credits the customer correctly, eliminating the financial losses tied to rough manual trackingfrappe.iofrappe.io. Finally, the overall repair turnaround time has been shortened: with structured workflows and automatic notifications, approvals are faster and bottlenecks have nearly disappeared, which makes it possible to return trucks to customers more quicklyfrappe.io. All in all, Van Dyk Trucks professionalized its management through open-source software: less paper and Excel, more visibility, and ultimately better customer service (deadlines met, error-free invoices).

Challenges encountered and solutions: The transition to a single ERP required rethinking the company's habits. At first, resistance to change may have been a classic issue: moving from Excel to an integrated software calls for staff to adapt. Van Dyk overcame this by involving its teams in the rollout and training them on the new processes, which are often simpler once mastered. A more technical challenge was the migration of existing data (customers, maintenance histories, parts in stock) to the new tool: thanks to ERPNext's import tools and support from the implementation provider, the SME was able to consolidate its scattered data into the ERP database without loss of information. Finally, the ERP had to be customized for sector-specific needs (for example, core-charge tracking). Here again, the openness of the code made it possible to add suitable features. In the end, Van Dyk Trucks successfully streamlined its truck repair operations, as the ERPNext vendor sums it up: "ERPNext successfully streamlined truck repair management at Van Dyk,"frappe.io notably achieving the elimination of redundant manual tasks and real-time visibility into the businessfrappe.io. This success was built by gradually removing each obstacle (fragmented data, manual processes) through a tailored open-source solution.

Case no. 3: Walmart – A global giant optimizes its open-source cloud (very large enterprise)

Company profile: Walmart needs no introduction: it is one of the largest retail companies in the world (around 2.3 million employees worldwide), with stores across the United States, Canada and many other countries. This retail giant runs an immense IT estate for its in-store and online operations. Around 2020–2022, Walmart set out to sharpen its "hybrid cloud" strategy by relying heavily on open-source solutions for its technology infrastructure.

Open-source software adopted: Walmart set up its own private cloud based on OpenStack, a very widely used open-source cloud infrastructure platform. OpenStack orchestrates tens of thousands of servers across Walmart's distribution centres and stores; in 2022 Walmart was running more than 10,000 OpenStack servers across its 5,500 stores and warehouses. It is "one of the largest OpenStack deployments in the world," according to Kevin Evans, Vice-President of Infrastructure Services at Walmart. In parallel, Walmart developed an internal cloud-native platform built on Kubernetes (another major open-source project) to manage its containerized applications. This in-house platform, launched in 2020, interfaces with both the public clouds and Walmart's OpenStack private cloud. In short, Walmart's technology architecture marries FOSS at every level: OpenStack for the IaaS (infrastructure) layer, Kubernetes for the application management layer, and numerous open-source automation tools developed in-house.

Reasons for choosing open source: Walmart's primary motivation was to regain control of its costs and its technological destiny in the face of the public-cloud giants (Amazon AWS, Microsoft Azure, Google Cloud). Rather than be entirely dependent on a single external provider, Walmart wanted to diversify its options. "Betting only on AWS, Azure or Google leads to higher costs than having the ability to choose between several platforms," explains Kevin Evans, stressing that "whatever your size, having choice will help you control costs." By building its own internal open-source cloud, Walmart gave itself the choice of running its applications either on its own infrastructure (based on OpenStack) or on the public clouds, depending on what is most advantageous. Open source was an ideal lever for this: OpenStack and Kubernetes are freely available, highly scalable and free of proprietary lock-in, allowing Walmart to adapt the code to its extreme needs. Furthermore, as Walmart was looking to compete with Amazon (including on the cloud front), it was strategic to reduce its dependence on AWS. Open source also offers the community and trust needed: it is not a risky bet, since the biggest players (including competitors such as Tencent or Bloomberg) also use OpenStack and Kubernetes. Finally, open source lets Walmart innovate faster internally (no software procurement cycles—engineers can deploy or modify tools directly). The company was thus able to build, in 2020, its "Walmart Cloud Native Platform" on Kubernetes to standardize deployment across different clouds, proof of the flexibility open source offers compared with rigid proprietary solutions.

Results and observed benefits: The gains for Walmart were spectacular at the scale of a multinational. By adopting this hybrid, open-source-based cloud strategy, Walmart managed to save enormous sums on its IT costs. As early as 2022, the trade press ran headlines saying that "Walmart's multi-cloud architecture saved millions in IT costs," while also accelerating development. Indeed, thanks to its OpenStack private cloud, Walmart can provide its developers with compute, storage and network resources at a cost far below that of the major public clouds. "We can do it at a much lower cost," confirms Kevin Evans, comparing their internal cloud to commercial offerings. This approach reduced cloud spending by 10 to 18% compared with an all-public scenario—which represents savings of several million dollars on the IT budget. Furthermore, the combined use of OpenStack and Kubernetes vastly increased the organization's agility: Walmart performs around 170,000 application deployments per month on its website, or 1,700 times more than with the old system, thanks to this unified infrastructure. Walmart's internal OpenStack environment reached a staggering scale: by 2021, it exceeded one million active compute cores, and it continues to grow well beyond that. Mastery of a massive private cloud allows Walmart to absorb load spikes (such as seasonal promotions) on its own servers, while keeping control of performance. In addition, Walmart was able to optimize its IT operations at scale: for example, what previously took 30 days to update OpenStack (a heavy operation) now takes only 48 hours thanks to the automation tools its engineers developed. They designed a "non-disruptive" update system that even lets them skip OpenStack versions to save time. The infrastructure has become more reliable and self-healing: Walmart coded systems that continuously monitor the health of OpenStack components and remediate failures automatically, as well as scripts that proactively isolate failing machines before they cause outages. In short, the massive adoption of open-source software (OpenStack, Kubernetes, etc.) allowed this retail giant to achieve substantial savings, gain independence from its vendors, and reach impressive technical velocity—all while proving that an open-source infrastructure can support one of the most demanding IT operations on the planet.

Challenges encountered and solutions: The transition to an open-source cloud at this scale was not without difficulties. Initially, OpenStack upgrades were laborious and risky, requiring many person-hours and intense coordination between teams. Walmart overcame this challenge by investing in automation: starting in 2018, they developed an automated, stateless update process for OpenStack, eliminating manual migrations and service interruptions. As a result, they update more than a million compute cores each year in just a few days, where it previously took a month. Another challenge was to orchestrate a complex multi-cloud environment (private OpenStack + Azure + Google Cloud) transparently for developers. Here again, the solution was software-based: Walmart created a common abstraction layer that hides the differences between AWS/Azure/Google and their internal cloud, offering a unified interface to their development teams. In doing so, the internal applications became "agnostic" as to where they run: they can be deployed indifferently on OpenStack or on a public cloud, depending on the cost or performance sought. To reach this level, Walmart had to develop in-house numerous open-source tools and secure the cooperation of technology partners. Kevin Evans notes that, initially, some vendors did not allow as much flexibility, but that Walmart "applied a bit of pressure" to get Microsoft and Google, for example, to let some of their software run on any cloud. Walmart's weight shifted the lines, and today everyone recognizes that "the value is in the software, not necessarily in the infrastructure where it runs." Finally, let us mention the internal culture: Walmart had to convince people internally that "no, OpenStack is not dead" and that, on the contrary, it powers their innovation. The tangible results (falling costs, faster deployments than ever) largely won over the skeptics. The company also actively contributes to the OpenStack community, sharing its experience. By overcoming these challenges, Walmart proved that with open-source software and in-house expertise, even a very large enterprise can compete with the biggest commercial providers.

Similarities and differences by size and sector

These three stories—a micro online-retail business, a mechanical-services SME and a retail multinational—demonstrate that open-source software can deliver benefits at every level, but with distinct approaches and stakes.

Common points: In each case, the adoption of FOSS solutions was driven by needs for cost reduction, operational efficiency and technological independence. StepEarly wanted to avoid the costs and limitations of proprietary software in its startup phase, Van Dyk Trucks sought to eliminate the inefficiencies of scattered tools, and Walmart aimed to free itself from the pricing and lock-in of the public clouds. All of them saw concrete benefits: better productivity (fewer manual tasks, more automation), better visibility into their activities (thanks to data integration), and often an improvement in customer service (fewer order errors at StepEarly, reduced repair turnaround at Van Dyk, faster deployment of new features at Walmart). Another common denominator is the importance of community and partners: none of these companies reinvented the wheel alone. StepEarly and Van Dyk relied on expert ERPNext integrators/partners to implement the tailored solution, proof that an ecosystem of providers has grown up around open-source software to help small organizations. Walmart, for its part, was able to count on the OpenStack/Kubernetes community and even influence its vendors, showing the strength of numbers when a company adopts and contributes to a major open-source project. Finally, each company had to overcome adoption challenges—whether technical (data migration, scaling up) or human (changing practices, training)—and met them thanks to the flexibility of open source (the ability to adapt the tool) and an investment in skills (training its team or surrounding itself with specialists). These examples confirm the claim, made in a McKinsey report, that "the adoption of open source is a major differentiator of the highest-performing organizations."

Differences by size: Of course, the stakes are not identical for a micro-business and for a global giant. The scale of the project first: StepEarly deployed an ERP in a few weeks for a handful of users, whereas Walmart manages more than a million compute cores and thousands of internal users on its platform—the skills and infrastructure involved are in no way comparable. Furthermore, the specific objectives differed: the micro-business was above all looking to structure its basic processes (sales, customer tracking) and to appear "big" in the eyes of its customers thanks to a professional tool, whereas the very large enterprise wanted to optimize an already extremely sophisticated IT architecture and cut eight-figure costs. Dependence on a single vendor was critical for Walmart (not depending on AWS, which is also a commercial competitor), which was not a factor for StepEarly or Van Dyk (they were fleeing unsuitable or overly expensive solutions, but not a direct competitor). In terms of resources, a very large company can afford to develop additional open-source tools in-house, contribute to the code, and even push the industry in its direction (Walmart imposed certain conditions on Microsoft/Google), whereas a small company will often have to accept the tool as is or rely on the community for improvements. For example, StepEarly could not have coded an entire ERP feature on its own; it used what already existed by integrating it cleverly (but nothing prevents it from sponsoring a later development—that is the advantage of open source).

Differences by sector: The field of activity shapes priorities. In e-commerce (StepEarly), the emphasis was on commercial management—leads, orders, web integration—to support the growth of online sales. In repair services (Van Dyk), the focus was on shop management, parts inventory and accurate billing of work performed. Each sector benefited from open source differently: StepEarly improved its customer experience (automatic confirmation emails, real-time order tracking) to stand out in a competitive marketfrappe.iofrappe.io, while Van Dyk improved its operational profitability (reduction of non-billable tasks, fewer lost parts, better use of mechanics' time)frappe.iofrappe.io. On the mass-distribution side (Walmart), open-source software served an objective of IT infrastructure performance and robustness, invisible to the end customer but crucial to ensuring that the stores and the website run without interruption during purchase peaks. Where the first two companies adopted vertical open-source software (an ERP/CRM tailored to their trade), Walmart instead adopted horizontal infrastructure open-source software (cloud, containers) that it integrated into a proprietary whole. Finally, note that in retail, Walmart was able to pool its open-source efforts with others (OpenStack is used by other commerce giants), whereas StepEarly in online furniture or Van Dyk in truck mechanics were pioneers in their niche in implementing an open-source ERP—a paying choice, but one that took a certain boldness for their size.

Specific stakes: For the micro-business StepEarly, the main risk was to get the digital transition right from the start so as to support growth. The story shows that by investing early in an open-source tool, it was able to structure its business and avoid the chaos experienced by some hypergrowth startups (poorly managed orders, overwhelmed customer support, etc.). For the SME Van Dyk, the stake was to modernize an existing business without disrupting customer service: here again, open source offered a smooth, modular transition (they were able to configure ERPNext gradually according to their workflows). For the very large enterprise Walmart, the stake was downright strategic vis-à-vis competitors and vendors: choosing open source meant arming itself for the battle over cost control and large-scale innovation. We thus see that FOSS is versatile enough to address very varied stakes, from the simple invoicing of a small shop right up to the global deployment of a cloud infrastructure.

Conclusion: Open source, a cross-cutting asset for competitiveness and autonomy

These three corporate cases—although very different in size and sector—all illustrate the transformative power of open-source software. Whether it is a Quebec micro-business or a global leader, FOSS made it possible to gain competitiveness: lower software costs, improved internal processes, and ultimately a better value proposition for customers. For StepEarly, this translated into easier growth and increased customer trust thanks to a high-performing back office. For Van Dyk Trucks, into optimized operations and eliminated errors, guarantees of productivity and profitability. For Walmart, into a strengthened margin and a faster-than-ever technological innovation capacity, giving it a competitive edge against Amazon and the like.

Beyond the benefits, these stories also underline that adopting open source is a strategic investment. It is not enough to install an open-source software to succeed: it must be accompanied by organizational change (training teams, rethinking processes) and sometimes technical change (developing specific features, integrating with the existing setup). Very small businesses and SMEs will benefit from relying on the ecosystem (integrators, mutual-aid communities) to make the leap, while large companies will often be able to contribute actively to the open-source projects they use, advancing the state of the art while meeting their own needs.

Comparing sizes, we see that open-source software acts as an equalizer: it gives smaller organizations access to world-class tools (a complete ERP, an office suite, etc.) without prohibitive costs, and it gives larger ones the freedom not to submit to the dictates of single vendors. In either case, the result is greater digital sovereignty for the company—a particularly relevant point in Quebec and Canada, where local players are seeking to innovate without depending entirely on foreign giants. Indeed, a report commissioned by Quebec estimates the potential savings at more than $265 million if organizations adopted more open-source softwaretvanouvelles.ca.

In conclusion, the 2020–2022 period demonstrated that open-source software is a catalyst for success for companies of every size. From startups to multinationals, those that dared to go open source are today reaping concrete advantages: flexibility, savings, speed and increased reliability. Each company must naturally adapt the open-source approach to its own reality (human resources, business objectives), but these inspiring examples—local and international—show that the game is worth the candle. Open source establishes itself not only as a viable alternative, but often as a winning strategic choice for building more agile, more independent and future-oriented companies.

Sources:

• StepEarly's experience with ERPNext, Frappe case study (2021)frappe.iofrappe.iofrappe.io
• ERPNext implementation at Van Dyk Trucks, Frappe case study (2021)frappe.iofrappe.io
• Walmart's open-source cloud strategy, TechTarget (2022); OpenInfra Summit (2025)
• "Adopting open-source software, a competitiveness factor," McKinsey via Opensource.com (2021)
• Potential savings from open-source software in Quebec (study, 2021)tvanouvelles.ca