Client: Minna Thomas
Business: Freelance WordPress Developer
Location: Kochi, India
Timeframe: January – June 2026
Note on figures: Minna shared her invoicing spreadsheet and Ucartz support ticket history for this write-up. Revenue and support figures come directly from those records. Wherever a figure is an estimate rather than a logged value, the case study identifies it as such.
Author’s note: This case study is based on interviews with Minna Thomas and documents she voluntarily shared, including invoices, support history, and hosting records. Some financial figures have been rounded for readability, as noted where relevant.
The Background
Minna had spent four years building WordPress hosting websites for local businesses in Kochi, including bakeries, boutique clothing stores, dental clinics, and logistics companies. ; bakeries, boutique clothing stores, a couple of dental clinics, one small logistics company. Every project ended with some version of the same question:
“Can you also host my website?”
For years her answer was the same: point them to a third-party host, send an affiliate link, move on. But hosting problems don’t respect job titles. When a client’s site went down, they called Minna, not the hosting company.
The Problem
By January 2026, Minna was managing 32 client websites spread across 6 different hosting providers, based on her own account of who she was invoicing and supporting at the time. Her recurring pain points, tracked loosely in a notebook before this project started:
- An estimated 7–9 hosting-related support messages a week (Minna’s own count, not a formal log)
- No recurring revenue; income stopped the day a project shipped
- 6 separate dashboards to check on client sites
- Time lost mediating between clients and hosting company support queues
She was doing the work of hosting support without being paid for it.
The Turning Point
In February, a long-term eCommerce client’s site slowed to a crawl during a weekend sale. The hosting provider blamed the site’s plugins. Minna suspected that wasn’t the real cause, but without server-level access she couldn’t prove it.
She spent close to five hours that Saturday going back and forth between the client and the hosting provider’s support chat. By her own estimate from the store’s analytics dashboard, the slowdown likely cost the client somewhere in the range of ₹30,000–₹40,000 in abandoned checkouts. She didn’t have exact figures, since she wasn’t the one running the store’s payment reports.
That evening she decided: if she was already responsible for the support, she should own the hosting too.
Looking for the Right Solution
Minna spent about two weeks comparing providers, mostly at night after client work. She seriously evaluated three reseller options before deciding.We haven’t named the other two providers because this comparison reflects Minna’s personal evaluation rather than a formal benchmark. Without a rigorous side-by-side comparison, naming them wouldn’t be fair.
| Provider | Why it was rejected |
|---|---|
| A well-known budget host | Cheapest option, but no free migration support and a shared-only architecture with no NVMe tier |
| A mid-tier reseller brand | Good features, but WHM access was locked behind a higher-priced plan than she wanted to start with |
| Reseller Hosting | Matched her checklist at a starting cost she could justify, and included migration support in the base plan |
Her checklist: white-label branding, WHM/cPanel access, NVMe storage, straightforward account creation, free migration for her 32 existing sites, and support she could actually reach on a weekend.
The Migration And What Actually Went Wrong
She budgeted two weekends. It took closer to three.
Week 1: Purchased the reseller hosting plan, built three packages (Starter, Business, WooCommerce), and began migrating the simpler brochure sites first.
Week 2: Requested migration for the remaining sites. This is where things got messy, in fairly ordinary ways:
- Two sites had DNS propagation delays of up to 18 hours, meaning those two clients technically saw a brief mismatch between old and new nameservers.
- One WooCommerce store had a plugin conflict with a caching module that broke checkout for about two hours until Minna and Ucartz support tracked it down.
- Email migration for one client’s custom mail setup took an extra two days because of an old SPF record she’d forgotten was still pointing at the previous host.
None of this was catastrophic, and nothing was unrecoverable, but it wasn’t the clean weekend she’d planned for. Of the 32 sites, 27 migrated with no visible disruption; the remaining 5 had issues ranging from a few hours to two days before being fully resolved.
Week 3 was mostly cleanup reissuing SSL certificates on two domains and updating a handful of hardcoded absolute URLs that had broken after the move.
Small Moments That Built Confidence
A Monday morning. A new client, a small physiotherapy clinic, signed off on a website proposal. Minna created a hosting account in WHM and had login credentials in the client’s inbox within about ten minutes. no affiliate link, no third-party signup form.
A Wednesday. A client accidentally deleted a folder of product images. Instead of opening a ticket with a company that had never heard of the client before, Minna contacted Ucartz support directly. Files were restored from backup the same day.
A Friday. Checking her invoicing spreadsheet, Minna noticed hosting subscriptions had started showing up as a line separate from project fees , not a huge number yet, but one that hadn’t required a new sales pitch to generate.
What the Revenue Actually Looks Like
By month six, Minna’s hosting book broke down like this. The original 32 clients were joined by 9 new hosting customers who signed up for hosting directly (rather than being referred elsewhere), bringing the total to 41 hosted accounts:
| Package | Clients | Monthly Fee (₹) | Monthly Revenue (₹) |
|---|---|---|---|
| Starter | 20 | 600 | 12,000 |
| Business | 14 | 900 | 12,600 |
| WooCommerce | 7 | 1,800 | 12,600 |
| Total | 41 | — | ₹37,200 gross |
Against that gross figure, her actual costs (rounded to the nearest ₹10 based on her invoicing spreadsheet):
- Reseller hosting plan cost: ~₹8,500/month
- Payment gateway fees (roughly 2% of gross): ~₹740/month
- Time spent on hosting admin/support (self-estimated, unpaid): ~4 hours/month
That puts her net recurring margin at roughly ₹27,960/month before accounting for her own time which is a meaningful number, but noticeably less impressive than a bare “₹37,200 in revenue” headline would suggest. She considers her own admin time the real ongoing cost, since it’s the thing that could grow if her client count doubles.
Performance, With Actual Numbers
Minna ran GTmetrix tests on three representative sites before and after migration, rather than relying on general “it feels faster” impressions: the bakery’s brochure site (Starter), the physiotherapy clinic’s site (Business), and the WooCommerce clothing store (WooCommerce). Tests were run from the same GTmetrix test location (Mumbai), on default settings, with cache cleared beforehand, after DNS propagation for each site had fully completed. Each figure below is the average of three separate test runs per site, taken on the same day of week to reduce traffic-timing variance:
| Metric | Before (avg. of 3 sites, 3 runs each) | After (avg. of 3 sites, 3 runs each) |
|---|---|---|
| Time to First Byte (TTFB) | ~780 ms | ~260 ms |
| Largest Contentful Paint | 3.4s | 1.9s |
| Uptime, measured via UptimeRobot (5-minute interval monitoring set up by Minna) | ~99.2% (30-day window, prior host) | ~99.9% (30-day window, Ucartz) |
She notes these are three sites, not all 32, and that results varied; the WooCommerce clothing store, which carries heavier plugin bloat, saw a smaller improvement than the other two, since part of its slowness was clearly coming from the plugin stack rather than the server itself.
Business Impact After Six Months
Support load: Hosting-related support messages dropped from an estimated 7–9/week to roughly 2–3/week. Minna attributes this mainly to two things: fewer outages (since the previous host’s shared infrastructure had noticeably more downtime), and the fact that she now resolves most issues herself in WHM instead of waiting on a third party’s queue which also means fewer messages arrive in the first place, since clients aren’t following up on stalled tickets.
Client retention: Among the 41 hosted accounts, she recorded zero client losses over the six months, compared to 4 losses in the same period the prior year though she’s cautious about over-crediting hosting alone for this, since overall client relationships and support responsiveness likely both played a part.
New signups: 9 new clients signed up for hosting directly, rather than being referred elsewhere.
Client Feedback
From the physiotherapy clinic client:
“Before this, our email issues sometimes took two days to sort out because nobody knew who was actually responsible. Now if something’s wrong, Minna usually has it fixed within an hour, because she’s the one who can actually log in and look.”
From the WooCommerce store owner, referencing the plugin conflict during migration:
“There was a bumpy couple of hours during the move when checkout broke, which wasn’t great timing. But it got fixed the same day, and it hasn’t happened since so I’d rather deal with that once than keep dealing with slow support every month.”
Addressing the Obvious Questions
What happens if Minna stops freelancing?
The hosting accounts are tied to her reseller account, not to her individually but she acknowledges this is a real dependency risk for her clients, and one she hasn’t fully solved. It’s a fair concern for anyone considering a similar setup.
Can clients leave if they want to?
Yes , cPanel accounts are portable, and backups can be exported. Minna has migrated one client away from her hosting (to an in-house server the client’s parent company set up), which she mentions specifically because it undercuts the idea that this is a lock-in arrangement.
What if reseller hosting has an outage? It has happened once, for about 40 minutes in April, affecting a subset of accounts on a shared node. Minna refunded the affected clients’ hosting fee for that month as a goodwill gesture, which wasn’t required by her plan’s SLA but was small enough to be worth doing.
Lessons Learned
The migration wasn’t as clean as planned, the revenue is smaller once costs are subtracted, and not every client outcome was directly caused by the hosting switch. But the core shift held up: Minna stopped referring clients to companies that kept the recurring revenue, and started keeping that relationship and that income herself.
Is Reseller Hosting Right for You?
This applies to anyone already fielding hosting questions without getting paid for it: WordPress developers, web design agencies, freelancers, digital marketing agencies, IT consultants, and managed service providers.
If you’re already answering “can you host it too?” for free, reseller hosting is a way to get paid for the answer with the understanding that it comes with real operational overhead (support time, occasional migration headaches, and infrastructure dependency) rather than being a purely passive income stream.
In Minna’s case, those capabilities- white-label branding, WHM/cPanel access, NVMe-backed servers, migration assistance, and 24×7 technical support were the specific features that made her reseller model practical, rather than a list of abstract selling points.
FAQ
Q: How long does migrating existing client websites actually take?
For Minna, it took roughly three weekends rather than the two originally planned. Of 32 sites, 27 moved with no visible disruption; 5 had issues (DNS delays, a plugin conflict, an email migration snag) that took between a few hours and two days to fully resolve.
Q: Is the reported revenue the actual profit?
No. Gross hosting revenue was ₹37,200/month; after the reseller plan cost (₹8,500) and payment processing fees (~₹740), net margin was closer to ₹27,960/month, before accounting for unpaid admin time.
Q: Did performance actually improve, or is that just marketing language?
Minna tested three representative sites with GTmetrix before and after migration. TTFB dropped from ~780ms to ~260ms on average, and uptime improved from an estimated 99.2% to 99.9%. Results varied by site , one plugin-heavy site saw limited improvement regardless of hosting.
Q: What if something goes wrong technically – does the developer need server admin skills?
Not for account-level management. Minna handles WHM/cPanel tasks herself and relies on Ucartz’s 24×7 support for anything deeper, including the plugin conflict and DNS issues encountered during migration.
Q: Can clients leave if they’re unhappy?
Yes. cPanel server management accounts and backups are portable. One of Minna’s 41 hosted clients did move to different infrastructure during this period, which she notes specifically to avoid implying a lock-in setup.
Q: What happens if the reseller hosting itself has downtime?
It has, once , a 40-minute outage in April affecting a subset of accounts. Minna refunded the affected clients that month’s hosting fee, though this wasn’t contractually required.
