AlterCall / Sales visibility / System 04 of 06
2021Recorded work
Sales funnel and daily KPI visibility
Give the sales team a daily view of registrations, course engagement, appointments, sales and collected cash, with a clear source for each measure.
- Noah’s contribution
- Noah developed and documented reporting workflows and described building the sales dashboard with a collaborator.
- Historical stage
- Historical collaborative dashboard and configured course-KPI walkthrough
- Part of the business
- AlterCall overview ↗
- Google Sheets
- Make / Integromat
- Stripe
- Close
- GoHighLevel
- Kajabi
- Zapier
- Lucidchart
Inside this system
The workflow
The handoffs
inside the work.
Follow the main path and its branches. Select a step for context; the account below explains what was built, tested or planned.
- Registration, start and bookings
Separate scenarios supply course, discovery and qualifying closing-call milestones. - Successful payment intent
Successful Stripe payment events supply the daily collected-cash path. - Subscription or one-time sale
Invoice and subscription data determine the amount on the modeled sales path. - Human qualification feedback
The daily form supplies qualified and unqualified link counts. - Find today’s tracking row
Each event selects the dated record and the specific counter it updates. - Convert collected cash
Convert Stripe minor units and add actual received payment amounts. - Calculate modeled sale value
Branch between recurring amount × required payments and the one-time amount. - Extract qualification counts
Read the form’s supplied qualified and unqualified values for immediate updates. - Daily KPI tracking sheet
Keep distinct funnel counts, collected cash, modeled sales and qualification measures. - Setter and closer visibility
Review appointments, attendance and sales activity in the collaborative dashboard. - Trace the source workflow
Column headers and linked process documentation show where each measure comes from.
Key records
The information
that carries forward.
| Record | Information | Purpose |
|---|---|---|
| Daily tracking row | Date, registrations, starts, bookings, qualification and financial fields | Compare stages without collapsing them into one total. |
| Sales activity | Conversations, appointments set/held, reschedules and no-shows | Understand the sales handoff and appointment outcomes. |
| Payment-derived amounts | Successful cash amount and separately modeled contract value | Distinguish money received from the value attributed to a sale. |
Inside the system / 01
Give the sales funnel distinct milestones
The dashboard separated outreach conversations, appointments set, appointments held, reschedules and no-shows. Setters and closers had their own views, alongside entry routes such as free courses and webinars.
Noah built the dashboard with a collaborator. Separate automated updates supplied daily registration, course-start, discovery-booking, closing-booking and qualification counts, keeping each milestone distinct.
Inside the system / 02
Make the source of a number discoverable
The tracking sheet used a dated daily record. A scenario found today’s row and incremented the relevant field when its event occurred. Form registration contributed to the registration counter; a course-start event updated started courses; discovery and closing bookings had their own paths and conditions.
The column headings linked back to the scenario responsible for each measure. A Lucidchart diagram also linked the scenarios, sheets, GoHighLevel workflows and Zaps in their general order. That gave a maintainer a route from a visible number to the automation that produced it.
Inside the system / 03
Separate payment cash from a sale’s modeled value
The financial paths distinguished successful payments from the larger value attached to a sale. Successful Stripe payment intents contributed cash received for the day. Stripe’s minor-unit amounts were converted before being added to the spreadsheet totals.
For subscription sales, the walkthrough calculated a modeled total by multiplying the recurring amount by the number of required payments. One-time payments followed a separate amount path. That modeled contract value described expected payments; it was not the same as cash already collected, and it was not an accounting determination of recognized revenue.
Inside the system / 04
Bring human feedback into the same operating view
The daily feedback form supplied qualified and unqualified link counts. The walkthrough described moving those updates from a midnight batch to immediate processing. That connected human qualification activity with the event-generated course and booking measures.
The contribution was a daily operating view with distinct measures and traceable sources. It was not an audited financial system; concurrent-update handling, full financial reconciliation and quantified sales improvement were not established.
Within AlterCall