A useful relationship system helps a team answer three questions: who matters, how are we connected, and what should happen next? Start with those questions when deciding whether your spreadsheet needs a better structure or a different way of working.
Start with the work your list needs to support
A company name, a contact and a status column can be enough for a focused campaign. A spreadsheet gives the team a familiar place to sort opportunities, record notes and agree priorities.
Look more closely when the same person appears in several lists, an introduction gets lost in a comment, or a colleague needs to reconstruct months of conversation before making a call. Those are useful signals that important context has become difficult to follow.
Before changing tools, choose three questions the team struggles to answer. For example: who can introduce us to the right person, which conversations involve the same organization, and which active opportunities have no next action?
Capture meaningful connections
A graph represents entities and their connections. People, organizations, opportunities and activities can each have their own record, with relationships describing how they connect. This follows the basic graph model of nodes, relationships and properties described in Neo4j’s introduction to graph databases.
For a business team, the useful detail is the meaning of the connection. “Introduced us after an industry event” gives more context than “knows.” Record where that information came from, when it was checked and whether it is confirmed or still an assumption.
The same organization can be a potential customer, an integration partner and a source of introductions. Keep those opportunities distinct while connecting them to a shared organization record. A relationship view can complement an existing CRM; decide which system owns each record before creating another place to update it.
An illustrative example
A single “contacted” status leaves several questions unanswered. Who owns each conversation? Has Alex agreed to make the next introduction? Are the sales and integration discussions dependent on one another?
A connected record keeps Jordan, Alex, Northstar and the two opportunities separate. It can then show the introduction, the open ownership question and the next action for each opportunity. The information becomes easier to review without treating every conversation as the same deal.
Make the next action visible
Choose a small set of fields that help someone do the work:
- Purpose: the outcome being explored and why it matters to both sides.
- Context: the relevant conversation, introduction or source.
- Owner: the person responsible for moving this opportunity forward.
- Next action: a specific step and a date when one has been agreed.
- Open question: what must be understood before making the next decision.
Replace “follow up” with something someone can complete: “Ask Alex to confirm the workflow owner before arranging the scoping call.” Record the answer in the opportunity so the next colleague does not have to repeat the research.
Give different opportunities room to develop
Define stages around the actual decision process. A sales opportunity might move through discovery, a scoped proposal and a commercial decision. A partnership could require agreement on a shared use case, a technical review and a coordinated activity.
Some relationships have no immediate transaction attached. Give them a clear reason to stay in touch and a sensible review date. Avoid creating artificial urgency or filling a pipeline with opportunities that nobody has qualified.
A getting-started checklist
- Choose one workflow, such as a partner-integration pipeline or a focused sales segment.
- Collect only the organizations, people and current opportunities needed for that workflow.
- Merge duplicates and agree which system is the source of truth for each record.
- Label confirmed connections, assumptions and outdated information clearly.
- Give each active opportunity an owner and a concrete next action.
- Set access around genuine business need and leave unnecessary personal details out.
- Review the map with the team, remove unused fields and agree how updates will happen.
Try the structure on a manageable set of current relationships before attempting a full migration. Include a handoff between colleagues in the trial: can the receiving person understand the context and take the next step without an extra explanation?
Measure useful work
Establish a baseline before claiming improvement. Track opportunities without an owner, overdue next actions, duplicate records and the time needed to prepare for a conversation. Ask the team which updates still create unnecessary work.
The useful test is whether people can find trustworthy context and act on it. Keep the model small enough to maintain, then expand it when another relationship or workflow genuinely needs to be represented.
ProtoGraph is being developed around this connected approach to sales, partnerships and business development. Its current website experience is an illustrative concept. Explore the approach, then discuss the relationship workflow your team needs.