Strategic Gifting logo

Strategic Gifting

Organization
LeadMagic
strategic-gifting

Strategic B2B gifting — John Ruhlin Giftology, Sendoso/Alyce/Reachdesk platforms, buyer gifting compliance, ABM tier budgets, gifting sequences, and CRM tracking. Use when sending executive gifts, direct mail, Sendoso campaigns, or designing gift plays for target accounts. Triggers on: "Sendoso", "Giftology", "strategic gifting", "corporate gifts sales", "ABM gifts", "direct mail gift", "buyer gifting", "physical touchpoint", "gift play", "Alyce", "Reachdesk".

Overview

PublisherLeadMagic
Repositorygtm-skills
Skill namestrategic-gifting
Stars
72
Forks
18
Bundled files
12
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 12 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by LeadMagic on GitHub. Read the source before you install it.

Installation

Install the Strategic Gifting AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/LeadMagic/gtm-skills/tree/main/skills/abm/strategic-gifting
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/LeadMagic/gtm-skills.git /tmp/gtm-skills
mkdir -p .claude/skills
cp -r /tmp/gtm-skills/skills/abm/strategic-gifting .claude/skills/strategic-gifting
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Strategic Gifting in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Strategic Gifting on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Strategic Gifting is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Strategic Gifting

Overview

"Send a mug, call it ABM" wastes budget and annoys buyers. Strategic gifting is a relationship signal — proof you researched the person, respect their policy, and timed the touch to the deal journey. John Ruhlin's Giftology teaches go-deep-not-wide: one remarkable gift beats 100 logo pens. Sendoso (and peers Alyce, Reachdesk, Postal.io) operationalize logistics — address verification, warehouse, CRM triggers — but cannot replace Giftology personalization.

Gifting is not bribery, review incentives (see review-platforms ToS), or a substitute for solving business pain. Use inside ABM programs (abm-strategy) with tier budgets and compliance gates.

When to Use

  • "Set up Sendoso for sales"
  • "Giftology playbook for enterprise"
  • "What gift to send a CRO?"
  • "ABM direct mail + gift sequence"
  • "Buyer gift policy compliance"
  • "Sendoso vs Alyce"
  • "Gift to unblock deal" (usually: don't — diagnose first)
  • "Post-close customer gift"

Do not use for G2/review gift cards — review-platforms (platform ToS). Do not use for customer advocacy rewards at scale — customer-marketing.

Authoritative Foundations

  • John Ruhlin — Giftology. Relationship gifting: personalization, no logo, 3-gift system (them / family / team), story-driven notes. Source: Giftology and Ruhlin Group methodology.
  • Sendoso. Revenue sending platform: eGift, physical gifts, direct mail, CRM/MAP integrations, address confirmation, analytics. Use for execution after Giftology brief is written.
  • ITSMA ABM tiers. Gift budget scales with 1-to-1 vs 1-to-few vs 1-to-many — never same playbook for Tier 1 and Tier 3.
  • Winning by Design Bowtie. Physical touches bridge marketing → sales; post-close gifts support retention (right side of bowtie).

Step-by-Step Process

Phase 1 — Gift vs No Gift Decision

Send gift whenDo NOT send
Tier 1/2 ABM account with research doneCold outbound with no relationship
Post-discovery — reference their wordsActive price negotiation
Post-close thank-youTrying to "unstick" stalled deal (bribery)
Champion appreciation mid-cycleExceeds known company gift cap
Event no-show recovery (personal)Generic holiday blast to list

Stalled deal? Load buyer-indecision (JOLT) — not bigger gifts.

Phase 2 — Giftology Principles (Ruhlin)

Load references/giftology-ruhlin.md.

  1. Go deep, not wide — budget into fewer remarkable gifts
  2. 3-gift system — recipient / family / team
  3. Personalization > price — hobby, alma mater, conversation callback
  4. Story is the gift — object delivers the narrative
  5. No logo — swag is advertising, not gifting
  6. Handwritten note — 3 sentences, references specific conversation

Phase 3 — Platform Selection

Load references/gifting-platforms.md.

PlatformBest for
SendosoSalesforce/HubSpot teams, mixed eGift + physical, SDR/AE self-serve
AlyceEnterprise compliance, recipient choice ("pick your gift")
ReachdeskGlobal ABM, warehouse + marketplace
Postal.ioDirect mail + handwritten at scale
Manual / localTier 1 ultra-custom (Ruhlin-style concierge)

Integrations: CRM task on send, attribution field gift_sent_date, amount, story note. One-direction log — never automate gift without AE approval on Tier 1.

Phase 4 — Budget by ABM Tier

Load references/gifting-by-tier.md.

TierAccounts$/account/yearGift types
1 (1-to-1)5–15$500–2,000Custom physical, team experiences
2 (1-to-few)15–50$150–500Cluster mailer + modest personal
3 (1-to-many)50–200+$25–75eGift, book, useful tool — no junk swag

Track cost per meeting held and cost per opp created — not sends.

Phase 5 — Gifting Sequence Timeline

Load references/gifting-sequence.md.

MomentGift?Example
Pre-first meetingNo—
Post-discovery (D3–5)Small personalReference call detail
Mid-evaluation W3–4Team giftCatered lunch, team asset
Negotiation / legalNo—
Post-close D1Family / thank youRuhlin Gift 2
90d post-closeCheck-in giftRetention bowtie

Coordinate with email: mail arrives before email references it (abm-1-to-few Week 2 pattern).

Phase 6 — Compliance & Buyer Policies

Load references/gift-compliance.md. Gifting spend on Ramp → gtm-spend-management (GTM-GIFT card, monthly cap per tier).

  • Ask champion: "What's your gift policy limit?"
  • Federal / industry rules (gov, healthcare, finance) — often zero
  • Never exceed disclosed cap; document in CRM
  • Finance may require gift disclosure on vendor forms — vendor-contracts
  • Anti-bribery: gift must be defensible as relationship marketing, not quid pro quo

Phase 7 — Sendoso Campaign Build

Load references/sendoso-playbook.md + templates/sendoso-campaign.md.

  1. Create Touch aligned to ABM play (not standalone blast)
  2. Enable address confirmation for physical
  3. Manager approval workflow for >$X
  4. Personalization fields: first_name, account, note from AE
  5. Trigger: manual (Tier 1) or CRM workflow (Tier 3 eGift)
  6. SLA: SDR contacts within 24h of delivery scan

Phase 8 — Multi-Stakeholder Gifting

For buying committees (multi-thread-orchestration):

RoleGift approach
ChampionPersonal Giftology (Gift 1)
Economic buyerConservative; often eGift or book — check policy
BlockerUsually no gift — solve concern
End usersTeam gift (Gift 3) after pilot success

Never gift only champion while ignoring EB on enterprise deals.

Phase 9 — Measurement

MetricTarget (directional)
Delivery → meeting bookedTrack per tier
Gift-assisted opp creationCRM field required
Cost per meeting<1/10 expected ACV
Policy violationsZero

Output Format

RequestDeliverable
Tier 1 gift plantemplates/gift-brief.md per stakeholder
Sendoso setuptemplates/sendoso-campaign.md
ABM gifting programBudget + sequence + compliance
Post-close retentionBowtie gift calendar

Run scripts/check-output.py before delivery.

Quality Check

  • Giftology personalization — not logo swag blast
  • Company gift policy checked or documented
  • No gift during active negotiation
  • Timeline matches deal stage (not pre-first-meeting)
  • CRM log: what, when, why, story
  • Budget matches ABM tier
  • Platform choice justified (Sendoso vs manual)
  • SDR/AE follow-up SLA within 24h of delivery

Common Pitfalls

  1. Sendoso without strategy. Automated Starbucks cards to cold lists. Fix: ABM tier + Giftology brief first.
  2. Logo swag. Fix: Ruhlin — no logo on relationship gifts.
  3. Gift to unstick deal. Fix: JOLT / deal desk — business problem.
  4. Ignore gift cap. Fix: ask champion; log in CRM.
  5. No follow-up. Gift arrives; nobody calls. Fix: 24h SLA + task in CRM.
  6. Same gift Tier 1 and Tier 3. Fix: references/gifting-by-tier.md.

Execution Artifacts

  • references/framework-notes.md — Framework index and authority routing | templates/output-template.md | Deliverable structure | | scripts/check-output.py | Validator | | File | Use | |---|---| | references/giftology-ruhlin.md | Core principles + 3-gift system | | references/sendoso-playbook.md | Sendoso setup and workflows | | references/gifting-platforms.md | Sendoso vs Alyce vs Reachdesk | | references/gifting-by-tier.md | ABM budget matrix | | references/gifting-sequence.md | When to send / not send | | references/gift-compliance.md | Policies, anti-bribery | | templates/gift-brief.md | Per-recipient plan | | templates/gift-crm-log.md | CRM field spec | | templates/sendoso-campaign.md | Campaign checklist |

Related Skills

  • abm-1-to-1 — Strategic account context
  • abm-1-to-few — Direct mail + email coordination
  • abm-strategy — Tier model and measurement
  • multi-thread-orchestration — Committee gifting
  • buyer-indecision — Stalled deals (not gifts)
  • event-driven-outreach — Event follow-up gifts
  • pipeline-management — Stage-appropriate touches

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Strategic Gifting AI skill do?

Strategic B2B gifting — John Ruhlin Giftology, Sendoso/Alyce/Reachdesk platforms, buyer gifting compliance, ABM tier budgets, gifting sequences, and CRM tracking. Use when sending executive gifts, direct mail, Sendoso campaigns, or designing gift plays for target accounts. Triggers on: "Sendoso", "Giftology", "strategic gifting", "corporate gifts sales", "ABM gifts", "direct mail gift", "buyer gifting", "physical touchpoint", "gift play", "Alyce", "Reachdesk".

Why use Strategic Gifting on TypingMind?

Because you install it once and use it with any model. Strategic Gifting is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Strategic Gifting in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/LeadMagic/gtm-skills/tree/main/skills/abm/strategic-gifting. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Strategic Gifting?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Strategic Gifting?

As many as you like. As long as a model supports skills, you can use Strategic Gifting with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Strategic Gifting AI skill free?

Yes. It is published on GitHub by LeadMagic under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇