field note
Keep, Swap, or Own: What to Do With Software You Already Pay For
By Shafen Khan//Updated /5 min read
short answer
Keep the tools your team opens every day when the hand-work left over is small. Swap when the category is right and this vendor is bad. Own the workflow when a person is still doing, by hand, the job the subscription was bought to do, and the office will keep a named person on it. To see which is which, list every tool you pay for and the work that still happens by hand next to it.
Bring the list. Get a straight answer on which line is which.
tl;dr
- Software you already pay for is a decision, not a default. The cost of keeping a vendor is staff time, and staff time never appears on the same page as the invoice.
- Keep what is actually used. Swap a bad vendor in the right category. Own the workflow when a person is still doing the job by hand.
- 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.
Most offices never decide, 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.
The work that 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 the subscription looks cheap and the person looks like payroll.
Keep
Keep is a real answer, more often than a vendor of replacements wants to admit. It 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.
The wrong keep fails quietly. No outage, no angry email, just a person 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 right when the category is correct and this vendor is bad: it is slow, it locks your data, or it bills you for seats nobody uses.
The part quotes leave out is the overlap. Nobody trusts the new tool yet, so the work still happens in the old one and you pay twice, for longer than anyone plans. And if the category itself was the miss, a nicer version is a more expensive way to stay wrong.
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, in 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. It is a fixed price for a defined result, in writing, before work starts, and you own what it builds. Ongoing management is optional. There is no hourly rate.
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. 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 |
The honest map is usually mixed: keep the tools people actually live in, swap the one wrong vendor, and own the one or two workflows where a person is still doing the job by hand.
Four questions for the first call
- What leftover work does this remove, specifically? A feature list means you are being sold a category.
- What do I keep if I stop paying? Data, the workflow, both, or neither. Not knowing is the problem.
- What runs in parallel, and for how long? No plan for the overlap means two invoices.
- Who owns this after a staffing change? A named role, not a person who might leave.
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.
If the right-hand column is mostly empty, you do not have this problem. If three or four lines on the right are a person's morning, you have found the decision, 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 it is a fixed price for a defined result, in writing, before work starts. You own what it builds. 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.
pass it on
Send it to a coworker, your boss or a friend who has this problem.
Handing it to someone who prefers paper? Get the one-pager to pass on.
Make the list.
Spend a week writing down the tools you pay for and the work that still happens by hand. Bring the list, and you will hear which lines are a keep, which are a swap, and which are a build. If none of them are ready, that is what you will hear.