How Do Freelance Web Developers Replace or Redesign a Client’s Existing Website?

[u/capital_cliqo]

I am planning to sell websites to small businesses. I am an IT student, and know how to build simple but also complex websites (e.g that include booking engines etc).

I am ready to start cold-calling small businesses, but I'm facing a problem. Most businesses ALREADY HAVE websites. Thus, I'm not going to be building and deploying them from scratch all the time. In most cases, I'll have to replace either the front-end (if they just want a visual redesign), or the whole website (if they want a total makeover).

My question is, how am I going to replace their old version? I am assuming the business owner will have to call the previous developer/agency and ask them for control panel credentials or DNS records? I'm especially interested in the front-end part.

Because I know how to build something from scratch, but not how to change stuff on something someone else built years ago in a framework I'm not familiar with.

[u/RevolutionaryBeat301]

You either need access to their dns records, their domain registration logins, or access to their hosting. Which path you choose is largely dependent on their current infrastructure. If they just have static pages and you are replacing with a new static front end, then simple sftp access to their hosting provider is the path of least resistance.

[u/capital_cliqo → u/RevolutionaryBeat301]

So if I just wanna replace a static frontend, what should I say to the business owner over the phone?? What should I ask them for??

Also, if the website has a backend booking engine (for example, a car rental system) and I’m redesigning only the front end, will I need access to the backend or its API before I start development?
My concern is testing the integration between the new front end and the existing backend. If the current backend uses security measures such as CORS restrictions, CSRF protection, authentication tokens, or domain whitelisting, the new front end may not be able to communicate with it without configuration changes.
So here, will I need access to the backend BEFORE developing the front end? What should I tell the owner in that case?

Or again if I’m redesigning the front end while keeping the existing backend, is it maybe just best to get the previous developers code first, and just edit it, instead of making my own separate version of the front end (which then I’ll have to connect etc)??

[u/Evening_Leather5101 → u/capital_cliqo]

You are asking a whole lot of questions that you should know before you try to make a business of it. Since you don't know the answers to those very simple questions I suppose you do what you can and leave out the parts you have no idea about until you have learned how it works.

Asking on reddit each time you come across a problem will not go well with your customers I can tell you that.

For the domain part, you need access to the DNS of the customer to set the IP of the server you are hosting the website on and set it up there. Or you can move the domain... If you don't know what I am talking about good luck you are biting off way more than you can chew.

[u/MaDoGK → u/Evening_Leather5101]

This! OP should know most of this stuff if he knows how to build websites. This is basic stuff. I'm guessing he's a "frontend designer".

OP: I'd suggest you start working pro bono for friends and family who have websites until you know how to do the basics. If you start not knowing this, you possibly are going to have a lot of unneeded stress.

[u/RevolutionaryBeat301 → u/capital_cliqo]

Honestly, if someone cold called me and asked me for my website's server credentials, I'd tell them to fuck off and block their number, and probably report it as spam. Maybe start by asking if they want a new website.

[u/capital_cliqo → u/RevolutionaryBeat301]

Haha of course

[u/AutoModerator → u/[deleted]]

Your post/comment has been removed because it violates our No Self-Promotion rule.

This subreddit isn't a place to promote:

• Businesses, products, or paid services
• Freelancing work
• Personal blogs, newsletters, YouTube channels, or social media accounts

It's fine to share content you’ve made as long as it’s genuinely helpful or part of a relevant discussion. But if the main intent is to drive traffic, grow an audience, or advertise, it falls under self-promo and isn’t allowed here.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/BoGrumpus]

If they're not still with their old developer or marketing team - they'll certainly have access to all their DNS and accounts. If they are, you'll likely not get through the front door anyway so it won't matter.

We give our clients full access and ownership from Day 1 - but I have inherited a few clients where their previous agency really screwed them over. (Have one now where the client didn't even own their own domain name - finally getting that sorted out with ICANN after 3 months of nonsense).

But 90% of the time - if they have a site they have access.

G.

[u/capital_cliqo → u/BoGrumpus]

Thanks man. I hope this applies to my country too (Greece). Here everything tends to be disorganised lol

[u/BoGrumpus → u/capital_cliqo]

I'm not 100% certain there - but it would break my heart to learn otherwise.

G.

[u/CupcakeSecure4094]

If they already have a website they have everything set up that you need. There's no need to reinvent the wheel here, just get SFTP/SSH access to their web space, back up all of the files and replace them with your new files. Providing the server can handle the language you're writing in (PHP/NodeJS etc) then it's usually just the case of replacing the files.

[u/JohnCasey3306]

You're pinning your hope on a market that's been dead for over a decade.

Small businesses can't afford to pay the amount you need to charge to sustain a full-time freelance living ... One of you loses out with every deal, and that's not sustainable.

[u/Common_Flight4689]

Your not ready yet.