You asked for budget for quality management software and got one sentence back: “Excel is good enough, we’ve always done it this way, and we pass our audits.” Conversation over. You go back to forty spreadsheets, three shared folders and the same audit coming up.
The mistake is almost always the same: we answer with features. Version control, traceability, approval workflows, automatic reminders. Your boss isn’t asking about features. They’re protecting a budget, their own time, and the risk of starting a project that may never finish.
This isn’t an “Excel vs. software” piece. If you want the mechanics of the move, that’s already written in how to migrate your QMS from Excel without disrupting operations, and the maths of the cost is in how much not having ISO 9001 software costs you. This is the other thing: the kit for the conversation. What to say, backed by which numbers, in which order.
Table of Contents
Your boss isn’t arguing about software
“Excel is good enough” rarely means what it says. It usually translates into one of three things, and none of them is solved by a demo:
- “I don’t want to spend on something that isn’t hurting me today.” The document chaos hurts you, not them. As long as audits are passed, management sees a system that works.
- “I don’t want another project that dies halfway.” They have probably lived through an implementation that stalled. They’re protecting their credibility, not the budget.
- “I don’t see what I get.” You’re selling order. They buy time, controlled risk and the ability to grow without hiring.
Your job in that meeting isn’t to prove Excel is bad. It’s to prove the problem is already costing money that nobody has ever added up.
The four arguments that don’t work
Before the script, what to leave at the door. All four sound reasonable and all four lose the meeting:
- “Excel isn’t traceable.” That’s jargon. To someone who doesn’t live inside the system, “traceable” means nothing concrete.
- “Everyone in our industry already has software.” Social proof works on peers, not on the person signing the invoice. The answer will be “well, we don’t.”
- “We’ll get a nonconformity.” It’s a threat that hasn’t happened, and if you passed last year’s audit, the evidence is on their side.
- “I’m losing a huge amount of time.” Your time isn’t a line in their budget. It becomes one when you turn it into hours and money.
How to build the conversation in five steps
1. Bring a number before you ask for anything
Don’t walk in asking. Walk in reporting. Work out what it costs today to keep the system running by hand: hours chasing signatures, hunting for the current version of a document, assembling the audit folder, rebuilding a record someone overwrote. Multiply by the hourly cost of the people involved. The manual QMS management cost calculator does it in a few minutes and gives you the annual figure. That number is your opening line, not your conclusion.
2. Pick one pain, and one they’ve felt
Don’t bring ten problems. Bring one management has lived through: the customer who asked for a record and it took four days to find, the audit that took two people working a weekend, the obsolete procedure that stayed in use for six months. One concrete case with a date beats ten general arguments.
3. Translate the risk into their language
Management doesn’t buy “compliance”, it buys continuity. The real risk of a spreadsheet-based system isn’t the nonconformity: it’s depending on one person who knows where everything is, and on a file nobody backs up. Frame it that way: “if I’m not here tomorrow, how long does it take someone else to pull the documentation for a customer?”
4. Ask for the minimum, not for everything
Asking to “digitise the quality system” is asking for a project. Asking to “run one process for ninety days” is asking for a small decision. Pick the process that hurts most, usually document control or corrective actions, and propose starting there only. A tightly scoped pilot disarms the “projects here die halfway” objection.
5. Close with a date, an owner and a criterion
A conversation without a date is a lost conversation. Leave the meeting with three things written down: what will be tested, who evaluates it, and which number decides it in ninety days (for example, hours spent preparing the next internal audit). If it isn’t approved, at least it’s on record what approval would take.
The script, line by line
This is the ammunition. The middle column is what most of us say; the right-hand column is what actually moves the decision:
| What your boss says | What we usually answer | What actually works |
|---|---|---|
| “Excel has worked for ten years” | “Yes, but it’s very manual” | “And it cost us X hours last year. Here’s the breakdown. The question isn’t whether it works, it’s whether it’s still worth it at that price” |
| “We passed the audit” | “This time it could go wrong” | “We passed it with two people working a Saturday. What I’m proposing is to pass it the same way, without that Saturday” |
| “There’s no budget this year” | “It’s an investment, not a cost” | “Understood. What would I need to show for it to make next cycle’s budget? I’ll prepare it with numbers” |
| “Have an assistant handle it” | “It’s not that simple” | “We can, and the knowledge leaves when that person does. Today we depend on one head to find any record” |
| “What if the team doesn’t use it?” | “They will use it” | “That’s why I’m proposing one process and ninety days. If they aren’t using it by then, we stop and we’ve lost nothing” |
The only slide you need
If you have to present it formally, don’t build twenty slides. Build one, with five lines in this order:
- The number: what running the system by hand costs per year.
- The case: one real incident, with a date, that management remembers.
- The ask: one process, ninety days, one owner.
- The risk of doing nothing: dependence on one person and on unbacked files.
- The decision date: when it gets reviewed, and against which metric.
No architecture, no module lists, no vendor comparison tables. That comes later, and the vendor can work through it with you.
What to do if the answer is still no
A “no” with no criterion attached is the worst outcome, because it comes back just as vague six months later. Ask one question before you leave: “what would have to be true for the answer to be yes?” The answer gives you the condition, and conditions can be worked on.
Then put it in writing somewhere it has consequences. The adequacy of resources is a mandatory input to the management review: if the system only holds together with overtime and a shared spreadsheet, that belongs in the minutes, not in your memory. A topic that shows up twice in a row in minutes signed by management stops being your opinion and becomes an open issue of the system.
Frequently asked questions
Can Excel comply with ISO 9001?
Yes. The standard doesn’t require any software: it requires control of documented information, evidence and traceability. Spreadsheets can deliver that. The right question isn’t whether it complies, but how many hours a month it takes to keep it compliant, and what happens when the person holding it together isn’t around.
Which argument carries the most weight with management?
The cost of running the system by hand, expressed in hours and converted into money. It’s the only one that speaks the language of the person who signs. The second strongest is single-person dependency.
How do I answer “there’s no budget”?
Don’t push inside the same cycle. Ask what it takes to enter the next budget and offer to prepare it with numbers. While you’re there, ask whether a scoped pilot is possible: pilots often fit where full projects don’t.
How do I lower the perceived risk of the decision?
Small scope and a clear exit. One process, an evaluation deadline and a success criterion agreed up front. It helps a lot if the vendor has public pricing and a money-back guarantee, because that makes the decision reversible; at QualityWeb 360 it’s 60 days.
When is the best moment to raise it again?
Right after something hurts: an audit that ate weekends, a customer complaint you couldn’t document, the departure of the person who held the system together. That’s when the number you prepared stops being theoretical.
If you already have the number and the case, the next step is seeing what your system looks like without the manual hours. You can book a demo and walk into that meeting with your boss carrying more than a promise.
