- Going live is the start of the work: most of the improvements come after real businesses start using the product.
- The parts nobody sees, such as email delivery, sign-in security and connection checks, decide whether people trust the product.
- Small changes that save an owner a few minutes a day often matter more than big new features.
This is a companion to how we validate an idea before we build it. That piece covers what happens before a product exists. This one covers what happened after Unavoidable CRM, our CRM with a built-in AI receptionist for small UK businesses, went live.
Is launch day the finish line?
No. Launch day is the first day you start learning properly. Before it, every decision is a guess about how people will use the product. After it, you can watch. The CRM went live in July 2026, and its public changelog has kept growing ever since, with several changes shipped in the first week of October alone.
That pace is only possible because the studio runs every product on one shared platform for sign-in, billing and hosting, so a fix or improvement does not mean rebuilding the foundations. We explain how that works in shared infrastructure across a studio.
Why does the plumbing matter so much?
Because people judge a product by whether it quietly works, not by its feature list. A CRM that sends a booking confirmation which lands in spam, or that loses its link to your phone line without telling you, loses trust fast, however clever the rest of it is.
A good share of what we shipped after launch is work customers will never see directly:
- Email delivery. In September all of the system's transactional emails moved to Postmark, a service built for that job.
- Sign-in security. Failed log-in attempts are now throttled per email address and cleared after a successful sign-in.
- Connection health checks. Since 1 October the CRM watches its connections to a customer's website, Twilio, Retell, Stripe and Postmark, so a broken link is spotted rather than discovered by a missed booking.
None of these makes a good screenshot. All of them make the product more dependable, and that is what keeps people using it.
Should people be able to try it before they sign up?
Yes, and as early as possible. The CRM offers a 14-day free trial, but a trial still asks someone to create an account before they know whether the product suits them. On 7 October we added a free demo with no sign-up at all, so a business owner can click around a working CRM first.
The lesson is simple: every step between curiosity and use loses people. The fewer things someone has to commit to before they see the product working, the fairer the test of whether it is right for them.
What do busy owners actually need from a product?
Mostly, they need it to save them time without asking for attention. The people we build the CRM for are owner-operators who are usually doing the work themselves. They do not want another dashboard to check. They want the right thing in front of them at the right moment.
Two recent changes came from that idea. A new Today page puts website orders, tasks due, appointments, text replies and new contacts for the day on one screen. And owners and admins now get an email whenever a customer texts in, so a reply does not sit unseen in an inbox nobody opened. Neither is a big feature. Both remove a small daily chore, and those add up.
How do real users change the roadmap?
They pull it in directions you would not have planned on your own. Once businesses with online shops and bookable packages started using the CRM, the changelog filled up with work for them: instant order updates from WooCommerce so new orders land in the CRM within seconds, purchase tags for product options, and booking sections so one confirmation email can cover each package, weekend or extra.
None of that was on the original plan. It is the kind of detail you only learn you need once real businesses run their days on the product. The skill is telling the difference between a request that helps many customers and one that only suits a single case, which is a question we come back to in running several products with a small team.
Why write every change down in public?
Because it keeps us honest and it helps customers. A public changelog shows people the product is alive and improving, tells them what has changed before they stumble on it, and gives us a record of what we actually shipped rather than what we meant to. It is one of the simplest ways we build in public.
What would we tell another small team?
- Plan for launch to be the start of the work, and keep time free for what you learn in the first weeks.
- Spend real effort on the parts nobody sees: email delivery, sign-in security and the connections your product depends on.
- Let people try the product before they commit, with as few steps as possible.
- Look for small changes that save your users a few minutes every day.
- Write every change down where customers can see it.
You can see every product the studio runs on our portfolio page, or browse the rest of the blog.
Questions
When did Unavoidable CRM go live?
In July 2026. It is built and owned by Unavoidable Studio Ltd in Leeds and is in use by UK small businesses.
What changed most after launch?
The reliability work nobody sees, such as email delivery and connection health checks, and small time-savers like the Today page and alerts when a customer texts in.
Where can I see what has shipped?
Every change is listed with its date on the Unavoidable CRM changelog.
Founder of Unavoidable Studio, a UK venture studio in Leeds building six software companies at once. Answers his own inbox.