Fortress / Customer success
Keeping the customer promise in view
An account view connecting what was promised, how delivery compared and when the renewal conversation needed to happen.
Explore story & flowSalesforce & Revenue Systems
The sale is justthe beginning.
Connect the pipeline to the promise. CRM ownership, purchasing, quoting and customer success—followed by two distinct Claude skills for AI-assisted Salesforce work.
6 stories · Business context first · Engineering one layer deeper
Inside the Salesforce customer success module
SALESFORCEOne customer. Three questions.
What did we agree to?
- Contractual obligations
- Service-level agreements
- Key performance indicators
The module tracked client commitments, SLAs and KPIs so Customer Success could see what had been promised.
Read the full diagram explanation
A Salesforce customer success module brought together obligations, SLAs, KPIs, operational actuals, renewal dates, ARR and TCV. These are groups of information in an account view; the diagram does not imply data feeds from Ironclad or other systems.
A REPEATING PATTERN
Complex information→A usable system→A clearer decision
Customer records become a working view of pipeline, purchasing and commitments.
THE CUSTOMER & THE COMMITMENT
Beyond the pipeline.
Start with the problem.
Then look under the hood.
Fortress / Procurement
Making purchasing a visible workflow
A Salesforce requisition module brought non-labor purchasing, vendor negotiation and supplier information into one process.
Explore story & flowFortress / Revenue operations
From first interest to a commercial agreement
Connecting the commercial journey across HubSpot, Salesforce, DealHub and contract management in Ironclad.
Explore story & flowTHE NEXT INTERFACE
Two skills.
Two different jobs.
A business-data question and an administration question need different workflows. Each Claude skill has its own story.
Explore the AI architecture library ↗Bringing Salesforce data into a Claude skill
A purpose-built skill for cross-functional Salesforce data work, developed and iterated in Claude.
A separate skill for Salesforce administration
Using Claude to look up users and privileges and assist with Salesforce administration flows.
FOLLOW YOUR CURIOSITY
Find your thread.
Browse this collection or connect the dots across all three.
Refine by company, period, capability, technology or domain
6 stories
Taking ownership of the revenue platform
From a platform ownership gap to a shared foundation for accounts, opportunities and pipeline decisions.
Making purchasing a visible workflow
A Salesforce requisition module brought non-labor purchasing, vendor negotiation and supplier information into one process.
From first interest to a commercial agreement
Connecting the commercial journey across HubSpot, Salesforce, DealHub and contract management in Ironclad.
Keeping the customer promise in view
An account view connecting what was promised, how delivery compared and when the renewal conversation needed to happen.
Bringing Salesforce data into a Claude skill
A purpose-built skill for cross-functional Salesforce data work, developed and iterated in Claude.
A separate skill for Salesforce administration
Using Claude to look up users and privileges and assist with Salesforce administration flows.
LET’S CONNECT THE DOTS
What’s the complex problem
on your desk?
Explore how engineering depth and commercial judgment can work together.
Start a conversationThese are personal accounts of professional work. Company and client names identify context and do not imply endorsement. Conceptual diagrams explain relationships; they are not production screenshots.