field note
Keep, Swap, or Own: What to Do With Software You Already Pay For
The cost of keeping a vendor never shows up as a line item, which is why it never gets decided.
/8 min read
tl;dr
- Software you already pay for is a decision, not a default. Most offices never make it, because the cost of keeping a vendor is staff time, and staff time never appears on the same page as the invoice.
- Three options: keep paying, swap to a competitor in the same category, or stop renting that category and own the workflow.
- Keep is right when the tool is actually used and the leftover hand-work is small. It is the wrong default when a person is still doing, by hand, the job the subscription was bought to do.
- Swap is right when the category is correct and this vendor is bad. It is the expensive way to stay wrong when the category itself was the miss.
- Own is right when the workflow is yours, you will maintain it, and you want the data and the process to survive a cancelled subscription. It is the wrong purchase if nobody will own it after the build.
- Before you shop, list every tool you pay for and, next to it, the work that still happens by hand. That list is the decision. A vendor demo is not.
A portal renews. Nobody notices. The work it was supposed to do is still being done by a person, by hand, in a spreadsheet that lives on one laptop. The invoice is small enough that it never comes up in a meeting. The person is forty minutes a day, which is why it should.
That gap is the whole subject of this note. Not which CRM is better. Not which AI to buy. The software you already pay for, and the three things you can actually do with it.
I wrote earlier about the chat bubble that gets sold as intake, and about the difference between a conversation and a decision. Both of those notes stop at a purchase you have not made yet. This one is about the purchase you already made, which is the one most offices never reopen.
The decision, named
Three options. Not two, and not a dozen.
- Keep. Stay with the vendor. Pay the invoice. Live with whatever leftover work the tool does not do.
- Swap. Replace this vendor with a competitor in the same category. New portal, same job.
- Own. Stop renting that category. Put the capture, the routing, and the record in something you keep if you cancel a subscription.
Most offices never reach this list, because the cost of keeping a vendor is not on the same page as the invoice. The invoice is $89 a month. The leftover work is a person. Those two numbers are never asked to compete, so keep wins by default, every year, without anyone choosing it.
Why a spreadsheet does not settle this
When I sit down with a small office to look at what they already pay for, the first instinct is always a list: tool, monthly cost, who owns the login. That list is useful and it is not the decision. It tells you what is visible. The waste is the work that still happens around the tool, and that work has no line item.
A receptionist retypes what a client already typed into a form that does not reach the practice system. A bookkeeper exports a CSV every Monday because two subscriptions do not talk. A manager chases a portal nobody else can see. None of that appears next to the $89. So when budget time comes, the subscription looks cheap and the person looks like payroll, and payroll is not a software decision.
The audit only works if it makes that leftover work felt. Not summarised. Felt: this is the hour, this is the person, this is the thing they do after the tool has already been paid for. Once that is in the room, keep, swap, and own become real options instead of a habit.
Keep
Keep is a real answer. It is the right answer more often than a vendor of replacements wants to admit.
Keep is right when people on your team open the tool every day, the leftover hand-work next to it is small, and switching would cost more than the waste. A practice management system that actually holds the chart, a bookkeeping tool the accountant already lives in, a calendar everyone already uses: those are not the problem, even if a salesperson can show you a shinier version of each.
What keep costs, when it is the wrong keep: the leftover work becomes “how we do things.” Workarounds harden. Nobody can say what the subscription is for, only that cancelling it feels risky. A year later you are still paying, still retyping, and the original reason for the tool is a sentence nobody in the building can finish.
What breaks: nothing dramatic. That is the trap. Keep fails quietly. No outage, no angry email from a vendor, just a person who has been doing a job a piece of software was already paid to do, every weekday, until they leave and the next person inherits the workaround.
Swap
Swap is the move the market is built to sell you. A new logo in the same category. The demo is always better than the thing you have, because the thing you have is the one your team has already found the holes in.
Swap is right when the category is correct and this vendor is bad. The portal is the right shape of product, and this portal is slow, or locks your data, or bills you for seats nobody uses. Then a competitor in the same category is a real comparison, and you can judge it on migration cost, what you own at the end, and whether the leftover hand-work actually shrinks.
What swap costs: the new subscription, the overlap while both run, the hours of moving records, the week where nobody trusts the new one yet so the work still happens in the old one. That overlap is the part quotes leave out. You pay twice for a period that is longer than anyone plans.
What breaks: you swapped the vendor and kept the miss. If the original problem was that a chat bubble cannot do intake, a nicer chat bubble is a more expensive version of the same wrong purchase. If a person is still exporting the CSV, a different dashboard does not stop the export. Swap only pays off when the category was already right.
Own
Own means the workflow lives in something you keep if a vendor goes away. The form, the routing, the record, the notification to a named person. Not a second dashboard you log into. The system your staff already open in the morning.
Own is right when the leftover work is the product: the retyping, the chasing, the CSV, the inbox nobody else can see. Those are not features a category of SaaS forgot to add. They are the gap between a rented tool and the way this particular office actually runs. Closing that gap is a build, not a subscription change.
What own costs, in the numbers I publish: one well-defined workflow is $3,000 to $5,000 to build, and you own it. Two or three connected workflows run $7,500 to $15,000. Ongoing management, if you want it, is $1,500 to $3,000 per month. Everything is a project against a defined outcome. There is no hourly rate, because an hourly rate prices my time rather than your result.
Set that against the leftover work, not against the $89. If a staff member spends forty-five minutes a day retyping or exporting, that is roughly a full working week every quarter. The math is usually not close. The reason it still does not get decided is that those forty-five minutes never compete for budget against things that have invoices.
What breaks: you now have something to maintain. If nobody owns it after a staffing change, it rots the same way a rented tool rots, except you cannot blame a vendor. Notifications that still go to someone who left. A form that validates too loosely, junk piles up, trust erodes, and everyone quietly goes back to the old workaround while you keep the build. Own is the wrong purchase if the office will not keep a named person on it.
The comparison, plainly
| Keep | Swap | Own | |
|---|---|---|---|
| Right when | The tool is used and leftover work is small | The category is right, this vendor is not | The leftover work is the actual product |
| You pay | The invoice, plus any hand-work you ignore | New invoice, overlap, migration hours | A build you keep, then optional care |
| You keep if you cancel | Usually not the data, almost never the workflow | Depends on the new vendor, ask before you sign | The workflow and the record |
| Fails by | Quietly: workarounds harden, nobody notices | A nicer version of the same miss | Nobody owns it after a staffing change |
| Measurable by | Whether leftover hand-work shrank this year | Whether the leftover work shrank after cutover | Response time, retyping hours, named owner |
These are not mutually exclusive across the whole office. The honest map is usually mixed: keep the tools people actually live in, swap the one that is the wrong vendor in the right category, own the one or two workflows where a person is still doing the job by hand. Owning everything is a different business than the one most small offices are running.
How to tell which one you are being sold
Four questions, and you can ask them on the first call.
- What leftover work does this remove, specifically? If the answer is a feature list, you are being sold a category. The right answer names a thing a person currently does by hand.
- What do I keep if I stop paying? Data, the workflow, both, or neither. Both can be fine. Not knowing is not.
- What runs in parallel, and for how long? If the vendor has not planned the overlap, you will pay for two tools and work in the old one.
- Who owns this after a staffing change? A named role, not a named person who might leave. If nobody has asked you this, they are installing, not replacing.
Where to start
Not with a demo. Spend one week on a two-column list. Left column: every tool you pay for. Right column: the work that still happens by hand next to it. A tally sheet is enough. Who opens it, how often, and what they still retype, export, or chase.
If the right-hand column is mostly empty, you do not have this problem, and anyone selling you a replacement is selling you a swap you do not need. If three or four lines on the right are a person's morning, you have just found the decision, and you found it before a vendor told you which option you were buying.
common questions
Questions I get asked on this
How do I know if I should keep a tool I already pay for?
Look at the work, not the invoice. If people on your team open it every day and the leftover hand-work next to it is small, keep it. If a person is still doing by hand the job the subscription was bought to do, the invoice is not evidence that it is working. It is evidence that it renews.
What is the difference between swapping vendors and owning the workflow?
A swap stays inside the same category: a new portal, a new CRM, a new intake widget. You still rent. Owning the workflow means the capture, the routing, and the record live in something you keep if you stop paying a vendor. Swap is the right move when the category is correct and this vendor is bad. Own is the right move when the category itself was the miss.
What does it cost to own a workflow instead of renting the software?
At Genesis Flow Labs, a single well-defined workflow generally lands in the $3,000 to $5,000 range to build, and you own it. Two or three connected workflows run $7,500 to $15,000. Ongoing management, if you want it, is $1,500 to $3,000 per month. Everything is priced as a project against a defined outcome, never by the hour. Set that against what the leftover hand-work currently costs you, not against the $89 subscription.
Can I keep some tools and own others?
Yes, and that is usually the honest map. Most small offices should keep the tools that are actually used, swap the one that is the wrong vendor in the right category, and own the one or two workflows where a person is still retyping, exporting, or chasing. Owning everything is a different business than the one you are running.
What breaks most often when a small office tries to replace a vendor?
The overlap period. The old tool stays live because nobody trusts the new one yet, so you pay twice and the work still happens in the old place. The second failure is quieter: the new thing works, then a staffing change happens, and nobody owns it. Same shape as an intake system whose notifications still go to someone who left.
next step
Make the list.
Spend a week writing down the tools you pay for and the work that still happens by hand. Send me the list. I will tell you which lines are a keep, which are a swap, and which are a build. If the honest answer is that none of them are ready, that is what you will hear.
Prefer email? [email protected]