Technology decisions made for the business, not the salesperson
Three made-up stories about choosing software, leading technology part-time and fixing a process before automating it. Not client projects.
3 min readMade-up stories, not client work
Story 1 of 3
Choosing a new customer system
The short version: Choose software by how you work, not by who gave the best demo.
A wholesale company has outgrown spreadsheets and wants a proper customer system. Three vendors have already given impressive demos.
What's going wrong
Every demo looked great, and each was built to show off strengths, not to test the company's real work.
What we'd do
- Write down how you sellThe steps, the people and the reports leaders need, in plain language.
- Set the must-havesSeparate essentials from extras before looking at any product.
- Scripted demos with your dataEach vendor shows the same real tasks, so the comparison is fair.
- Count the full costLicenses, setup, training, integrations and support over several years.
- Plan the switchData moved, staff trained and a fallback ready for the first weeks.
How we'd know it worked
- A written comparison of the finalists against agreed must-haves
- A full multi-year cost estimate
- Staff using the new system for daily work after launch
- The catch
- A careful selection takes a few extra weeks. It's much cheaper than replacing the wrong system a year later.
- What the business gets
- A system that fits how the company works, chosen with eyes open on cost.
Story 2 of 3
A part-time technology leader
The short version: Get senior judgment for the hours you need, and a plan to stand on your own.
A growing company has several vendors, rising tech bills and no one senior to own technology. A full-time executive isn't affordable yet.
What's going wrong
Decisions are made piecemeal, vendors aren't held to account, and nobody sees the whole picture.
What we'd do
- Take stockEvery system, contract and cost in one place, with the risks highlighted.
- A one-year roadmapPriorities, budget and owners, agreed with leadership.
- Manage the vendorsClear expectations, regular reviews and contracts that serve the business.
- Plan the exitHelp hire and hand over to a full-time leader when the company is ready.
How we'd know it worked
- Leadership can see all technology costs and contracts in one place
- Roadmap reviewed every quarter
- A clear handover when a full-time leader is hired
- The catch
- Part-time leadership means fewer hours each week, so priorities must be sharp. That focus is often a benefit in itself.
- What the business gets
- Senior technology judgment at a fraction of a full-time salary, with a clear path to independence.
Story 3 of 3
Fixing the process before automating it
The short version: Fix the process first. Then automate what's left.
A services company takes a week to turn a signed order into an invoice. Leadership wants software to speed it up.
What's going wrong
Automating a messy process just produces mess faster.
What we'd do
- Map the processFollow one order from signature to payment and note every handoff and delay.
- Remove the wasteDrop duplicate approvals and re-typing before buying anything.
- Then automateUse the tools the company already owns where possible, and add new ones only where needed.
- Measure the differenceTrack the time from signed order to invoice, before and after.
How we'd know it worked
- A documented process everyone agrees on
- Clear reduction in days from order to invoice
- Each new tool justified by the time it saves
- The catch
- Process work is less exciting than new software, and it asks people to change habits. It's where most of the gain comes from.
- What the business gets
- Faster cash flow and less admin, often with little or no new software.
What all 3 stories have in common
Start with the business. Choose independently. Leave a plan you own.
Most technology regrets start with buying software before understanding the problem. We work the other way around.
- 1
Business first
How the company makes money and where time is wasted, before any product names come up.
- 2
Independent advice
Recommendations based on your needs and total cost, not on a sales pitch.
- 3
Plain-language plans
Roadmaps leaders can read, budget for and hold people to.
- 4
You own the result
Decisions, contracts and documentation stay with you.
Good technology decisions are business decisions. We make them independently, in plain language, and leave you owning the plan.
If you liked this, read
About these stories. These stories are made up to show how we think. They are not client projects, describe no real business, and contain no measured results.
Next: Cloud that fits the business, not the brochure
Three made-up stories about where to host, how to stay up, and how to stop overpaying. Not client projects.
Read the next story