Djangogigs.com - Details for the legitlead application development gig

LegitLead is a lead validation solution developed in django/python. The purpose of LegitLead is to validate online leads and detect lead fraud. The application takes data in from an API can calls out to a number of API services to obtain additional data about the lead. All data are collected into a progress database and connected to a highcharts (highcharts.com) front end reports. The current application lives on heroku.com.

We are looking for a good developer to build additional features to LegitLead. The new features that need to be developed include the following:

1. Add admin view of all reports for a specific account

Admin users should be able to see reports from any other users. The desired feature will allow the admin to login as any user, without having access to the user's password.

1. Enable the date filters in the reporting interface

Currently, these filters do not work. Date should be based on opt-in date provided in the lead record.

1. Create usage reports to be viewed by account owner and admin.

LegitLead charges for every lead that is evaluated by the system. The report should show the count, the rate and the total cost. Rates are set at the account level. The report should be filtered by date, which is the data the record is received by LegitLead.

Admin's should be able to see reports for all accounts. Accounts can only see their reports.

1. API Development

The API required fields list must be trimmed down to the bare essentials. Also, the API needs to provide a LegitLead score at the lead level whenever a lead is processed. This response must happen in real time.

API should be configurable to provide results of Rules (as defined below). The response should show LL score, accept/reject code, reason code for reject.

1. Acceptance Rules

Users can set up rules for what leads are accepted. This feature gives them a control panel to set up rules. The rules feature will use a series of pull down options to create the rule. For example,

Accept leads with LegitLead Score of 65 or higher for all sources

Accept leads with email valid score of 90 or higher for all sources

Accept leads with email valid score of 95 or higher for affid=MA

Rules can be set using overall scores, database metrics, and at affid or subid levels.

1. Compete the email confirmation metric

There is a code base for this feature. Essentially, the app sends emails via Sendgrid. It also collects click-through data from the Sendgrid post every time a user clicks on a link contained in the email message. This process is a new metric called Email Confirmation. The metric calculates how many users confirm their registration, normalized on a scale from 0 to 100. This feature must be enabled with a flag when posting into the api.

1. Change UI to support large lists of affid and subid values

We need a better UI design to support large lists of affid and subid values. The current UI limits us to 20 unique values.

If you are interested, please respond and share any relevant experience you have. I'm interested in developers who have worked with API's, business intelligence applications and/or python. If this appears to be a fit, I will provide you with access to the application and code.

Feel free to contact me if you have any questions.

Dave Linhardt LegitLead