Blockchain CRM
Enterprise blockchain work is not sold to a single customer; every institution the network will stand on has its own legal, IT and business unit. As the proof of concept ends and the pilot begins, which of those institutions is waiting on which question is on nobody's list.
Every institution joining the network is its own account record and the project links them under a single opportunity; in Rapitek CRM the opportunity does not move while an exit condition is empty.
- Keep every institution joining the network in its own account record and tie the project to those accounts under a single opportunity
- Define the proof of concept, pilot and production stages separately and write the exit condition of each stage onto the record
- Record the legal, IT and business unit counterparts with their roles, and see who is waiting on which question
- Drop recurring technical questions into the queue as case records; let the resolution note stay on the case and be read from the same record at the next institution
| Consortium Accounts | Every institution joining the network is a separate account record; the project opportunity links those accounts, and progress per institution is visible on its own card. |
|---|---|
| Stage Gates | Proof of concept, pilot and production are stages of the opportunity; the condition for moving to the next stage is written in a field on the record, and when it is left empty the rule defined during setup stops the stage from progressing. |
| Stakeholder Roles | The legal, IT and business unit counterparts are contact records; the role is a field, and open questions sit as tasks tied to the person. |
| Technical Question History | Recurring integration questions are opened as case records; the resolution note is written onto the case, and later cases opened with the same question are read from these records. |
What lengthens the sales cycle in distributed ledger projects is not technical difficulty but organisational scatter: each of the institutions joining the same network asks its own lawyer about data sharing and its own IT department about integration. The answers given during the proof of concept stage are spread across e-mail chains; as the pilot starts, the same questions come round again from another institution and the team does the same work a second time.
In Rapitek CRM every institution joining the network is a separate account record, and the project links those accounts under a single opportunity; who holds which role sits in a field on the contact records. Proof of concept, pilot and production are separate stages, and the exit condition of each stage is written into a field on the record. The resolution note for recurring technical questions is written onto the case, so the answer given to the next institution is read from the same records.
The scope of the plans and the items priced separately are written on the pricing page.
