Case Study: Building the Revenue Operations System We Wanted to Run Ourselves
How Cadensoft Built an AI-Assisted Sales Operating System Around Context, Relationships, and Founder Judgment
Executive Summary
Founder-led sales depends heavily on judgment.
Knowing which prospects deserve attention. Understanding how to approach a new relationship. Remembering what was discussed during the last conversation. Recognizing when a contact may be more valuable as a referral source or strategic partner than as an immediate buyer. Following up at the right time with the right context.
As activity grows, maintaining that context becomes increasingly difficult.
Cadensoft experienced this challenge internally as its own business development efforts expanded. Prospect research lived in one place, LinkedIn engagement in another, meetings created additional information, CRM records required manual updates, and valuable details from conversations could easily become disconnected from the next action.
Existing AI sales tools could help generate messages, but generating more outreach was not the problem Cadensoft wanted to solve.
The objective was to create a revenue operations system that could maintain context throughout the entire relationship.
Cadensoft built its own system in Salesforce first, treating the company as “Client Zero.”
The resulting platform researches and assesses prospects, analyzes communication preferences, distinguishes sales opportunities from strategically valuable relationships, prepares the founder for meetings, captures what was learned during conversations, reassesses opportunities as new information becomes available, documents why those assessments changed, and uses the complete relationship history when assisting with follow-up.
AI supports the process throughout, but the founder remains responsible for the relationship.
Every message is reviewed and sent by a person.
Every meeting remains a human conversation.
The system’s role is to make sure that person enters each interaction with the context needed to make a better decision.
Client Background
Cadensoft works with founder-led organizations to improve the operational systems behind growth, delivery, and execution.
That made its own revenue operation an important proving ground.
Like many founder-led organizations, business development depended heavily on the founder’s personal knowledge of prospects and relationships.
That model works when the number of active relationships is limited.
As outreach expands, however, the amount of information that needs to be remembered grows quickly.
Who is this person?
Why did we originally connect?
What matters to their business?
How do they prefer to communicate?
Are they actually a potential buyer?
Could they be a referral source, partner, or valuable industry relationship instead?
What happened during the last conversation?
What did they object to?
What did we agree to do next?
Which relationships deserve attention today?
Cadensoft wanted those answers to become part of the operating system rather than remain dependent on memory.
So before offering the model to clients, we built it for ourselves.
The Challenge
Founder-Led Sales Has a Context Problem
Most sales systems are good at storing activity.
A lead was created.
An email was sent.
A meeting occurred.
A task is due.
Those records are useful, but activity alone does not explain the relationship.
For founder-led selling, context matters significantly more.
A founder preparing for a conversation needs to understand not only what happened but why the relationship matters and what should happen next.
Cadensoft identified several points where that context was routinely at risk.
Prospect research could happen inconsistently.
Information gathered during research did not automatically influence future communication.
Meeting preparation depended too heavily on memory and manual review.
Important details from calls could remain buried in notes or transcripts.
CRM classifications could become outdated as new information emerged.
Follow-up drafting often required reconstructing the history of the relationship.
And traditional pipeline classifications did not adequately account for valuable contacts who might never become direct customers.
The underlying problem was not a lack of sales activity.
It was the absence of a connected reasoning layer across that activity.
Why Generic Sales Automation Wasn’t Enough
The market already contains an enormous number of tools capable of automating outreach.
Many can generate an email from a prospect’s name, title, company, and a basic customer profile.
Cadensoft wanted something different.
A useful system needed to understand more than who the prospect was.
It needed to understand the evolving relationship.
That required bringing research, fit, communication preferences, strategic value, meetings, conversations, objections, next steps, and prior activity into the same operational context.
Cadensoft also made a deliberate architectural decision to keep core business logic inside systems it controls.
Salesforce became both the system of record and the system of action.
External tools could participate in workflows, but critical context and routing logic would remain visible and portable rather than becoming buried inside individual third-party configurations.
The objective was not to automate the founder out of the sales process.
It was to give the founder better information at every point where judgment mattered.
The Cadensoft Approach
Build Context Before Generating Communication
The system begins by developing a more complete understanding of the prospect.
LinkedIn profile information captured on the lead record can trigger an AI-generated insights report that evaluates communication characteristics and provides practical guidance for engagement.
The system identifies a primary communication style and associated traits, then provides recommendations for how to approach:
- Initial connection
- Post-connection engagement
- Meeting requests
- Objection follow-up
- Calls to action
- Meeting conversations
- Continued follow-up
An AI Profile Summary also captures relevant expertise, leadership signals, and potential relevance to Cadensoft.
The goal is not to create a personality label for its own sake.
It is to give the person responsible for the relationship practical context before communication begins.
Evaluate Fit Without Pretending to Know More Than We Do
Prospect research also triggers an AI-assisted ICP Fit Assessment.
The assessment considers available evidence and produces:
- Fit assessment
- Fit summary
- Likely role in an opportunity
- Best-fit segment
- Pipeline priority
- Relationship priority
- Evidence supporting the assessment
- Explicit uncertainty where information is still missing
That final component is important.
The system is designed to distinguish between what it knows and what it is inferring.
Rather than treating an AI assessment as objective truth, uncertainty becomes part of the record and can be resolved as the relationship develops.
Recognize Relationships Beyond Direct Sales Opportunities
Not every valuable business relationship should be forced into a buyer-or-not-buyer classification.
Cadensoft separately evaluates strategic relationship potential across areas such as:
- Direct opportunity
- Referral potential
- Strategic partnership
- Thought leadership
The system then recommends an appropriate relationship motion.
Pipeline Priority and Relationship Priority are maintained separately.
This means someone with limited immediate buying potential can still be recognized as a high-value relationship rather than being treated as an unqualified lead and forgotten.
Prepare for the Conversation, Not Just the Meeting
When a meeting is booked, the system creates a dedicated Meeting Preparation record.
Rather than simply displaying CRM fields, the preparation brief organizes available intelligence around the conversation itself.
It includes:
- Who the prospect is
- Why the meeting exists
- Current fit and priority
- Relevant positioning angles
- Positioning to avoid
- Communication guidance
- A structured agenda
- The intended objective for the call
The result is a repeatable preparation process designed to prevent the founder from entering important conversations cold.
Turn Conversations Into Updated Intelligence
A CRM becomes less useful when what was actually learned during a meeting never makes it back into the record.
Cadensoft designed the post-call workflow to address that gap.
Meeting notes and transcripts are summarized into structured information, including:
- Key discussion points
- Current state
- Buying signals
- Objections
- Decision authority
- Agreed next steps
That new information automatically triggers another fit assessment.
The prospect is not permanently classified based on what was known before the first conversation.
Fit, priority, recommended actions, and communication guidance can evolve as the system learns more.
Make AI Decisions Auditable
Dynamic AI assessments introduce another problem.
If a system changes a prospect from one priority to another, the user should be able to understand why.
Cadensoft created Progression Events to provide that audit trail.
When AI-driven fields change, the system records:
- Affected fields
- Previous values
- New values
- Rationale
- Triggering event
The CRM therefore preserves more than the current answer.
It preserves the reasoning history behind how that answer evolved.
Use the Full Relationship When Assisting With Follow-Up
Email, text, LinkedIn activity, meeting information, research, and assessments are maintained around the same relationship record.
When the founder requests a suggested follow-up email, the system can use that accumulated context rather than generating copy from a generic prompt.
The draft is still reviewed.
The founder decides whether it should be edited, sent, or discarded.
AI assists with recall and synthesis.
The person remains responsible for the communication.
Turn Intelligence Into Daily Focus
Context only creates value when it changes action.
A daily prioritization workflow evaluates the active pipeline and relationships to identify where the founder’s attention is most valuable.
Rather than beginning the day by manually reviewing every open record, the system creates a ranked set of priorities based on factors such as fit, engagement, and relationship importance.
The purpose is simple:
Help the founder determine where limited time should be spent.
Strategic Takeaway
Founder-led businesses rarely suffer from a complete lack of sales information.
The information is usually everywhere.
It exists in CRM records, LinkedIn conversations, email threads, meeting transcripts, text messages, personal notes, and the founder’s memory.
The opportunity is to turn that fragmented information into usable context.
Cadensoft built its Revenue Operations System to create that continuity for its own business first.
The result is a system that helps us understand who we are speaking with, prepare for conversations, capture what we learn, reassess relationships as they evolve, explain why priorities change, and determine where human attention is most valuable.
AI participates throughout the process.
The relationship remains human.
And because we built the system around our own operating reality first, it now serves as the working model for helping other founder-led organizations design a revenue operation around theirs.
Project Snapshot
Client
Cadensoft, LLC, Internal “Client Zero” Initiative
Industry
Professional Services & Revenue Operations
Focus Area
Revenue Operations, Sales Workflow Orchestration & Applied AI
Core Challenge
Creating a sales process where prospect intelligence, conversations, meetings, relationship context, and next actions remain connected throughout the entire business development lifecycle
Solution Type
AI-Assisted Revenue Operations System Built in Salesforce
Capabilities Applied
Prospect Intelligence, ICP Assessment, Communication Style Analysis, Relationship Prioritization, Meeting Preparation, Conversation Summarization, Dynamic Reassessment, Workflow Automation, Omni-Channel Context, AI-Assisted Drafting, Auditability
Primary Outcome
A working revenue operations system that gives the founder structured context before outreach, before meetings, after conversations, and when determining where to focus next
Project Status
Live Internal Operating System and Foundation for Client Implementations
Before You Add More Sales Automation, Understand the Operation
Most founder-led businesses already have a collection of sales tools. The more important question is whether the underlying process gives you the context, visibility, and consistency needed to use them effectively.
The Revenue Operations Diagnostic examines how your current sales process actually works, where information and opportunities are being lost, and what should be improved first.
Related Solutions
AI-Powered Solutions
Apply AI where it can improve research, synthesis, prioritization, workflow execution, and decision support without removing human judgment from the process.
Explore Applied AI Solutions
Solution
The resulting system functions as an orchestration layer across Cadensoft’s revenue operation.
AI Prospect Intelligence
ICP Fit Assessment
Strategic Relationship Assessment
Communication Style Guidance
Meeting Preparation
Post-Meeting Intelligence
Dynamic Reassessment
Progression Events
Omni-Channel Relationship Context
Context-Aware Drafting
Daily Prioritization
Operational Impact
Because Cadensoft is Client Zero, we are deliberately not presenting conversion improvements or revenue lift that have not yet been established through external client implementations.
The current outcomes are operational capabilities we use within our own revenue process.
Every Prospect Begins With Context
Every Meeting Has a Preparation Framework
Conversations Become Part of the Operating System
Relevant information becomes structured CRM context that can influence future decisions.
Assessments Evolve With Evidence
The system does not assume that the initial assessment remains correct indefinitely.
AI-Driven Changes Can Be Explained
Valuable Relationships Don't Disappear Because They Aren't Buyers
Follow-Up Begins With the Relationship History
The Founder Starts With Priorities Instead of a Database
Where should I spend my time today?
The System In Practice
A Fictional Demonstration Using the Live System
To demonstrate the workflow publicly without exposing real prospect information, Cadensoft created a completely fictional lead and processed it through the production system.
The prospect, company, business characteristics, and initial inputs in this example are fictional. The resulting assessments and workflow outputs were generated by Cadensoft’s actual Revenue Operations System.
The fictional prospect was configured as the founder and CEO of a growing multi-location physical therapy organization.
Based on the initial profile, the system identified a communication style characterized as metrics-driven, operationally focused, direct, and process-oriented.
The system recommended leading with a specific metric, keeping requests concrete, and avoiding a product-first sales approach.
The initial fit assessment classified the fictional prospect as a strong potential fit and likely economic buyer while explicitly identifying information the system did not yet know, including current systems, budget, and timing.
When a meeting was booked, the system generated a six-part agenda and preparation guidance around the prospect’s likely priorities and communication style.
After a fictional call transcript was processed, the system reassessed the relationship.
Pipeline Priority increased based on information learned during the conversation.
A previously unknown operational risk became relevant based on a stated data-handling requirement.
The recommended next action changed to reflect the specific commitments made during the meeting.
Each change was recorded in the Progression Events audit trail with its previous value, new value, and rationale.
The demonstration illustrates the core design principle of the system:
The record becomes more useful as the relationship develops.
What We Learned Building It For Ourselves
Building the system internally reinforced an important principle.
AI becomes substantially more useful when it is given institutional context.
A language model can write an email with very little information.
That does not mean the email will reflect the history of a relationship, the founder’s judgment, what was learned during the last conversation, the organization’s positioning, or the next action that actually makes sense.
Those capabilities require an operating system around the model.
The same principle applies when Cadensoft implements revenue operations systems for clients.
The objective is not to reproduce our Salesforce configuration exactly.
It is to understand how that organization sells, what its people know, how relationships develop, where information is lost, how decisions are made, and where AI can responsibly extend human judgment.
The system should reflect the business.
Not the other way around.