What carries over
| What you did as a technical support engineer | Where it shows up now |
|---|---|
| Fixed DNS and SSL tickets | Keep domains and certificates healthy |
| Cleaned hacked sites | Offer security checks in the plan |
| Explained server limits | Advise owners on the right hosting plan |
| Followed SLAs | Set response times in your care plan |
What is new
- Writing a care plan with a clear list of what is included.
- Sending a monthly report a site owner can read in two minutes.
- Agreeing access, backups and payment in writing.
Try it: Who Owns This Fix
Decide which fixes your care plan covers and which the host handles.
Who Owns This Fix
Your first proof in 30 days
Run one month of care on a real site with permission and send the owner a one-page report. Keep the checklist and report as your sample.
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
Worries, answered
I have never had my own clients. Start with one owner you know; a sample report does most of the explaining.
What about hosting? Recommend hosting; you do not need to resell it to run care plans.
Pay, honestly
We haven't verified pay data for this route. Care plans are often paid monthly by clients, so price by the work and risk per site and agree it in writing.
Your realistic 90 days
You worked as a technical support engineer. This plan moves you toward your first WordPress care clients in 90 days, using what you already do.
Assumes 2–3 hours a day alongside finding clients, a laptop and a phone, and free plans only. Every step has a smaller version and a way to pause. Use them. It runs in three blocks of 30 days, each ending with a signal that you're on track. A signal is not a promise of clients or income.
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | List 10 site owners you know | 10 names |
| 2 | Pick one who will let you look after their site | 1 yes |
| 3 | Take a full backup and test a restore on staging | Restore tested |
| 4 | Read the WordPress hardening guide | Notes |
| 5 | Write what your plan includes and excludes | Scope |
| 6 | Draft a one-page monthly report | Template |
| 7 | Note 3 care plans other freelancers sell and their prices | 3 prices noted |
Days 1–30: First care month
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Run one month of care on a real site and send a one-page report | about 8 hours over 3 weeks | report sent | Updates and backup only. | Stop at the end of the step you're on and write two lines about where you stopped. Pick it up from those notes later. |
| Show your care report to 5 site owners | about 1 hour | 5 messages | Show it to 2 site owners. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 30: The owner of your trial site reads the report and asks a question or asks you to keep going.
Days 31–60: Pitches
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Turn your case into a one-page care plan with a monthly price | about 8 hours | plan + price | Plan only. | Put it on hold while client work takes up your time, then come back to it. |
| Pitch your care plan to 10 site owners | about 5 hours | 10 logged | Pitch 5 site owners. | Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up. |
Signal by day 60: One site owner agrees to a trial month.
Days 61–90: Your first paying clients
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Practise a 10-minute care-plan pitch for a site owner | about 2 hours | 2 practice runs | 1 run. | Optional. Skip it if the week is full; nothing later depends on it. |
| Ask 3 former colleagues for referrals to site owners | about 2 hours | 3 asks | Just one instead of 3. | Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up. |
Signal by day 90: A client pays for a second month.
Other worries
Age, a career gap, no degree, English, family pressure and savings are covered on the route page and the role page.
One search that fits your background
Most clients will come from people you already know and referrals. If you also want freelance listings, the full set of search strings for this move is on the route page. Use them on LinkedIn and in local business groups. Add your city to any of them with AND, so you see local work first.
Client-finding moves that matter for this route
- Show your sample monthly report.
- Ask site owners you know if they want ongoing care.
- Agree scope and access in writing before you start.
Fake-job traps
Watch for 'developer internships' or 'live project training' that charge a registration, laptop or certificate fee, 'test tasks' that ask you to build a full product for free, and anyone asking for an OTP, UPI PIN, a deposit or remote access to your bank before you start. Real employers never charge you to hire you. Use official domains only. Report in India at cybercrime.gov.in or call 1930; in the US, ReportFraud.ftc.gov.
Back to Support Engineer · About the WordPress Care Business route · Development hub
Quick quiz: does this path fit?
Answer each, then press Check. Every answer explains itself.
Make your Path Card
A shareable reminder of where you're heading. The day count starts the first time you open this page; quest XP comes from your log above.
Scam check before you apply anywhere
- Real job and gig platforms are free to join. Never pay a "joining" or "training" fee.
- Never share an OTP or UPI PIN — no genuine employer needs them.
- Use official domains only; type the address yourself.
- India: report at cybercrime.gov.in or call 1930.
- US: report at ReportFraud.ftc.gov.
Small steps, every day.
Each quest has a smaller version for hard weeks, and a pause button. Nothing is lost.
Keep exploring
Sources
Checked 27 Oct 2026. We opened every link below ourselves. Search volumes on this site come from OpenSEO keyword research (Oct 2026).
| What we checked | Where |
|---|---|
| WordPress Advanced Administration: backups | developer.wordpress.org |
| WordPress Advanced Administration: hardening WordPress | developer.wordpress.org |