Razor Web Server / Client Proof of Concept Workscope

Hi Lawson,
Thank you for sharing the requirements and technical stack — everything points toward a well-structured, modern .NET application, and I’d like to make sure I align perfectly with your expectations before getting started.
I have a few key questions to clarify the scope and ensure the build is approached in the most effective way:
Could you share the primary goal of the application and the type of users it’s being built for? This helps shape both the architecture and user experience decisions.
With .NET Aspire included, are you planning for a distributed/microservices architecture, or would you prefer a modular monolithic approach with room to scale later?
For the front end, do you have a preference between Blazor Server and Blazor WebAssembly, and will the application require real-time or highly interactive UI components?
Regarding the database, is there an existing SQL Server schema already defined, or should the data model and structure be designed as part of the project?
Is there a specific reason ADO.NET is required for data access, or would you be open to a hybrid approach if it improves maintainability without affecting performance?
Are there any authentication or authorization requirements already in place, such as role-based access or integration with an identity provider?
Where do you plan to host the application (e.g., Azure, on-premise, or hybrid), especially considering the use of .NET Aspire?
Will the system need to integrate with any third-party services or APIs from the outset?
Lastly, what are the key priorities for the first release, and are there defined timelines or milestones to work toward?
Once I have clarity on these points, I can map out the most efficient and scalable way to deliver the solution.
Looking forward to your response.