Hit a wall trying to build a free website: when is it time to go pro?

Look at it from a client's perspective: someone ordering a 2000 Euro solid wood dining table isn't going to trust a website sitting on a random platform's subdomain and hand over a deposit. You pay for that free service tenfold with the first client you lose.

The technical limitations aren't just ads. On free plans, SSL certificates sometimes fail to renew, server response times are terrible, and most importantly, you can't integrate structured schema data with your Google Maps business profile.

Last year I was paying 22 Euro a month for a website builder for my plumbing business in Marseille. In the second year I paid 60 Euro for hosting plus 12 Euro for a domain and switched to an open-source setup. My annual bill went from 264 Euro down to 72 Euro.

free tools are total bait feels easy at first then you want custom email they ask for money you want an uplad form they say upgrade your plan just switch to your own host and dont waste time imo.

Self-hosting might be 70 Euro a year, but if you lack technical know-how, you'll spend hours dealing with updates, patching security holes, and tweaking the layout. Are you factoring in the hourly value of your own time?

Register a domain tomorrow and set up a basic business email right away. Even if you can't rebuild the entire website yet, sending quotes from a professional email address will immediately ease trust issues.

Under French commercial regulations, business websites must clearly display legal notices, company registration numbers, and data processing policies. Free website builders don't always give you the flexibility to manage these mandatory legal disclosures properly.

went through the exact same thing in crraftsmanship trades like carpentry your portfolio photos are everything. its frustrating when platform ads pop up right over your work. build your own clean site you wont regret it.

The answer above hits the nail on the head. Implementing a change request process doesn't slow things down, it speeds them up.

Proven by experience.

i disagree with you on this point but implementing a change request process doesn't slow things down, it speeds them up.

thats all, sorry if I went on too long.

I'm in the same situation, that's why I'm asking. Implementing a change request process doesn't slow things down, it speeds them up.

I'm a small business, let me explain from my side. If you don't write this down from the start, it leads to arguments later.

If I were you, I'd go this route.

My question might sound amateurish, sorry about that. When making a decision, first look at what data you have on hand.

Good luck with that.

quick summary for newcomers: In legacy systems, the most expensive thing is unknown dependencies.

if you have questions write them; I'll anser as best I can.

do you think this works at any scale? when making decisions wrrite down the worst-case scenario too not just the best.

The cheap-looking path usually ends up costing more later. Just because everyone does it doesn't mean it's right.

That's all, sorry if I went on too long.

Three different views emerged, they all complement each other. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

Just because everyone does it doesn't mean it's right. Good luck with that.

I'm writing this so you don't make the same mistake. In legacy systems, the most expensive thing is unknown dependencies.

Of course, it varies if your situation is different.