Technology research UX - Track monthly changes in Churn, Pricing, Potential... KPIs
- or -
Post a project like this2015
€347(approx. $375)
- Posted:
- Proposals: 5
- Remote
- #2166582
- OPPORTUNITY
- PRE-FUNDED
- Awarded
Description
Experience Level: Expert
We provide a web application for predictive sales analytics. We have an advance working prototype working since the beginning of this year. You can see some features in action here:
https://qymatix.de/en/predictive-sales-analytics-qymatix-welcome/
This is one of several improvements we would like to work on. This is a full-stack development.
Our tool creates advanced calculations per customers, churn, pricing and cross-selling potential.
We would like to expand the databases where these current calculations are stored to save a history of the last month and last three months results.
I created a mock-up on how it could look like in the element qy-insights-customer-details.html
Server-side is Python/Django, Front end is Polymer JS. We will give you access to the code in our repository once the project is accepted.
Finished work should be pushed back to the repository. It should work once deployed. It will definitely need python, JS and expansion of the calls get_insights and get_customers in the API.
If there is no history to show, the results should show a "-" in the front-end. The back end must be able to work around possible errors so that the front end will always work.
https://qymatix.de/en/predictive-sales-analytics-qymatix-welcome/
This is one of several improvements we would like to work on. This is a full-stack development.
Our tool creates advanced calculations per customers, churn, pricing and cross-selling potential.
We would like to expand the databases where these current calculations are stored to save a history of the last month and last three months results.
I created a mock-up on how it could look like in the element qy-insights-customer-details.html
Server-side is Python/Django, Front end is Polymer JS. We will give you access to the code in our repository once the project is accepted.
Finished work should be pushed back to the repository. It should work once deployed. It will definitely need python, JS and expansion of the calls get_insights and get_customers in the API.
If there is no history to show, the results should show a "-" in the front-end. The back end must be able to work around possible errors so that the front end will always work.
Lucas P.
100% (102)Projects Completed
97
Freelancers worked with
28
Projects awarded
16%
Last project
25 Apr 2024
Germany
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies