Japanese web services company Ongoing

Profile Renewal: A Full Rebuild, Driven by Real Usage

Leading the full renewal of the same long-running platform. We audited every one of its 200+ features against real production access logs to decide what to keep, cut, or redesign, so the rebuild is scoped by evidence, not guesswork.

Team Spec and engineering lead with a delivery-partner team, a forward-deployed engineer, and a security advisor
200+ Features audited
Production access logs Basis
Evidence-based scoping Approach
Spec, requirements, scope lead Role

The Challenge

Fifteen years of accumulated features had to be sorted into keep, cut, and redesign, without relying on opinion or institutional memory.

What We Do

We checked real production access logs to confirm which features are actually used, then set the rebuild scope from that evidence. We lead the requirements, specification, and scoping.

Why It Matters

Not a blind port of everything, and not guesswork about what to drop. Paired with the maintenance work, it shows both halves of how we treat inherited systems: keep them alive, then rebuild them on evidence.