LMS Developer / eLearning Developer - scoping document for an internal employee training platform

We run a B2B SaaS with US-based customers, and our team has grown fast since we started rolling out our mobile companion. Onboarding new customer-success, ops and sales people - and keeping everyone current as the product changes - has outgrown the mix of shared docs, recorded walkthroughs and a hosted LMS trial nobody keeps up. We want an internal learning platform we own, not another generic tool we outgrow in a year. Looking for an experienced lms developer to deliver a written scoping document before we commit to the build. We are leaning a React Nextjs front end with a Node backend, the same direction one team already scoped our admin console, but we want a senior elearning developer opinion in writing before we lock anything. We would rather have one full stack team own the platform end to end than split it across separate hires. No call needed - we want a structured written deliverable our team leads can read and argue with internally. What the scoping document should cover: Content model - courses, modules and lessons, and how a non-engineer authors and reorders them without filing tickets How training maps to people - role-based learning tracks, auto-assignment for new hires, and what a manager sees about their team Completion and versioning - what happens to a completed record when we update a module after the product changes Bringing existing content across - the SCORM packages and compliance courses we already paid for What makes the cut for v1 and what should wait Pitfalls you have seen in internal LMS builds like this Anything else a senior would want a non-technical founder to understand Specifics about our product, our customers, and our internal headcount and current tooling will be shared only after the contract is signed, under NDA. To apply, please share: 2-3 learning platforms or course products you have shipped, links welcome A short note on how you would phase a build like this Your fixed price for the scoping document If the scoping lands well, this is the first step of a longer engagement - the build itself and the phases after it.