BLOG
After The Launch
Phase 1 and 2 are complete. Now let's dive into what Phase 3 entails: After the launch.
Jacobus van Devnter
The first part of this series was about the work before the build. The second was about the build itself. This is the final part, and it covers the phase most people forget to plan for: the work after your product is live.
Launch is not the finish line. It is the start of a different kind of work. A live product still has to find its users, keep them, get better, and prove it is moving the numbers you built it to move. Phase 3 is where that work happens.
What Phase 3 actually is
Phase 3, Marketing, Momentum and Impact, runs from the day the product goes live and onwards. Where Phase 1 gave you certainty and Phase 2 gave you a working, hosted product you own, Phase 3 gives you traction. It covers three continuous streams of work in parallel: Marketing (positioning, launch messaging, campaigns, whichever channels make sense), Momentum (ongoing iteration on the live product, small features, upgrades, fixes), and Impact (measuring what the product is doing for the business, growth tracking, retention, conversion signals).
The point of naming them separately is that they are three different disciplines, not one. Most agencies do one and call it "support."
The team you get, and why they stay
The team that built your product stays with you through this phase. No handoff to an account manager who has never seen the code, no ticket queue that treats your product as one of many. The project manager, the developers, the UX designer, and the principal software architect who shipped it are the same people driving what happens next. That continuity is what makes small changes small, and big changes possible without a rebuild. Marketing sits alongside the tech team.
What changes for you, month by month
The output of Phase 3 is not a single deliverable. It is a rhythm. A product that keeps improving each month, refined onboarding, a feature you scoped in Phase 1 as optional and now want live, a fix for something a customer flagged. A marketing motion that fits where the product is: early on the work is about finding the first users, later it is about deepening the relationship with the users you have. And growth tracking that tells you the truth: dashboards on the metrics that matter, so you know whether the product is winning or drifting.
How we work through it, the retainer
Phase 3 runs on a retainer. That word carries some baggage in the software world, so it is worth being direct about ours. You commit to an agreed number of hours per month, and those hours belong to your product. If they are not spent on the planned roadmap that month, they do not disappear and they are not pocketed. They go into optimisation, refactoring, or getting a head start on the next feature. Every hour paid for is an hour of work on your product.
The scope inside the retainer is agreed together at the start of each month, so it reflects what you actually need next, not a list from a year ago. Because the same team is on the retainer, the conversation about what to do is short. They already know your product.
How long it lasts
Phase 3 runs for as long as the product is live. What changes over time is the shape of the work inside it. In the first few months after launch the emphasis is usually on marketing and closing early product gaps. Six months in it shifts toward iteration and growth. A year in it is often about scale, new markets, new features. The retainer flexes with that. You can resize or reshape it as the product's needs change.
Why this phase matters the way it does
A product that is not marketed, iterated, or measured after launch quietly fades. Software is not a physical product. It lives in the ongoing relationship between the product, its users, and the team maintaining it. Phase 3 is where the value of everything earlier compounds. A clean Phase 1 makes iteration cheap. A disciplined Phase 2 makes optimisation possible. A trustworthy retainer makes both worth continuing. Skip Phase 3 and the money you spent in Phases 1 and 2 slowly stops earning.
Where this lands, and where this series ends
Phase 1 gave you a blueprint. Phase 2 gave you a working, hosted product you own. Phase 3 keeps that product working, keeps improving it, and keeps it earning its place. The three phases are the shape of our delivery model. A blueprint without a build is a document. A build without a life after launch is a demo. Marketing without a solid product is noise. Together, they are what it takes to actually get a piece of custom software into the world and keep it there.
