furiousOyster / software-defined-org

Infrastructure is better as software. Organizations too.
0 stars 0 forks source link

Sales pipeline should be plain text #3

Open furiousOyster opened 6 years ago

furiousOyster commented 6 years ago

If we can't operate our sales process in plain text, it doesn't help us to have an app do something we don't already understand.

Each Sales lead should have a current status panel in a standard format, and there should be a log of all contact made with the client.

The status panel should always include the expected revenue from the opportunity.

ScottMaxwellBTL commented 6 years ago

Propose this as the first iteration - it can be changed as with everything else under the SDO.

The status panel for each Sales Lead should be enough to get a snapshot of where we are in the cycle, what's happening next, what events (including meetings, emails and calls) have happened and what the overall size of the opportunity is.

The status panel would have:

  1. Name of Organisation
  2. Use case summary - what's the proposal?
  3. Stage - How much do we know, and are they ready to move?
  4. Next steps - Where did we leave it with them?
  5. Contact (and job role) - The main contract.
  6. Other contacts - anyone else we've had dealings with.
  7. Last contact - Date and with who?
  8. Industry verticals - Standard list around the obvious ones.
  9. Functional buckets - a wider list to help us sort them into similar proposals if we want to.
  10. Total Opportunity size - for this proposal and potential overall.
  11. Comms Events - briefly, a log of who has said what and when.

To make this simple we should track these as .md files inside of GitHub.

ScottMaxwellBTL commented 6 years ago

@furiousOyster Have just opening a repository to cover this. Check it out. Special focus on the questions in the template...

ScottMaxwellBTL commented 6 years ago

https://github.com/BlockchainTechLtd/SalesLeads