Do it yourself or hand it off? A 10-question PHP checklist

Why decide by your site's conditions, not your skills?

Because the same person can find the job easy on one site and risky on another. How your host handles versions, your backups, custom code and customer data are what decide the outcome.

Most small businesses don't have a security person on staff, and budgets are tight. In a 2025 survey of 291 US small business professionals commissioned by CrowdStrike, two-thirds said cost keeps them from upgrading security tools, and "only 7% believe their current budget is fully sufficient." The same survey found that "70% of SMBs rely on outside experts to guide security decisions."¹ Leaning on outside help is the norm, not the exception.

Hesitating is natural, too. Research on help-seeking describes "a threat to self-esteem caused by the perceived inadequacy": asking for help can feel like admitting you're not good enough, so people put it off.² But handing something off isn't a confession; it's a judgment call. Nobody says a business owner who uses an accountant doesn't understand numbers.

1. Do it yourself: your conditions are good. Plan half a day and do it in-house
2. Share the work: get help with the hard parts, like backups and testing, and do the rest yourself
3. Hand it off: you hit a red question. Hand off the work, but keep the accounts in your name

All three are right answers. The right one is the one that fits your conditions.

Conditions, not courage.

Jeensuk's take"I should be able to do this myself" and "I don't know enough to try" are both poor reasons. The reason should be your website's conditions.

The 10-question checklist: what do you need to answer?

Answer each statement below with yes or no, and count your yeses. Count "not sure" as no. Questions 2, 6 and 9, marked red, are looked at separately.

These ten questions and the score ranges below are ATATAKAI Digital's own criteria, based on how the work actually goes. They are not an official standard from any government or hosting company. Host details are as of October 25, 2026.

Jeensuk's takeIt's fine to have a lot of "not sure." Just knowing which boxes you can't fill tells you who to ask, and what.

How do you read your score?

First check whether all three red questions (2, 6 and 9) are yes, then count your yeses. If any red question is no, we recommend handing it off, whatever your count.

1. Do it yourself: all red questions are yes, and you have 8 or more yeses. Go ahead and do it yourself. There's no need to hand it off.
2. Share the work: all red questions are yes, and you have 5 to 7 yeses. Get help only with the boxes that came up no.
3. Hand it off: 4 or fewer yeses, or a no on any red question. Hand off the work, and keep the accounts and contact details in your name.

The culprit is almost always a plugin or an active theme. — Kinsta, "How to update the PHP version in WordPress"

Jeensuk's takeEven a cold sends you to the doctor at 104 degrees. The red questions are that 104.

If you do it yourself, where do you start?

Block half a day on your calendar and stick to this order: back up, update, test, switch, check. It's the same order WordPress.org lays out.⁶

Back up your files and database together, right before the upgrade.⁵ Switch the version from your host's menu. If you get a white screen, don't panic: switch back to the previous version first, then look for the cause. Our host-by-host guide, white-screen guide and upgrade timetable are coming soon in English.

Jeensuk's takeIf your conditions are good, doing it yourself is the best way to learn. Once you've done it, the next version is much lighter.

If you share the work, how do you split it?

Hand off only the boxes that came up no, and do the rest yourself. Backups and staging sites are the least familiar parts for first-timers, so getting help with just those two is a good place to start.

For example, if questions 3 and 4 (backups and rolling back) were no, practice taking a backup and rolling back together with a pro, then switch the version yourself. If question 7 (staging) was no, hand off only the testing on a staging copy. Splitting it this way costs less, and someone at your company learns how to do it.

Jeensuk's takeHelp isn't all or nothing. You can borrow just the one hard box.

If you hand it off, what should stay in your hands?

Hand off the work, but keep the domain and hosting accounts, the registrant contact details, and at least one WordPress admin account in your company's name. That way, your website stays yours even if the vendor changes.

If the accounts are in the vendor's name, getting them back takes time if you ever lose touch. Before you hire anyone, ask about the scope of the work, how they back up and roll back, what they'll check afterward, and what it will cost when the same job comes around again. Our guides to the five website keys and to getting your site back from a lost developer are coming soon in English.

If upgrading PHP every few years is a burden, you can also compare moving to a website that doesn't run on PHP at all.

Jeensuk's takeHand off the work, not the keys. A good vendor is one that hands the keys back to you.