The month after go-live is when a client decides whether to trust you with the next thing, and it is exactly when most vendors go quiet. The build team rolls onto another project, the client hits the first real-world snag, and the reply is a ticket number. I now plan the first thirty days after launch as a phase of the project, with named people and its own budget line.
What does the launch month actually involve?
Real users doing things nobody on the team predicted. Real data with shapes staging never had. Volumes that make a slow query visible for the first time. All of that is normal. It is what production looks like, and no amount of staging shows it to you first.
So the phase has a shape, and it is the same five things every time:
- A named engineer on point, with a second name for cover.
- Response times for the first two weeks that are tighter than the eventual support contract.
- A ten-minute morning check of error logs and the slowest endpoints.
- A short weekly note covering what real people did and what we changed because of it.
- A launch review, booked on the calendar before launch day.
The morning check matters more than it sounds. Most launch problems announce themselves quietly, as a growing error count or a job that runs a little longer each night. Catching them on day three instead of day twelve is the difference between a message and an incident.
Why does silence in week two hurt so much?
Because the client is nervous in a way they will not say out loud. They have just told their own organisation the thing is live. Their credibility is now attached to our software. If their first email after launch gets a two-day auto-reply, that fear turns into a story about the vendor.
Compare that with a call in week two where we open with: here is what we saw, here is what we fixed without being asked, here is what we would change now that we have watched real usage. I have had that call turn a cautious client into one who asked for a roadmap conversation on the same day. Same software. Different month.
The bill that only shows up after launch
Running costs stay theoretical until real traffic arrives. Hosting scales up, storage grows past the plan, email volumes trigger a higher tier, and a third-party API moves past its free band. The first month is when a client finds out what the thing costs to keep running.
| Cost line | Why it moves after launch | What we usually do about it |
|---|---|---|
| Hosting | Real traffic replaces polite staging traffic | Right-size the instance after week two |
| Storage | Uploads and logs grow every single day | Set a retention rule, archive the rest |
| Transactional email | Volume crosses the plan's band | Change tier, or batch the notifications |
| AI tokens | Users paste whole documents into a box | Shorter prompts, caching, an input cap |
For AI features the token bill is the one that surprises people, since a feature that cost pocket change in testing meets real users who paste in whole documents. I bring the actual first-month numbers to the week-two review, next to the estimate, because a client should never learn the real bill for automation from their finance team before they hear it from me.
That conversation also decides what we tune. Sometimes a caching change or a shorter prompt cuts the bill by a third. Sometimes the answer is that the estimate was wrong and we say so.
What happens on day thirty?
A forty-five-minute launch review with the client. What broke, what surprised us on both sides, what we would do differently, and what the next ninety days should hold. It closes the build cleanly and it opens the relationship, which is the whole point.
At Shanti Infosoft I ask delivery leads to book that review before launch day, so it exists on the calendar when everyone is still paying attention. Reviews booked after launch have a way of never happening. On the SaaS products we build and keep running, the launch month is written into the plan as a phase with a name, an owner and a cost.
One more habit: I keep the launch-month engineer partly on the project for the following month too. Rolling them off on day thirty-one loses the person who knows what production actually did.
Which is scarier on your projects, launch day itself, or the quiet fortnight after it?
Written by Sonal Jain, delivery lead at Shanti Infosoft, a CMMI Level 5 team that has launched software for 700+ companies.
Top comments (0)