Sales Every Day Agent

Skill packs › Skill

Sales Every Day AgentIN EVERY PACK

The Sales Every Day Agent — the capstone. Runs on a schedule (that’s the point), reads YOUR funnel and YOUR weekly MAA, and comes back each morning with ONE staged selling action – the email drafted, the post written, the follow-up list ready. You review over coffee and click send. Nothing invented, nothing sent without you.

Skill file sales-every-day.md · last updated Aug 2, 2026

How to run it. Download any pack from the skill-pack directory, unzip it into your Claude project folder, and this skill is one of the files inside. You do not paste it anywhere — the agent reads it when the job calls for it. This one ships in every pack.

The rule this agent enforces: you sell every day. Not “launch twice a year.” Not “post when inspired.” One deliberate selling action, every working day, aimed at the weakest stage of YOUR funnel. Most owners don’t skip this because they disagree — they skip it because deciding what today’s action is costs more willpower than doing it. So the agent decides, stages, and hands you the finished draft. You keep the judgment and the send button.

The daily-selling discipline was battle-tested inside Sigrun’s SOMBA program (her Sales Every Day® system); this is the general-business edition.

Read these first, every run: your brand-voice document, your ideal-client file, and your links file (real domains, offer pages, socials) — plus your latest weekly MAA (see the weekly-brand-maa skill). Everything below is grounded in those. If a file is missing, say which one and use the rest.

The funnel this agent watches

Lead magnet → Low-ticket offer (the small obvious next step, typically $7–197) → Core offer → Follow-up → Recurring/retainer. Revenue = traffic × conversion, stage by stage. Your weekly MAA names your weakest stage; this agent turns that diagnosis into daily motion. The most common gaps we see: a lead magnet and a core offer with nothing low-ticket in between, or no opt-in page at all. Local-business variant of the same funnel: free estimate → small paid diagnostic → the full job → review + referral ask → maintenance plan.

Why this agent is SCHEDULED (the whole point)

Every other skill waits for you to remember it. This one doesn’t. Tell Claude once — “Create a scheduled task: every weekday at 7am, run my sales-every-day skill and leave today’s action pack in my Outputs folder” — and from then on it behaves like a tiny sales department that reports for work before you’re awake. That’s the difference between having agents (you drive every run) and employing them (they run in loops and come back to you).

Hard rules

  • Draft-only. Emails = drafts, never sent. Pages = drafts, never published. DMs = a prepared list with suggested wording, never messaged. YOU send.
  • Nothing invented. Offers, prices, testimonials, links — only from your files or pages actually fetched and verified live. No fabricated urgency, no fake scarcity, no made-up bonuses.
  • Your voice. Brand-voice file governs. Style gate as a mechanical LAST pass: no “not just X, but Y”, no em-dash soup, no AI-tell words, quotes verbatim.
  • One action per day. Never a to-do list of five things. The agent’s discipline protects yours.
  • Log every run to Outputs/sales-every-day/log.md (date · funnel stage targeted · action staged · what you did with it). The agent reads the log first — it never repeats yesterday’s action, and it notices when you haven’t sent anything in 3 days (and says so, kindly, once).

Inputs

  • Latest weekly MAA — weakest stage + this week’s focus (run the weekly-brand-maa skill if you don’t have one).
  • Your knowledge base: brand-voice, ideal-client, links file, offers + prices if listed.
  • Your list size / email platform if connected (optional), your site (optional), your socials (optional).
  • The log from previous runs.

The daily loop (steps)

  1. Read state. Log first. Then MAA + knowledge base. Identify: weakest funnel stage, this week’s focus, what was staged yesterday and whether it went out.
  2. Pick TODAY’s action from the stage playbook below — the single highest-leverage move you can complete as a draft right now. Weekly rhythm guide: Mon plan + pipeline sweep · Tue content-to-offer · Wed list email · Thu follow-up day · Fri proof + MAA handoff. The stage playbook overrides the rhythm when a stage is BROKEN (no opt-in page beats everything).
  3. Build the asset, completely. Not an outline — the finished draft, grounded in your files, links verified live.
  4. Stage it where you can act in one click (email draft, page draft, ready-to-paste post + open-this-profile list). If your CRM (HighLevel, etc.) or email platform is connected, stage the email/page/automation as a DRAFT right inside it. Say exactly where it is.
  5. Report in 5 lines: today’s action · why this stage · where the draft is · what to click · yesterday’s action status (sent/not).
  6. Fridays only — pre-fill your weekly review. Three answers drafted from this week’s log: what went out, what’s next, where you had trouble — so the weekly MAA takes one minute, not twenty.

Stage playbooks (what “today’s action” looks like)

No opt-in / lead-magnet page (fix FIRST — nothing enters an empty funnel):

  • Day 1: full opt-in page draft — headline, 3 bullets, form block, your lead magnet’s promise in your voice.
  • Day 2: the lead magnet itself outlined from your best existing content (a video or post you already made).
  • Day 3: delivery email + welcome email drafts. Day 4: a social post driving to it. Day 5: MAA proof check.

Low-ticket gap (lead magnet + core offer but nothing in between — the #1 gap):

  • Day 1: low-ticket concept memo — 3 candidates carved FROM your core offer (a module, a workshop, a template pack, a paid diagnostic), each with price point and one-line promise; recommend one.
  • Day 2: its sales page draft. Day 3: the “P.S. upgrade” email to lead-magnet takers. Day 4: social proof post. Day 5: pipeline math — how many low-ticket buyers = one core-offer client.

No core-offer sales page: page draft from your testimonials + offer facts, then traffic moves.

Funnel complete → daily selling rhythm (rotate, never the same move twice in a row): one value email with a P.S. offer mention · one follow-up sweep (everyone who raised a hand in 30 days, with suggested one-line personal replies — sell without selling) · one same-day offer when the moment fits · one proof post (client win, verbatim quote) · one open-loop content post → lead magnet. For local businesses add: one review ask to a just-served customer · one quote-chase call list with talking points.

Output

Outputs/sales-every-day/<date>/ with the day’s asset file(s) + report.md (the 5-line report), and the appended log line. If email/site/CRM access is connected: the draft staged there, status verified and stated.

Definition of done

  • One finished, sendable asset exists for today — review under 10 minutes, send in one click.
  • It targets your CURRENT weakest stage, not a generic tip.
  • Zero invented facts/links/prices; style gate run LAST, mechanically.
  • The log line exists; the agent knows what tomorrow must not repeat.

Pairs with

→ weekly-brand-maa (the diagnosis this acts on) → measurement-analytics (real numbers instead of snapshots) → content-agent / content-factory (your raw material) → dollar-a-day-strategist (amplify the winners) → recursive-self-improvement-qa (grade the week, sharpen next week)


Built by Dennis Yu (BlitzMetrics / Local Service Spotlight). Scheduled by design: a sales department that reports for work before you wake up — and never sends a word without you.

<!– learning:ghl-mcp-truth-2026-07-27 –>

Connecting to a CRM / marketing platform — and the one hard limit

Work at whatever tier the client has granted, and say which tier you used in every report.

  • Tier 0 — nothing connected. Read their files and public pages, produce finished drafts. Full value on day one.
  • Tier 1 — email platform. Stage the day’s email as a real draft. Never schedule, never send.
  • Tier 2 — their website. With a WordPress application password, publish opt-in and sales pages as drafts.
  • Tier 3 — CRM. See below.
  • Tier 4 — ads + analytics. Read-and-recommend only. Never change a budget, never spend.

HighLevel / GoHighLevel (and white-labels of it, e.g. SOMBAio): connect through HighLevel’s official MCP server at https://services.leadconnectorhq.com/mcp/, authenticated with a Private Integration Token the client creates at Settings → Private Integrations in their own location. Never ask for, or accept, an account password — a PIT is scoped and revocable.

What the connector gives you (36 tools): contacts (create/update/upsert/tag/search), conversations (search, read, send), opportunities and pipelines, payments (orders, transactions), calendars, forms, custom fields, social posts, blog posts, and email templates (create + fetch).

What it does NOT give you — state this plainly rather than working around it: you cannot create or edit a funnel/landing page through HighLevel’s API. Funnels are absent from the MCP entirely, and the REST Funnels API is read-only (list funnels, list pages, count pages). No create, no update, in any version. So: write the page onto the client’s own website as a draft (better for their SEO anyway, and platform-neutral), and hand them paste-ready copy mapped to their page template. Never drive the CRM’s UI by browser automation to fake a page build.

Send safety: conversations_send-a-new-message sends a real message to a real person. Never call it on a scheduled run — draft it and let the human send. Treat social-media-posting_create-post as publishing and get an explicit yes per post. emails_create-template is safe: it creates a template, it does not send a campaign.


Other skills: ai-search-visibility · boil-the-ocean · client-access-checklist · client-relationship-cadence · content-agent · content-factory

The full run order is on the skill-pack directory. Every skill here is one task from the Task Library — the library is the catalogue of what can be done; a pack is the subset you install; an agent is who runs it.

Where this sits in the system

A skill is a document. A pack is a folder of documents. Neither one does any work. Work happens when a job runs those skills on a schedule, checks its own output, and keeps its files somewhere it can read them again tomorrow. That is the whole difference between owning skills and having an agent.

  1. Skill — one task, written down to a standard, so an agent can run it without you in the room. There are 239 of them.
  2. PackYOU ARE HERE — those skills bundled into a download you install in one paste.
  3. Agent — a named role with a job description — not a chat window you retype every morning.
  4. Job — a schedule, a QA cycle, and somewhere to keep working files. Miss any of the three and nothing runs twice.
  5. Proof — every finished run written up in public, and the lesson pushed back into the skill.

The map: The System · every asset: Asset Tracker · next door: Asset Tracker.

Scroll to Top