No Single Source Sells the Whole Toolbox
Every organization runs on tools. A business exists to do a job – serve customers, ship a product, deliver a service – and it cannot do that job with people alone. It needs tools: the things that let the work actually happen.
Many of those tools are physical, and always will be – hammers, brooms, copiers, the computers on people’s desks. But a sizable and growing share of them are digital – software and the data it manages. The ledger became accounting software. The filing cabinet became a document store. The Rolodex became a CRM. The phone tree became a help desk. This article is about that digital part of the toolbox.
No single source sells the whole toolbox
Here is the catch: no single vendor can supply every tool a business needs. A modern organization depends on dozens of distinct digital tools, and they come from many different sources – commercial vendors, cloud providers, and the open-source community. The big productivity suites cover a slice of it, but no one of them covers finance and customer support and asset management and identity and monitoring and everything else.
Some vendors push back on this with the promise of a single pane of glass – one console to see and manage everything at once. In practice it too often turns into a “Single Pain of Glass”: the console unifies that vendor’s own products and a handful of integrations, then stops at the edge of what they actually sell. That is real value, but it is still not the full suite a business needs – the tools they don’t make are yours to source, run, and connect.
The only way to get the entire toolbox from a single source is to write it all yourself – and that is not realistic. A few years ago, building and maintaining your own complete suite of business software was simply out of reach for almost any organization. And even today, with large language models and AI coding assistants accelerating how fast software gets written, building and maintaining your entire toolset in-house remains a very hard, very expensive proposition. AI makes writing code faster; it does not make running, securing, integrating, and supporting dozens of bespoke applications cheap.
So every real business assembles its toolbox from many places. The practical questions are not whether to use many tools, but which ones, and how to make them work together.
A quick tour of the toolbox
The digital tools a business relies on span an enormous range of jobs. Grouped roughly by what they do:
- Finance & accounting – ERP and accounting, billing and subscriptions, invoicing and time tracking, expense management, payment processing, procurement and spend, budgeting and FP&A, treasury, corporate tax, payroll
- Sales & marketing – CRM, configure-price-quote (CPQ), quotes and proposals, marketing automation, SEO/SEM, social media management, ad platforms, e-commerce, point of sale, customer data platforms
- Customer & communication – help desk and ticketing, live chat and chatbots, call and contact centre, team chat, unified communications, client portals
- Operations – project management, workflow automation, robotic process automation, scheduling and booking, field service, fleet, inventory, warehouse (WMS), supply chain (SCM), transportation (TMS)
- People & HR – human resources, onboarding, performance management, employee scheduling, time tracking, learning management
- Documents & collaboration – office suites, document management (ECM), file sharing, wikis and knowledge bases, e-signature, forms and surveys, note-taking, diagramming and whiteboarding, PDF processing
- Content & creative – CMS and website builders, digital asset management, graphic design, video production and editing, webinars, digital signage
- Data & analytics – databases, data warehouses, business intelligence, dashboards, reporting, ETL and data integration, OCR and document intelligence
- IT foundation – email, identity and access (IAM/IGA), multi-factor auth, monitoring and observability, backup and disaster recovery, endpoint and mobile management, IT asset management, patch management
- Security – endpoint protection (EDR/XDR), SIEM and log analytics, vulnerability management, password managers, secrets management, email security, GRC and compliance
- Industry-specific – healthcare (EHR/EMR), legal and dental practice management, property and real estate, hospitality and restaurants, nonprofit and donor management, insurance, manufacturing execution, agriculture, and many more
And even that is only a slice. Our own tool catalog tracks more than 200 distinct categories of business and IT software, spanning over 3,800 individual tools – a measure of just how large and varied the digital toolbox has become, and how many different sources it is spread across.
How shared tools have been delivered: terminals to web apps
Most of the tools above share a requirement: many people use them at the same time, against one shared set of data. Your sales team all work the same CRM; your accountants all post to the same ledger. How that “many people, one shared system” need is delivered has gone through three eras.
Terminals (the mainframe era). In the earliest model, one central computer – a mainframe or minicomputer – did all the work, and people sat at terminals: screens and keyboards with little or no computing of their own, wired back to the central machine. Everyone shared one system and one set of data. This model is decades old but far from dead: core banking, airline reservations, insurance, and government systems still run on mainframes, reached today through terminal emulators.
Client-server. When PCs put real computing power on every desk, the model split in two. A program – the client – was installed on each person’s computer, and it talked over the network to a central server and database. The shared data stayed central; the rich interface ran locally. This dominated the 1990s and 2000s, but it had a cost: you had to install and update the client software on every machine, and it was usually tied to one operating system.
Web applications. The web turned the browser into a universal client. The application runs on a server; the browser simply displays it. There is nothing to install on each machine beyond a browser everyone already has, the data and logic stay central, you update once on the server and everyone immediately has the new version, and people can reach it from anywhere, on almost any device.
What a web app is
A web application is software you use through a web browser. Its logic and data live on a server; the browser is the client. You do not install the application on each computer – you point a browser at a URL. Because the server holds the shared state, many people can use the same application and the same data at the same time. A web app may be delivered as a hosted service (SaaS, run by the vendor) or self-hosted (run on infrastructure you control); either way, the model is the same.
Why we focus on web apps
The toolbox is far too large to cover every category, so this article focuses on web applications. They are the best current way to deliver a tool that has to be used by many people at once: shared data, no per-machine installs, access from anywhere, and one place to update and secure. That is exactly the shape of tool most businesses now need, which makes it where the rest of this discussion lives.
SaaS or self-hosted – and the deployment question
A web app can reach you two ways. SaaS (Software as a Service) means the vendor runs it for you: you sign up, log in, and they handle the servers, the updates, and the backups. Self-hosted means you run the same kind of application on infrastructure you control – your own servers or cloud account.
The trade-off is real:
- SaaS is easy to start and there is nothing to operate, but you rent it per seat, your data lives on someone else’s system, and you live with the vendor’s choices – price increases, feature changes, and the limits of what they let you integrate or export.
- Self-hosting keeps your data and control in-house, lets you integrate freely, and often costs far less at scale – but it has historically carried a heavy operational burden: someone has to install each app, configure it, secure it, monitor it, and – the part that quietly hurts most – keep it updated, across every app, indefinitely.
That last point is where many self-hosting efforts stall. Standing an app up once is easy; keeping dozens of them patched and current for years is not.
This is exactly the gap a deployment platform closes. ResorsIT’s Deployers treat each tool as a maintained recipe – the steps to install, update, and remove it – and keep that recipe current across every site it manages. The Deployers are themselves managed resources, and their payloads can be downloaded from Rhodium or built by your own team. New versions roll out from one source of truth instead of being chased by hand on each server. Deployment and updates become a managed, repeatable process rather than a standing chore – which makes self-hosting practical at the scale of a full toolbox: you keep the control of running it yourself, with something much closer to the ease of SaaS.
And this is not limited to web apps. The same recipe model installs and updates local, on-host software too – desktop and server utilities on managed machines – so the whole software estate, web and local alike, stays current the same way.
The ideal: a few shared services tie the apps together
Running dozens of web apps from many different vendors solves the tool problem but creates a new one: dozens of disconnected islands. The ideal is to make them behave like one coherent system, and three shared services do most of that work.
One identity for everything – an IdP, governed by IGAP. Instead of a separate username and password in every app, every app trusts a single Identity Provider (IdP), so each person has one secure login everywhere. Around that sits IGAP – Identity Governance, Administration, and Provisioning: deciding who should have access to which app, creating and removing those accounts automatically as people join, change roles, and leave, and keeping an auditable record of it all. Across dozens of apps, doing this by hand is slow and a real security risk; doing it from one place is the ideal.
One front door – central dispatch, the Hub. People should not have to track dozens of URLs and bookmarks. A central dispatch point – a Hub – gives each person one place to find and open the tools they are entitled to, and gives the organization one place to route and present them.
One view of health – monitoring with TIGA. With many apps running at once, you need a single view of whether they are up, how they are performing, and what they are logging. A monitoring layer – ResorsIT’s is called TIGA – gathers metrics, logs, and alerts from across all the apps so problems show up in one place instead of being scattered over dozens of separate dashboards.
Identity (IdP + IGAP), a central Hub, and unified monitoring (TIGA) are the backbone that turns a pile of separate web apps into something an organization can actually run – and they are exactly what a platform like ResorsIT is built to provide.
Conclusion
Every business runs on tools, and a large and growing share of them are digital. No single vendor sells the whole toolbox, and – even in the age of AI – writing it all yourself is not realistic. So you assemble it: dozens of web applications, chosen for the job, drawn from many sources, including the deep catalog of open-source options. The hard part was never finding tools; it is making them behave like one system instead of dozens of disconnected islands.
That is the problem ResorsIT is built to solve. It lets an organization run the web apps it chooses – SaaS or self-hosted – and ties them together with the shared services that make a toolbox into a platform: one identity for everyone (IdP) with full governance and provisioning (IGAP), one Hub as the front door to every tool, unified monitoring (TIGA) for one view of health across them all, and automated Deployers that install and keep each tool updated across every site. You get the freedom and economics of choosing – and self-hosting – the best tools for the job, with the coherence, security, and ease that used to require locking yourself into a single vendor.
The toolbox will only keep growing. The advantage goes to the organizations that can adopt the right tools freely and still run them as one.