--- title: "How to choose a QMS: a buyer's guide · VisualQMS" url: "https://visualqms.com/resources/how-to-choose-a-qms/" language: "en" description: "How to choose a QMS: the questions to ask any vendor, what a good answer sounds like, and the costs buyers miss. A buyer's guide from Solution Management." --- A decision you live with # Choose a QMS on your own terms A QMS is a decision you live with for years, often made on a few demos and a price that is hard to compare. Here are the questions to put to any vendor, and what a good answer sounds like. [Book a demo](https://visualqms.com/book-a-demo/) [Talk to us about your setup](https://visualqms.com/contact/) On this page 1. [Six steps from requirements to a pilot](#six-steps-from-requirements-to-a-pilot) 2. [Eight questions to put to every vendor](#eight-questions-to-put-to-every-vendor) 3. [Whether people use it decides the rest](#whether-people-use-it-decides-the-rest) 4. [Questions buyers ask before they choose](#questions-buyers-ask-before-they-choose) Start with what you are buying. A quality management system is where your [controlled documents](https://visualqms.com/features/document-control/), processes and quality records live, plus the workflows that move them: review and approval, corrective action, change, audit, training, risk. Its job is to make the next audit calmer and the everyday work easier. The common failure is the opposite. The quality team maintains the system while the floor and engineering route around it, back to the shared drive and the spreadsheet, because finding the current revision of a procedure is faster there. By the time an auditor asks for that revision, the gap is obvious. And the cost of choosing wrong is rarely the licence fee. It is the stalled rollout, the second migration two years later, and the audit findings in between. The questions below are written to work with any vendor. We make and implement [VisualQMS](https://visualqms.com/what-is-visualqms/), so under each criterion we say what VisualQMS does, and where a specialist may fit you better. One rule holds for every conversation you are about to have. No software makes you certified to a standard; certification rests with your own quality system and an accredited certification body. Treat any vendor that claims its software is "certified to ISO 9001" as a red flag, and look for "[supports / helps you meet](https://visualqms.com/features/quality-standards/)" language instead. Requirements before demos ## Six steps from requirements to a pilot 1. ### Step 1: Write down what you need first Your own requirements list is the only thing standing between you and someone else's. Before you book a single demo, write down your real processes, the standard or standards you work to, the documents and records an auditor asks you for, and who will use the system day to day, including the operators and engineers who are not in quality. Skip it and the first slick demo becomes your requirements, and you buy what you were shown rather than what you need. Keep it short and concrete: name the SOPs, the control plans, the CAPA workflow, the people on the production floor who have to find a current revision. 2. ### Step 2: Shortlist three to five vendors With that list in hand, research the field and cut it to a handful that plausibly fit your industry and size. A tool built for one regulated sector and a cross-industry QMS solve different problems, so read 'top 10' lists with your own requirements in mind. Read each vendor's own pages with a sceptical eye and note which ones are honest about what they do not do. A vendor that tells you where it is not the right fit is giving you usable information. 3. ### Step 3: Demo on your own documents A canned example shows you the product at its best. Your own documents show you the product. Ask every shortlisted vendor how the system handles your processes and your records, and bring a real SOP, a control plan, or a CAPA you are working through and ask how it would behave. A vendor that engages with your documents is answering your question; one that steers you back to a fixed script is answering a different one. 4. ### Step 4: Test it with a non-quality user A demo is aimed at the quality team, but the system has to work for everyone outside it. Put it in front of someone from production or engineering and ask them to find the current revision of a procedure. If they can do it without help, by clicking an activity on a process map or searching by what the document is, adoption is realistic. If only the quality team can navigate it, expect the rest of the business to route around it once the pilot is over. 5. ### Step 5: Get a scoped quote and the full cost picture Now narrow to finalists and get real numbers. Ask each one for a written quote tied to your team size and the modules you need, then ask plainly what is not in it: setup, data migration, training, and validation can arrive as separate invoices. Get the one-off costs in writing alongside the subscription. And ask what it costs to get your own data out if you ever leave, so you are comparing total cost rather than sticker price. 6. ### Step 6: Decide, then start small Pick the tool, then keep the first rollout narrow. Stand up one area first, such as document control plus a single workflow, and run it with a real team before you commit the whole company. A pilot tells you about adoption and admin burden in a way no demo can, and you learn whether people use it before you roll it out across every department. The same yardstick for all ## Eight questions to put to every vendor Demos and quotes only compare when every vendor is measured on the same points. Each criterion comes with the question to ask, what a good answer sounds like, and what VisualQMS does. ### Will people use it? A QMS only pays back if the floor and engineering use it instead of routing around it. The other seven criteria rest on this one. Ask: how does a production operator find the current revision of a procedure, and what does the day to day look like for someone who isn't in quality? A good answer: people find the right document by what it is or by clicking an activity on a process map, in tools they already open. In VisualQMS an activity on the process map opens the latest approved version of the document, or you search by what the document is. ### Will the records hold up in an audit? Version history, approvals and signatures are where an auditor pushes hardest, and they are the records that have to hold up. Ask: show me the version history on one document, how a review and approval is recorded, and how electronic signatures work. A good answer: every document carries its version history and a recorded review and approval, shown live rather than on a slide. In VisualQMS a controlled document has a working version and a published one, every review and approval is recorded, and each check-in or change of a document's details adds a row to its version history. Signing uses tools such as DocuSign or Adobe Sign, with your own subscription to that service. ### Does it map to your standards? Tagging a document to a requirement is the easy half. The half that matters is spotting the requirement that nothing is tagged to. Ask: can we link our processes and documents to the requirements of the standards we work to, and see where a requirement isn't covered? A good answer: requirements you can import or create, documents tagged to them, and a view of the gaps, described as 'supports' rather than 'certified to'. By design, VisualQMS supports the requirements of the most common quality standards: you import a standard's statements or create them, tag documents and process maps to them, and manage several standards in one system. ### Can you start small? A monolithic suite makes you buy and roll out everything at once, whether or not you are ready for all of it. Ask: can we start with document control and one workflow, then add CAPA, audit, and change later, and will new modules share the same documents and records or start empty? A good answer: you begin small, and added modules connect to what is already there. In VisualQMS you aren't required to use every module: controlled documents and the process maps usually come first, and add-on modules such as CAPA, [deviations](/modules/deviation-management/ "Deviation Management"), [non conformances](/modules/non-conformance-management/ "Non Conformance Management"), internal audit, risk assessments and change requests can be added at the start or later, cross-referenced to the rest. ### Does it fit your tools? A QMS behind a separate login gets used less, and its records drift from the live business data they are meant to reflect. Ask: how does it work with Microsoft 365 and our ERP or CRM, and how does it pull live data, via connectors, SQL, or APIs? A good answer: documents reachable from the Office tools people already open, plus a clear integration path for business data. VisualQMS is tightly integrated with Microsoft 365, with integration available for SharePoint Online, Microsoft Teams and Salesforce, and it fetches customers, products and vendors from ERP or CRM systems through APIs, direct ODBC connections and other methods. ### Does it fit your industry? Many eQMS tools are built for one regulatory world and treat everywhere else as a footnote. Ask the vendor to show your industry's actual workflow on your records, without locking you into a single framework. A good answer: your workflow on your own records, configuration that follows the way you already work, and room for more than one standard in the same system. VisualQMS modules are pre-configured, and set up for your organisation during implementation. They can be configured further or from scratch, and you can manage several quality standards in one system. Customers have validated VisualQMS for their intended use, so it can be done. A validation covers your own set-up and the way you use the system, so your company is responsible for it and sizes it to the risk. Tell us early what your validation has to cover, and we'll go through it for your set-up. ### How much does AI help? AI is the easiest thing to put on a slide and the hardest to verify, so scrutinise the claims in a live demo instead. Ask: where does the AI get its answers, does it show the source, which licences and editions does it need, and can it approve or change a record? A good answer: the AI shows the documents behind an answer, uses only content the user is allowed to see, and never approves records. VisualQMS is built on M‑Files, whose AI assistant M‑Files Aino shows the documents an answer came from and only uses content the user may see; what's available depends on your M‑Files edition, hosting and licences. ### What does the price leave out? How a tool is priced changes both the total and how far it can spread inside the company. Ask: is pricing per module, per user or both, what's included, and is there a minimum floor? A good answer: pricing tied to the modules you use and your team size, with inclusions spelled out and the one-off costs itemised. Watch for high entry floors, and for licensing that makes every new department its own subscription. For VisualQMS, we deliver the necessary software licences for M‑Files, Elements.cloud and VisualQMS and quote them for your setup, and M‑Files can be used for other business areas too. ## Put these eight questions to us [Book a personal demo](https://visualqms.com/book-a-demo/) Where it matters most ## Whether people use it decides the rest The criteria for choosing a QMS do not carry equal weight. If you weight one above the others, make it adoption. A tool that scores well on features and poorly on day-to-day usability delivers a shadow system, because the people who keep quality real (operators, engineers, line leads) stop using it and go back to the drive. The best audit trail in the category doesn't help if the current revision never makes it into the system because logging in is friction. In the demo, watch how someone outside quality finds a document, and listen to the verb. If they have to _remember_ where it was filed, the tool is built for the quality team and everyone else will adapt or avoid it. If they find it by _what it is_, searching metadata or clicking an activity on a [process map](https://visualqms.com/features/visual-processes/) that opens the approved document, the rest of the business can self-serve. In [VisualQMS](https://visualqms.com/what-is-visualqms/), documents are found through metadata rather than folder location, and the process view is one of the ways in. Make 'will people use it' a scored criterion. ![A VisualQMS process map for handling a customer complaint, with the step "Assess severity and contain" opened beside it: the procedure QP-08, notes on severity and a view of open complaints](https://visualqms.com/img/Mkc8iL0TdJ-200.webp) Click "Assess severity and contain" and its procedure, QP-08, opens beside the map, with the notes for that step. ### Who can change a workflow[#](#who-can-change-a-workflow) Second only to day-to-day use, the criterion buyers most often under-weight is who can change a workflow once it is live. Most selection guides ask whether a tool is 'customisable' and stop there; the better question is who edits it, and how. A workflow that needs a professional-services ticket every time you add an approval step becomes a slow tax on running quality. Ask each vendor to change a field or an approval route during the demo, and watch who has to do it. Pair that with a careful read of the [pricing model](https://visualqms.com/pricing/): a low licence price hiding a large mandatory services fee, or licensing that bills every new department as a new subscription, can cost more over three years than it first appears. ### Count the whole bill[#](#count-the-whole-bill) Vendors quote a subscription and put everything else in a generic 'TCO' bullet, which makes the price you see only half the number. The costs buyers under-budget are the one-off ones: setup and configuration, data migration (which scales with how messy your legacy records are), training, and validation if your industry requires it. Ask every vendor whether migration and training sit inside the implementation fee or arrive separately, and what it costs to get your own data out if you ever leave. On the platform side, M‑Files comes with VisualQMS, and you can also use it for [other business areas](https://visualqms.com/beyond-qms/), with pre-configured modules for contract management, human resources and project management. ## See VisualQMS against your own requirements Hold any QMS up against your requirements list and the eight questions, ours included. Book a personal demo and put them to us. Our help while you find and select a QMS is free of charge. [Book a demo](https://visualqms.com/book-a-demo/) [Talk to us about your setup](https://visualqms.com/contact/) ## Questions buyers ask before they choose Cloud or on-premise: which should we choose? This is an IT and compliance decision more than a feature one. Cloud lowers the setup and maintenance burden; on-premise or your own cloud matters when your data rules require it. Ask each vendor what hosting options they offer and how identity and access are managed. VisualQMS runs on premise, hosted, in your own cloud or on M‑Files Cloud. One caution that applies to any vendor: if they claim ISO 27001 or SOC 2, ask to see the actual report, and treat the data-handling practices and the certificate as separate things. See [integrations](https://visualqms.com/integrations/) for more. How long does implementation take? There is no standard answer, and a vendor who offers one before asking about your scope is guessing. It depends on how many processes you bring across, how clean your existing records are, and how many modules you start with, so ask each vendor what the time depends on for your scope, and who does the setup. Ask whether the document and process setup is included or a separate fee. Starting with one area rather than every module at once shortens the path to a working system. VisualQMS lets you start with some modules and add others later, and we often implement it remotely, across time zones. See [implementation](https://visualqms.com/implementation/). Do we need every module? No, and a vendor that requires the full suite up front is a flag. Starting with document control plus one workflow keeps a pilot small. You then add CAPA when corrective actions outgrow email, internal audit when the schedule gets serious, and risk and change as you mature. What matters is whether added modules connect to the same documents and records or arrive as separate tools you reconcile later. In VisualQMS, controlled documents and the process maps usually come first. Browse the [modules](https://visualqms.com/modules/), from [CAPA](https://visualqms.com/modules/capa-management/) and [internal audit](https://visualqms.com/modules/internal-audit/) to [risk](https://visualqms.com/modules/risk-management/) and [change](https://visualqms.com/modules/change-management/), and pick the one or two that solve your most pressing problem first. Per-seat or modular pricing: what's the difference for cost? Many eQMS tools price on two axes, often together: per person on the system, and per module you turn on. There is rarely a public list price, so you get a quote for your team size and the modules you need. Watch for a high minimum floor that prices smaller teams out, and for licensing that turns every new department into a new subscription. For VisualQMS, we deliver the necessary licences for M‑Files, Elements.cloud and VisualQMS and quote them for your setup. Get a scoped quote on the [pricing page](https://visualqms.com/pricing/). What costs do buyers usually miss? The subscription is only part of the bill. Budget for setup and configuration, moving your existing documents and records across (data migration, which scales with volume and how messy the legacy records are), training, and validation if your industry requires it. Ask any vendor whether migration and training sit inside the implementation fee or are billed separately, and what it costs to get your data out if you ever leave. Get a scoped number rather than relying on figures quoted for the category. For how the pricing models compare and the costs buyers under-budget, see [what an eQMS costs](https://visualqms.com/resources/qms-software-cost/). Do we need a validated system, and what does it cost? Only if your regulatory world requires it. In pharma and GxP settings, computer system validation (the documentation that shows a system does what it should) can be a real, separate cost, and you should ask any vendor to evidence exactly what it provides rather than trust a checkbox. Where validation isn't required, the priority is a complete, defensible record of reviews, approvals and versions. In VisualQMS, reviews and approvals are documented in records, and each check-in or change of a document's details adds a row to its version history. Customers have validated VisualQMS for their intended use, so it can be done. A validation covers your own set-up and the way you use the system, so your company is responsible for it and sizes it to the risk. Tell us early what your validation has to cover, and we'll go through it for your set-up. See [VisualQMS in life sciences](https://visualqms.com/industries/life-sciences/). We're on spreadsheets and SharePoint: when's the right time to move? The usual triggers are a failed or painful audit, version confusion (two people editing two copies of the 'current' SOP), corrective actions tracked in email, and growth or new customers raising the documentation bar. If finding the current revision of an SOP already takes a folder search and a 'check with so-and-so', you have outgrown the shared drive. Start by writing your requirements down, bring [document control](https://visualqms.com/features/document-control/) under one system, then add workflows, and run a small pilot before committing the whole company. For the full migration path, see [replacing Excel and SharePoint with a real eQMS](https://visualqms.com/solutions/replace-spreadsheets-sharepoint/), or [talk to us about your setup](https://visualqms.com/contact/) first. On this page 1. [Six steps from requirements to a pilot](#six-steps-from-requirements-to-a-pilot) 2. [Eight questions to put to every vendor](#eight-questions-to-put-to-every-vendor) 3. [Whether people use it decides the rest](#whether-people-use-it-decides-the-rest) 4. [Questions buyers ask before they choose](#questions-buyers-ask-before-they-choose) [Book a demo](https://visualqms.com/book-a-demo/)