Product Plan
| Support Type | Payment Type | SLA | Services | Upgrades | Launch Date |
|---|---|---|---|---|---|
| Standard business hours | Credit Card only | 2 days, 4 days, Web only | No | Yes (this means they can use their support tickets on the 4.0 when it comes out) | Jan 1st, 2017 |
Price
Support Plan | Tickets | Cost |
|---|---|---|
Tier 1 | 5 | $2,000 |
Tier 2 | 10 | $3,000 |
Tier 3 | 15 | $3,500 |
Comments: we need a way to track how many tickets a client has left for support
How to identify potential clients
Source | Action |
|---|---|
CRM: Return To Marketing | Professional Email |
CRM: Closed Lost | Professional Email |
CRM: Inactive | Professional Email |
Forums | Professional Email, Popup (like the whitepaper one), Forum post. |
New Leads | Automated page on our website |
Pricing Page Mockup
Request Tickets Form Mockup
Onboarding Steps
When a user fills out the form an email will be sent to a designated person (TBD?). They will perform the onboarding process and reach out to the user to collect their credit card information.
Then the user will have the amount of tickets purchased.
Since this will be on the community edition, no licenses will be generated.
Target Segment
- Who are we targeting?
- What is the company size? Is it small companies with few users? Or is it large companies using the community plan already that just don't need more and don't want to pay more?
- Other target?
- What does Success or Non Success Look like?
- How many sales per month?
- How much revenue per month?
- What would it look like if this is not a good idea and should be turned off?