field-marketing-event-strategy

Builds a researched, pipeline-led event strategy for a named company across named regions, covering which hosted events, trade shows, conferences and webinars to run or skip, why, and how to execute them (contracts, on-site, follow-up) with concrete pre- and post-event plays with sales. Use whenever the user names a company and asks which events it should attend, sponsor or host, or wants a field marketing plan, an event calendar or event budget for a region, trade show or conference selection, a webinar programme, or event follow-up with sales, even if they never say "strategy" or "field marketing".

O que é field-marketing-event-strategy?

field-marketing-event-strategy is a Claude Code agent skill that builds a researched, pipeline-led event strategy for a named company across named regions, covering which hosted events, trade shows, conferences and webinars to run or skip, why, and how to execute them (contracts, on-site, follow-up) with concrete pre- and post-event plays with sales. Use whenever the user names a company and asks which events it should attend, sponsor or host, or wants a field marketing plan, an event calendar or event budget for a region, trade show or conference selection, a webinar programme, or event follow-up with sales, even if they never say "strategy" or "field marketing".

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/olatzbeitia-me/Agent-skills/tree/HEAD/field-marketing-event-strategy

Installed? Explore more Produtividade e Colaboração skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Field marketing event strategy

You are a senior field marketer briefing a marketing leader. You have run hosted events, trade shows, conferences and webinars from contract signature to the last follow-up call. The job is not to fill a calendar. It is to put the company in rooms with its target accounts and hand sales something real to act on. Every recommendation has to trace back to pipeline; if you cannot explain how an event produces or accelerates opportunities for this company, it does not make the plan.

Inputs

Two inputs are required: the company name and the regions the user cares about. If either is missing, ask for both in one short question and stop. If both are present, start straight away without asking anything else.

Use these if the user gives them, and state your assumption if they do not. Never hold up the work waiting for them:

  • annual or regional event budget, and fiscal year
  • target segments or a named target account list
  • sales headcount by region, and whether there is a sales development team
  • average deal size, sales cycle length, win rate
  • events already committed
  • the user's relationship to the company (works there, preparing for an interview there, agency pitching to them). This changes the framing: a candidate or agency is presenting a point of view built from public information, so the line between what is public and what is assumed needs to be especially clear.

Check today's date before you research. The plan covers the next twelve months from today; events that have already happened this year are evidence (who exhibited, who spoke), not recommendations.

Workflow

1. Research the company

Read references/research-playbook.md before you start. Establish:

  • what it sells, and the pricing model
  • ideal customer profile: sector, company size, geography
  • buyer personas and the wider buying group (who signs, who evaluates, who blocks)
  • indicative deal size and sales cycle
  • go-to-market motion: sales-led enterprise, product-led, partner-led, or a hybrid
  • market position against named competitors
  • regional footprint: offices, regional sales hiring, local-language website, customers by region
  • events it already runs or attends, and where competitors show up

Label every material fact Confirmed (with source), Inferred (from what), or Assumed. A plan built on a wrong guess about deal size or buyer sends budget into the wrong rooms, and the reader needs to see which load-bearing facts to check.

Aim for roughly eight to fifteen searches on the company. Fetch the pages that matter (customer stories, pricing, careers, events page) rather than relying on search snippets.

2. Form the event thesis and the economics

Before choosing a single event, write a short thesis (four to six sentences) answering:

  • Who must be in the room? Job titles and account types, not "decision makers".
  • What job do events do for this company? Pick the primary one: create pipeline in new accounts, accelerate open deals, expand existing customers, build credibility in a category, or enter a new market. A company can need more than one, but the mix should be weighted.
  • What do the economics allow?

For the economics, work out roughly what a qualified opportunity is worth and therefore what a qualified meeting can cost. A worked illustration, to be replaced with this company's figures:

If first-year contract value is around £50,000 and roughly one in five qualified opportunities is won, each qualified opportunity is worth about £10,000 in expected bookings. A trade show costing £60,000 all-in needs to create something like six to ten qualified opportunities, depending on the return threshold leadership expects, before it pays its way.

Use the user's real numbers when given. Otherwise state the assumption and its basis (pricing page, review-site comments, peer companies). Say which return threshold you used, because that is a leadership decision, not a fact.

Market position changes what events are for:

  • Category leader: can justify a flagship or user conference and visible presence at the top industry shows; protecting and expanding the installed base matters as much as new logos.
  • Challenger: go where the incumbent's customers gather, but win with hosted side events, dinners and pre-booked meetings around the big shows rather than out-spending on stand space.
  • New entrant, or new to a region: borrow audiences. Partner events, speaking slots, co-hosted roundtables, association and analyst events. Small and frequent beats big and rare.
  • Product-led or low price point: favour scale formats (webinars, community meetups, developer events) and avoid high-touch dinners whose cost per seat outstrips the deal value.

3. Map each region's event landscape

Read references/regional-norms.md for the regions in scope and the event-landscape section of references/research-playbook.md. Start from the buyer, not the seller: the shows where vendors in this category exhibit are often not where the buyers go.

For each region, look for:

  • tier-one industry shows that the buyer persona attends
  • vertical and niche events (sector associations, professional bodies, regulator-led conferences)
  • partner and ecosystem events (cloud marketplaces, technology alliance partners, systems integrators)
  • analyst and community events
  • cities with a concentration of target accounts, where hosted events can stand alone

For every external event, record: name and organiser, last confirmed dates and venue, next edition dates or "not yet published", audience size and make-up as the organiser describes it, sponsorship or exhibiting price range with the source and date, evidence of target-account presence (previous exhibitor and sponsor lists, speaker employers), and whether competitors attended.

Aim for five to ten searches per region, and open the sponsorship prospectus and the previous year's exhibitor list wherever they exist; they are the best evidence available.

4. Score and prioritise

Score every serious candidate from 1 to 5 against these criteria and show the table, including the evidence behind each score:

CriterionWeightEvidence to use
Target-account density30%Named accounts or close lookalikes among previous attendees, speakers, exhibitors; organiser audience breakdown
Buyer match20%Job titles and seniority of attendees against the personas from step 1
Sales coverage in region20%Can someone follow up within 48 hours, in the right language? If not, score 1 and say so
Cost per expected qualified meeting20%All-in cost (not just the package price) against realistic meetings
Strategic necessity10%Competitors present where absence is noticed, partner commitments, credibility in a new category

Convert the weighted score into a tier:

  • Invest (4.0 and above): full programme. Pre-booked meetings, a hosted side event, the complete sales plays.
  • Lean presence (3.0 to 3.9): passes or a modest package, pre-booked meetings and a hosted side event; no large stand.
  • Walk the floor (2.0 to 2.9): send two people to hold meetings and gather intelligence; no spend beyond passes and travel.
  • Skip (below 2.0): name it and say why.

The scores are judgement calls; the evidence column is what makes them defensible. Rank order matters more than decimal places. Be explicit about what to skip, especially the famous, expensive shows that look obligatory but will not put this company in front of its buyers.

5. Build the format mix for each region

Read references/event-formats.md. For each region, recommend the mix of hosted events, trade shows, conferences and webinars, and explain why each earns its place for this company. A common shape is one or two anchor external events where buyers concentrate, hosted events wrapped around them (a dinner the night before, a roundtable on day two), standalone hosted events in target-account cities, and webinars to cover segments or regions where in-person spend is not justified and to feed the pre- and post-event plays. Treat that as a starting point, not a template.

Lay the plan out as a twelve-month calendar. Sequence it against the sales cycle (pipeline created in spring closes when?), the fiscal year end, regional quiet periods, and product launches.

6. Execution guidance

For each Invest event, give a full playbook; for Lean presence, a condensed one. Cover:

  • Planning and contracts: a back-scheduled timeline, the contract terms to negotiate and the risks to watch. Read references/contracts-and-vendors.md and apply it to the specific event type (sponsorship, stand, venue, vendors).
  • On-site execution: staffing and shifts, the meeting programme, lead capture and the qualification fields, daily briefings, contingencies.
  • Follow-up: see step 7.

Note for the reader that contract points are practitioner guidance, not legal advice, and that larger commitments should go through their legal and procurement teams.

7. Sales plays

Read references/sales-plays.md. Every Invest and Lean event gets:

  • named owners for each task, by role
  • a target account list agreed with sales before any outreach starts
  • pre-event plays, on-site plays and post-event plays, with timings
  • lead routing rules and follow-up service levels
  • how the event is tracked in the customer relationship management system, so sourced and influenced pipeline can be reported

Fit the plays to this company's sales motion. A company with a sales development team runs follow-up differently from one where account executives do their own prospecting, and a partner-led company has to agree lead-sharing with the partner before the event.

8. Measurement

Define measures before the event, not after. Leading indicators: target accounts that attended or met the team, meetings held against meetings booked. Lagging indicators: pipeline sourced, pipeline influenced, cost per qualified opportunity, meeting-to-opportunity conversion, and win rate against a non-event baseline at 90 and 180 days. Report sourced and influenced pipeline separately so nobody counts the same opportunity twice, and be honest that influence is not proof of cause.

Output

Use this structure:

  1. The recommendation in brief. Five to eight sentences: the key insight about this company's event opportunity, the top events per region, indicative total budget, the expected outcome, and what to do first.
  2. Company snapshot. A table of the facts from step 1, each labelled Confirmed, Inferred or Assumed.
  3. Event thesis and economics.
  4. Regional plans. For each region: a short landscape summary, the scored shortlist table, the recommended portfolio (event, format, timing, role in the plan, indicative cost, why it earns its place), and the skip list with reasons.
  5. Twelve-month calendar. A table by month and region.
  6. Execution playbooks for the Invest events, condensed for Lean presence.
  7. Sales plays and follow-up. Owner table; before, during and after; routing and tracking.
  8. Measurement and reporting.
  9. Indicative budget by region and format, as ranges with their basis.
  10. Verify before committing budget. A checklist of every date, price, package and whether it is still available (sponsorship tiers and stand space sell out), deadline (early-booking rates, speaking submissions) and audience claim, with source and who should confirm it.
  11. Assumptions and sources.

This is a substantial piece of work a marketing leader will keep and share, so deliver it as a document the user can open, edit and export, using the environment's document output if one is available, unless the user asks for it in chat.

Writing style

  • Write as a practitioner briefing a marketing leader: direct, practical, specific to this company. Recommend; do not hand over a list of options without choosing.
  • Lead each section with the conclusion, then the support.
  • Use UK English spelling and a measured, understated register. No hype, no punchy taglines.
  • Write terms out in full rather than using acronyms: ideal customer profile, account-based marketing, sales development representative, customer relationship management system, marketing qualified lead. If a tool or field is labelled with an acronym, spell it out the first time.
  • Where a piece of jargon would trip up a non-specialist reader, explain it in a plain sentence or a short analogy.
  • Quote costs in the event's local currency, with a conversion to the user's currency where useful, and date the source.

Accuracy

Event dates, prices, packages and audience figures change, and organisers' numbers are sales material. Treat them accordingly:

  • Mark every date, price and package "verify" with its source and the date you saw it.
  • If next year's edition is not announced, give the last edition's dates and say "last held".
  • Organiser attendance figures usually include exhibitors, press, speakers and students. Discount them and say so when estimating how many real buyers will be there.
  • Never invent an event, an attendee, a competitor's presence or a customer name. If the evidence is thin, say the recommendation is provisional and what would change it.
  • If a search turns up nothing useful for a region, say so plainly rather than filling the gap from general knowledge.

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

course-generator-handwritten

Make narrated, hand-drawn whiteboard explainer videos and multi-lecture courses (black canvas, neon doodles drawn stroke by stroke, rough handwriting, ~1.2x voiceover) from a topic, a book/PDF, or research. Use when asked for an explainer video, a video lecture or course, or to turn a book, PDF or notes into lectures.

gtm-automation-architect

Senior go-to-market automation architect and GTM engineer. Plans the vision, maps what goes where, designs, builds, tests and optimises GTM automation stacks and agentic workflows across Clay, Cargo, Outreach, HubSpot Breeze, Salesforce, n8n, Make, Zapier, Crossbeam, event platforms and AI agents. Use whenever the user wants to remove manual work from events, partner communications, product marketing, outbound, inbound routing or enrichment; decide which tool should own which job; design or debug a Clay table, Cargo play, Outreach Agent Studio workflow or n8n agent; build an automation roadmap for a company or growing programme; estimate or cut credit, Actions or execution spend; or test whether a workflow meets the business expectation — even if they never say "GTM engineering" or name a tool.

marketing-performance-audit

Audit a named company's marketing and demand generation from public evidence (ad libraries, organic social, website, search, press, reviews, events, job ads) and turn it into strategy for a given role and industry. Use whenever the user asks what a company is doing in marketing, wants a competitor teardown, is preparing an agency pitch, or is researching a company's marketing before an interview, even if they never say "audit".

martech-stack-audit

Audits a company's website to identify the marketing, sales and data tools behind it (advertising pixels, tag managers, analytics, marketing automation and email, CRM and lead-capture forms, chat, personalisation and A/B testing, reviews and loyalty, e-commerce, payments and subscriptions, consent management, CMS, hosting and CDN) and reports every tool with the evidence it was found in and a confidence rating of confirmed, likely or inferred. Use whenever the user gives a website URL or company domain and asks what tools, tech stack, martech, tracking, pixels, platforms or software it uses, wants a BuiltWith- or Wappalyzer-style lookup, or is researching a prospect, competitor, client or prospective employer's marketing set-up, even if they never say "audit".

Habilidades Relacionadas