Case study Business Relationship Intelligence Platform
Business Relationship Platform & Pipeline OS that turned
40 hours of weekly outreach into 5
Built for a high-touch B2B founder running memberships, brand partnerships, corporate prospects, media collaborations, and a product line at once with a lean VA team and hundreds of active contacts across every vertical.
Who this was built for
One founder. Six relationship types. Zero generic CRM fit.
A founder running a multi-vertical business across memberships, brand partnerships, corporate prospects, media collaborations, and a product line simultaneously. Every relationship type has a different journey, different touchpoints, and different commercial outcomes. The team is lean: a founder and a small number of virtual assistants handling hundreds of active contacts across all verticals.
Generic CRMs failed not because they lacked features but because they assumed all relationships work the same way. A membership pipeline looks nothing like a corporate sales cycle. A podcast speaker relationship is nothing like a brand partnership negotiation. Off-the-shelf tools forced the business to adapt to the software. This system was built the other way around.
Pain points we resolved
What was burning time and clarity
- Contacts scattered across spreadsheets, inboxes, and notes with no single source of truth
- No structural difference between relationship types everything forced into one generic pipeline
- Hours spent every week drafting follow-up messages from scratch with no context at hand
- No visibility into which relationships had gone quiet or were at risk of stalling
- VA delegation happening over WhatsApp and email with zero audit trail
- Inbound enquiries landing in an inbox with no automatic routing or assignment
- No way to see, at a glance, where pipeline health stood across all six verticals simultaneously
What we built
A relationship OS built around the business not the other way around
A relationship operating system structured around how the business actually works not how a SaaS vendor thinks it should work.
Six categories, six distinct pipelines
Members, brand partners, corporate prospects, podcast speakers, programme participants, and product clients each live in their own structured environment with category-specific fields, pipeline stages tailored to that relationship journey, and Kanban or list views depending on how the team prefers to work. No relationship type is forced into a model that doesn't fit it.
A unified contact database underneath
Despite six categories, every contact lives in one searchable database. Global search across names, companies, emails, tags, and interaction notes. Saved filter views for frequent queries. The founder sees everything; VAs see what they're permitted to see.
Interaction timeline on every record
Every note, call, message, stage change, and file upload is logged chronologically on the contact record with a timestamp and the name of the user who made the entry. The full relationship history is always one click away.
Follow-up scheduling with overdue flagging
Every contact and pipeline card carries a follow-up date, note, and assignee. When a due date passes without completion, it surfaces automatically across the dashboard and pipeline views. Relationships don't stall because someone forgot.
Access control & team management
Delegate without losing oversight
The founder needed to delegate without losing oversight. Three-tier role-based access was built from the ground up. Onboarding a new VA takes minutes. Offboarding is one click.
Owner
Full access to every contact, every pipeline, every setting, and the complete audit log. Manages all users, configures pipeline stages, controls notification defaults, and exports data at any time.
Admin VA
Can create, edit, log interactions, manage pipeline cards, and handle follow-ups across all contacts and categories. Operational access without administrative control.
Limited VA
Scoped to specific contact categories only. A VA managing podcast speaker outreach sees nothing from the membership or corporate pipeline. Permissions are set per user and can be adjusted or revoked instantly by the Owner.
Audit log
Records every action taken in the system every create, edit, delete, and stage change attributed to the user who made it, with a timestamp. The founder has complete visibility into team activity without micromanaging.
The AI layer
Where 40 hours of weekly outreach becomes 5
Context on demand, drafts from the full timeline, and a weekly briefing that replaces a manual CRM review with nothing leaving the system automatically.
AI Contact Summary
One click on any contact record generates a structured brief full relationship history, current pipeline status, open threads, last interaction, and anything that appears to need attention. Built for the founder returning to a contact after weeks away. No digging through notes, no context reconstruction.
AI Draft Follow-up
When a follow-up is due, the AI reads the contact's full interaction timeline, current pipeline stage, and relationship category then produces a contextually appropriate draft message. The founder or VA reviews, edits, and sends manually. Nothing leaves the system automatically. The cognitive load of starting from a blank page, for every contact, every week, is gone.
Lead Qualification Assist
The AI reads each prospect's source, notes, interaction frequency, and pipeline stage then flags them as warm, cold, or unclear with a one-line rationale. The founder and VAs prioritise their week based on actual signal rather than gut feel.
Weekly Relationship Digest
Every week, an AI-generated briefing lands in the founder's inbox: who has gone quiet, what is progressing, what is overdue, and where the strongest opportunities currently sit across all six pipelines. One email replaces a full manual CRM review session.
Automation
Workflows running silently in the background
Beyond AI, a set of workflow automations handle the operational work that previously fell through the cracks.
Inactivity auto-flag
If no interaction is logged on a contact within a configured number of days, the record is flagged on the dashboard automatically. No relationship goes cold without the team knowing.
Post-stage follow-up scheduling
When a pipeline card moves to a new stage, a follow-up is scheduled automatically for a set number of days later. The relationship never stalls between stages waiting for someone to remember.
Auto-assign on inbound enquiry
New website enquiries create or match a contact record, route to the correct category, and assign to the right VA automatically. The founder's inbox is no longer a manual triage queue.
Overdue flagging
Surfaced in real time across the dashboard and all pipeline views the moment a due date passes. Nothing hides.
Results
From manual outreach grind to a 5-hour week
Weekly outreach drafting dropped from 40 hours to 5. Contacts moved from scattered tools into a single source of truth. Six structured pipelines replaced one generic funnel, VA oversight gained scoped access and a full audit log, inbound enquiries auto-routed, stalled relationships flagged in real time, and the weekly pipeline review became one AI digest email.
40h→5h
Weekly outreach drafting
6
Structured relationship pipelines
AI
Weekly digest replaces CRM review
Before & after
What changed for the business
| Metric | Before | After |
|---|---|---|
| Weekly outreach drafting time | 40 hours | 5 hours |
| Contact visibility | Scattered across tools | Single source of truth |
| Relationship types managed | One generic pipeline | Six structured pipelines |
| VA oversight | WhatsApp, email, trust | Scoped access + full audit log |
| Inbound enquiry handling | Manual inbox triage | Auto-routed and assigned |
| Stalled relationships | Discovered late or never | Auto-flagged in real time |
| Weekly pipeline review | Manual CRM scan | AI digest, one email |
Building a custom CRM or relationship OS?
We've shipped multi-pipeline systems for high-touch B2B operators. Let's map yours.
Start the conversation →forgex.systems