Responsive Web Site

Responsive design website that allows 3 categories/types of users to login, each with different pages, forms, and features. User A functions: 1. log in securely 2. enter data into a form with roughly 5-6 data fields 3. search and read reviews and profiles of User type Bs 4. subscribe to 3 different levels of access (free, silver, gold) 5. receive instant notifications of responses to User A's requests from multiple User type Bs 6. sort User type B's responses by 4 different data fields within the response 7. allow User type A to select a quote from one of the User type Bs who responded with a quote 8. all User type A to select a date and time from a scheduling tool were availability is published by User B 9. user type A can opt out of ads User type B: 1. login 2. subscribe to 2 levels of functionality (silver, gold) 3. create profiles (1 full page, contact info, rates, services offered, references, testimonials, star ratings) 4. receive realtime notification of new requests submitted by User type As. 5. respond with a quote 6. allow User type B to update a scheduling tool with dates and times available 7. be able to create an google type ads that are shown in the web app to User type As User C (sysAdmin): 1. maintain DB 2. create categories of job types that User A will select from to make a request for service by User B 3. maintain available levels of subscription, payments, billings, advertising 4. method to set a revenue share ratio for transactions consumated between User type A and User type B Backend: 1. Java/Spring based server side 2. MySQL DB 3. Domain model will consist of ~50-100 classes 4. 3-6 RESTful APIs written in OpenAPI for webapp to communicate with 5. 10-20 microservices to represent core business logic and functionality 6. 1 API for each microservice 7. 1 API for accessing DB General architecture of the server side is a 3-layer API/microservice architecture (digital client, business, and system layers) each wrapped with an API and implemented in Java/Spring using a contract-first approach to development. A domain model will be provided for the classes that will be used in the microservices. API specs will be provided, but assume no more than 1 resource per API file and up to all REST methods and multiple URLs with query parameters. Realtime notification needs to occur two-ways between User type A and User type B for their request/responses and scheduling. Vendor must follow strict, purest form of Scrum with 2 week sprints. Any missed Sprints will impact future work Please reply with any questions of the requirements as I'm sure this is very much incomplete.