Sales Data & Reporting Auditor

Why This Role Exists

Zion currently manages ~15 sales reps across multiple offers while also running recruiting, interviews, call reviews, and data integrity. Data integrity is the piece with the lowest skill ceiling and the highest time cost.

Per Josh's Framework 6 (Pipeline Management), this is a named, separate seat for a reason:

Josh once had sales managers audit the CRM daily — chasing reps for missed forms, unmarked show-ups, blank fields. It completely destroyed his capacity model for sales management. The fix was a dedicated CRM Admin owning the tech and data side, so managers spend 30 minutes in the CRM and know everything is where it's supposed to be.

The purpose of this role is to protect the sales manager's capacity. Every hour it buys back gets redeployed into call reviews, rep coaching, and client acquisition — the things that actually move revenue.

The Two Audit Paths

Every issue this person finds falls into one of two buckets. They are handled differently. This distinction is the entire job.

Path 1 — Data Accuracy ? the Auditor fixes it

Data that is wrong or missing because of a system gap, not a rep behavior problem.

• Booked call on the calendar with no lead source attribution.

-Lead in CRM with no meeting date attached.
-Duplicate leads or duplicate calendar events
-Calendar event missing setter initials
-Disposition logged but revenue field blank
-Timezone or date errors on booked calls

Action: fix it directly, log it in the daily report as a count.

Path 2 — Rep Non-Compliance ? the Auditor tags, never cleans
-Data that is wrong because a rep didn't do their job.
-Call happened, no disposition logged
-Show / no-show never marked
-Post-call form not completed
-Lead marked lost with no attempt history
-Deal closed with no payment terms entered
-
Action: tag the rep, create the task, escalate in the daily report. Do not fix it for them.

Non-negotiable, per Josh: "CRM admins audit — they don't clean. Cleaners create lazy reps."

The ---------- nt reps learn someone downstream cleans up after them, compliance collapses permanently and the data problem becomes structural. The Auditor's job on Path 2 is to make non-compliance visible, not invisible.

Daily Responsibilities

Morning — booked call audit (start of day)Pull every call on the calendar for the current day and produce:

1. Total booked calls today, by closer
2. Source attribution on every booked call — Ads (self-booked) / Phone Setter / DM Setter / Triage / Reschedule / Referral
3. Setter attribution by initials on every setter-sourced call
4. Confirmation status per the calendar color convention:
Unmarked = unconfirmed
Red = no answer
Yellow = text confirmation received
Light green = same-day confirmation received
5. Exception list — every call with no confirmation touch at all. This is the highest-value output of the morning report. Every unconfirmed call is a booked call at risk, and it is actionable before the call, not after.

End of day — outcome audit
1. Live calls (showed) vs. booked calls, by closer and by setter.
2. Show rate for the day, and rolling 7-day
3. No-shows and cancellations, with reschedule status: rescheduled / attempted, not reached / no attempt made
4. "No attempt made" list — every no-show nobody has touched. Escalate by name.
5. Missing dispositions — every call with no outcome logged, tagged to the rep.
6. Cash collected logged against calls, where applicable

Weekly — rollup
1. Show rate by setter, trended
2. Booked calls by source, trended — which channel is actually producing.
3. Data-accuracy issue counts by type, trended (are the same issues recurring?).
4. Rep non-compliance counts, by rep name

Metrics This Role Owns

Metrics & Definition:

Booked calls / day = Total on calendar, by closer
Source attribution % = % of booked calls with a source recorded. Target: 100%
Confirmation coverage = % of tomorrow's calls with a confirmation touch logged
Live calls / day = Calls that showed
Show rate = Live ÷ booked, daily and rolling 7-day
Reschedule capture rate = % of no-shows with a documented reschedule attempt
Disposition compliance = % of completed calls with an outcome logged
Data accuracy issues = Count found, count fixed, by category

Show rate belongs to the setter and confirmation layer. It is never a closer metric. This role reports it against setters, not closers.

Explicitly NOT This Role

• Not a sales role.
• No dialing, no setting, no closing, no prospect contact.
• Not a call reviewer. Call quality grading stays with Zion.
• Not a coach. They report data on reps. They never give reps feedback or direction.
• Not a cleaner for rep non-compliance. See Path 2 above.
• Not the person who d ---------- what the numbers mean. They report accurately and flag anomalies. Interpretation and action are Zion's.

Required Skills:
-Must have

• High-volume, detail-heavy data work with near-zero error tolerance
• CRM competence — Close CRM strongly preferred; HubSpot / Salesforce / GHL acceptable
• Google Sheets: pivot tables, lookups, conditional formatting
• Google Calendar
• Slack
• Written English clear enough to write a report a manager reads in 60 seconds

Overlap with US Eastern business hours

Nice to have

• Zapier or Make
• Experience inside a sales team (understands what a booked call, show rate, and disposition actually are)
• Prior audit or QA role

Disqualifying

• Needs to be told the same thing twice
• Reports numbers without flagging when a number looks wrong

Reporting Cadence

When - What - Where

Daily, by 9:00 AM ET - Morning booked-call audit + unconfirmed exception list - Slack
Daily, within 30 min of last call - EOD outcome audit + no-attempt list - Slack
Weekly, Monday AM - Rolling rollup - Slack + Sheet

Format requirement: every report is scannable in under 60 seconds. Number first, exception list second, everything else omitted. Nobody reads a wall of data — the exception list is the product.

30-Day Ramp

Week 1 — observe and document

Shadow the current manual process. Document it as they learn it — that document becomes the role's SOP and its first deliverable.

Week 2 — morning report only

Own the morning booked-call audit. Zion verifies against source data daily. Accuracy before scope.

Week 3 — add EOD report

Both daily reports running. Auditor begins flagging Path 1 data-accuracy issues and fixing them.

Week 4 — full scope

Weekly rollup added. Path 2 rep tagging goes live. Zion spot-checks weekly instead of daily.

Ramp gate: the role is not considered ramped until Zion has spot-checked a full week of reports against source data and found zero discrepancies. Wrong data is worse than no data — it produces confidently wrong decisions.

Documentation Requirement

Every process this person runs gets documented as they run it, not after. By day 30 there should be a complete SOP covering: where each number is pulled from, how each is calculated, the report template, and the escalation path for each issue type.

Per Josh: document while doing, not before delegating. If this person leaves, the replacement should be productive in a week off the SOP alone. The right sequence: hire this person to run it manually and document the exact logic while doing it. That documentation becomes the automation spec. Once the reports are automated, the role shifts from producing the data to auditing it — which is the seat Josh actually describes, and it scales.

Hire for the manual work. Scope the job so it produces the automation.

How to Apply
To be considered for this role, you must include the word "Sesquipedalian" in your email subject line or within the very first sentence of your message. Applications lacking "Sesquipedalian" will automatically be skipped out.

We are reviewing applications on a rolling, fast-track basis to fill this seat immediately with the right candidate. Qualified applicants will receive prompt outreach for an initial interview.