Before Platform v2, I was effectively the only frontend engineer: the product, the marketing websites and everything customers clicked on. 671 of the 693 commits to the main app in that period were mine.
A marketing website that scored 38/100 in an SEO audit, and no single map of the product's API.
A rebuilt website on Next.js 15 and React 19 with schema, canonical tags, llms.txt and redirects, plus an API collection with 132 endpoints.
The problem
One engineer, two products: an enterprise app that every new customer wanted to sign in to their own way, and a marketing site that had to rank and convert.
The idea
Build the pieces once so they can be configured per customer: SSO, themes and walkthroughs, instead of custom code for each deal.
How I did it
- Added several SSO providers per customer, customer themes and guided mobile walkthroughs (early 2025).
- Built an API collection tool in a week (Aug 2025): 132 endpoints across 17 categories, used to test and document the backend.
- Upgraded the app from Next.js 13 to 15 for a security assessment, taking known vulnerabilities from 79 to 53.
- Rebuilt the website (v6) from August 2025: 20 routes, 11 case studies, 49 legacy URLs redirected, duplicate H1s fixed, structured data and llms.txt added.
The impact
Enterprise customers could onboard with their own identity provider and branding without new code, and the company got a new website and a documented API. This is also the codebase I learned to hand over cleanly when we moved to Platform v2.
When you’re the only one on something, build it to be configured, not customised.