What Happens After Your Website Launches

The site goes live. Everyone is pleased. The invoice is paid.

Then it is Tuesday, and something is wrong, and you realise you do not know who you are supposed to tell.

Launch is not the end of a website project. It is the point where a project becomes a thing that exists, and things that exist need someone responsible for them. Almost nobody discusses this before signing, and it is one of the largest differences between studios that costs nothing to ask about.

What actually breaks

Not dramatically. Websites rarely explode. They erode.

Things get old. The software your site is built on gets updated — sometimes for security. A site left untouched for three years is running old code, and old code is how sites get compromised. Not because anyone targeted you: automated tools scan the entire internet for known holes, and they do not care how small your business is.

Things outside change. A payment provider changes their API. A courier changes their tracking format. Google changes what it wants. Your site did not change; the world moved and left it behind.

Browsers move. A phone released next year renders something slightly differently and one page looks wrong.

Certificates expire. Your SSL certificate has a date on it. When it passes, browsers show visitors a red warning that says, essentially, this site is unsafe. It is a five-minute fix and it will lose you a week of enquiries if nobody notices.

People break things. Someone pastes text from Word and the formatting arrives with it. Someone uploads a 6MB photo and the page gets slower. Someone deletes a paragraph they meant to edit.

The three ways studios handle this

Handover and goodbye. You get the files, the passwords, and best wishes. Cheapest, and legitimate if you have someone technical. The risk is not price — it is that when something breaks in eight months, you are hiring a stranger to work on unfamiliar code, and that costs more per hour than the person who wrote it.

Available, billed as needed. No monthly fee. Something breaks, you email, they fix it, they invoice. Fine for most small businesses. The question to ask is response time: "available" means nothing if it means three weeks.

Retainer. Monthly fee, agreed scope. Updates, monitoring, some hours of changes. Worth it when the site is doing real work and downtime costs money. Waste when the site is a business card.

None is wrong. What is wrong is not knowing which one you bought.

The questions to ask before you sign

Ask these during the sales conversation, not after:

"What happens if something breaks the week after launch?" There is usually a warranty period — a stretch where the studio fixes their own bugs free. Find out how long. If the answer is "we don't do that", know it.

"What if I need a change in six months?" Process or shrug. The shrug means you are starting over with someone new.

"Who has the passwords?" You should. Domain, hosting, everything. If your studio holds your domain in their account and you fall out, you have a problem that lawyers solve slowly. This happens and it is ugly.

"How fast do you reply?" Not a contract clause necessarily. But "same day" and "when we get to it" are different products.

"What if you disappear?" Nobody likes this question. Ask it anyway. Is the site built on something a normal developer can pick up, or something only they understand? This is the structural risk of hiring one person, and the answer should not be a joke.

What you should own, without argument

Whatever the arrangement:

• Your domain. Registered to you, in an account you control. Not your studio's account, not your cousin's.
• Your hosting. Same. If your studio manages it, fine — but the account is yours and you can get in.
• Your code and files. You paid for it.
• Your content. Text, images, everything.
• Your analytics. In your account, with them added as a user. Not the reverse. If any of these live somewhere you cannot reach, you do not own your website. You are renting it, and the rent is your continued relationship with someone.

The bare minimum, if you do nothing else

For a small site with no support arrangement:

1. Know where your domain is registered and when it expires. Turn on auto-renew. Expired domains are how businesses lose their website and their email in one afternoon.
2. Know where your hosting is and that you can log in. Test it now, not during an emergency.
3. Know that backups exist and where. Ask your host. Most have them. "I assumed" is not an answer that has ever helped anyone.
4. Check the site works once a month. Open it on a phone, fill in your own contact form. Broken contact forms are silent — you do not get an error, you get nothing, and nothing looks exactly like no enquiries.
5. Watch the certificate expiry. Most hosts auto-renew. Confirm yours does. Twenty minutes of setup, and it covers the failures that actually happen to small websites.

The one that catches everyone

Test your contact form. Now, from your phone, as a stranger would.

Forms break silently. An email address changes, a mail service updates something, a spam filter starts eating your own notifications. The form still submits. The visitor still sees "thank you". Nothing arrives, and nobody tells you, and you conclude your website does not work — when in fact it was working the whole time and dropping every single message on the floor.

This is not rare. Do it once a month. It costs sixty seconds.

We're DAKER, a web design and development studio in Baku working with startups and small businesses across Europe. Every site we build comes with two months of support included — and after that we stay reachable, because the person who wrote your site is the person who fixes it. Get in touch.