There was very little documentation or source-code handover, so before planning what came next, part of the work was simply understanding what was already there and what could realistically be carried forward.
What I did
Turning a loosely defined redevelopment idea into something the owner and development team could actually reason about together
I worked closely with the owner to turn conversations into something more concrete: software requirements, user-role and feature flows, MVP scope, success criteria, and a Definition of Done. I also mapped out the trade-offs between continuing with the existing application and rebuilding it, so the decision was not just about which option sounded cleaner technically.
From there, I put together an initial product structure in Figma, helped look for a third-party development partner, and followed the implementation through GitHub activity, local builds, and technical reviews. My role was less about writing the code myself and more about reducing ambiguity around what the team was trying to build and how far the current system could reasonably take us.
For internal projects, I keep the details broad enough to explain the work without exposing private data, internal processes, or anything that should stay inside the company.