Rewrite, or keep building?
A founder had built an app, a ticket page and a venue site himself, on two backends joined by a hand-written bridge. He could not tell which way to go.
“I thought a discovery sprint was going to be high-level reassurance. It was way more valuable than I expected. It gave me a clear roadmap with confidence and clarity.”
Context
A London events start-up connecting communities with venues. The founder had built all of it himself since 2023: a mobile app, a ticket page and a venue website, on two separate backends joined by a hand-written bridge. He had just got clear on what set the business apart, and wanted the technical foundations right for the growth ahead.
Challenge
He couldn’t decide whether to rewrite or keep building. Every fix felt as if it might break something else, and there were no tests, no staging environment and no backups. He didn’t want a developer taking instructions. He wanted someone who understood the business and could turn commercial decisions into technical choices.
What I did
A two-week discovery sprint, run while a festival ticket release was live, so nothing could be touched without care. For each decision I set out the options, what each meant for the business, and my recommendation, and the founder made the final call. Two things didn’t go to plan: Stripe’s payment confirmations weren’t reaching the server, and a scheduled job had been failing every minute since January without anyone knowing. Making the live ticketing solid became the first phase. The report set out seven goals, a target architecture and a seven-phase roadmap, written so the founder could explain every decision himself.
Outcome
The answer was neither a rewrite nor more of the same. Keep the front end and the payment logic, and rebuild the backend around one database and one central layer. The first phase is done, and he’s now building the foundation himself with AI, working from the technical specification.
What came out of it
- Rewrite-or-keep decision for an events platform, settled in a two-week discovery sprint
- Business decisions turned into technical options, with the founder making the final call
- Payment and scheduled-job failures found and made the first phase of the roadmap
- Seven goals, a target architecture and a seven-phase roadmap a non-technical founder can explain himself
- First phase done, and the founder now building with AI from the specification