all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
Rough notes from our team meeting on 2/20/13: -For our business – we need to know data stats, values, amounts, etc. How much? How many? How often? -What are the market indicators for us? -Sub out the code building of custom pieces – or open up the “API” (Application Programming Interface) for others to use. -Emails – not others with an adilas address. Have our reps keep their own email addresses. -Minimal bridging of reps and users. -Revamp the salesperson commission calculator. -More validation and the known issues page. -Page by page validation. -No more collecting setup fees for reps. Keep things at arm’s length. -$100 per hour for adilas training, consulting and setup. -Tech support – free up to 15 minutes – charge after that. Maybe don’t focus on the time amount – what is the nature of the call? -Lay some things out so that everybody plays within certain rules or levels. -The reps and what they serve – open field. -Use the flex grid or admin (hidden) corp-wide settings to map corps to clusters. (Cluster idea: content server - number of data servers) -Load the deal – prep for the next sale. For example: your rep will be giving you their fees. -Note in the Tahoe – Use the monthly accomplishments as the base for the developer’s notebook. Treat it like a drill-down *-Systems thinking – huge concept! -Create or start towards the dream system and how the structure will go. -Play as a team! -The definition of a rep or a consultant is very loose. Basically, it is someone who knows something about adilas and is willing to share and teach. -Think modular data. Move, balance, delete, harness, pair up. -Excretory (waste) system – we need a way to get rid or purge waste. -Think about Newtek – they have tons of servers. Some shared, some dedicated, etc. Think at that level. -Show dynamics of the system. -Let the customer set their own value (what is it worth). We could then come back and say what we think. -At first, until we get some historical data, we need to make an educated guess on price and service levels. -Review or possible review every 6 months. -Pricing for each client is based on industry and usage. Basically, customized for each business based on type or size. -Pricing is also based on habits (usage patterns). -Every client is different. -We may need to cut and snip. -We do have access to total usage and stats. -Pros and cons – comparison charts – list of features. -Web-based and software enhanced. -We want an API and full business platform. -XML, web service, some other format. |