Client & Vendor Intelligence Platform
Converted historical relationship knowledge into reusable organizational intelligence.
Business value
Every client relationship has an owner and a next step, and every vendor evaluation starts from what the company already knows.
- My role
- Data cleanup and consolidation · CRM / VRM data model · Re-engagement workflow · Scorecard and tier design · Dashboards, access and rollout
- Skills
- Data cleanup and de-duplication
- Data modeling
- CRM / VRM design
- Workflow design
- Scorecard design
- Dashboard design
- Permission design
- Built with
- Structured database
- Custom CRM / VRM web app
- Rating forms
- Task automation
- Authentication and role-based access
Confidentiality note. Company-specific data, configurations, workflows and diagrams in this case study have been anonymized and reconstructed for public presentation.
The request
The company already had valuable experience from past client and vendor relationships, but it was fragmented across employees, project history and operational tools — so it could not be reused consistently when evaluating future relationships.
- Pain point 01
Years of client and vendor history sat in cluttered, duplicated records across old tools and projects.
- Pain point 02
Relationships went quiet with no one assigned to follow up.
- Pain point 03
Each vendor evaluation started from scratch, and one person’s feedback couldn’t be compared with another’s.
What I built
- 01A cleaned, de-duplicated relationship base rebuilt from years of cluttered historical records
- 02A CRM for clients: companies linked to parent groups, contacts with owners and tiers, and re-engagement tasks for relationships that have gone quiet
- 03A VRM for vendors: structured profiles, engagement history and an eight-axis scorecard combining objective signals with team ratings
- 04Operating dashboards for both — coverage, re-engagement status, scorecard completeness and tiers
- 05Authenticated, role-based access from day one
Try it — explore the CRM and VRM
A simplified version of both workspaces. In the CRM, open a company and work its re-engagement tasks. In the VRM, open a vendor and see how a scorecard becomes complete and earns a tier.
- All companies, people and numbers are fictional.
- CRM: tick a re-engagement task and watch the contact turn active and the dashboard update.
- VRM: open Rowan Vega and submit the team rating — the scorecard completes and a tier is assigned.
- The real scoring weights are withheld; this demo averages the axes equally.
- Active 2
- Re-engage 5
- No re-engagement needed 2
- Maya CollinsBrand Manager · re-engage4.5Tier I
- Daniel OkaforHead of Content · re-engage4.5Tier I
- Lena FischerMedia Specialist · no follow-up needed4.0Tier II
- Tom ReyesMarketing Coordinator · re-engage3.5Tier II
How I thought about it
- 01
Clean the history first
Reusable intelligence is only as good as the records underneath it, so the old data was consolidated, de-duplicated and structured before anything was built on top.
- 02
Make feedback comparable
Internal feedback is collected in a fixed format so it can be compared across organizations and over time.
- 03
Turn data into follow-up
Every quiet client relationship gets a re-engagement status, an owner and a task — so the CRM drives action, not just storage.
How it was delivered
Run as a project: from the team’s request to something people use every day.
- 01Intake
Collected what teams need to know when choosing, reviewing or reconnecting with a client or vendor.
- 02Clean up
Consolidated and de-duplicated years of cluttered historical records from past projects and old tools.
- 03Design
Designed the data model — company hierarchy, owners, tiers, re-engagement status and the eight-axis scorecard.
- 04Build
Built the CRM and VRM workspaces, re-engagement tasks, rating forms, dashboards and role-based access.
- 05Roll out
Assigned owners, connected team ratings to project close, and handed the workspaces to the teams.
Result
Historical client and vendor knowledge became a reusable organizational asset instead of information scattered across tools, projects and individual memory.
07Technical detailsFor the deeper read: Organizational memory, not only a database · Scorecard · What was delivered · What remained controlled / human
Organizational memory, not only a database
The system holds what the company has learned about each organization it works with:
- Relationship history
- Unified organization records
- Client · vendor
- Previous collaboration
- Past projects
- Who worked with them
- Internal feedback
- Structured, comparable
- From people who worked with them
- External signals
- Objective business signals
- Scorecards
- Consistent framework
- Weights withheld
- Access
- Authenticated
- Role-based
That makes it the basis for consistent evaluation and organizational memory that outlasts individual employees and individual projects.
Scorecard
The scorecard combines objective external and business signals with structured feedback from internal points of contact who previously worked with the organization.
Scoring is requested inside each project document as part of project close, so evaluation happens in the flow of project work rather than as a separate exercise. Where scoring is triggered — Case 04 →
What was delivered
- CRM
- Company hierarchy
- Owners and tiers
- Re-engagement tasks
- VRM
- Vendor profiles
- Engagement history
- Eight-axis scorecards
- Relationship records
- Structured history
- Previous collaboration
- Access
- Authenticated
- Role-based permissions
- Scorecards
- Objective signals
- Structured internal feedback
- Historical data
- Cleaned and de-duplicated
- from past projects and old tools
- Relationship intelligence
- Reusable across
- future evaluations
What remained controlled / human
- Subjective feedback comes from people who actually worked with the organization.
- The scorecard informs a decision; it does not make one.
- Access is authenticated and limited by role.