Do not rip it out and rebuild. Harvest the organs.
When you inherit a system, a tool, a competitor's playbook, or an AI's plan, the instinct is a clean rebuild. It is usually the slowest, most wasteful option. Take the parts that work, leave the rest, and narrow the real work to a few pieces.
When you inherit a system you did not build, an agency setup, a competitor's playbook, a legacy process, an AI's recommendation, the instinct is to rip it out and start clean. It feels decisive. It is usually the slowest and most expensive option, because most of what is in front of you already works. The better move is to harvest the organs: take the parts that are good, leave the rest.
Sort before you rebuild
Go through the thing part by part and tag each piece, instead of judging the whole as one lump. The founder who skips the sort and defaults to rebuild throws away every working part along with the broken ones, and pays for the privilege. A few minutes of sorting saves you months of rebuilding what you already had.
Four buckets
Keep
It works and it fits. Leave it alone. Do not gold-plate a part that is already doing its job, and do not rebuild it just because you did not make it.
Harvest
The whole does not fit your situation, but a piece of it is genuinely good. Take that piece and leave the rest. This is the bucket most people miss, because they judge the container instead of the contents.
Fix
It is broken but worth repairing. These are the known problems, the parts you can see are wrong. Cheaper to fix than to replace, so fix them rather than starting over.
Cut
It is actively doing harm. Remove it. Do not try to save it out of sentiment or sunk cost. This is the only bucket where rip-it-out is the right call.
Where you use it
An agency or setup you inherited. A competitor's funnel you are studying. A plan an AI just handed you. A legacy process nobody documented. Even a new hire's existing way of working. In every case the reflex is keep-none or keep-all, and both are lazy. The work is in the sort, and the sort is where the value is.
Why this beats a clean rebuild
Rebuilding what already works is one of the most common ways founders burn months and feel busy doing it. A clean start is emotionally satisfying and rarely correct. The disciplined harvest gets you the working parts immediately and narrows the actual work down to the few pieces that need it. Decisive and wasteful is still wasteful.
So the next time something lands in your lap that you did not build, resist the rebuild. Sort it into keep, harvest, fix, and cut, and you will usually find that most of the job was already done for you. Take the organs. Leave the corpse.
Rebuilding things that already half worked?
Knowing what to keep, harvest, fix, and cut is how you stop burning months on clean rebuilds. That kind of triage is a large part of what I do inside a business. The strategy call is free and it is a real diagnosis. If the timing is not right, the community costs nothing.