Skip to content
cccskills
FreePublished on GitHub

field-call-route-discipline

Use to run the daily field motion: routes, call plans, face-to-face cadence, and post-call follow-through.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Field call route discipline

Use this to run the daily field motion. Start from the territory with account tiers and market potential, the call pattern or cadence SLAs, this week's route days, and the open threads from prior calls.

Tier the book

Prioritize the book by call pattern and market potential: tier each account, set the face-to-face cadence per tier, and sequence this week's route so the highest-potential due calls come first.

Plan the route

Plan the route day by day: calls in drive order, objective per call, and buffer for the drop-in that matters. A day with no plan is a day the territory plans for you.

Pre-call plans

Write the pre-call plan before every call: the objective, the two questions that matter, the likely objection with your answer, and the word-for-word ask. One screen, five minutes, no exceptions.

Keep the cadence

Keep the face-to-face cadence SLA: tier-A accounts see you on schedule, and a missed cadence gets a rebook date within the week, not next quarter.

Post-call notes

Write the post-call analysis right after: what was learned, what changed on the opportunity, the dated next step, and the CRM update drafted. The call is not done until the note exists.

Week review

Review the week against the plan: calls made versus planned, cadence hits and misses, pipeline moved, and next week's route seeded. Misses get a cause and a fix, not a carry-forward. Hold the review as a weekly 1:1 pipeline inspection first; the team review is optional. Cover late-stage deals fast, then dissect early-stage ones: how you will work each, the next step, and why any stage moved back. Open with forecast variance before wins, work from a pre-read dashboard, and keep live time for decisions only.

What you hand back

The tiered call plan with cadences, daily routes in drive order, pre-call plans, post-call notes with dated next steps, and a week review with fixes.

Fallbacks

No tiering yet means you draft tiers from deal size and potential labeled INFERENCE and get their yes. No CRM access means the call log lives in the sheet until it can be keyed in. Nothing goes to the buyer and no commitment is promised without your explicit yes.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Write ad variants that each test one idea, within platform limits and supported claims.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill