Running a business
A helper and a website are two different problems
Business picked up. Congratulations. Your reward is two new headaches showing up in the same week.
You need another pair of hands. You also need a real place online where people can find you, because "ask around for the guy with the white van" only scales so far. Both feel urgent. Both cost money. So it's tempting to lump them into one big project called "getting serious."
Don't. That's how you end up with a website that's half built and a helper who's standing in the driveway Friday afternoon asking when payday is.
They're two problems. Different deadlines, different risks, different ways of going sideways. Handle them one at a time.
What each one actually is
A helper is a promise. Somebody shows up at 7, carries the heavy end, and expects to get paid on time, every time. If you blow it, a real person is short on groceries. And the paperwork has dates on it whether you're ready or not.
A website is a storefront. It sits there answering questions while you're up a ladder. If it's slow or ugly, you lose some leads. That stings. But nobody misses rent because your contact form uses a weird font.
One of these has a person on the other end. That settles the order.
People first. Pages second.
If both are on your plate, sort out the helper before you touch the website. A clunky site costs you a few calls. A missed payday costs you a good worker, plus a possible mess with the tax calendar. And good workers are a lot harder to find than website templates.
Before their first day, nail down three things:
- Employee or contractor. This isn't a label you get to pick because it makes the paperwork smaller. It depends on the actual work.
- What you're paying, and on what day. Write it down. "I'll get you squared away" is not a pay schedule.
- How the money gets to them, and where the record lives. The back of a lumber receipt doesn't count.
Payday should not live in your head walks through all of that. Read it before the first payday, not after.
Then the website, at the size it actually needs
Once payday runs without you lying awake about it, the website gets its turn. And the first question isn't which host to pick. It's what the site has to do.
If it's your name, your services, where you work, and a phone number, a website builder is probably plenty. That's a brochure. You don't need a server farm to hand out a brochure.
If it has to save form entries, run a small tool, or hold more than one site, a small rented server starts to make sense.
Either way, it doesn't live on the same laptop you do the books on. The one with the cracked corner. You know the one.
Your site should not live on your laptop gets into that choice in more detail.
The one place they overlap
Here's where the two problems shake hands: your helper is going to end up touching the website. Or at least the stuff behind it.
Picture a Tuesday. You're on a roof. A customer fills out the booking form, and your helper's the one who sees it. Next month they're updating the holiday hours. Someday they'll be the one who notices the contact form quietly stopped sending anything.
So when you set up the site, give them their own login. Not yours. Decide up front what they're allowed to change. If they move on someday, you remove one login and you're done.
The alternative is changing every password you own at 11 on a Sunday night. Nobody does that twice on purpose.
That's about as tangled as these two should ever get.
The short version
- Two problems, two projects. Don't let "getting serious" turn them into one blurry weekend.
- People before pages. Payday has a deadline. The website can wait a week.
- Size the site to the job. A builder for a brochure, a small server when the site has to do something.
- Separate logins. Your helper gets their own access, not your password on a sticky note.
Get the helper paid on time, put the site somewhere that stays awake, and neither one gets to move into your head rent free.