Early in my first operations job, my manager slid a folder across the desk and asked me to “get some numbers” for a warehouse fit-out. I spent a week on the phone and came back proud, holding four quotations that could not be laid side by side: one included racking, one assumed we owned the forklifts, two never mentioned delivery. She looked at the folder, then at me, and said something I have repeated to every junior colleague since: collecting comparable quotes is a career skill, and nobody will ever put it on a syllabus for you.<\/p>\n
She was right. Whether you end up in procurement, project management, marketing, or running your own venture, the ability to turn a vague need into a written requirement \u2014 and then into offers you can genuinely rank \u2014 quietly separates the people who get budgets approved from the people who get sent back for “more detail”. This piece is about how to build that skill deliberately, and what a healthcare marketplace taught me about doing it properly.<\/p>\n
The folder I handed my manager failed for one reason: every supplier had answered a different question. Each call began with my rough description and ended with their assumptions baked into a price. Ranking those figures would have meant rewarding whoever assumed the least work.<\/p>\n
Years later I watched the same lesson formalised in an unexpected place. A relative was weighing treatment options for my uncle, and instead of ringing hospital receptions she used MyHospitalNow, where a written medical requirement draws competing treatment estimates from hospitals<\/a>. The sequence impressed me more than the technology: she stated the need once, the platform looked the request over, several hospitals responded with their own estimates, and she studied them together before approving one and getting connected. One brief, many answers, a deliberate pause before commitment. That is the whole craft, transplanted into healthcare.<\/p>\n Habit one: write the requirement before you want the answer.<\/strong> A requirement scribbled after the first sales call inherits that vendor’s framing. Professionals draft the spec cold \u2014 scope, constraints, timeline, what “done” means \u2014 and only then open conversations. The discipline feels slow; it is actually the fastest route to numbers that mean something.<\/p>\n Habit two: send the identical document to every candidate.<\/strong> Tailoring the brief to each supplier feels courteous and ruins the exercise. If the plumber, the fit-out firm, and the training vendor each receive a different description, their prices drift apart for reasons unconnected to value. People building a long-term career in operations learn this early, the same way engineers mapping a realistic progression through DevOps roles and tooling<\/a> learn that repeatable process beats improvisation.<\/p>\n Habit three: read offers on several axes at once.<\/strong> Price, yes \u2014 but also who exactly will do the work, where they are, and what evidence backs their claims. MyHospitalNow lays hospital bids out with charges, facility information, and location visible together, alongside the trust signals the platform itself attaches (it describes its listed hospitals as verified \u2014 a claim worth noting as the platform’s own). The layout teaches the reader a habit: never let a single column decide.<\/p>\n You do not need a warehouse project to rehearse. The next time your family picks a coaching centre, draft a one-paragraph requirement \u2014 subjects, schedule, budget ceiling, distance \u2014 and ask three institutes to respond to it in writing. The exercise mirrors what a structured approach to shortlisting tutors and degree programmes<\/a> recommends, and it costs an evening. Asking, by the way, obliges you to nothing: on MyHospitalNow the quote request a patient submits carries no charge \u2014 the platform answers that question plainly on its own pages \u2014 and the same is true of almost every honest supplier you will ever brief. People who believe a request creates a debt collect one quote per decision for their whole careers.<\/p>\n Small rehearsals compound. The colleague who can produce three comparable responses for a team offsite is the one trusted with the vendor selection for the new CRM, and later with the capital project.<\/p>\n Nobody writes “good at comparable quotes” on a r\u00e9sum\u00e9, but the skill shows up everywhere hiring managers look. “Ran a structured selection across five suppliers, cut onboarding spend 20%” is a bullet built entirely on this craft. Founders feel it even more sharply: a small firm automating its back office lives or dies on supplier choices, which is why guides to bringing automation into a growing SME’s daily operations<\/a> keep circling back to disciplined vendor comparison before any contract is signed.<\/p>\n In the room, the skill sounds like better questions. What does this figure exclude? Which assumptions would change it? If two offers differ by thirty percent, what are they actually pricing differently? The person asking those questions reads as senior, whatever their title says.<\/p>\n My manager retired last year. At her send-off she told the warehouse story \u2014 kindly \u2014 and added the ending I never knew: the fit-out we eventually commissioned came in under budget because the rewritten brief surfaced a cheaper racking layout two suppliers had silently priced around. The saving was not negotiation; it was comparability.<\/p>\n That is the career skill in one line: make offers answer the same written question, weigh them on more than price, and only then commit. Healthcare platforms have turned the sequence into a product \u2014 MyHospitalNow being the clearest example I have seen, with its requirement-first flow from submission through competing bids to a considered approval \u2014 but the habit itself is free, portable, and learnable this week. Start with the next decision on your desk, however small. Write it down first.<\/p>\n","protected":false},"excerpt":{"rendered":" A story-driven look at the workplace craft of turning vague needs into written briefs and comparable quotes \u2014 and why it quietly accelerates careers.<\/p>\n","protected":false},"author":6,"featured_media":1125,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[166],"tags":[],"class_list":["post-1124","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-technology"],"_links":{"self":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1124","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/comments?post=1124"}],"version-history":[{"count":0,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1124\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/media\/1125"}],"wp:attachment":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/media?parent=1124"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/categories?post=1124"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/tags?post=1124"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}The three habits behind the skill<\/h2>\n
Practising on low-stakes decisions<\/h2>\n
What this looks like on your CV \u2014 and in the room<\/h2>\n
The quiet confidence of compare-then-commit<\/h2>\n