Thursday, November 19, 2026← Weras Labs main siteTürkçe
WerasBlog

What's happening in AI, software, technology and science; plain and sourced.

Subscribe
Software

Software Launch Checklist: 40 Things to Check Before You Go Live

Most launch-day surprises come from small steps someone forgot. Here's a checklist, organized by topic, to run through before you take your web app live.

Software Launch Checklist: 40 Things to Check Before You Go Live
Image: SpaceX · Unsplash · Unsplash License

A software launch checklist is a list you use before taking a web app live to confirm that no critical step has been skipped across security, performance, data, legal compliance, search visibility, monitoring, and communication. Most launch-day problems don't come from complex bugs. They come from forgotten small steps: a domain that wasn't pointed, an email that never sent, a backup that wasn't taken. The list below is a starting point you can adapt to your own project.

Before launch: planning

A few decisions need to be made before you get to the checklist:

  • Launch date and time: If possible, don't schedule it right before a campaign that will bring heavy traffic; pick a working day when problems can be dealt with. A Friday evening launch can mean spending the weekend firefighting if something goes wrong.
  • Owners: Who will be on hand on launch day, and who makes the call if something breaks?
  • Rollback plan: If there's a serious problem, how do you get back to the previous state?
  • Soft launch: Can you open it to a limited group of users first?

The rollback plan is usually the most neglected part. Before launch, have written answers to these questions: How many minutes does it take to roll back to the previous version? Can database schema changes be reversed? What happens to new records created during the launch if you roll back? If you're replacing an old system, keeping the old one available in read-only mode for a while after launch gives you a safety net to fall back on.

A soft launch is also an effective way to reduce risk. Opening the app first to internal users, then to a few selected customers, and finally to everyone lets you see problems from real-world use with a small group. Asking users for direct feedback at this stage also surfaces issues analytics can't show you.

Software launch checklist: technical items

Infrastructure and domain

  1. The domain points to the right server and DNS records have been checked.
  2. The HTTPS certificate is active and all HTTP requests redirect to HTTPS.
  3. Either the www or the non-www address has been chosen as primary, and the other redirects to it.
  4. Production environment variables and API keys are set correctly and kept separate from the test environment.
  5. Domain, hosting, and service accounts are in the company's name, and you have access.

Security

  1. Admin accounts are protected with strong passwords and two-factor authentication.
  2. Test and demo accounts have been removed or disabled.
  3. It's been tested with different roles that users can only access their own data.
  4. Login and form endpoints have rate limiting against abuse.
  5. Error messages don't show users technical details or secrets.
  6. Libraries in use have been checked for known security vulnerabilities.

Data and backups

  1. Automatic database backups are switched on.
  2. Restoring from a backup has been tested at least once.
  3. Data migrated from the old system has been spot-checked.
  4. Test data has been cleared out of the production database.

Performance

  1. Key pages load in a reasonable time on mobile devices and slow connections.
  2. Images are served at appropriate sizes and formats.
  3. Indexes exist for frequently used database queries.
  4. A basic load check has been done for the expected number of users.

Email and notifications

  1. Transactional emails (sign-up, password reset, order confirmation) are sending in production.
  2. SPF, DKIM, and DMARC records are configured for the sending domain.
  3. Emails reach inboxes at different email providers without landing in spam.

Monitoring

  1. An error tracking tool is connected to production and alerts go to the right people.
  2. Uptime monitoring checks whether the server and app are up.
  3. Analytics is set up and the key conversion steps are being measured.
  1. The privacy policy and data protection notice (in Turkey, the KVKK disclosure) are live and linked from the relevant forms.
  2. Unchecked consent boxes and a recording mechanism exist for processing that requires explicit consent.
  3. Cookie preferences prevent non-essential cookies from loading without consent.
  4. Terms of service and, where applicable, distance selling texts are live.
  5. If you take payments, the payment provider's live mode has been approved and tested with a real transaction.

Search and social sharing

  1. Every page has a unique title and meta description.
  2. A sitemap has been created and submitted to the search console.
  3. robots.txt doesn't block search engines in production (the block from the test environment has been removed).
  4. If you're migrating from an old site, old URLs permanently redirect to the new ones.
  5. Social sharing images and titles (Open Graph) display correctly.
  6. A custom 404 page exists.

Communication and support

  1. There's a clear support channel where users can report problems.
  2. Your team has had a short training on the new system.
  3. Existing users, if any, have been told about the change in advance.
  4. A priority bug-fix plan is ready for the first days after launch.

Launch day flow

Running launch day in a simple order reduces stress:

  1. Take a final backup.
  2. Deploy, then quickly try the main flows in production (sign-up, login, the core action, and payment if there is one).
  3. Watch error tracking and server metrics closely for the first few hours.
  4. Announce it to your team and, if needed, to users.
  5. Collect incoming feedback in a single list and prioritize it.

The first weeks after launch

Launch isn't an ending; it's when the product meets real users. In the first weeks:

  • Track where users get stuck using analytics and feedback,
  • Fix critical bugs quickly and plan small improvements for the next release,
  • Keep an eye on performance and error rates,
  • Settle the post-launch maintenance and support arrangement.

Sorting requests from the first weeks into "bug," "improvement," and "new feature" also makes life easier. Bugs get handled quickly under warranty or maintenance, while improvements and feature requests can be collected, prioritized, and turned into the scope of the next release. That way every request that arrives in the post-launch excitement gets considered without derailing the plan.

Finally, hold a short retrospective a few weeks after launch: What went to plan, what was a surprise, and what will you do differently next time? Adding the outcomes to your checklist makes every launch calmer than the last.

Conclusion

This software launch checklist won't fit every project exactly, but its sections apply to most web apps. Reviewing it a few weeks before launch and sharing it with the people responsible turns launch day into a calm operation. At Weras Labs, launch and post-launch support are a standard part of the process; you can see how we work on our services page, or get in touch about a project that's getting ready to launch.

#launch#checklist#web app#deployment

From Weras Labs

We can help you with this

We turn what you just read into working software for your business. You talk to the person writing the code; price and timeline are clear from day one.

Frequently asked questions

What's the best day to launch software?

Pick a working day when problems can be addressed quickly. Launching right before a weekend or just before a big campaign makes it harder to fix any issues that come up.

What is a soft launch?

It means opening the app to a limited group of users first. That way, problems that show up in real-world use can be found and fixed before every user is affected.

Why are backups so important on a launch checklist?

If something during or after launch causes data loss, a working backup is your only safety net. Taking backups isn't enough; restoring from one must have been tested at least once.

Should the test environment be shut down after launch?

Usually not. Keeping a separate test or preview environment for trying new features before they go live is recommended, but it should be hidden from search engines and contain no real personal data.

About the author

Habip Dayan

Habip Dayan

Founder of Weras Labs

Habip Dayan is the founder of Weras Labs, a company that builds software products for professionals and teams. He has been building software since 2018 and writes about AI, cloud architecture and product design.

Comments

Be respectful; no ads or personal data. Comments that break the rules are removed.

Software Launch Checklist: 40 Items