ProgrammableMarketing/usepylon.com (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 6
  • This quarter · 9
  • Big bets · 3
  • Wildcards · 3
  • How we can help
Generated Oct 21, 2026
  1. Programmable
  2. Playbooks
  3. Pylon
Pylon logo

growth playbook · Oct 21, 2026

usepylon.com (opens in a new tab)

Pylon growth playbook

Diagnosis

Pylon is hiring for the post-sales side and for Europe, not for marketing. Three new heads (Customer Success, Support, Solutions) will run the company's biggest bet, moving 1,600+ customers to agentic support and usage-based billing, while a London team across sales, CS and support opens EMEA.

There is no marketing role on the board, so growth has to come from what those leaders do in public and from proof: the support team as customer zero, the CS lead as a known voice, migration plans and pilots that close deals.

The gaps this playbook targets are specific: the security page says the whole company is in San Francisco and says nothing about where data lives, no published customer story is European, and the credit estimator ends in a number buyers cannot take to finance.

Growth Score

8/10

Biggest Opportunity

Win Europe and the move to credits with proof Pylon already has: an EMEA buyer pack, European stories, a published migration plan, backtested pilots and a cost brief customers can forward.

Biggest Risk

The pricing change to credits could dent 159% net retention if customers face surprise costs, while slower European security reviews delay the London team's first quarter.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    An EMEA buyer pack that answers data residency, GDPR and "who is in Europe?" before the first call

    List the ten questions EMEA prospects asked in security reviews this year and write one-paragraph answers.

    High impact First result in 3 weeks
  2. 2

    Turn the credit estimator into a cost brief a buyer can forward to finance

    Write the brief template using the estimator's own three inputs.

    High impact First result in 1 month
  3. 3

    Publish "how Pylon runs support on Pylon": the customer-zero numbers, every month

    Pull last month's internal support metrics from Pylon's own workspace.

    Medium impact First result in 1 month

02

Your idea portfolio

21 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 7 ideas are marked Unexpected: plays you are unlikely to have tried.

    1 of these are things Programmable can build and run for you.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 4Big bets · 9Fill-ins · 5Reconsider · 3
Effort →

Showing 21 of 21 ideas

This week 6

Quick wins with a clear first action.

  • 01

    The new London AE is told to navigate data residency, GDPR and procurement, but the security page answers "Where are you based?" with "The entire company is based out of San Francisco" and says nothing about where data lives. A European security reviewer reads that as a reason to wait.

    High impactLow effort First result in 3 weeks Account Executive

    First action

    List the ten questions EMEA prospects asked in security reviews this year and write one-paragraph answers.

    How to measure it

    EMEA deals passing security review within 3 weeks

    Now
    –
    Target
    80%
    By
    1 quarter

    Steps

    1. 1

      Collect the questions

      Pull the last ten EMEA security questionnaires and note every repeated question.

      Account Executive, EMEA 1 day

    2. 2

      Confirm the facts

      Get the hosting region, any EU option and the sub-processor list confirmed by engineering.

      Head of Solutions 2 days

    3. 3

      Rewrite the FAQ

      Replace "The entire company is based out of San Francisco" with the three offices.

      Account Executive, EMEA 1 hour

    4. 4

      Publish the DPA

      Make the DPA and sub-processors downloadable from the trust center.

      Head of Solutions 1 day

    5. 5

      Build the EMEA page

      London team, GDPR answers, certifications and a review booking link.

      Account Executive, EMEA 2 days

    6. 6

      Use it in outbound

      Attach the PDF to first-touch emails to European security-sensitive accounts.

      Account Executive, EMEA 1 hour

    7. 7

      Review monthly

      Add every new question from deals to the page.

      Account Executive, EMEA 1 hour a month

    First result
    3 weeks
    Cost
    $0
    Owner
    Account Executive, EMEA

    Smallest test

    Send the draft pack to three EMEA prospects in active review and track whether questionnaires shrink.

    Why it works

    A short EMEA page and a matching PDF: where customer data is hosted today and any EU option, the DPA and sub-processor list as downloads (not "ask us"), the certifications already held (SOC 2 Type 2, ISO 27001, ISO 42001), the London team, and a 30-minute security review offer. Update the FAQ answer so it names San Francisco, New York and London.

    European deals stall in procurement, not in the demo. Pylon already holds the certificates that matter; the gap is that the page does not say so in the words a European reviewer searches for, and the AE is measured on closing in a region where the company looks absent.

    Ready to use

    ChecklistEMEA security answers to publish

    [ ] Where is customer data hosted, by default?
    [ ] Is an EU hosting option available, and from when?
    [ ] Download link for the DPA
    [ ] Current sub-processor list with locations
    [ ] SOC 2 Type 2, ISO 27001 and ISO 42001 reports: how to request
    [ ] How AI agents use customer data, and whether it trains any model
    [ ] Who in London to contact for a security review

    Risks and how to handle them

    • Promising an EU option that does not exist yet

      Only state what engineering confirms; say "on request" or "planned" where true.

    • Legal wording

      Have counsel review the DPA summary.

    Evidence

    • HiringAccount Executive, EMEA (London, posted October 15, 2026): "EMEA is already a meaningful part of Pylon's business, and London is where we're investing next", with a small team being built "across sales, customer success, and support, in a new region and a new office". The AE runs full-cycle inbound and outbound deals, handles "data residency, GDPR, and procurement cycles", and feeds what they learn into "positioning, messaging, and playbooks". Sales stack adds Amplemarket and Salesfinity.Source
    • Your websiteTrust & Security page: SOC 2 Type 2, GDPR ("Ask us for our DPA"), HIPAA BAA on enterprise, ISO 27001 and ISO 42001; security reviews and custom MSAs are Enterprise-only. Its FAQ answers "Where are you based?" with "The entire company is based out of San Francisco, CA", and lists "Andreesen Horowitz". Nothing on the page covers where data is hosted or an EU option.Source
    • HiringHead of Solutions: Pylon's "first dedicated Solutions leader", owning the technical journey from pre-sales solution design to implementation and long-term success across Sales Engineering, Implementation, Forward Deployed Engineering and Professional Services, with playbooks "that reduce deployment time". The post lists Series B, $51M raised, 100+ employees, offices in San Francisco and NYC, "London coming soon".Source
  • 02

    Agentic features run on credits, and the pricing estimator shows a range like 6,800 to 14,000 credits a month. The Head of CS owns moving 1,600+ customers to usage-based billing, and a buyer who cannot explain a range to finance delays the switch.

    High impactLow effort First result in 1 month Head of Customer Success

    First action

    Write the brief template using the estimator's own three inputs.

    How to measure it

    Briefs sent before renewal that convert to credit plans

    Now
    –
    Target
    60%
    By
    2 quarters

    Steps

    1. 1

      Write the template

      Inputs, range, drivers, caps, seats included.

      Head of Customer Success 1 day

    2. 2

      Add the email option

      A button under the estimator that sends the brief.

      Product Manager 2 days

    3. 3

      Explain the range

      One paragraph each on what pushes usage up or down.

      Head of Customer Success 2 hours

    4. 4

      Add spend controls

      List the controls customers can set today.

      Product Manager 2 hours

    5. 5

      Use it at renewals

      CSMs send a brief 60 days before each renewal.

      Head of Customer Success ongoing

    6. 6

      Track questions

      Log finance questions that come back and update the brief.

      Head of Customer Success 1 hour a week

    First result
    1 month
    Cost
    $0
    Owner
    Head of Customer Success

    Smallest test

    Send hand-made briefs to ten customers renewing next quarter.

    Why it works

    After the estimator, offer "email me this as a brief": the inputs, the credit range, what drives the low and high end, the seats included, three ways to cap spend, and how the AssemblyAI-style results compare. Account managers send the same brief to existing customers before their renewal.

    Usage pricing raises a budget question that a seat price never did. Answering it in writing, with the customer's own numbers, turns a hesitation into an approval and gives CS a standard document for every migration conversation.

    Risks and how to handle them

    • Customers anchor on the high end

      Show what typical customers at that volume actually used.

    Evidence

    • Your websitePricing page: Professional $89/seat, Advanced $139/seat (RBAC, customer portal, custom reporting, data warehouse, SAML SSO as an add-on), Enterprise on quote. Agentic features "run on credits", bought per year or as you go; an estimator turns tickets per month, % automated and % needing deep investigation into a monthly credit range (for example "6,800 - 14,000"), and sales "will help you estimate".Source
    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
    • Your websiteAssemblyAI case study: migrated off Zendesk; first response time for in-app chat fell 97% (15 minutes to 23 seconds); 50% of eligible inquiries resolved without a person; 24/7 chat without weekend staffing.Source
  • 03

    The new Head of Support is told to be "customer zero" and define how AI changes support. Pylon's buyers are support leaders who want to see exactly that, and nobody else can show it with real numbers from inside the product.

    Medium impactLow effort First result in 1 month Head of Support

    First action

    Pull last month's internal support metrics from Pylon's own workspace.

    How to measure it

    Readers who book a demo from the post

    Now
    –
    Target
    15 a month
    By
    1 quarter

    Steps

    1. 1

      Pick the metrics

      Five numbers that can be shown every month.

      Head of Support 2 hours

    2. 2

      Pull the data

      From Pylon's own workspace analytics.

      Head of Support 2 hours

    3. 3

      Write the first post

      Numbers, one workflow change, one thing that failed.

      Head of Support 1 day

    4. 4

      Review

      Founders check nothing customer-identifying is shown.

      Head of Support 1 hour

    5. 5

      Publish and share

      Blog, LinkedIn and the CS team's customer newsletter.

      Head of Customer Success 1 hour

    6. 6

      Repeat

      Same template every month.

      Head of Support 1 day a month

    First result
    1 month
    Cost
    $0
    Owner
    Head of Support

    Smallest test

    Post one month's numbers on LinkedIn and count the replies from support leaders.

    Why it works

    A monthly post and Slack-community thread: ticket volume, share handled by agents, first response time, escalation rate, what changed in the workflow and what failed. The Head of Support writes it; the Head of CS shares it with customers.

    Buyers trust a vendor that uses its own tool in public, and the numbers double as sales proof that refreshes every month without new case-study approvals.

    Risks and how to handle them

    • A bad month in public

      Publish anyway with what was learned; that builds more trust than a perfect record.

    Evidence

    • HiringHead of Support: leads support across the US and EMEA, stands up a new New York team, defines "how AI changes support at Pylon", is "customer zero" for Pylon's own workflows and the feedback loop into the roadmap, and will "test whether there's a real support-led revenue opportunity for Pylon".Source
    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
    • Your websiteAssemblyAI case study: migrated off Zendesk; first response time for in-app chat fell 97% (15 minutes to 23 seconds); 50% of eligible inquiries resolved without a person; 24/7 chat without weekend staffing.Source
  • 04

    The site scores F on security headers and D- on Mozilla Observatory, and the trust page spells a lead investor "Andreesen Horowitz". Pylon sells into teams that will put the vendor through a security review; small signs of carelessness are noticed.

    Medium impactLow effort First result in 1 week Head of Solutions

    First action

    Run the site through Mozilla Observatory and list the missing headers.

    How to measure it

    Reviews closed in one round

    Now
    –
    Target
    70%
    By
    1 quarter

    Steps

    1. 1

      List the gaps

      Missing headers from the Observatory report.

      Head of Solutions 1 hour

    2. 2

      Add the headers

      Through Webflow and the CDN settings.

      Head of Solutions 1 day

    3. 3

      Fix the copy

      Investor spelling and the location answer.

      Head of Solutions 15 minutes

    4. 4

      Write the AI section

      What agents can see and do, logging, approvals, ISO 42001 in plain words.

      Head of Solutions 1 day

    5. 5

      Link it

      From pricing, enterprise and the EMEA page.

      Head of Solutions 1 hour

    6. 6

      Re-test

      Re-run Observatory and record the new grade.

      Head of Solutions 15 minutes

    First result
    1 week
    Cost
    $0
    Owner
    Head of Solutions

    Smallest test

    Fix the spelling and add the AI section today; do headers next.

    Why it works

    Add the standard security headers on the marketing site, fix the spelling, add an "AI governance" section that explains ISO 42001 in plain words (what agents can access, logging, human approval), and link the trust center from every pricing tier.

    ISO 42001 is rare and answers the question every buyer of AI agents asks; it is listed but not explained. Fixing the visible basics removes easy objections before the Solutions team ever gets involved.

    Risks and how to handle them

    • Headers break embedded demos

      Test the interactive demos after each change.

    Evidence

    • Your websiteTrust & Security page: SOC 2 Type 2, GDPR ("Ask us for our DPA"), HIPAA BAA on enterprise, ISO 27001 and ISO 42001; security reviews and custom MSAs are Enterprise-only. Its FAQ answers "Where are you based?" with "The entire company is based out of San Francisco, CA", and lists "Andreesen Horowitz". Nothing on the page covers where data is hosted or an EU option.Source
    • programmable.infoSite scan: security headers grade F and Mozilla Observatory D-; DMARC "reject"; mobile LCP at the 75th percentile about 2.0 s, 18% faster than a year ago; Webflow; legal entity Pylon Labs, Inc.; status page operational.Source
    • HiringHead of Solutions: Pylon's "first dedicated Solutions leader", owning the technical journey from pre-sales solution design to implementation and long-term success across Sales Engineering, Implementation, Forward Deployed Engineering and Professional Services, with playbooks "that reduce deployment time". The post lists Series B, $51M raised, 100+ employees, offices in San Francisco and NYC, "London coming soon".Source
  • 05

    Every comparison page claims 300+ migrations and 90% finished in under two months, but there is no plan a buyer can read. The first Solutions leader is asked to build playbooks that cut deployment time; the migration plan is the one buyers want before they sign.

    High impactLow effort First result in 1 month Head of Solutions

    First action

    Write the Zendesk plan from the last five completed migrations.

    How to measure it

    Win rate on migration deals

    Now
    –
    Target
    +10 points
    By
    2 quarters

    Steps

    1. 1

      Gather the facts

      Timelines and steps from the last five migrations.

      Head of Solutions 2 days

    2. 2

      Write the plan

      Week by week, both sides' tasks.

      Head of Solutions 2 days

    3. 3

      Add the backtest

      How agent settings are tested on past tickets before launch.

      Head of Solutions 1 day

    4. 4

      Publish

      On each comparison page as a download.

      Account Executive 2 hours

    5. 5

      Train sales

      Walk AEs through using it on calls.

      Head of Solutions 1 hour

    6. 6

      Repeat for Intercom

      Same template for the second source system.

      Head of Solutions 2 days

    First result
    1 month
    Cost
    $0
    Owner
    Head of Solutions

    Smallest test

    Send the draft plan in two open Zendesk deals and ask for feedback.

    Why it works

    A public week-by-week plan per source system: what is exported, how Slack channels and history move, what runs in parallel, who does what on each side, and the backtest of agent settings against past tickets before go-live. Sales attaches it to every competitive deal.

    Switching cost is the main reason teams stay on Zendesk. A concrete plan with named steps lowers the perceived risk more than any claim, and it is reusable by every AE and implementation engineer.

    Ready to use

    CopyZendesk to Pylon migration plan

    Week 0: kickoff, export scope, Slack Connect channel inventory
    Week 1: data export and mapping; integrations connected (CRM, Linear or Jira)
    Week 2: parallel run on one channel; agent settings backtested on past tickets
    Week 3: team training; routing and SLAs set
    Week 4: full switch; Zendesk kept read-only
    Week 6: review against baseline first response and resolution times

    Risks and how to handle them

    • Customers hold Pylon to the timeline

      State the assumptions each timeline depends on.

    Evidence

    • Your websiteSix comparison pages (Zendesk, Fin, Plain, Front, Salesforce, Jira). Each claims "300+ migrations" with "90% of migrations finished in under 2 months"; the Plain page says Pylon lets teams "backtest a new agent configuration against past issues before it touches a live ticket". The homepage says "Trusted by 1,500+ B2B customers globally".Source
    • Your websiteSeries B post (August 19, 2025): $31M co-led by a16z and Bain Capital Ventures, $51M in total; 750+ customers and "2 years of 5x+ YoY revenue growth"; 150+ companies migrated from Zendesk, Intercom and Salesforce Service Cloud. Founded November 2022; the first product was a Slack-to-Zendesk integration.Source
    • HiringHead of Solutions: Pylon's "first dedicated Solutions leader", owning the technical journey from pre-sales solution design to implementation and long-term success across Sales Engineering, Implementation, Forward Deployed Engineering and Professional Services, with playbooks "that reduce deployment time". The post lists Series B, $51M raised, 100+ employees, offices in San Francisco and NYC, "London coming soon".Source
  • 06

    The London AE is told EMEA is "already a meaningful part" of the business, yet every customer story that names a headquarters is in North America. A European buyer looks for a peer and finds none.

    High impactLow effort First result in 6 weeks Account Executive

    First action

    Ask CS for the ten largest European accounts by usage.

    How to measure it

    European customer stories live

    Now
    –
    Target
    2
    By
    6 weeks

    Steps

    1. 1

      Find the accounts

      Top European customers by usage and health.

      Head of Customer Success 1 day

    2. 2

      Ask

      A short request from the London CS lead.

      Head of Customer Success 1 day

    3. 3

      Interview

      30 minutes each; get two numbers.

      Account Executive, EMEA 1 week

    4. 4

      Write

      Same template as the AssemblyAI story.

      Account Executive, EMEA 2 days

    5. 5

      Approve

      Customer approves wording.

      Account Executive, EMEA 1 week

    6. 6

      Publish

      On the EMEA page and in outbound.

      Account Executive, EMEA 1 hour

    First result
    6 weeks
    Cost
    $0
    Owner
    Account Executive, EMEA

    Smallest test

    Get one quote with a name and title this week for the EMEA page.

    Why it works

    Find the European customers with the most usage, ask two for a short story with a named person and two numbers, and publish them alongside a European logo row on the EMEA page.

    Peer proof in the same region is what shortens the first deals in a new office, and it costs only customer time.

    Risks and how to handle them

    • Customers will not be named

      Publish with the industry and country and use named stories later.

    Evidence

    • Your websiteThe sitemap lists 24 customer stories. Of the 18 that state the customer's headquarters, 17 are in the US (mostly San Francisco and New York) and one is in Toronto; none is in Europe. Stories include AssemblyAI, Together AI, Writer, Merge, Sardine and Hightouch.Source
    • HiringAccount Executive, EMEA (London, posted October 15, 2026): "EMEA is already a meaningful part of Pylon's business, and London is where we're investing next", with a small team being built "across sales, customer success, and support, in a new region and a new office". The AE runs full-cycle inbound and outbound deals, handles "data residency, GDPR, and procurement cycles", and feeds what they learn into "positioning, messaging, and playbooks". Sales stack adds Amplemarket and Salesfinity.Source
    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source

This quarter 9

The core plays for the next three months.

  • 07

    Moving 1,600+ customers to agentic, usage-based billing is the Head of CS's top job, and pricing shifts are when accounts churn or shrink. The post asks for someone who has lived this exact shift.

    High impactMedium effort First result in 1 quarter Head of Customer Success

    First action

    Build the customer list with today's seats and an estimated credit range for each.

    How to measure it

    NRR on migrated cohorts

    Now
    –
    Target
    >=140%
    By
    3 quarters

    Steps

    1. 1

      Segment

      By ticket volume and current seats.

      Head of Customer Success 1 week

    2. 2

      Write segment plans

      Brief, pilot, review, renewal terms.

      Head of Customer Success 1 week

    3. 3

      Give trial credits

      A fixed amount to try agent features before switching.

      Head of Customer Success 1 week

    4. 4

      Pilot with ten accounts

      Run the plan end to end.

      Head of Customer Success 1 month

    5. 5

      Track cohorts

      Weekly NRR and contraction by cohort.

      Head of Customer Success ongoing

    6. 6

      Roll out

      Remaining customers in waves.

      Head of Customer Success 2 months

    First result
    1 quarter
    Cost
    Trial credit cost
    Owner
    Head of Customer Success

    Smallest test

    Run the full plan for five accounts renewing next month.

    Why it works

    Segment customers by expected usage change, run a 60-day plan per segment (brief, pilot of agent features, trial credits, a review of results), and track net retention by cohort weekly with a save motion for accounts whose spend would rise sharply.

    A planned migration with the customer's own numbers keeps trust; a surprise invoice loses it. Cohort tracking shows early which segments need different terms.

    Risks and how to handle them

    • Spend shock for heavy users

      Caps and a transition discount for the first term.

    • CS team stretched

      Prioritise top revenue accounts first.

    Builds on

    Evidence

    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
    • Your websitePricing page: Professional $89/seat, Advanced $139/seat (RBAC, customer portal, custom reporting, data warehouse, SAML SSO as an add-on), Enterprise on quote. Agentic features "run on credits", bought per year or as you go; an estimator turns tickets per month, % automated and % needing deep investigation into a monthly credit range (for example "6,800 - 14,000"), and sales "will help you estimate".Source
    • Your websiteAssemblyAI case study: migrated off Zendesk; first response time for in-app chat fell 97% (15 minutes to 23 seconds); 50% of eligible inquiries resolved without a person; 24/7 chat without weekend staffing.Source
  • 08

    The Head of CS is expected to host CS leader dinners and become a name buyers know; Pylon has offices in all three cities and its buyers are support and CS leaders.

    High impactMedium effort First result in 2 months Head of Customer Success

    First action

    Pick the first topic and invite five customers in San Francisco.

    How to measure it

    Opportunities from dinner prospects

    Now
    –
    Target
    25%
    By
    2 quarters

    Steps

    1. 1

      Set the calendar

      One city a month, rotating.

      Head of Customer Success 1 day

    2. 2

      Pick topics

      Three topics tied to the agentic shift.

      Head of Customer Success 1 day

    3. 3

      Invite

      Customers first, then target accounts from AEs.

      Account Executive 2 weeks

    4. 4

      Host

      Head of CS or Support leads the conversation.

      Head of Customer Success 1 evening

    5. 5

      Follow up

      AEs book calls within a week.

      Account Executive 1 week

    6. 6

      Publish takeaways

      A short anonymised write-up after each dinner.

      Head of Customer Success 2 hours

    First result
    2 months
    Cost
    $1,500-3,000 per dinner
    Owner
    Head of Customer Success

    Smallest test

    Host one dinner in San Francisco with eight guests.

    Why it works

    Monthly dinners of 10-12 heads of support and CS, hosted by the Head of CS or Head of Support, on one topic (moving a team to agents, usage pricing, Slack support at scale). Half customers, half prospects from the AEs' lists; AEs follow up within a week.

    Peers persuade peers. A customer describing their migration over dinner does more than a demo, and the format fits a team with no marketer.

    Risks and how to handle them

    • Turns into a sales pitch

      No slides; customers speak, Pylon listens.

    Evidence

    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
    • HiringHead of Support: leads support across the US and EMEA, stands up a new New York team, defines "how AI changes support at Pylon", is "customer zero" for Pylon's own workflows and the feedback loop into the roadmap, and will "test whether there's a real support-led revenue opportunity for Pylon".Source
    • HiringAccount Executive, EMEA (London, posted October 15, 2026): "EMEA is already a meaningful part of Pylon's business, and London is where we're investing next", with a small team being built "across sales, customer success, and support, in a new region and a new office". The AE runs full-cycle inbound and outbound deals, handles "data residency, GDPR, and procurement cycles", and feeds what they learn into "positioning, messaging, and playbooks". Sales stack adds Amplemarket and Salesfinity.Source
    • HiringAccount Executive (New York): full-cycle inbound and outbound sales to B2B tech companies under 500 employees "with exposure to larger accounts over time", discovery, demos and 1-2 week trials, $10k-$100k ARR deals, sourcing part of their own pipeline.Source
  • 09

    Pylon sells itself as the platform for "the entire post-sales team", and the Head of CS owns cross-sell and upsell directly. Most accounts start in support.

    High impactMedium effort First result in 1 quarter Head of Customer Success

    First action

    List the 50 largest accounts where only the support team uses Pylon.

    How to measure it

    Multi-team accounts

    Now
    –
    Target
    +30%
    By
    2 quarters

    Steps

    1. 1

      Find the accounts

      Support-only accounts by size.

      Head of Customer Success 2 days

    2. 2

      Map the teams

      CS and post-sales roles at each account.

      Head of Customer Success 1 week

    3. 3

      Build the pilot

      Two-week CS pilot with account health views.

      Head of Customer Success 1 week

    4. 4

      Offer it

      Through the account's CSM.

      Head of Customer Success 1 month

    5. 5

      Review

      Results meeting at day 14.

      Head of Customer Success ongoing

    6. 6

      Price

      Seats or credits for the second team.

      Head of Customer Success 1 day

    First result
    1 quarter
    Cost
    $0
    Owner
    Head of Customer Success

    Smallest test

    Run the pilot with three accounts.

    Why it works

    For each account, map who else touches customers (CS, account management, solutions) and offer a CS-team pilot using account intelligence and health signals already in Pylon; track expansion by team added.

    Selling to a second team inside a happy account is the cheapest growth available and keeps NRR high while new logos ramp in EMEA.

    Risks and how to handle them

    • Second team uses a different tool

      Lead with the integrations to their CRM.

    Evidence

    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
    • Your websiteSeries B post (August 19, 2025): $31M co-led by a16z and Bain Capital Ventures, $51M in total; 750+ customers and "2 years of 5x+ YoY revenue growth"; 150+ companies migrated from Zendesk, Intercom and Salesforce Service Cloud. Founded November 2022; the first product was a Slack-to-Zendesk integration.Source
    • Your websiteSitemap: 583 URLs, of which 410 are blog posts, 51 integration pages (including MCP, Claude, ChatGPT, Cursor and Devin), 30 videos, 24 events and webinars (for example "Why B2B is leaving Zendesk", "Zendesk migration"), 5 interactive demos and 5 AI agent pages.Source
  • 10

    The AE runs 1-2 week trials, and the Plain page says agent settings can be backtested on past issues. The new Solutions leader is asked to set the standard for how technical work is done.

    High impactMedium effort First result in 6 weeks Head of Solutions

    First action

    Write the report template from the AssemblyAI numbers.

    How to measure it

    Pilot-to-close rate

    Now
    –
    Target
    50%
    By
    2 quarters

    Steps

    1. 1

      Define the pilot

      Steps, owners, and exit criteria.

      Head of Solutions 1 week

    2. 2

      Build the report

      Backtest results, projected savings, credit estimate.

      Head of Solutions 1 week

    3. 3

      Train AEs

      When to offer it and how to run kickoff.

      Head of Solutions 2 hours

    4. 4

      Run five pilots

      Measure time per pilot.

      Head of Solutions 1 month

    5. 5

      Refine

      Cut steps that do not change decisions.

      Head of Solutions 1 week

    6. 6

      Make it standard

      Every qualified deal over a size threshold.

      Account Executive ongoing

    First result
    6 weeks
    Cost
    Solutions time
    Owner
    Head of Solutions

    Smallest test

    Backtest one open prospect's tickets by hand.

    Why it works

    A fixed pilot: connect, backtest agent settings on the prospect's last 1,000 tickets, show the share that would have been resolved and time saved, then run live for a week. End with a written results report the champion takes to their boss.

    A backtest on the buyer's own history is proof no slide can match, and a fixed format makes pilots fast enough for AEs to run many at once.

    Risks and how to handle them

    • Backtest overstates results

      Show ranges and the tickets it got wrong.

    Builds on

    Evidence

    • Your websiteSix comparison pages (Zendesk, Fin, Plain, Front, Salesforce, Jira). Each claims "300+ migrations" with "90% of migrations finished in under 2 months"; the Plain page says Pylon lets teams "backtest a new agent configuration against past issues before it touches a live ticket". The homepage says "Trusted by 1,500+ B2B customers globally".Source
    • HiringAccount Executive (New York): full-cycle inbound and outbound sales to B2B tech companies under 500 employees "with exposure to larger accounts over time", discovery, demos and 1-2 week trials, $10k-$100k ARR deals, sourcing part of their own pipeline.Source
    • HiringHead of Solutions: Pylon's "first dedicated Solutions leader", owning the technical journey from pre-sales solution design to implementation and long-term success across Sales Engineering, Implementation, Forward Deployed Engineering and Professional Services, with playbooks "that reduce deployment time". The post lists Series B, $51M raised, 100+ employees, offices in San Francisco and NYC, "London coming soon".Source
    • Your websiteAssemblyAI case study: migrated off Zendesk; first response time for in-app chat fell 97% (15 minutes to 23 seconds); 50% of eligible inquiries resolved without a person; 24/7 chat without weekend staffing.Source
  • 11

    Pylon began as Slack-to-Zendesk and its best customers run support in shared channels. Companies that publish "join our Slack" or Discord support links are telling the world they have exactly the problem Pylon solves.

    High impactMedium effort First result in 1 month Account Executive

    First action

    Find 50 companies with "join our Slack" support links in their docs.

    How to measure it

    Reply rate

    Now
    –
    Target
    8%
    By
    1 quarter

    Steps

    1. 1

      Define the signal

      Public Slack or Discord support links in docs and help centres.

      Account Executive 1 day

    2. 2

      Build the list

      200 companies with size and stack.

      Account Executive 1 week

    3. 3

      Write the message

      Reference their setup and one relevant customer story.

      Account Executive 1 day

    4. 4

      Send in batches

      50 a week through Amplemarket.

      Account Executive 1 month

    5. 5

      Track

      Replies and meetings by segment.

      Account Executive ongoing

    6. 6

      Share with EMEA

      Run the same list for European companies.

      Account Executive, EMEA 1 week

    First result
    1 month
    Cost
    Data tool costs
    Owner
    Account Executive

    Smallest test

    Send 25 messages and count replies.

    Build the prospect list. The list compiled from public sources, verified, deduplicated and delivered to your CRM. Usually live within days.

    Book a working session

    Why it works

    Build a list of B2B tech companies whose docs or help pages invite customers to a Slack or Discord community, filter to under 500 employees, and open with a note about their own public setup and the Slack Agent.

    The signal is public and precise: it shows both the channel and the pain, so outbound reads as relevant rather than cold.

    Risks and how to handle them

    • Feels like surveillance

      Only reference what they publish.

    Evidence

    • Your websiteSeries B post (August 19, 2025): $31M co-led by a16z and Bain Capital Ventures, $51M in total; 750+ customers and "2 years of 5x+ YoY revenue growth"; 150+ companies migrated from Zendesk, Intercom and Salesforce Service Cloud. Founded November 2022; the first product was a Slack-to-Zendesk integration.Source
    • HiringAccount Executive (New York): full-cycle inbound and outbound sales to B2B tech companies under 500 employees "with exposure to larger accounts over time", discovery, demos and 1-2 week trials, $10k-$100k ARR deals, sourcing part of their own pipeline.Source
    • Your websiteSitemap: 583 URLs, of which 410 are blog posts, 51 integration pages (including MCP, Claude, ChatGPT, Cursor and Devin), 30 videos, 24 events and webinars (for example "Why B2B is leaving Zendesk", "Zendesk migration"), 5 interactive demos and 5 AI agent pages.Source
  • 12

    Pylon has six comparison pages; third-party roundups also put Thena, Unthread, ClearFeed, Help Scout, HubSpot Service Hub and Intercom on shortlists. There is no marketer, so AEs feel the gap first in calls.

    Medium impactMedium effort First result in 2 months Account Executive

    First action

    List the competitors mentioned in the last 30 lost and won deals.

    How to measure it

    Demo requests from new comparison pages

    Now
    –
    Target
    20 a month
    By
    2 quarters

    Steps

    1. 1

      Pick rivals

      From deal notes.

      Account Executive 1 day

    2. 2

      Check facts

      Each rival's own site.

      Account Executive 2 days

    3. 3

      Draft

      Table, fit, migration link.

      Account Executive 1 week

    4. 4

      Review

      Founders and Solutions check claims.

      Head of Solutions 2 days

    5. 5

      Publish

      With dated sources.

      Account Executive 1 day

    6. 6

      Update

      Quarterly review.

      Account Executive 2 hours a quarter

    Who to approach

    • Thena

      Slack, email and chat support with AI agents.

    • Unthread

      Slack-based support ticketing.

    • ClearFeed

      Slack and Teams support tooling.

    First result
    2 months
    Cost
    $0
    Owner
    Account Executive

    Smallest test

    Publish the Thena page first.

    Why it works

    Add pages for Thena, Unthread, ClearFeed and HubSpot Service Hub with a fair table, where each fits, and the migration plan. AEs write the first draft from their own call notes; founders review.

    Buyers searching "X vs Pylon" decide on whichever page they find; a fair page on Pylon's site earns that click.

    Risks and how to handle them

    • Claims go stale

      Date the page and cite each rival's site.

    Builds on

    Evidence

    • Competitor researchThird-party roundups of Pylon alternatives list Thena, Unthread, ClearFeed, Help Scout, Freshdesk, HubSpot Service Hub, Intercom, Front and Zendesk. CB Insights describes Thena as centralizing support across Slack, email and chat with AI agents and routing.Source
    • Your websiteSix comparison pages (Zendesk, Fin, Plain, Front, Salesforce, Jira). Each claims "300+ migrations" with "90% of migrations finished in under 2 months"; the Plain page says Pylon lets teams "backtest a new agent configuration against past issues before it touches a live ticket". The homepage says "Trusted by 1,500+ B2B customers globally".Source
    • HiringPylon's careers board (pylon-labs) lists 15 roles: the two AEs, the three Heads (Customer Success, Support, Solutions), a Product Support Engineer, a Product Manager, a Product Designer, a Head of People & Operations and six engineering roles (Product, Infrastructure, Security, AI, New Grad, Intern). There is no marketing role.Source
  • 13

    Pylon has integration pages for Devin, Cursor, Claude, ChatGPT and MCP and just launched with Devin. Each partner's users are engineering-heavy B2B teams who also run support.

    Medium impactMedium effort First result in 1 quarter Product Manager

    First action

    Write the kit from the Devin launch and note what worked.

    How to measure it

    Partner-sourced pipeline

    Now
    –
    Target
    10% of new pipeline
    By
    3 quarters

    Steps

    1. 1

      Review the Devin launch

      What drove sign-ups.

      Product Manager 1 day

    2. 2

      Write the kit

      Page, video, webinar, posts, lead path.

      Product Manager 1 week

    3. 3

      Pick next partners

      By shared customers.

      Product Manager 1 day

    4. 4

      Run one launch

      Second partner.

      Product Manager 1 month

    5. 5

      Measure

      Sign-ups and pipeline by partner.

      Product Manager ongoing

    6. 6

      Repeat

      One launch a quarter.

      Product Manager ongoing

    First result
    1 quarter
    Cost
    $0-5,000 per launch
    Owner
    Product Manager

    Smallest test

    Ask the Devin team which channel brought most attention.

    Why it works

    One kit per integration: a joint use-case page, a short demo video, a co-hosted webinar, a post on both companies' channels and a partner-sourced lead path. Run it for every new agent integration.

    Partners bring audiences Pylon cannot reach alone, and a kit makes each launch cheap enough to repeat without a marketing team.

    Risks and how to handle them

    • Partner priorities differ

      Agree the audience and date in writing.

    Evidence

    • Your websiteSitemap: 583 URLs, of which 410 are blog posts, 51 integration pages (including MCP, Claude, ChatGPT, Cursor and Devin), 30 videos, 24 events and webinars (for example "Why B2B is leaving Zendesk", "Zendesk migration"), 5 interactive demos and 5 AI agent pages.Source
    • Your websiteSeries B post (August 19, 2025): $31M co-led by a16z and Bain Capital Ventures, $51M in total; 750+ customers and "2 years of 5x+ YoY revenue growth"; 150+ companies migrated from Zendesk, Intercom and Salesforce Service Cloud. Founded November 2022; the first product was a Slack-to-Zendesk integration.Source
    • HiringPylon's careers board (pylon-labs) lists 15 roles: the two AEs, the three Heads (Customer Success, Support, Solutions), a Product Support Engineer, a Product Manager, a Product Designer, a Head of People & Operations and six engineering roles (Product, Infrastructure, Security, AI, New Grad, Intern). There is no marketing role.Source
  • 14

    The Head of Support is asked to test whether there is a support-led revenue opportunity. Support sees every account's friction and feature requests first.

    Medium impactMedium effort First result in 1 quarter Head of Support

    First action

    Define five expansion tags and add them to Pylon's own workspace.

    How to measure it

    Revenue influenced by support tags

    Now
    –
    Target
    10% of expansion
    By
    2 quarters

    Steps

    1. 1

      Define tags

      Five clear signals.

      Head of Support 1 day

    2. 2

      Route

      Automation to CS.

      Head of Support 1 day

    3. 3

      Train

      Support team spots and tags.

      Head of Support 2 hours

    4. 4

      Measure

      Tagged vs untagged revenue.

      Head of Support 1 quarter

    5. 5

      Decide

      Keep, change or stop.

      Head of Support 1 day

    6. 6

      Productise

      If it works, ship it as a customer feature.

      Product Manager 1 quarter

    First result
    1 quarter
    Cost
    $0
    Owner
    Head of Support

    Smallest test

    Tag for two weeks and count the signals.

    Why it works

    Tag tickets that signal expansion (more seats, new teams, higher limits, agent features) and route them to CS within a day; measure revenue from tagged accounts against untagged ones for a quarter.

    Pylon sells account context to its customers; proving support-led revenue inside Pylon gives CS a playbook and a story to sell.

    Risks and how to handle them

    • Support feels like sales

      Support only flags; CS sells.

    Evidence

    • HiringHead of Support: leads support across the US and EMEA, stands up a new New York team, defines "how AI changes support at Pylon", is "customer zero" for Pylon's own workflows and the feedback loop into the roadmap, and will "test whether there's a real support-led revenue opportunity for Pylon".Source
    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
    • Your websiteSitemap: 583 URLs, of which 410 are blog posts, 51 integration pages (including MCP, Claude, ChatGPT, Cursor and Devin), 30 videos, 24 events and webinars (for example "Why B2B is leaving Zendesk", "Zendesk migration"), 5 interactive demos and 5 AI agent pages.Source
  • 15

    Pylon serves 1,600+ B2B companies across Slack, email, chat and Teams. Support leaders have few public benchmarks for B2B, and the Head of CS is expected to speak and write.

    High impactMedium effort First result in 2 quarters Head of Customer Success

    First action

    Check which metrics can be aggregated with privacy terms in place.

    How to measure it

    Downloads in the first quarter

    Now
    –
    Target
    2,000
    By
    3 quarters

    Steps

    1. 1

      Check terms

      Confirm aggregate use is allowed.

      Head of Customer Success 2 weeks

    2. 2

      Pick metrics

      Five comparable measures.

      Head of Customer Success 1 week

    3. 3

      Pull data

      Engineering builds the aggregate query.

      Product Manager 2 weeks

    4. 4

      Write

      Findings and charts.

      Head of Customer Success 2 weeks

    5. 5

      Launch

      Dinners, LinkedIn, press.

      Head of Customer Success 1 week

    6. 6

      Personal reports

      Each customer's position.

      Head of Customer Success 1 month

    First result
    2 quarters
    Cost
    Design and engineering time
    Owner
    Head of Customer Success

    Smallest test

    Publish one metric (first response by channel) as a LinkedIn post.

    Why it works

    Publish yearly medians by company size and channel: first response, resolution time, share handled by agents, channel mix. Gate the full report lightly; give every customer their own position against the medians.

    A benchmark becomes the number journalists and support leaders quote, and it gives CS a reason to meet every account.

    Risks and how to handle them

    • Customer data concerns

      Aggregate only, with thresholds per segment.

    Evidence

    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
    • Your websiteSeries B post (August 19, 2025): $31M co-led by a16z and Bain Capital Ventures, $51M in total; 750+ customers and "2 years of 5x+ YoY revenue growth"; 150+ companies migrated from Zendesk, Intercom and Salesforce Service Cloud. Founded November 2022; the first product was a Slack-to-Zendesk integration.Source
    • Your websiteAssemblyAI case study: migrated off Zendesk; first response time for in-app chat fell 97% (15 minutes to 23 seconds); 50% of eligible inquiries resolved without a person; 24/7 chat without weekend staffing.Source

Big bets 3

Larger plays that can change the trajectory.

  • 16

    Pylon is building sales, CS and support in London, and the AE has to handle data residency. If European buyers can keep data in the EU, the security objection disappears.

    High impactHigh effort First result in 3 quarters Product Manager

    First action

    Count European deals lost or delayed on data location in the last year.

    How to measure it

    EMEA share of new ARR

    Now
    –
    Target
    30%
    By
    4 quarters

    Steps

    1. 1

      Size the demand

      Lost and delayed deals.

      Account Executive, EMEA 2 weeks

    2. 2

      Scope hosting

      Engineering estimate.

      Product Manager 1 month

    3. 3

      Hire

      Solutions and support in London.

      Head of Solutions 1 quarter

    4. 4

      Local contracts

      Currency and DPA terms.

      Account Executive, EMEA 1 month

    5. 5

      Launch

      Announce with the European customer stories.

      Account Executive, EMEA 1 week

    6. 6

      Review

      EMEA win rate quarterly.

      Account Executive, EMEA ongoing

    First result
    3 quarters
    Cost
    Hosting and hiring costs
    Owner
    Product Manager

    Smallest test

    Ask ten European prospects whether EU hosting would change their timeline.

    Why it works

    Plan an EU hosting option, staff London with sales, CS, support and a solutions engineer, and run European pricing and contracts (EUR and GBP invoices, local DPA terms).

    A regional office without regional hosting wins the easy deals; with it, Pylon can sell to European companies with stricter rules.

    Risks and how to handle them

    • Cost before demand

      Gate the build on measured lost deals.

    Builds on

    Evidence

    • HiringAccount Executive, EMEA (London, posted October 15, 2026): "EMEA is already a meaningful part of Pylon's business, and London is where we're investing next", with a small team being built "across sales, customer success, and support, in a new region and a new office". The AE runs full-cycle inbound and outbound deals, handles "data residency, GDPR, and procurement cycles", and feeds what they learn into "positioning, messaging, and playbooks". Sales stack adds Amplemarket and Salesfinity.Source
    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
    • HiringHead of Support: leads support across the US and EMEA, stands up a new New York team, defines "how AI changes support at Pylon", is "customer zero" for Pylon's own workflows and the feedback loop into the roadmap, and will "test whether there's a real support-led revenue opportunity for Pylon".Source
    • HiringHead of Solutions: Pylon's "first dedicated Solutions leader", owning the technical journey from pre-sales solution design to implementation and long-term success across Sales Engineering, Implementation, Forward Deployed Engineering and Professional Services, with playbooks "that reduce deployment time". The post lists Series B, $51M raised, 100+ employees, offices in San Francisco and NYC, "London coming soon".Source
  • 17

    The Head of CS runs a Championship program where CSMs master a workflow and teach it. Support leaders everywhere are working out how agents change their jobs and careers.

    High impactHigh effort First result in 3 quarters Head of Customer Success

    First action

    Write the outline from the Championship program.

    How to measure it

    Certificates earned

    Now
    –
    Target
    1,000
    By
    4 quarters

    Steps

    1. 1

      Outline

      Five modules.

      Head of Customer Success 2 weeks

    2. 2

      Record

      Short videos by the support team.

      Head of Support 1 month

    3. 3

      Build the test

      Practical tasks.

      Head of Customer Success 2 weeks

    4. 4

      Launch with customers

      Their teams first.

      Head of Customer Success 1 month

    5. 5

      Open it

      Public launch.

      Head of Customer Success 1 week

    6. 6

      Track

      Certificate holders by account.

      Head of Customer Success ongoing

    First result
    3 quarters
    Cost
    $10,000-30,000
    Owner
    Head of Customer Success

    Smallest test

    Run one live module for customers and survey attendees.

    Why it works

    Turn the program into a free public course and certificate: how to design agent workflows, measure them, and change team roles. Customers' teams get it first; it becomes the default training for AI-native support.

    Owning the training for a new way of working makes Pylon the default vendor for people who took it, the way certifications built earlier software categories.

    Risks and how to handle them

    • Seen as product training

      Teach the method, then the tool.

    Evidence

    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
    • HiringHead of Support: leads support across the US and EMEA, stands up a new New York team, defines "how AI changes support at Pylon", is "customer zero" for Pylon's own workflows and the feedback loop into the roadmap, and will "test whether there's a real support-led revenue opportunity for Pylon".Source
    • Your websiteSitemap: 583 URLs, of which 410 are blog posts, 51 integration pages (including MCP, Claude, ChatGPT, Cursor and Devin), 30 videos, 24 events and webinars (for example "Why B2B is leaving Zendesk", "Zendesk migration"), 5 interactive demos and 5 AI agent pages.Source
  • 18

    The New York AE sells under 500 employees "with exposure to larger accounts over time"; Advanced and Enterprise tiers already include RBAC, SSO, custom MSAs and security reviews.

    High impactHigh effort First result in 4 quarters Head of Solutions

    First action

    List current customers over 500 employees and their deal history.

    How to measure it

    Accounts over $100k ARR

    Now
    –
    Target
    Double
    By
    4 quarters

    Steps

    1. 1

      Define the offer

      Services, terms and price.

      Head of Solutions 1 month

    2. 2

      Pick targets

      Accounts with an existing foothold.

      Account Executive 2 weeks

    3. 3

      Build proof

      Enterprise case study.

      Head of Customer Success 2 months

    4. 4

      Sell

      Pair AEs with solutions engineers.

      Account Executive ongoing

    5. 5

      Review

      Win and loss reasons.

      Head of Solutions quarterly

    6. 6

      Adjust

      Product gaps to roadmap.

      Product Manager ongoing

    First result
    4 quarters
    Cost
    Solutions headcount
    Owner
    Head of Solutions

    Smallest test

    Take one 1,000-person prospect through the full offer.

    Why it works

    Define an enterprise offer: named solutions engineer, migration plan, security review in two weeks, a quarterly business review, and multi-team rollout. Pick 50 larger target accounts where a team already uses Pylon.

    Larger accounts carry the most expansion room, and the new Solutions function is the piece that makes them winnable.

    Risks and how to handle them

    • Long cycles slow the team

      Cap enterprise deals per AE.

    Builds on

    Evidence

    • HiringAccount Executive (New York): full-cycle inbound and outbound sales to B2B tech companies under 500 employees "with exposure to larger accounts over time", discovery, demos and 1-2 week trials, $10k-$100k ARR deals, sourcing part of their own pipeline.Source
    • HiringHead of Solutions: Pylon's "first dedicated Solutions leader", owning the technical journey from pre-sales solution design to implementation and long-term success across Sales Engineering, Implementation, Forward Deployed Engineering and Professional Services, with playbooks "that reduce deployment time". The post lists Series B, $51M raised, 100+ employees, offices in San Francisco and NYC, "London coming soon".Source
    • Your websitePricing page: Professional $89/seat, Advanced $139/seat (RBAC, customer portal, custom reporting, data warehouse, SAML SSO as an add-on), Enterprise on quote. Agentic features "run on credits", bought per year or as you go; an estimator turns tickets per month, % automated and % needing deep investigation into a monthly credit range (for example "6,800 - 14,000"), and sales "will help you estimate".Source
    • Your websiteTrust & Security page: SOC 2 Type 2, GDPR ("Ask us for our DPA"), HIPAA BAA on enterprise, ISO 27001 and ISO 42001; security reviews and custom MSAs are Enterprise-only. Its FAQ answers "Where are you based?" with "The entire company is based out of San Francisco, CA", and lists "Andreesen Horowitz". Nothing on the page covers where data is hosted or an EU option.Source

Wildcards 3

Unexpected experiments, each with a cheap way to test it.

  • 19

    Pylon's automations run on "Skills", and its team builds them daily as customer zero. Support leaders want working examples, not concepts.

    Medium impactLow effort First result in 1 quarter Head of Support

    First action

    Pick ten Skills from Pylon's own workspace.

    How to measure it

    Skill imports

    Now
    –
    Target
    500
    By
    2 quarters

    Steps

    1. 1

      Choose

      Ten Skills.

      Head of Support 1 day

    2. 2

      Write up

      What, why, how to use.

      Head of Support 1 week

    3. 3

      Build import

      One-click into a workspace.

      Product Manager 2 weeks

    4. 4

      Publish

      Gallery page.

      Product Manager 1 day

    5. 5

      Invite submissions

      Customer Skills with credit.

      Head of Customer Success ongoing

    6. 6

      Measure

      Imports and trials.

      Product Manager ongoing

    First result
    1 quarter
    Cost
    $0
    Owner
    Head of Support

    Smallest test

    Publish five recipes as a blog post.

    Why it works

    Publish 20 Skills Pylon uses (triage, escalation, refund checks, release notes) as readable recipes with a one-click import for customers. Invite customers to submit their own.

    A library is useful before anyone buys, ranks for specific searches, and makes switching feel like importing a working setup.

    Risks and how to handle them

    • Recipes expose internal processes

      Review each before publishing.

    Evidence

    • HiringHead of Support: leads support across the US and EMEA, stands up a new New York team, defines "how AI changes support at Pylon", is "customer zero" for Pylon's own workflows and the feedback loop into the roadmap, and will "test whether there's a real support-led revenue opportunity for Pylon".Source
    • Your websiteSitemap: 583 URLs, of which 410 are blog posts, 51 integration pages (including MCP, Claude, ChatGPT, Cursor and Devin), 30 videos, 24 events and webinars (for example "Why B2B is leaving Zendesk", "Zendesk migration"), 5 interactive demos and 5 AI agent pages.Source
    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
  • 20

    The Head of Support is told to define what roles and career paths look like as AI changes support. Support leaders are hiring for these new roles and have no place to find people.

    Medium impactLow effort First result in 2 quarters Head of Support

    First action

    Ask ten customers whether they are hiring support roles now.

    How to measure it

    Companies posting jobs

    Now
    –
    Target
    100
    By
    2 quarters

    Steps

    1. 1

      Define roles

      Three role descriptions.

      Head of Support 1 week

    2. 2

      Build the board

      Simple listing page.

      Product Manager 2 weeks

    3. 3

      Seed it

      Customer openings.

      Head of Customer Success 2 weeks

    4. 4

      Promote

      Dinners and LinkedIn.

      Head of Customer Success ongoing

    5. 5

      Connect

      Employers to AEs where relevant.

      Account Executive ongoing

    6. 6

      Review

      Keep or close after two quarters.

      Head of Support 1 day

    First result
    2 quarters
    Cost
    $0-5,000
    Owner
    Head of Support

    Smallest test

    Post a list of ten customer openings on LinkedIn.

    Why it works

    A free job board and community for "support engineer", "agent operations" and similar roles, seeded with Pylon customers' openings. Every employer is a support leader Pylon wants to know.

    Helping buyers hire makes Pylon part of how the new roles are defined, and the board fills Pylon's own pipeline of contacts.

    Risks and how to handle them

    • Off-strategy

      Time-box it to two quarters.

    Evidence

    • HiringHead of Support: leads support across the US and EMEA, stands up a new New York team, defines "how AI changes support at Pylon", is "customer zero" for Pylon's own workflows and the feedback loop into the roadmap, and will "test whether there's a real support-led revenue opportunity for Pylon".Source
    • HiringHead of Customer Success: inherits "159% NRR" and a 15+ person team across SF, NYC and London; owns NRR, GRR, churn and the quarterly expansion number; leads "the company's biggest bet", Agentic Support deployment across "1,600+ customers"; owns "the customer migration motion to agentic, usage-based billing"; runs dogfooding and a "Championship" program; is expected to speak, write and host CS leader dinners so that "the person who runs CS at Pylon should be a name our buyers know".Source
    • HiringPylon's careers board (pylon-labs) lists 15 roles: the two AEs, the three Heads (Customer Success, Support, Solutions), a Product Support Engineer, a Product Manager, a Product Designer, a Head of People & Operations and six engineering roles (Product, Infrastructure, Security, AI, New Grad, Intern). There is no marketing role.Source
  • 21

    Pylon integrates with incident.io, Rootly and PagerDuty, and Rootly is a published customer. During an outage, B2B support teams must update hundreds of shared channels at once.

    Medium impactLow effort First result in 1 quarter Head of Solutions

    First action

    Write one outage-update template with the Rootly team.

    How to measure it

    Workspaces with incident templates on

    Now
    –
    Target
    200
    By
    2 quarters

    Steps

    1. 1

      Pick partners

      Start with Rootly.

      Head of Solutions 1 day

    2. 2

      Design templates

      Three update stages.

      Head of Solutions 1 week

    3. 3

      Build triggers

      From the incident tool.

      Product Manager 2 weeks

    4. 4

      Co-publish

      Joint post and webinar.

      Head of Solutions 2 weeks

    5. 5

      Roll out

      To existing customers.

      Head of Customer Success 1 month

    6. 6

      Measure

      Usage and response during incidents.

      Head of Solutions ongoing

    First result
    1 quarter
    Cost
    $0
    Owner
    Head of Solutions

    Smallest test

    Run the template manually in Pylon's own next incident drill.

    Why it works

    Build ready templates for outage updates across Slack channels, customer portal and email, triggered from the incident tool; publish them jointly with each partner.

    Outages are when support quality is most visible; owning that moment ties Pylon to tools engineering teams already love.

    Risks and how to handle them

    • Partner overlap

      Agree who owns which message.

    Evidence

    • Your websiteSitemap: 583 URLs, of which 410 are blog posts, 51 integration pages (including MCP, Claude, ChatGPT, Cursor and Devin), 30 videos, 24 events and webinars (for example "Why B2B is leaving Zendesk", "Zendesk migration"), 5 interactive demos and 5 AI agent pages.Source
    • Your websiteThe sitemap lists 24 customer stories. Of the 18 that state the customer's headquarters, 17 are in the US (mostly San Francisco and New York) and one is in Toronto; none is in Europe. Stories include AssemblyAI, Together AI, Writer, Merge, Sardine and Hightouch.Source
    • Your websiteAssemblyAI case study: migrated off Zendesk; first response time for in-app chat fell 97% (15 minutes to 23 seconds); 50% of eligible inquiries resolved without a person; 24/7 chat without weekend staffing.Source

03

How Programmable can help

Where an idea in this playbook is something Programmable builds or runs, it's listed here with what we'd do. Everything else is yours to run.

Have it built

ProgrammableAgency

1 of the 21 ideas are things Programmable builds and runs for its customers: pages, outreach, prospect lists, booking flows and monitors. Pick one, or send the whole list.

Prospect lists1The list compiled from public sources, verified, deduplicated and delivered to your CRM.

A 30-minute session with the engineer who would build it, not a sales call. You leave with a plan whether or not you hire us.

Book a working session

Usually live within days.

Tools for the rest

ProgrammableInfo

Turn the research into a list you can act on

These ideas start with finding the right companies. Info finds them and the right person at each, researches every one and drafts the outreach, then asks before it sends.

  • Build this list in Info for idea #11 (opens programmable.info in a new tab)

New accounts: 100,000 free credits with code BETA100K

Find the companies (opens programmable.info in a new tab)
ProgrammableTalk

Fill the events in this plan

These ideas are events. Talk gets registrants for them and tells you who's coming and what their company does before the day.

Plan an event (opens programmable.talk in a new tab)
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • Alphanumeric Ideas growth strategyA Mohali-based digital marketing agency focused on pay-per-click (Google, Microsoft and other ad platforms) plus SEO, social media…21 growth ideas
  • HUD growth strategyA platform for building, running and quality-checking reinforcement learning (RL) environments, tasks and evaluations for AI agents…23 growth ideas
  • AthenaHQ growth strategyA generative engine optimization (GEO) platform that tracks and improves how brands appear in AI answers across ChatGPT, Perplexity…22 growth ideas
  • Movers+Shakers growth strategyA social-first creative agency (part of Stagwell): social strategy, campaigns, influencer and creator programs, always-on content and…22 growth ideas
  • b12 labs growth strategyAI software for chemical synthesis: Selenium plans retrosynthesis routes, Palladium designs high-throughput optimisation plates, and…23 growth ideas
  • KoRo growth strategyA Berlin food brand selling nuts, nut butters, dried fruit, snacks, protein and pantry staples in large packs online across Europe and in…22 growth ideas
  • Shopmonkey growth strategyCloud shop management software for auto repair and service shops: estimates, invoices, digital inspections, scheduling, inventory…21 growth ideas
  • Finite State growth strategyA product security platform for connected devices: binary and firmware analysis, SBOMs, reachability-based triage, threat modeling and…22 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on October 21, 2026, and cites them throughout. Pylon did not commission, review or endorse it, and Programmable is not affiliated with Pylon. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Pylon runs its business.

Something wrong, or do you represent Pylon? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 306 ideas

    EMEA buyer pack, trust page fixes, cost brief, migration plan, customer-zero post and European stories.

  2. Days 31 to 609 ideas

    Credit migration programme, dinners, multi-team expansion, the 14-day pilot, Slack-signal outbound, comparison pages and the partner kit.

  3. Days 61 to 906 ideas

    Support-led revenue test, the benchmark, the talent network, and decisions on EU hosting, certification and up-market.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value support in Slack and Teams shared channels in one inbox. The most cited problem: context scattered across CRM, Slack and engineering tools.

  • Agents that already know the account
  • Repetitive first-line questions
  • In their words: “shared channels”

Market

Competitive landscape

5 competitors compared: Zendesk, Intercom (Fin), Plain, Thena and 1 more.

  • Gap to exploit: Clear cost models for AI support features
  • Zendesk: Pylon positions it as built for consumer support, not B2B
  • Intercom (Fin): Less focus on shared Slack channels

Hiring signals

Pylon's 15 open roles are weighted to post-sales leadership and Europe, with no marketing hire.

  • Account Executive, EMEA: New London office; data residency, GDPR and procurement are part of the job. Ideas 1, 6, 16.
  • Account Executive: Under-500-employee B2B tech, 1-2 week trials, own outbound. Ideas 10, 11, 12.
  • Head of Customer Success: 159% NRR, migration to usage-based billing, CS leader dinners and a public voice. Ideas 2, 7, 8, 9, 15, 17.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks first (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence