Customer Relationship Management mode for board
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
The Deck app is excellent, and in fact it has so many features that it is extremely close to being useful as a fairly advanced Customer Relationship Management (CRM) program for businesses. This would have huge enterprise value. I am proposing that boards in the Deck app could have a CRM mode which adds certain features.
How would Deck be used as a CRM?
Each list would represent a sales stage, and each card will become a sales opportunity. As opportunities progress, they get moved along the sales pipeline, just like in Kanban.
See Odoo for another open source example of a CRM, you will find tutorial videos for such a CRM like this that show the functionality.
What features are missing to be a CRM?
At a minimum, each sales stage should have a defined probability of success, and each opportunity a potential value. Then one can add logic to produce a value of the sales pipeline by multiplying all the opportunity values by the probabilities for each stage and summing them up for all stages.
Later other functionality could be added, e.g.
- notes associated with stages to give instructions for what each stage represents and when you can move to the next stage
- clients database (where clients can be companies, organisations or individuals) attached to sales opportunities (cards), and clients linked to contacts from the contacts app
- importing emails from the mail app to opportunities notes
- reminders to follow up client interactions
Describe alternatives you've considered
Forking the Deck app to create a new CRM app, but it seems too daunting.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or implementation entry points. Start by reviewing how Deck boards, lists, and cards are represented and rendered, then clarify the CRM scope and acceptance criteria before work begins; the proposal currently covers multiple future integrations and does not define a complete done state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100