Leads CRM
Source, status, assigned closer, first contact, tags, and pipeline stage.
Notion backend for a high-ticket sales business
A growing sales coaching and remote-closing business replaced spreadsheet operations with one connected Notion backend.
High-ticket sales 7 connected databases 4-week implementation
When spreadsheets stopped being the backend
The business sold coaching programmes and trained remote closers. Leads, calls, payments, active clients, team performance, and content were tracked across Google Sheets and separate tools. The CEO had to assemble the weekly picture manually from four or more sources.
What had to change
Seven databases, one operating view
Calls Tracker
Lead, call type, result, duration, notes, and relationships to the team.
Payments
Amount, currency, payment method, status, and client relationship.
Active Clients
Programme, start date, renewals, progress, coach, and session notes.
Team Performance
Calls, closed deals, revenue, and conversion rollups for every closer.
Content Pipeline
Topic, format, platform, status, deadline, and owner.
Executive Dashboard
Connected views for weekly metrics, active deals, top closers, and monthly revenue.
Built in four weeks
- 1
Week 1 - Audit and architecture
Reviewed the spreadsheet trackers, designed relations, field types, and the integration naming plan.
- 2
Week 2 - Data model
Built the seven databases with relationships, rollups, and automation-ready fields.
- 3
Week 3 - Working views
Created filtered views by status, owner, and date, including a sales board and content calendar.
- 4
Week 4 - Dashboard and handover
Assembled the executive dashboard and completed a recorded walkthrough for the team.
Documented operational result
“We finally see the whole business - and I no longer need to collect the numbers manually before every team call.”
Designed to connect, without a rebuild
- ManyChat: source tags for lead attribution.
- Calendly: invitee email, event start time, and event type mapped to calls.
- Stripe: payment method, payment ID, and webhook status fields prepared.
- Typeform: Leads CRM mapping prepared through Make.
- Make and Zapier: standardized field names and API-ready relations.
- Slack: a scheduled dashboard digest planned through Make.
The client identity and selected implementation details are anonymized for confidentiality.
Need one source of truth for sales operations?
Bring the current workflow to a 30-minute diagnostic.