Customer/Staff management, service pricing, reporting & Rostering Web Application

We're currently working on an in-house Desktop & Mobile application that encompasses a full Customer/Staff management & Rostering tool. This project is for an experienced which are fully capable of having this project completed by Sept 1st, and prepped for Customer Release. The service itself is fully backend driven, with the API at about 90% completion. All core feature sets are already available for integration - the remaining feature sets are designed to be ad-hocced towards the project's end. We will require the contractor to integrate their designs as views within CodeIgniter3, with all logic being performed against the available API. Note that AJAX will be required for most calls, as to prevent most logic being performed through page refreshes etc. The backend API provides the following CRUDs; * Registration/Login (verification via SMS) * Service Management (Service name, price, duration, capable staff members etc) * Staff Management (some staff may provide some services - and not others) * Pricing Group Management (different staff members may provide different prices on different services, or spend longer completing them) * Business Hours Management (Open hours etc) * Staff Roster Management (work hours, holidays, etc etc) * Customer Management * Bookings Management (Customer makes Booking, requesting Service with Staff member at Time) * Product/Inventory Management (simple key-value database) * Out-call Management (A Customer requesting a staff member call to them) * Business Details management (Business name, address, Geolocation etc) * Payment System --- Additionally, the following read/display tools must be in place: * Calendar (combining open hours, staff rosters, and all services booked across a day) * Analytics (display all breakdowns across graphs/charts etc as designated by the API) Note that the Calendar display should work as the main frontend toolkit for the end user. The user must be capable of browsing the work set out across that day - or tap on an empty slot to add a task, or drag an existing task to move it. While the Calendar sent from the backend should be read-only, it is directly driven by Staff, Rosters, Bookings, etc etc. --- Finally, and most importantly - the web application should behave different based on the account type. The account type could be for a Business Owner, or a Freelancer. In the event of a Freelancer, we assume there is only one staff member - as such, separate staff rosters or pricing groups do not need to be displayed; but rather, Open Hours should be inferred from one individual roster, etc. Much of this will be done on the backend, but featuresets will need to be hidden from the Customer (i.e: they don't need to see pricing groups per staff member, as there is only one pricing group). --- In the event of a successful hire, either myself or another member of engineering may visit you/your agency on-site. Or, if suitable, we will fly you to Ireland and book a hotel/AirBnB for you, and work with you on-site at our offices for a maximum of one week in either case. Please open your bid with the word "Yellow", followed by your Country of Residence to ensure you have read this project description in its entirety. Note that the deadline for the final delivery date (Sept 1st) is absolutely set in stone - applicants or agencies contacting us in regards to this contract will need to bear this in mind. Missing this delivery date would cause us to miss our launch window, which would strongly affect the end of our business year.