Case study · Vertical SaaS · Revenue operations
Leading vertical SaaS for golf course operators, serving more than 1,500 courses.
Claude to Salesforce integration
Noteefy's sales reps couldn't read their own revenue data without having to involve a software engineer for every question. We built a custom Claude to Salesforce integration, so any rep can ask any question of their pipeline in plain English without using engineering resources.
Stack
Django
React
Trigger.dev
PostgreSQL
Datadog
Salesforce MCP
ClaudeDeployed in Noteefy's own environment, scoped to native Salesforce ACLs.
The problem
The sales team couldn't ask their own systems a question without an engineer in the loop. Ten reporting requests a week piled up in the engineering queue.
Which accounts are stuck in proposal over 30 days in our top segment?
A question a rep should answer in seconds was taking a week and a sprint ticket. Sales is information work, and the team that can ask better questions of its own data wins more deals.
Engineering reporting queue
10Pipeline by region
waiting 3d
QBR cohort export
waiting 2d
Stuck deals · top segment
waiting 1d
Vertical breakdown
waiting 5h
+ 6 more in queue
Our approach
We ran the engagement as a phased program, not a tool drop. Each phase had explicit gates so leadership could see progress from kickoff to rollout.
Phase 1
Readiness
Mapped Salesforce permissions and the recurring questions reps were asking.
Phase 2
Build
Built a custom Claude to Salesforce integration, tuned to how this revenue team actually works.
Phase 3
Deploy
Shipped to the customer's private environment with every integration wired and live.
Phase 4
Train
One on one custom onboarding with all reps on the revenue team, against their own pipeline and data.
What we shipped
Three deliverables, built and rolled out together.
Custom Claude to Salesforce integration
Salesforce exposed to Claude as a queryable surface, scoped to each user's native permissions.
Reports on demand
Reps describe what they need in plain English. The system returns the slice, cohort, or chart in seconds.
Per rep training and setup
One on one with all reps, against their own pipeline. Workspace, access, and prompts wired before the session ended.
Security & governance
Deployed in the customer's private environment. No data ever left their tenant.
The integration layer enforces each user's native permissions. The system cannot query data the user couldn't already see.
Zero training on their data, contractually, under enterprise terms with the model provider.
Permission scope · per user
Read
Update
Export
Account Exec
Sales Manager
SDR
Mirrors native source-system ACLs
Adoption
Training wasn't a lecture. We ran a one on one with every rep on the revenue team, showed them what they could now ask their own systems, and had everything set up on their laptop before the call ended. The result: 100% adoption across the revenue team.
Active reps · weekly
100%
W1
W2
W3
W4
W5
W6
W7
Outcomes
What changed after the rollout.
Engineering capacity reclaimed
Sales reporting requests to engineering dropped from ten a week to zero. Sprint capacity that used to service pipeline queries now ships product.
A faster sales team
Reps pull their own numbers, research accounts, and build their own quarterly review lists. The team moves 5x as fast, and prep before a customer meeting went from an hour to two minutes.