sales-skills/sales-sweeplift

SweepLift Platform Help

SweepLift runs incentivized lead-generation campaigns: paid ads → landing page → a pre-qualification survey → a gift-card reward → a booked meeting, with leads scored 0–10 and pushed to your CRM. Help the user set up campaigns, design surveys that filter bad-fit leads, protect show-rate, tune incentive economics, and wire the data into their stack.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

Ask only what you need (skip if the prompt already answers it):

1. What's the goal? — (A) launch a first incentivized campaign, (B) fix a running campaign (junk leads / no-shows / cost), (C) wire SweepLift data into a CRM/Slack, (D) evaluate whether incentivized lead gen fits their motion/pricing.
2. Sales motion & ACV — high-ACV B2B (where a $50–200 incentive is cheap vs. a meeting) is where this works; low-ACV/PLG usually isn't.
3. Stack — which CRM (HubSpot, Salesforce), and do they want API, Zapier, or native sync?
4. Where's the pain — lead quality, show-rate, cost-per-meeting, or fraud (gift-card farmers)?

Skip-ahead rule: if the user's prompt already contains enough context, go straight to Step 3.

Step 2 — Route or answer directly

| If the user is really asking about… | Route to | |---|---| | Designing a lead-scoring model across CRMs/MAPs (weights, MQL/SQL thresholds) | /sales-lead-score | | Sending physical gifts / e-gifts to known named accounts for ABM | /sales-account-map | | Retargeting strategy across ad platforms (not the incentive layer) | /sales-retargeting | | Landing-page / funnel conversion strategy generally | /sales-funnel | | Reward fulfillment / payout compliance (1099, global gift cards) as an API layer | /sales-marketplace-payouts | | Connecting tools via Zapier/webhooks generally | /sales-integration |

When routing, give the exact command: "This is a {domain} question — run: /sales-{skill} {user's original question}".

Step 3 — SweepLift platform reference

Read references/platform-guide.md for the full reference — modules and automation surface, pricing/plan gates, data model (JSON), the API/Zapier surface, and integration recipes. For the known API surface specifically, see references/sweeplift-api-reference.md.

Answer using only the relevant section — don't dump the whole guide.

Step 4 — Actionable guidance

Ground every answer in these imperatives:

• Lead with the survey, not the incentive. The pre-qualification survey (≥5 questions that both qualify and disqualify) is what separates real pipeline from gift-card farmers — tell the user to design disqualifiers first, then set the incentive. An incentive with a weak survey buys junk leads faster.
• Protect show-rate deliberately. A booked meeting is not a held meeting — the recurring failure is prospects who remember only the gift card. Recommend releasing the reward after the meeting is held (not on booking), plus reminders and an educational-video step that makes non-serious leads self-select out.
• Size the incentive to the meeting, not the click. State a starting point (~$50 for a 30-min meeting; higher lifts volume, sometimes past what sales can handle) and frame it as best-effort — the real cost to benchmark is cost-per-meeting-held (~$200–300+), not cost-per-lead.
• Treat fraud as a design problem. Surface it explicitly: dedupe, disqualifier questions, the video filter, and reviewing lead-score distribution catch gift-card farmers; call it out even if the user didn't ask.
• For integration questions, be concrete about the surface. SweepLift pushes leads, 0–10 scores, and survey answers to the CRM/Slack in real time via its API and Zapier — but there are no public API docs; tell the user to request API access/keys from SweepLift and prototype the CRM mapping in Zapier first.
• Flag pricing as best-effort. It's a hybrid managed-service (~monthly fee) + ad spend + per-lead incentive model with no public tiers — point the user to confirm current numbers with SweepLift directly.

If you discover a gotcha or workaround not in references/learnings.md, append it there with today's date.

Gotchas

Best-effort from research (2026-07) — review these, especially plan-gated features and integration details that may be outdated.

• No-shows are the #1 failure. Prospects who only wanted the gift card book but don't attend. Release the reward after the meeting is held, add reminders, and gate the reward behind an educational-video/qualification step.
• A weak survey = junk leads. The incentive amplifies whatever your qualification lets through. Write disqualifier questions (budget, timing, fit) before touching the incentive value.
• Gift-card farmers / fraud. Repeat/fake entrants chase incentives. Use dedupe, disqualifiers, the video filter, and watch the 0–10 score distribution for anomalies.
• API exists but is undocumented publicly. Real-time push to CRM/Slack runs over SweepLift's API + Zapier, but docs.sweeplift.com doesn't exist — request access from SweepLift; don't assume self-serve keys.
• Not for low-ACV motions. A $50–200 incentive only pencils out when a meeting is worth far more; for PLG/low-ACV it usually attracts the wrong economics.
• Pricing is managed-service + ad spend + incentives, not a public self-serve SaaS tier — treat any number as best-effort.

Related skills

• /sales-lead-score — Design the lead-scoring model that SweepLift's 0–10 scores and survey answers feed into
• /sales-account-map — ABM strategy for named accounts (incl. gifting known contacts, vs SweepLift's inbound capture)
• /sales-retargeting — Retargeting-campaign strategy across ad platforms
• /sales-funnel — Landing-page and funnel conversion strategy
• /sales-marketplace-payouts — Reward-fulfillment and payout-compliance as an API layer
• /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code

Examples

Example 1: Junk leads flooding in

User says: "We turned on a SweepLift campaign with a $100 Amazon card and now we're drowning in leads that go nowhere." Skill does: Diagnoses it as a qualification problem, not a traffic problem — walks through adding ≥5 disqualifier survey questions (budget, authority, timing, fit), moving reward release to after the held meeting, and using the score distribution to spot farmers. Reframes the metric from cost-per-lead to cost-per-meeting-held.

Example 2: How much to offer

User says: "Is a $50 gift card enough to get VPs to take a 30-minute call?" Skill does: Gives the ~$50 starting point for a 30-min meeting (best-effort), explains that higher values lift volume but can outrun sales capacity and attract lower intent, and steers the decision by ACV and cost-per-meeting-held rather than by the headline incentive.

Example 3 (automation): Sync leads + scores to HubSpot

User says: "How do I get SweepLift leads, their 0–10 scores, and survey answers into HubSpot automatically?" Skill does: Explains SweepLift pushes leads, scores, and survey answers in real time via its API and Zapier; that there are no public API docs so you request access/keys from SweepLift; and recommends prototyping the field mapping (score → custom property, survey answers → contact fields) in Zapier first, then hardening to the API. Points to references/sweeplift-api-reference.md.

Troubleshooting

Prospects book but don't show up

Cause: The incentive rewards booking, not attending — some entrants only want the gift card. Solution: Release the reward only after the meeting is held; add reminder touches; keep the educational-video/qualification step so low-intent leads drop before booking.

Campaign attracts fraudulent / low-quality leads

Cause: Weak survey + attractive incentive = gift-card farming. Solution: Add hard disqualifier questions, dedupe entrants, use the video filter, and review the 0–10 score distribution for clusters of suspiciously identical or low-fit entries.

Leads/scores aren't reaching the CRM

Cause: Sync relies on SweepLift's API or Zapier, and there are no public API docs to self-configure. Solution: Request API access/keys from SweepLift, confirm the native connector (HubSpot/Salesforce/Klaviyo/Customer.io) or build the Zapier zap, and map score + survey-answer fields explicitly. See references/sweeplift-api-reference.md.