ProgrammableMarketing/useparagon.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 · 4
  • Wildcards · 3
  • How we can help
Generated Oct 18, 2026
  1. Programmable
  2. Playbooks
  3. Paragon
Paragon logo

growth playbook · Oct 18, 2026

useparagon.com (opens in a new tab)

Paragon growth playbook

Diagnosis

Paragon has one open role, an Account Executive asked to run full sales cycles with CTOs from $50k to $500k ACV and to build an outbound muscle, with a goal of 3 outbound meetings a week. That is a sales-led company whose next stage depends on pipeline the AE can create and close.

Paragon has strong material for it: 182 integration pages, 18 competitor pages, a tl;dv case study with hard numbers, and skills for coding agents already on GitHub. The gaps are in turning that into meetings: an empty pricing FAQ, proof buried in one case study, and no trigger-based outbound. This playbook is built around feeding and arming that AE.

Growth Score

7/10

Biggest Opportunity

Reach companies at the moment they decide to build integrations themselves (job posts, enterprise permission requirements, competitor integration lists) with a build-vs-buy estimate grounded in tl;dv's numbers.

Biggest Risk

Well-funded agent-integration rivals such as Composio and Nango compete on connector count and developer adoption, so without proof of speed and enterprise depth, deals become price comparisons.

01

Start here

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

  1. 1

    Outbound to companies hiring "integrations engineers", with a build-vs-buy estimate for the integrations in their job post

    Search this week's job posts for "integrations engineer" and "build integrations with Salesforce" at SaaS and AI companies with 30 to 500 staff, and pick the first 20.

    High impact First result in 2-3 weeks
  2. 2

    Answer the six pricing FAQ questions that are on the page with no answers

    Ask the AE for the five pricing questions prospects ask most and answer the six on the page first.

    High impact First result in 2 weeks
  3. 3

    Put tl;dv's numbers next to every "Book a demo": 75% less engineering time, Slack, Salesforce and HubSpot in under 3 weeks

    Write the proof line and add it under the homepage demo button.

    High impact First result in 2 weeks

02

Your idea portfolio

22 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.

  • 6 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 · 3Big bets · 9Fill-ins · 5Reconsider · 5
Effort →

Showing 22 of 22 ideas

This week 6

Quick wins with a clear first action.

  • 01

    The AE has to set 3 outbound meetings a week with CTOs and VPs of Engineering. A SaaS or AI company that posts a job for an integrations engineer, or lists Salesforce, HubSpot or Google Drive connectors in a job post, has just decided to build what Paragon sells, and the cost of that decision is easy to show.

    High impactLow effort First result in 2-3 weeks Account Executive

    First action

    Search this week's job posts for "integrations engineer" and "build integrations with Salesforce" at SaaS and AI companies with 30 to 500 staff, and pick the first 20.

    How to measure it

    Meetings booked from integration-hiring triggers

    Now
    –
    Target
    2 of the 3 weekly outbound meetings
    By
    6 weeks

    Steps

    1. 1

      Define the trigger

      Job posts from the last 14 days naming integration work or specific connectors, at companies selling software.

      Account Executive 1 hour

    2. 2

      Build the list weekly

      Pull posts every Monday; find the CTO or VP of Engineering for each company.

      Marketing 2 hours a week

    3. 3

      Make the estimate template

      Integrations named, weeks to build, yearly upkeep, total engineer-months, against Paragon's typical time to production.

      Solutions Engineering 3 hours once

    4. 4

      Fill it per company

      Ten minutes per prospect: the connectors from their post, priced in engineer time.

      Account Executive 10 minutes each

    5. 5

      Send and call

      Email the estimate, then call two days later to walk through it.

      Account Executive 2 hours a week

    6. 6

      Bring SE to call one

      Solutions Engineering joins the first call to show the named connectors working.

      Solutions Engineering 1 hour per meeting

    7. 7

      Track and tune

      Meetings per 100 sends by connector named and company size.

      Account Executive 30 minutes a week

    First result
    2 to 3 weeks
    Cost
    $0 to $300 a month for job-post data
    Owner
    Account Executive

    Smallest test

    Send 20 estimates by hand this week and count replies before automating the list.

    Run this outreach. The sequence sent for you: addresses found and verified, replies routed to your CRM. Usually live within days.

    Book a working session

    Why it works

    Every Monday, pull job posts from the last 14 days that mention building integrations or named connectors. For each company, send the head of engineering a one-page estimate: the integrations named in the post, the in-house time and yearly upkeep using tl;dv's own numbers (about 4 weeks to build and a week a year to maintain each), against Paragon's time to production.

    The trigger is public, fresh and specific, the estimate is about their roadmap rather than Paragon, and tl;dv's case study gives a credible benchmark. A hiring decision is the moment build-vs-buy is still open.

    Ready to use

    EmailIntegration-hiring trigger email

    Subject: The {connectors} integrations in your {role} post
    
    Hi {first name},
    
    Your {role} opening mentions building {connectors}. Teams we work with estimated about 4 weeks to build each one in-house and a week a year to keep each one working, so {n} integrations is roughly {engineer-months} engineer-months before upkeep.
    
    I put the estimate on one page (attached). tl;dv shipped Slack, Salesforce and HubSpot to production in under 3 weeks on Paragon and stopped maintaining them.
    
    Worth 20 minutes to see {first connector} running in your product?
    
    {name}
    Account Executive, Paragon

    Risks and how to handle them

    • Prospects find the job-post reference intrusive

      Reference only the public post, once, and lead with the estimate, which is useful either way.

    Evidence

    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
    • Your websitetl;dv case study: 75% less engineering time per integration, integrations about 4x faster, Slack, Salesforce and HubSpot in production in under 3 weeks, maintenance fully offloaded (estimated at about a week a year per integration in-house), and integrations became tl;dv's number one upsell driver.Source
    • programmable.infoSite scan: 182 integration pages, 18 "Paragon vs" competitor pages (Merge, Nango, Composio, Pipedream Connect, Prismatic, Workato Embedded and others), 21 use-case pages, build-vs-buy guides with newsletter landing pages for AlphaSignal and TLDR, RAG webinars, and 14 customer stories.Source
  • 02

    The pricing page asks "What is a Connected User?", "Is there a fee per execution?" and "Can I migrate existing integrations?" and then answers none of them. Those are the questions a CTO needs answered to forward the page to finance.

    High impactLow effort First result in 2 weeks Marketing

    First action

    Ask the AE for the five pricing questions prospects ask most and answer the six on the page first.

    How to measure it

    Pricing page to demo request

    Now
    –
    Target
    +20% relative
    By
    4 weeks

    Steps

    1. 1

      Collect the questions

      The pricing questions from the last 20 sales calls.

      Account Executive 1 hour

    2. 2

      Write the answers

      Plain answers, with one worked example of a Connected Users count.

      Marketing 3 hours

    3. 3

      Approve the numbers

      Confirm what can be said publicly about execution fees and migration.

      CEO 30 minutes

    4. 4

      Publish with FAQ schema

      Mark the answers up so they can appear in search and AI answers.

      Marketing 1 hour

    5. 5

      Link from demos

      The AE links the FAQ in every follow-up.

      Account Executive ongoing

    6. 6

      Measure

      Pricing page to demo request, before and after.

      Marketing 15 minutes a week

    First result
    2 weeks
    Cost
    $0
    Owner
    Marketing

    Smallest test

    Answer "What is a Connected User?" alone this week.

    Why it works

    Write two or three sentences for each of the six questions, including how Connected Users are counted and what drives the quote, and add an example: "A product with 200 customer orgs using 3 integrations."

    Quote-only pricing already adds friction; empty answers look like hidden pricing. Clear answers let the AE spend demos on the product instead of the price model.

    Risks and how to handle them

    • Publishing the model invites price shopping

      Explain how the quote is built, not the price list.

    Evidence

    • Your websitePricing: no listed price; a Platform plan ("Start building") and Enterprise (self-hosting, SLAs, SSO, professional services), with Connected Users priced by custom quote. The FAQ lists six questions ("What is a Connected User?", "Is there a fee per execution?", "Can I migrate existing integrations?" and three more) with no answers on the page.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
  • 03

    Paragon sells auth, permissions and SOC 2 to CTOs, and its homepage links to a missing page while the site grades F on security headers. Technical buyers do check, and these are cheap to fix.

    Medium impactLow effort First result in 1 week CTO

    First action

    Replace the broken homepage link today.

    How to measure it

    Mozilla Observatory grade

    Now
    –
    Target
    A
    By
    1 week

    Steps

    1. 1

      Fix the link

      Point "Workflow Builder Actions" at the right page.

      Marketing 15 minutes

    2. 2

      Add the headers

      CSP, frame and referrer policies on the marketing site.

      CTO 3 hours

    3. 3

      Test the site

      Check embeds, forms and analytics still work.

      Marketing 1 hour

    4. 4

      Re-run Observatory

      Repeat until the grade is A.

      CTO 30 minutes

    5. 5

      Add a weekly check

      Broken-link and header checks in CI or a monitor.

      CTO 1 hour

    6. 6

      Tell the AE

      A line for security questionnaires: the public grade.

      Account Executive 15 minutes

    First result
    1 week
    Cost
    $0
    Owner
    CTO

    Smallest test

    Fix the link and add the two simplest headers today.

    Why it works

    Fix the broken "Workflow Builder Actions" link, add a content security policy and the missing headers on the marketing site, and recheck with Mozilla Observatory until it reaches A.

    The AE sells to engineers who look under the hood. A clean security grade supports every SOC 2 and ISO 27001 claim on the page.

    Risks and how to handle them

    • A strict CSP breaks embeds

      Start in report-only mode for a week.

    Evidence

    • programmable.infoSite checks: the homepage links to a 404 (/use-case/workflow-builder-actions/workflow-builder-actions); the security-header check grades F and Mozilla Observatory C (50/100); news results for "Paragon" are dominated by unrelated companies such as Paragon Capital Management; the GitHub org's topics include claude-code, codex, cursor and skills.Source
    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
  • 04

    The best proof Paragon has is buried in one case study: 75% less engineering time per integration and integrations becoming tl;dv's top upsell driver. The homepage has quotes but no numbers.

    High impactLow effort First result in 2 weeks Marketing

    First action

    Write the proof line and add it under the homepage demo button.

    How to measure it

    Demo request rate on pages with the proof line

    Now
    –
    Target
    +15% relative
    By
    4 weeks

    Steps

    1. 1

      Write one line

      "tl;dv: 75% less engineering time per integration; Slack, Salesforce and HubSpot live in under 3 weeks."

      Marketing 15 minutes

    2. 2

      Place it

      Under demo CTAs and on the three matching integration pages.

      Marketing 2 hours

    3. 3

      Ask for two more numbers

      Copy.ai and CrewAI: one measured outcome each.

      CEO 1 week

    4. 4

      Rotate by page

      Match the proof to the page (AI customers on AI pages).

      Marketing 1 hour

    5. 5

      A/B test

      Half the traffic sees the line for two weeks.

      Marketing 1 hour

    6. 6

      Arm the AE

      Same line in the email signature and the first-call deck.

      Account Executive 15 minutes

    First result
    2 weeks
    Cost
    $0
    Owner
    Marketing

    Smallest test

    Add the line to the homepage only for a week.

    Why it works

    Add one proof line under each demo CTA and on the integration pages for Slack, Salesforce and HubSpot, linking to the case study. Ask two more customers (Copy.ai, CrewAI) for one number each.

    CTOs buy on engineering time saved. A number from a named customer answers "will this save us time" before the demo.

    Risks and how to handle them

    • One case study feels thin

      Add the two new numbers as they come in.

    Evidence

    • Your websitetl;dv case study: 75% less engineering time per integration, integrations about 4x faster, Slack, Salesforce and HubSpot in production in under 3 weeks, maintenance fully offloaded (estimated at about a week a year per integration in-house), and integrations became tl;dv's number one upsell driver.Source
    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
    • programmable.infoSite scan: 182 integration pages, 18 "Paragon vs" competitor pages (Merge, Nango, Composio, Pipedream Connect, Prismatic, Workato Embedded and others), 21 use-case pages, build-vs-buy guides with newsletter landing pages for AlphaSignal and TLDR, RAG webinars, and 14 customer stories.Source
  • 05

    Paragon's GitHub already carries skills for Claude Code, Codex, Cursor and opencode, but the site doesn't say so. A developer evaluating Paragon increasingly asks their coding agent to try it first.

    Medium impactLow effort First result in 3 weeks Solutions Engineering

    First action

    List the skills already in the GitHub org and test the Salesforce walkthrough in Claude Code.

    How to measure it

    Trials with a working integration within 7 days

    Now
    –
    Target
    +25% relative
    By
    6 weeks

    Steps

    1. 1

      Inventory the skills

      What exists, for which agents, and what each does.

      Solutions Engineering 2 hours

    2. 2

      Write the walkthrough

      One prompt, one integration, under 10 minutes.

      Solutions Engineering 3 hours

    3. 3

      Publish the page

      Skills, MCP setup and the walkthrough, linked from signup.

      Marketing 2 hours

    4. 4

      Track agent-origin trials

      Tag trials that start from the skills page.

      Solutions Engineering 1 hour

    5. 5

      Hand warm trials to the AE

      A working integration in week one triggers AE outreach.

      Account Executive ongoing

    6. 6

      Post it

      A short demo video on X and LinkedIn.

      Marketing 1 hour

    First result
    3 weeks
    Cost
    $0
    Owner
    Solutions Engineering

    Smallest test

    Record the walkthrough and send it to ten current trials.

    Why it works

    Publish a page and docs section listing the skills and MCP setup, with a 10-minute "ask your agent to add a Salesforce integration with Paragon" walkthrough, and link it from the trial signup.

    It shortens the path to a working first integration, which is what the AE and Solutions Engineering need before a deal moves, and it reaches engineers who never book a demo.

    Risks and how to handle them

    • Skills break as agents change

      A weekly test of the walkthrough in each agent.

    Evidence

    • programmable.infoSite checks: the homepage links to a 404 (/use-case/workflow-builder-actions/workflow-builder-actions); the security-header check grades F and Mozilla Observatory C (50/100); news results for "Paragon" are dominated by unrelated companies such as Paragon Capital Management; the GitHub org's topics include claude-code, codex, cursor and skills.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
  • 06

    Paragon runs dedicated build-vs-buy landing pages for AlphaSignal and TLDR, so it pays for newsletter sponsorships. Whether they produce AE meetings is the question that decides the budget.

    Medium impactLow effort First result in Next sponsorship Account Executive

    First action

    Pull the last two sponsorships' landing page visits and check how many became meetings.

    How to measure it

    Cost per AE meeting from newsletters

    Now
    –
    Target
    at or below outbound cost per meeting
    By
    next two sponsorships

    Steps

    1. 1

      Tag every sponsorship

      One landing page and UTM per issue.

      Marketing 30 minutes

    2. 2

      Join to the CRM

      Visits to demo requests to meetings to pipeline.

      Marketing 1 day

    3. 3

      Price each meeting

      Sponsorship cost divided by meetings.

      Marketing 1 hour

    4. 4

      Compare with outbound

      AE outbound cost per meeting on the same sheet.

      Account Executive 1 hour

    5. 5

      Decide

      Repeat, change the offer, or drop each newsletter.

      Marketing 1 hour

    6. 6

      Follow up fast

      Every sponsorship lead gets an AE email within a day.

      Account Executive ongoing

    First result
    Next sponsorship
    Cost
    $0
    Owner
    Account Executive

    Smallest test

    Score the last sponsorship by hand.

    Why it works

    Join each sponsorship's landing page traffic to demo requests, meetings and pipeline in the CRM, and report cost per meeting next to the AE's outbound cost per meeting.

    With one AE and a meeting target, every channel should be judged on meetings. The scorecard tells marketing which sponsorships to repeat and which to drop.

    Risks and how to handle them

    • Sponsorship value is mostly brand

      Track 90-day influenced pipeline as well as direct meetings.

    Evidence

    • programmable.infoSite scan: 182 integration pages, 18 "Paragon vs" competitor pages (Merge, Nango, Composio, Pipedream Connect, Prismatic, Workato Embedded and others), 21 use-case pages, build-vs-buy guides with newsletter landing pages for AlphaSignal and TLDR, RAG webinars, and 14 customer stories.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source

This quarter 9

The core plays for the next three months.

  • 07

    Paragon has 182 integration pages, which rank for searches like "Salesforce integration API". They describe the connector but end in a generic demo button.

    High impactMedium effort First result in 6 weeks Solutions Engineering

    First action

    Rank integration pages by visits and demo requests over the last 90 days.

    How to measure it

    Integration page demo requests

    Now
    –
    Target
    2x
    By
    90 days

    Steps

    1. 1

      Rank the pages

      Visits and conversions for the 182 pages.

      Marketing 2 hours

    2. 2

      Write the use cases

      Three concrete use cases per top page.

      Solutions Engineering 3 days

    3. 3

      Build reusable demos

      One working demo app per top integration.

      Solutions Engineering 2 weeks

    4. 4

      Add the booking link

      Routes to the AE with the integration noted.

      Marketing 1 day

    5. 5

      Prep the AE

      A one-page brief per integration for the first call.

      Solutions Engineering 2 days

    6. 6

      Measure

      Requests, meetings and pipeline per page.

      Marketing weekly

    First result
    6 weeks
    Cost
    About three weeks of Solutions Engineering time
    Owner
    Solutions Engineering

    Smallest test

    Do the Salesforce page first and watch it for a month.

    Why it works

    For the 20 most visited integration pages, add the specific use cases buyers build (sync contacts, ingest files for RAG, act through ActionKit), the time to production, and a booking link for a 20-minute demo of that integration.

    A visitor on the Salesforce page has a specific job. A demo of that exact integration is a stronger first call for the AE than a general product tour.

    Risks and how to handle them

    • Solutions Engineering time is scarce

      Record the demos so the AE can run the first call alone.

    Evidence

    • programmable.infoSite scan: 182 integration pages, 18 "Paragon vs" competitor pages (Merge, Nango, Composio, Pipedream Connect, Prismatic, Workato Embedded and others), 21 use-case pages, build-vs-buy guides with newsletter landing pages for AlphaSignal and TLDR, RAG webinars, and 14 customer stories.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
    • Your websitetl;dv case study: 75% less engineering time per integration, integrations about 4x faster, Slack, Salesforce and HubSpot in production in under 3 weeks, maintenance fully offloaded (estimated at about a week a year per integration in-house), and integrations became tl;dv's number one upsell driver.Source
  • 08

    The AE is asked to grow accounts "as customers add integrations". Customers' own users ask them for integrations every week, and tl;dv found integrations became its top upsell driver, so each customer has a backlog Paragon can help them sell.

    High impactMedium effort First result in 1 quarter Account Executive

    First action

    Pick the five largest accounts and book their first review.

    How to measure it

    Integrations added per reviewed account

    Now
    –
    Target
    2 a quarter
    By
    end of next quarter

    Steps

    1. 1

      Build the template

      Usage trend, competitor integration lists, user requests.

      Account Executive 1 day

    2. 2

      Pull competitor lists

      What integrations each customer's rivals advertise.

      Marketing 1 hour per account

    3. 3

      Run the review

      45 minutes with the customer's product lead.

      Account Executive 45 minutes each

    4. 4

      Scope with SE

      Time to ship the agreed integrations.

      Solutions Engineering 1 hour each

    5. 5

      Offer an upsell story

      Help them package integrations as a paid feature, as tl;dv did.

      Account Executive 30 minutes

    6. 6

      Track

      Integrations added and Connected Users growth per account.

      Account Executive quarterly

    First result
    1 quarter
    Cost
    $0
    Owner
    Account Executive

    Smallest test

    Run one review with a friendly customer and ask if it was worth their time.

    Why it works

    Each quarter, meet each customer's product lead with their Connected Users trend, the integrations their competitors list, and the requests their users make, and agree the next two integrations to ship.

    Expansion comes from more integrations and more connected users. Turning integrations into the customer's revenue (as tl;dv did) makes the next one easy to justify.

    Risks and how to handle them

    • Customers see it as a sales meeting

      Lead with their own user requests and competitor gaps.

    Evidence

    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
    • Your websitetl;dv case study: 75% less engineering time per integration, integrations about 4x faster, Slack, Salesforce and HubSpot in production in under 3 weeks, maintenance fully offloaded (estimated at about a week a year per integration in-house), and integrations became tl;dv's number one upsell driver.Source
    • Your websitePricing: no listed price; a Platform plan ("Start building") and Enterprise (self-hosting, SLAs, SSO, professional services), with Connected Users priced by custom quote. The FAQ lists six questions ("What is a Connected User?", "Is there a fee per execution?", "Can I migrate existing integrations?" and three more) with no answers on the page.Source
  • 09

    The AE is expected on site with prospects, and the strongest argument for Paragon is speed. A visit that opens with the prospect's own app connected to their top three tools makes the speed visible.

    High impactMedium effort First result in 2 months Account Executive

    First action

    Pick two open enterprise deals and ask each prospect which three integrations their customers request most.

    How to measure it

    Win rate on prototype-visit deals

    Now
    –
    Target
    1.5x other enterprise deals
    By
    2 quarters

    Steps

    1. 1

      Qualify the deal

      Enterprise, active evaluation, a named technical sponsor.

      Account Executive 30 minutes

    2. 2

      Ask for the top three

      Which integrations their customers request most.

      Account Executive 15 minutes

    3. 3

      Build the prototype

      Sandbox connections and a short demo script.

      Solutions Engineering 2 to 3 days

    4. 4

      Run the visit

      Open with the prototype, then the plan to production.

      Account Executive 1 day

    5. 5

      Leave it running

      Give their engineers the sandbox for a week.

      Solutions Engineering 1 hour

    6. 6

      Compare outcomes

      Prototype deals against others on win rate and cycle.

      Account Executive quarterly

    First result
    2 months
    Cost
    Travel plus about three Solutions Engineering days per deal
    Owner
    Account Executive

    Smallest test

    Do it for one deal this month.

    Why it works

    For qualified enterprise deals, Solutions Engineering builds a prototype of the prospect's three most requested integrations against a sandbox of their product before the visit, and the AE opens the meeting with it.

    CTOs discount claims of "10x faster" and believe what they see. A working prototype shortens the technical evaluation the AE has to navigate.

    Risks and how to handle them

    • Prototype time spent on deals that stall

      Only for deals past technical qualification.

    Evidence

    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
    • Your websitetl;dv case study: 75% less engineering time per integration, integrations about 4x faster, Slack, Salesforce and HubSpot in production in under 3 weeks, maintenance fully offloaded (estimated at about a week a year per integration in-house), and integrations became tl;dv's number one upsell driver.Source
    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
  • 10

    Paragon has written about how it and Merge differ on file storage permissions and runs webinars on permission-aware RAG. AI products that ingest customer files on a unified API hit this limit when an enterprise customer asks who can see what.

    High impactMedium effort First result in 4 weeks Marketing

    First action

    Turn the Paragon vs Merge permissions post into a two-page brief with a diagram.

    How to measure it

    Pipeline from permission takeouts

    Now
    –
    Target
    $400k
    By
    end of quarter

    Steps

    1. 1

      Write the brief

      How permission-aware ingestion works and where it breaks.

      Solutions Engineering 2 days

    2. 2

      Build the list

      AI products advertising file ingestion that name a unified API.

      Marketing 3 days

    3. 3

      Personalize

      Reference their docs or changelog in one line.

      Account Executive 10 minutes each

    4. 4

      Offer a review

      30 minutes with SE on their permission model.

      Account Executive ongoing

    5. 5

      Invite to the webinar

      The next permission-aware RAG session.

      Marketing 1 hour

    6. 6

      Track

      Replies, meetings and pipeline by competitor.

      Account Executive weekly

    First result
    4 weeks
    Cost
    $0
    Owner
    Marketing

    Smallest test

    Send the brief to 15 companies and count meetings.

    Why it works

    Build a short technical brief on permission-aware ingestion, list AI products that advertise Google Drive, SharePoint or Box ingestion and name a unified API vendor in their docs or changelog, and send the brief from the AE with an offer of a permissions review.

    It reaches buyers at the moment a real requirement (enterprise permissions) exposes a gap, which converts better than a generic comparison page.

    Risks and how to handle them

    • Claims about competitors go out of date

      Check each claim against their current docs before sending.

    Evidence

    • Your websiteWebinars on production RAG and permission-aware retrieval ("Access Control Permissions in RAG for AI Products") and a blog post comparing Paragon and Merge on file storage permissions.Source
    • programmable.infoSite scan: 182 integration pages, 18 "Paragon vs" competitor pages (Merge, Nango, Composio, Pipedream Connect, Prismatic, Workato Embedded and others), 21 use-case pages, build-vs-buy guides with newsletter landing pages for AlphaSignal and TLDR, RAG webinars, and 14 customer stories.Source
    • Competitor researchCompetitors: Composio raised a $25M Series A led by Lightspeed (about $29M total) and markets 500+ integrations with native MCP support for agents; Nango is described as code-first integrations with sync and RAG across 800+ APIs; Merge positions a unified API with enterprise governance.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
  • 11

    CrewAI is a named customer and its COO is quoted on the homepage. Agent builders using CrewAI need exactly what ActionKit provides: authenticated actions in their customers' tools.

    Medium impactMedium effort First result in 2 months CEO

    First action

    Ask CrewAI's COO whether they would co-publish a template.

    How to measure it

    Meetings from framework templates

    Now
    –
    Target
    15
    By
    8 weeks after publishing

    Steps

    1. 1

      Agree the scope

      One template, one docs page, one webinar.

      CEO 1 week

    2. 2

      Build the template

      An agent acting in Salesforce and Slack via ActionKit.

      Solutions Engineering 1 week

    3. 3

      Publish in both docs

      CrewAI docs and Paragon's.

      Marketing 2 days

    4. 4

      Run the webinar

      Joint, 30 minutes, recorded.

      Marketing 1 day

    5. 5

      Route signups

      Template signups go to the AE.

      Account Executive ongoing

    6. 6

      Repeat

      The next framework customer or partner.

      CEO quarterly

    Who to approach

    • CrewAI

      Existing customer and a major agent framework whose users need tool access.

    First result
    2 months
    Cost
    $0
    Owner
    CEO

    Smallest test

    Publish the template in Paragon's docs first and share it with CrewAI.

    Why it works

    Co-write a template and docs page with CrewAI showing an agent acting in Salesforce and Slack through ActionKit, with a joint webinar and a listing in CrewAI's integrations.

    Framework docs are where agent builders choose their tools. A co-built template turns a customer into a channel and gives the AE a stream of qualified AI companies.

    Risks and how to handle them

    • Framework favours a competitor

      Lead with the customer relationship and a working template.

    Evidence

    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
    • Competitor researchCompetitors: Composio raised a $25M Series A led by Lightspeed (about $29M total) and markets 500+ integrations with native MCP support for agents; Nango is described as code-first integrations with sync and RAG across 800+ APIs; Merge positions a unified API with enterprise governance.Source
    • programmable.infoSite scan: 182 integration pages, 18 "Paragon vs" competitor pages (Merge, Nango, Composio, Pipedream Connect, Prismatic, Workato Embedded and others), 21 use-case pages, build-vs-buy guides with newsletter landing pages for AlphaSignal and TLDR, RAG webinars, and 14 customer stories.Source
  • 12

    Paragon runs technical webinars on production RAG and permissions. Attendees are engineers with a live problem, and most will not book a sales demo.

    Medium impactMedium effort First result in Next webinar Marketing

    First action

    Add the office hour invite to the next webinar's follow-up email.

    How to measure it

    AE meetings per webinar

    Now
    –
    Target
    5
    By
    third webinar

    Steps

    1. 1

      Schedule the office hour

      Two days after each webinar.

      Marketing 15 minutes

    2. 2

      Invite attendees

      In the replay email, with a question form.

      Marketing 30 minutes

    3. 3

      Run it

      Solutions Engineering answers real questions.

      Solutions Engineering 30 minutes

    4. 4

      Offer 1:1s

      To attendees with a live project.

      Solutions Engineering as needed

    5. 5

      Hand over

      AE follows up with 1:1 attendees.

      Account Executive ongoing

    6. 6

      Measure

      Attendees, office hour, 1:1, meetings.

      Marketing monthly

    First result
    Next webinar
    Cost
    $0
    Owner
    Marketing

    Smallest test

    Try it after the next webinar.

    Why it works

    After each webinar, invite attendees to a 30-minute group office hour with Solutions Engineering, then offer a 1:1 review to those who bring a real architecture question; the AE follows up only with those.

    A technical next step converts engineers who ignore sales follow-up, and the AE gets meetings with context.

    Risks and how to handle them

    • Low office hour turnout

      Collect questions in advance and answer them on the replay.

    Evidence

    • Your websiteWebinars on production RAG and permission-aware retrieval ("Access Control Permissions in RAG for AI Products") and a blog post comparing Paragon and Merge on file storage permissions.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
  • 13

    Copy.ai, You.com, tl;dv and Crystal Knows are customers. Their direct competitors face the same integration requests and have to answer them to keep up.

    High impactMedium effort First result in 4 weeks Marketing

    First action

    List ten competitors of tl;dv and the integrations each advertises.

    How to measure it

    Meetings per 100 accounts

    Now
    –
    Target
    5
    By
    6 weeks

    Steps

    1. 1

      Pick the categories

      Where Paragon has a named customer.

      Marketing 1 hour

    2. 2

      List the peers

      Ten to 30 competitors per category.

      Marketing 2 days

    3. 3

      Map their integrations

      From their own integration pages.

      Marketing 2 days

    4. 4

      Rank the accounts

      Fewer integrations than the leader means a bigger gap.

      Account Executive 2 hours

    5. 5

      Send the angle

      "Your category ships these; here is how fast."

      Account Executive weekly

    6. 6

      Review

      Meeting rate by category.

      Account Executive monthly

    First result
    4 weeks
    Cost
    $0
    Owner
    Marketing

    Smallest test

    Work one category for two weeks.

    Why it works

    For each customer category (AI writing, meeting notes, search, sales intelligence), list competitors and the integrations they advertise, and give the AE a ranked list with a "your competitors ship these integrations" angle.

    The AE runs outbound with marketing from account lists. Category peers of happy customers convert best and the competitive angle is specific.

    Risks and how to handle them

    • Customers object to selling to rivals

      Never name the customer to their competitor.

    Evidence

    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
    • Your websitetl;dv case study: 75% less engineering time per integration, integrations about 4x faster, Slack, Salesforce and HubSpot in production in under 3 weeks, maintenance fully offloaded (estimated at about a week a year per integration in-house), and integrations became tl;dv's number one upsell driver.Source
  • 14

    "Can I migrate existing integrations?" is one of the unanswered pricing questions. Teams that already built integrations in-house, or on a competitor, need a path to switch before they can buy.

    Medium impactMedium effort First result in 1 month Solutions Engineering

    First action

    Document the last two customer migrations as the basis of the guide.

    How to measure it

    Migration deals opened

    Now
    –
    Target
    4
    By
    end of quarter

    Steps

    1. 1

      Document past migrations

      What moved, how long, what broke.

      Solutions Engineering 2 days

    2. 2

      Write the guide

      Steps, token migration, timelines.

      Solutions Engineering 3 days

    3. 3

      Package the offer

      Fixed scope and price for professional services.

      CEO 1 day

    4. 4

      Publish and link

      From pricing, competitor pages and the FAQ.

      Marketing 1 day

    5. 5

      Arm the AE

      A migration talk track.

      Account Executive 1 hour

    6. 6

      Track

      Migration deals and their cycle times.

      Account Executive monthly

    First result
    1 month
    Cost
    $0
    Owner
    Solutions Engineering

    Smallest test

    Offer the package to two open deals that already built integrations.

    Why it works

    Publish a migration guide (what moves, auth token migration, a typical timeline) and offer a fixed-scope migration package through Enterprise professional services.

    Switching cost is the main objection for teams already invested. A defined path turns "not now" into a scoped project the AE can sell.

    Risks and how to handle them

    • Migrations take longer than promised

      Quote ranges from real past migrations.

    Builds on

    Evidence

    • Your websitePricing: no listed price; a Platform plan ("Start building") and Enterprise (self-hosting, SLAs, SSO, professional services), with Connected Users priced by custom quote. The FAQ lists six questions ("What is a Connected User?", "Is there a fee per execution?", "Can I migrate existing integrations?" and three more) with no answers on the page.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
  • 15

    Most of the 14 customer stories predate the AI positioning, yet the homepage now leads with agents. The AE sells to AI companies and needs AI proof.

    Medium impactMedium effort First result in 6 weeks Marketing

    First action

    Ask Copy.ai, CrewAI and You.com for a 30-minute interview each.

    How to measure it

    AI customer stories live

    Now
    –
    Target
    3
    By
    6 weeks

    Steps

    1. 1

      Book interviews

      Three customers, 30 minutes each.

      CEO 1 week

    2. 2

      Get the numbers

      Time to ship, integrations, revenue impact.

      Marketing in interviews

    3. 3

      Write and approve

      One page each, customer-approved.

      Marketing 2 weeks

    4. 4

      Publish

      Customers page and relevant integration pages.

      Marketing 1 day

    5. 5

      Arm the AE

      One line per story for outbound.

      Account Executive 30 minutes

    6. 6

      Measure

      Story views in deals that close.

      Marketing monthly

    First result
    6 weeks
    Cost
    $0
    Owner
    Marketing

    Smallest test

    Publish one story first.

    Why it works

    Write three short stories with one measured outcome each (time to production, integrations shipped, revenue from integrations) for the AI customers already quoted on the homepage.

    Prospects want peers. AI-company stories with numbers match the new positioning and give the AE material for every outbound sequence.

    Risks and how to handle them

    • Customers decline numbers

      Use relative figures or time saved.

    Evidence

    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
    • programmable.infoSite scan: 182 integration pages, 18 "Paragon vs" competitor pages (Merge, Nango, Composio, Pipedream Connect, Prismatic, Workato Embedded and others), 21 use-case pages, build-vs-buy guides with newsletter landing pages for AlphaSignal and TLDR, RAG webinars, and 14 customer stories.Source
    • Your websitetl;dv case study: 75% less engineering time per integration, integrations about 4x faster, Slack, Salesforce and HubSpot in production in under 3 weeks, maintenance fully offloaded (estimated at about a week a year per integration in-house), and integrations became tl;dv's number one upsell driver.Source

Big bets 4

Larger plays that can change the trajectory.

  • 16

    The AE covers SMB, mid-market and enterprise from $50k to $500k ACV, and pricing is quote-only. Small AI startups that need two or three integrations take AE time for small deals.

    High impactHigh effort First result in 1 quarter CEO

    First action

    Count last year's deals under $20k and the AE hours they took.

    How to measure it

    Share of AE time on deals over $50k

    Now
    –
    Target
    80%
    By
    2 quarters after launch

    Steps

    1. 1

      Size small deals

      Count and AE time for deals under $20k.

      Account Executive 1 day

    2. 2

      Set the plan

      Limits, price and upgrade triggers.

      CEO 2 weeks

    3. 3

      Build checkout

      Card payment and usage limits.

      CTO 4 weeks

    4. 4

      Route by size

      Small signups to self-serve, large to the AE.

      Marketing 1 week

    5. 5

      Launch

      Pricing page, newsletter, social.

      Marketing 1 week

    6. 6

      Measure

      Self-serve revenue and upgrades.

      CEO monthly

    First result
    1 quarter
    Cost
    About six weeks of engineering
    Owner
    CEO

    Smallest test

    Offer a fixed small-team price by email to ten startups.

    Why it works

    Publish a self-serve plan with a clear price for a set number of Connected Users and integrations, with card checkout and an upgrade path to the quoted plans.

    It frees the AE for larger deals and catches startups that will not talk to sales, some of which grow into enterprise accounts.

    Risks and how to handle them

    • Self-serve undercuts quoted deals

      Cap Connected Users and keep enterprise features on quoted plans.

    Builds on

    Evidence

    • Your websitePricing: no listed price; a Platform plan ("Start building") and Enterprise (self-hosting, SLAs, SSO, professional services), with Connected Users priced by custom quote. The FAQ lists six questions ("What is a Connected User?", "Is there a fee per execution?", "Can I migrate existing integrations?" and three more) with no answers on the page.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
    • Competitor researchCompetitors: Composio raised a $25M Series A led by Lightspeed (about $29M total) and markets 500+ integrations with native MCP support for agents; Nango is described as code-first integrations with sync and RAG across 800+ APIs; Merge positions a unified API with enterprise governance.Source
  • 17

    Paragon sees which integrations AI products ship first, how fast and how usage grows. No competitor publishes that, and AI product leaders want to know what their category ships.

    High impactHigh effort First result in Launch quarter Marketing

    First action

    List the five questions the report will answer and check the data supports them.

    How to measure it

    Pipeline influenced by the report

    Now
    –
    Target
    $1M
    By
    6 months after launch

    Steps

    1. 1

      Pick the questions

      Five questions product leaders argue about.

      CEO 1 day

    2. 2

      Set privacy rules

      Aggregates only, minimum group sizes.

      CTO 1 day

    3. 3

      Analyze

      Usage by category and over time.

      CTO 3 weeks

    4. 4

      Design and write

      Short, one chart per finding.

      Marketing 3 weeks

    5. 5

      Launch

      Webinar, newsletter sponsorships, social.

      Marketing 1 week

    6. 6

      Arm the AE

      One outbound angle per finding.

      Account Executive 1 day

    First result
    Launch quarter
    Cost
    $5,000 to $10,000 in design and promotion
    Owner
    Marketing

    Smallest test

    Publish one finding as a blog post first.

    Why it works

    Publish a yearly report from aggregated, anonymized usage: the most connected tools by category, time to production, usage growth after launch and the rise of agent actions, with a launch webinar and AE follow-up.

    Original data earns links and press that comparison pages cannot. Each finding becomes an outbound angle and a reason for a CTO to take a call.

    Risks and how to handle them

    • Customers worry about their data

      Aggregates only, stated plainly.

    Evidence

    • programmable.infoSite scan: 182 integration pages, 18 "Paragon vs" competitor pages (Merge, Nango, Composio, Pipedream Connect, Prismatic, Workato Embedded and others), 21 use-case pages, build-vs-buy guides with newsletter landing pages for AlphaSignal and TLDR, RAG webinars, and 14 customer stories.Source
    • Your websitetl;dv case study: 75% less engineering time per integration, integrations about 4x faster, Slack, Salesforce and HubSpot in production in under 3 weeks, maintenance fully offloaded (estimated at about a week a year per integration in-house), and integrations became tl;dv's number one upsell driver.Source
    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
  • 18

    Enterprise already offers self-hosting and forward deployment. Enterprise buyers with committed cloud spend can buy marketplace software without a new vendor process.

    High impactHigh effort First result in 2 quarters CEO

    First action

    Ask the three largest open deals whether they buy through AWS Marketplace.

    How to measure it

    Cycle time on marketplace deals

    Now
    –
    Target
    30% shorter
    By
    3 quarters

    Steps

    1. 1

      Check demand

      How large prospects buy.

      Account Executive 1 week

    2. 2

      Register as a seller

      AWS Marketplace onboarding.

      CEO 2 weeks

    3. 3

      Build the listing

      SaaS contract with private offers.

      CTO 2 weeks

    4. 4

      Attach compliance

      SOC 2, ISO 27001, DPA.

      CTO 2 days

    5. 5

      Train the AE

      When to offer it.

      CEO 1 hour

    6. 6

      Co-sell

      Apply to AWS ISV programs after first deals.

      CEO ongoing

    First result
    2 quarters
    Cost
    Marketplace fees plus a month of setup
    Owner
    CEO

    Smallest test

    Offer one deal a private offer.

    Why it works

    List Enterprise on AWS Marketplace with private offers, attach the compliance documents and give the AE a marketplace path for deals above a set size.

    Marketplace procurement shortens legal and vendor onboarding, which is often the slowest part of a $100k+ deal for a young vendor.

    Risks and how to handle them

    • Fees cut margin

      Price the fee into private offers.

    Evidence

    • Your websitePricing: no listed price; a Platform plan ("Start building") and Enterprise (self-hosting, SLAs, SSO, professional services), with Connected Users priced by custom quote. The FAQ lists six questions ("What is a Connected User?", "Is there a fee per execution?", "Can I migrate existing integrations?" and three more) with no answers on the page.Source
    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
  • 19

    Agencies and dev shops build AI products for clients and get asked for integrations constantly. Each agency that standardizes on Paragon brings several end customers.

    High impactHigh effort First result in 2 quarters CEO

    First action

    List agencies that have built on Paragon for clients already and call three.

    How to measure it

    Share of new pipeline from partners

    Now
    –
    Target
    20%
    By
    3 quarters

    Steps

    1. 1

      Find the first partners

      Agencies already using Paragon.

      Account Executive 2 weeks

    2. 2

      Set the terms

      Referral fee or resale margin.

      CEO 2 weeks

    3. 3

      Build enablement

      Training and a partner sandbox.

      Solutions Engineering 4 weeks

    4. 4

      List partners

      A partners page by specialty.

      Marketing 1 week

    5. 5

      Co-sell

      Joint calls on partner deals.

      Account Executive ongoing

    6. 6

      Review

      Partner pipeline quarterly.

      CEO quarterly

    First result
    2 quarters
    Cost
    Referral fees plus enablement time
    Owner
    CEO

    Smallest test

    Sign one agency and run one joint deal.

    Why it works

    Recruit ten AI development agencies with training, a partner sandbox, referral fees or margin on resale, and co-listing on a partners page; the AE works their client deals with them.

    One AE can only run so many deals. Partners multiply reach into companies the AE would never find, and come with a trusted adviser already in the room.

    Risks and how to handle them

    • Partners deliver poor integrations

      Certify partners with a review of their first project.

    Evidence

    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
    • Competitor researchCompetitors: Composio raised a $25M Series A led by Lightspeed (about $29M total) and markets 500+ integrations with native MCP support for agents; Nango is described as code-first integrations with sync and RAG across 800+ APIs; Merge positions a unified API with enterprise governance.Source

Wildcards 3

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

  • 20

    News results for "Paragon" are dominated by unrelated companies such as Paragon Capital Management. AI assistants and search engines need consistent signals to connect the name to the product.

    Medium impactLow effort First result in 2-3 months Marketing

    First action

    Search "Paragon" and "Paragon integrations" in Google, ChatGPT and Perplexity and record what comes up.

    How to measure it

    Correct AI answers for "What is Paragon integrations?"

    Now
    –
    Target
    4 of 4 assistants
    By
    3 months

    Steps

    1. 1

      Record the baseline

      Search and AI answers for the name.

      Marketing 1 hour

    2. 2

      Fix the schema

      Organization schema with sameAs links.

      Marketing 2 hours

    3. 3

      Align profiles

      Same one-line description on every profile.

      Marketing 2 hours

    4. 4

      Use the full name

      "Paragon integrations" in titles and press.

      Marketing ongoing

    5. 5

      Earn mentions

      Guest posts and podcasts using the full name.

      CEO monthly

    6. 6

      Re-check

      Monthly searches and AI answers.

      Marketing 30 minutes a month

    First result
    2 to 3 months
    Cost
    $0
    Owner
    Marketing

    Smallest test

    Fix the schema and profiles this week and check AI answers in a month.

    Why it works

    Use "Paragon integrations" or "Paragon, the integration platform" in titles, profiles and press; complete Organization schema with sameAs links to LinkedIn, X, GitHub and Crunchbase; and keep the same description everywhere.

    Prospects who hear the name from a peer search for it. Consistent entity signals help search engines and AI answers point them at the right company.

    Risks and how to handle them

    • Slow to move

      Track monthly and keep the descriptions consistent.

    Evidence

    • programmable.infoSite checks: the homepage links to a 404 (/use-case/workflow-builder-actions/workflow-builder-actions); the security-header check grades F and Mozilla Observatory C (50/100); news results for "Paragon" are dominated by unrelated companies such as Paragon Capital Management; the GitHub org's topics include claude-code, codex, cursor and skills.Source
    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
  • 21

    SaaS companies publish their integration directories and changelogs. The number of integration fixes in a changelog is a public measure of the upkeep Paragon removes.

    Medium impactMedium effort First result in 2 months Solutions Engineering

    First action

    Run the audit by hand for five prospects and see whether the numbers are credible.

    How to measure it

    Meetings from upkeep audits

    Now
    –
    Target
    10
    By
    8 weeks after launch

    Steps

    1. 1

      Prove it by hand

      Five manual audits.

      Solutions Engineering 2 days

    2. 2

      Set the model

      Hours per integration fix, from customer data.

      Solutions Engineering 1 day

    3. 3

      Build the page

      Domain in, estimate out.

      CTO 2 weeks

    4. 4

      Route results

      Large estimates go to the AE.

      Marketing 1 day

    5. 5

      Promote

      In the newsletter sponsorships and outbound.

      Marketing ongoing

    6. 6

      Measure

      Audits, meetings, pipeline.

      Account Executive monthly

    First result
    2 months
    Cost
    About two weeks of engineering
    Owner
    Solutions Engineering

    Smallest test

    Send five manual audits to prospects.

    Why it works

    Offer a free audit page: enter a domain, get the integrations the company lists, how often their changelog mentions integration fixes, and an estimated engineer-time cost; the AE follows up with the larger results.

    It quantifies the "keep the upkeep off your roadmap" promise with the prospect's own data and gives the AE a specific opener.

    Risks and how to handle them

    • Estimates look arbitrary

      Show the method and the inputs on the result page.

    Evidence

    • Your websiteHomepage: "Connect your agent to customer data and tools. Keep the upkeep off your roadmap." Products Managed Sync, ActionKit and Workflows; named customers Appsmith, CrewAI, Crystal Knows, You.com, tl;dv and Copy.ai; SOC 2 Type II, HIPAA, GDPR and ISO 27001 listed.Source
    • Your websitetl;dv case study: 75% less engineering time per integration, integrations about 4x faster, Slack, Salesforce and HubSpot in production in under 3 weeks, maintenance fully offloaded (estimated at about a week a year per integration in-house), and integrations became tl;dv's number one upsell driver.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.Source
  • 22

    tl;dv's integrations are paid features that drive MRR and became their top upsell driver. Most SaaS companies give integrations away; showing them how to charge for them makes Paragon pay for itself.

    Medium impactLow effort First result in 1 month Account Executive

    First action

    Interview tl;dv's team on how they priced their integrations.

    How to measure it

    Deals with a second champion

    Now
    –
    Target
    50%
    By
    2 quarters

    Steps

    1. 1

      Interview tl;dv

      How they packaged and priced integrations.

      Account Executive 1 hour

    2. 2

      Write the guide

      Tiers, pricing, examples.

      Marketing 1 week

    3. 3

      Add a calculator

      Revenue from paid integrations by customer count.

      Solutions Engineering 2 days

    4. 4

      Use it in deals

      Share with product leaders.

      Account Executive ongoing

    5. 5

      Publish

      Gated or open on the site.

      Marketing 1 day

    6. 6

      Track

      Deals with a second champion and win rate.

      Account Executive quarterly

    First result
    1 month
    Cost
    $0
    Owner
    Account Executive

    Smallest test

    Share the tl;dv story with three product leaders in open deals.

    Why it works

    Write a guide on packaging integrations as paid features (which tiers, which integrations, how to price), with tl;dv as the example, and have the AE share it with product leaders in every deal.

    It reframes Paragon from a cost to a revenue source and brings a product or revenue leader into the deal alongside the CTO.

    Risks and how to handle them

    • Customers resist charging for integrations

      Show both models; the guide is advice, not a requirement.

    Evidence

    • Your websitetl;dv case study: 75% less engineering time per integration, integrations about 4x faster, Slack, Salesforce and HubSpot in production in under 3 weeks, maintenance fully offloaded (estimated at about a week a year per integration in-house), and integrations became tl;dv's number one upsell driver.Source
    • HiringAccount Executive, the only open role on the careers page: full cycle across SMB, mid-market and enterprise, selling to CTOs and VPs of Engineering at $50k-$500k ACV; "Outbound pipeline generation is a muscle we are building"; "goals of 3 outbound meetings set per week"; runs outbound "alongside marketing" with account lists and intent signals, partners with Solutions Engineering on technical scoping, grows accounts "as customers add integrations", and is expected on site with prospects. $150k-$300k OTE.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 22 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.

Outreach1The sequence sent for you: addresses found and verified, replies routed 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 #1 (opens programmable.info in a new tab)
  • Build this list in Info for idea #10 (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)
ProgrammableDigital

Show it, don't just describe it

These ideas need something to show: a demo, a video, an animation, graphics or a deck. Digital turns screenshots or the site into all of them, in the company's own brand.

Make a demo (opens programmable.digital in a new tab)
Website review of useparagon.com More example playbooks and reviews

More growth playbooks

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

  • Primitive growth strategyEmail infrastructure for AI agents: managed *.primitive.email addresses, a one-call send-and-wait-for-reply verb (primitive chat), hosted…23 growth ideas
  • Game Beauty growth strategyColour makeup inspired by video games and anime: licensed Street Fighter 6 and Attack on Titan collections, original palettes, lipsticks…21 growth ideas
  • Vooma growth strategyAI agents for freight brokers, carriers and 3PLs that quote, build loads, schedule appointments, book carriers and track shipments across…21 growth ideas
  • Real Chemistry growth strategyA global healthcare marketing and communications company (including 21GRAMS and Real Chemistry Media) offering media and influence…22 growth ideas
  • Wonderschool growth strategyA child care marketplace and operating system: parents find and enroll in care, providers start and run programs with software and…22 growth ideas
  • MotherDuck growth strategyA serverless cloud data warehouse built on DuckDB, with an isolated DuckDB instance (a Duckling) for every user, customer and agent, plus…21 growth ideas
  • FuseGlobal growth strategyA specialist staffing firm founded in 2000: long-term contract staffing, solution delivery and payroll services for SAP, technology…21 growth ideas
  • Navtech growth strategyA domain-specific AI development company: fine-tuned and RAG-based models, agentic systems and data engineering, built on the client's…21 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on October 18, 2026, and cites them throughout. Paragon did not commission, review or endorse it, and Programmable is not affiliated with Paragon. 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 Paragon runs its business.

Something wrong, or do you represent Paragon? 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 308 ideas

    Start the job-post outbound, answer the pricing FAQ, fix the site, put proof next to every demo button, publish the agent skills page and score the newsletter sponsorships.

    Programmable can ship 1 of these in days.

  2. Days 31 to 608 ideas

    Build the repeatable engines: prototype visits, permission takeouts, category account lists, the migration guide and webinar office hours, plus the name and upkeep-audit wildcards.

  3. Days 61 to 906 ideas

    Partners and proof (CrewAI templates, AI customer stories), then commit to the big bets on the first 60 days of evidence.

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 integrations in production in weeks, not quarters. The most cited problem: building and maintaining auth, retries and rate limits per integration.

  • Maintenance taken off the roadmap
  • Per-user permissions when ingesting customer files for RAG
  • In their words: “keep the upkeep off your roadmap”

Market

Competitive landscape

4 competitors compared: Merge, Composio, Nango and Prismatic and Workato Embedded.

  • Gap to exploit: Permission-aware ingestion for enterprise RAG
  • Merge: Common data models limit custom fields and permissions
  • Composio: Younger enterprise track record

Hiring signals

Paragon has a single open role, an Account Executive, and the post says a lot.

  • Account Executive: Sales-led growth with outbound being built: 3 outbound meetings a week, full cycle with CTOs at $50k-$500k ACV, on-site visits…

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