Cloud hosted SaaS application for a subscription based telecom inventory management application.

Circicom LLC is a startup company building a cloud hosted SaaS application for a subscription based telecom inventory management application. We’re looking for a team of 3 developers to build a single-page type application in an Azure cloud environment utilizing SQL databases, a Web API (restful API) middleware, and a multi-interface client for PC/desktop, tablet, and mobile access. The system will be a multi-tenant environment requiring end-user authentication, authorization, and account payment processing. The team of three will consist of frontend graphic design, frontend user interface (UI) development, and backend Web API development. The total application will consist of two separate yet integrated components, the marketing frontend pages (Home Pages) and the client frontend/backend application (Portal). The Home Pages for the site will contain basic feature information, sample screens, pricing, contact information and a link to log in to the client application. The marketing on these pages should be simple, make it easy to understand the purpose of the application, and primarily encourage clients to check out the client application for a free 30 day trial. Once logged into the Portal via a free trial or paid subscription account, the end user can then begin tracking their individual physical sites, their telecom vendors, and then ultimately their telecom circuits, satellite links, and mobile devices. Each of these pages is a single-page type application with an itemized list of inventory. Each item in the inventory is listed along with a few summary details for easier item understanding. For example, an itemized site listing would show a site code or name along with an address and phone number for additional information. Users can then add, edit, sort, or delete items in the list. Adding or editing an inventory item would display a form where all item details would be entered then saved into a database. The user interface to the lists and the detail forms is especially important. These pages or forms should be easy to understand, quick to load/save/close, easy on the eyes, and have similar details grouped together making efficient screen use of all types of displays from PC/laptops to mobile devices. Also in the Portal are a dashboard summary and a reporting page. The dashboard summary should be a widget based dashboard for displaying various stats about any or all of the client’s information. This could include but not be limited to: listing of circuits, satellite links, and/or mobile devices by status such as order, delivered, in service, canceled, etc.; total sites, vendors, circuits; top 10 vendors, circuits, costs, users, etc; recent change activity by user, location, or vendor; and these could be charts, graphs, or lists. The reporting page should contain a handful of “canned” reports but should also have an option for adhoc custom reports. The site will have an administration page via a link in the admin user profile or gear in the top right corner where a customer administrator would perform multiple functions for the site such as user management, drop-down field management, and account management. User management would include the basic add, change, delete of system users. This should include sending users an e-mail with a click to confirm changes link in it where users are notified of changes to their access. The details included in each inventory item will include many drop-down selections for the standardization of data in the system. These drop-down options should be managed centrally in the admin page and will include but not be limited to options such as site type, circuit status, port speeds, service types, vendor accounts, etc. Account management consists of a simple calculation of a customer total inventory items, selecting the appropriate account tier for the number of desired items to pay for, then processing monthly payments through an online payment provider. Security for the site is a top priority. All information in the site should remain confidential to the customers and their applicable users. All change activity must be properly logged. All API calls must be authenticated and contain a unique company ID. User logins must adhere to a strong password format (at least 8 digits, and contain one capital letter, and a number). Additional system requirements for the project include the ability that all lists, reports, graphs, data, etc should be able to be exported to CSV or excel format, printed, or saved to PDF format.