How I Turned a Patch-Fix into a $700 Rebuild for a UAE Healthcare Provider

A common tension in sales, especially in technical fields like web development, is the client's desire for a surgical repair versus the professional's knowledge that the patient needs a total transplant. Beginners often fall into the trap of agreeing to a "quick fix" because they fear losing the deal by proposing a larger, more expensive scope. They think they are being helpful, but in reality, they are setting themselves up for a project that will inevitably break again, damaging their reputation.

I recently sat down with Tolu, an entrepreneur running a high-stakes home healthcare business in the UAE. He came to me with a specific, seemingly simple request: "I need you to fix my e-commerce checkout flow." He wanted his website to function like his biggest competitor, Vallejo. He was focused on the surface—the buttons, the landing pages, and the user experience. But as we pulled back the curtain, it became clear the foundation was on fire.

Diagnosing the Silent Killer

Tolu’s business is impressive. They offer doctors on call, IV therapy, and laboratory services. This is a high-trust industry. However, the moment I looked at his backend, I saw red flags. His WooCommerce plugin was outdated and vulnerable. API keys were accessible to the public. His blog had even been hijacked by Russian hackers.

Tolu was initially resistant to a redesign. He had just paid another company to do one, and the "look" of the site was modern. He told me, "I don’t want to redesign the website. Security is in the backend, not the look and feel." This is where many salespeople fold. They agree to just "patch the security" to keep the client happy.

I chose a different path.

"I realized Tolu didn't need a designer; he needed a protector for his business foundation."

I didn't argue about the design; I agreed the layout was good. But I insisted on a ground-up rebuild. I explained that we would keep his visual identity—the colors, the fonts, and the general vibe—but rewrite the "DNA" of the site on a clean foundation. By framing it as a rebuild rather than a redesign, I addressed his technical debt without dismissing his previous investment.

Why the Deep Fix Wins the Deal

In sales psychology, we often deal with the "Endowment Effect," where people overvalue what they have already invested in. Tolu valued his recent "redesign." By suggesting a "rebuild from scratch," I was initially threatening that investment.

I had to pivot the conversation toward Future-Proofing. Industry research shows that 88% of online consumers are less likely to return to a site after a bad experience, and for a medical business, a security breach is a terminal event for brand trust. I shifted his focus from the cost of the rebuild to the cost of a total system failure.

I used a simple logical bridge:

• Acknowledge the Asset: I praised the existing layout and his drive to beat competitors.

• Expose the Risk: I shared my screen and showed him the live vulnerabilities. Seeing the Russian blog posts made the abstract threat of "security" very real.

• The "Same Look, Better Engine" Promise: I promised that the user wouldn't see a change in branding, only a massive increase in speed, security, and checkout efficiency.

Handling the "Maintenance" Trap

As we moved toward the close, Tolu asked for a monthly retainer. This is another area where beginners often stumble, either by overcharging for nothing or undercharging for too much work.

I was honest with him. I told him that because we were rebuilding the site correctly from the ground up, there shouldn't be much to "maintain" in the first few months. Instead of locking him into a paid retainer immediately, I offered 45 days of post-delivery support for free. This built immediate trust. I explained that minor changes like swapping a photo or a heading are part of my service, while new functionalities would be handled as separate, discounted projects.

This transparency shifted the dynamic. He stopped seeing me as a vendor trying to extract a monthly fee and started seeing me as a partner invested in the site’s actual performance.

Practical Reflection for Beginners

If you find yourself in a situation where a client wants a patch but needs a replacement, you must lead with diagnostic proof. Beginners often rely on "trust me." Experts rely on "here is why it is currently broken."

When you encounter resistance, don't push against the client's goal—push against their method. Tolu wanted a seamless checkout. I showed him that a seamless checkout is impossible on a compromised foundation. I didn't change his goal; I changed the roadmap. Always anchor your technical recommendations in the client's ultimate business outcome—in this case, securing patient trust and driving sales.

Frequently Asked Questions

How do you tell a client their previous investment was a waste without offending them?

You don't call it a waste. You acknowledge the value of the vision they created, then explain that the technical implementation hasn't kept pace with that vision. Frame your work as the missing piece that finally makes their previous investment functional.

What if the client strictly insists on only the small fix?

You have to decide if you want to be responsible for the inevitable collapse. It is often better to lose a small, "patch-work" deal than to win it and have your name attached to a site that crashes or gets hacked a month later.

Why offer 45 days of free support instead of a paid retainer?

Integrity builds long-term accounts. If the site is built correctly, there is very little maintenance to do in month one. By offering support for free, you prove you stand by your work. When the client eventually needs a major update, you are the only person they will call.

---

I have sent the itemized proposal to Tolu, covering the 15-page rebuild and the seamless e-commerce integration for $700. By being firm on the "how" and flexible on the "what," we moved from a minor fix to a full-scale partnership. And this is how the deal was closed.

If you want to learn sales through real decisions instead of theory, you’ll find more of these breakdowns as I keep documenting my work.