React Developer / React Nextjs - written scoping document for a new admin console (B2B SaaS)

We run a B2B SaaS with US-based customers and we are rolling out a mobile companion app for it. The next gap is on the web side. Our ops and customer success people need a small admin console to run the rollout - adoption dashboards, push campaign scheduling, feature flags per customer cohort, and basic role-based access. This is a new build next to our main product, not a rebuild of anything. Looking for an experienced React developer to deliver a written scoping document before we commit to the build. We are leaning React Nextjs for the console with a React Node backend behind it, but we want a senior opinion in writing before we lock the stack. We would also rather have one full stack developer team own the console end to end than split it between separate hires. No call needed - we want a structured written deliverable our team can discuss internally. What the scoping document should cover: Project setup for the console - App Router, TypeScript, folder structure that survives growth How the console talks to our existing product - shared API vs separate service, auth and roles Data model for campaigns, cohorts and feature flags What makes the cut for v1 and what should wait Pitfalls you have seen in admin console builds like this Anything else a senior would want a non-technical founder to understand Specifics about our product, customers and internal metrics will be shared only after the contract is signed, under NDA. To apply, please share: 2-3 dashboards or admin consoles 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.