Bridgehead Prepared for Bastien at Nango
Nango For Bastien

Integration Platform Software Sales Playbook

Bastien, we’ll build your new AE’s first 100 accounts in 10 days. The first 25 are below, and they’re yours either way.

If your AE seat stays open another quarter, ignore this. If it doesn’t, the next two minutes are worth it.

What we noticed

Your November 5 LinkedIn post says Nango went from 6,000 to 13,000+ GitHub stars this year, and your posting says Nango serves 800+ paying customers, including ServiceNow and Replit. That record is what your new AE gets to open every call with.

Your founding Account Executive role was posted today, and it is the first enterprise seller. Your posting says the seller builds repeatable messaging and deal patterns.

  1. March 23 Seed round recorded
  2. October 27 10,000+ pre-built tools for AI agents announced
  3. November 5 13,000+ GitHub stars announced
  4. November 9 Founding AE role posted; the first 25 accounts are on this page

What changes for your new AE

Your new AE starts day one with 100 accounts you approved and drafts written to the first five, instead of spending their first weeks finding them. Your posting says they will lead technical evaluations with your engineers, so every week saved on finding accounts is a week sooner to the first evaluation.

Your first 25 accounts

Picked from how your posting and your posts describe your buyers. Each one has the reason it’s here and the source.

Yours either wayKeep these 25 whether or not we ever talk.
Cut any you wouldn’t callTell us why, and we replace it. We keep going until you’d keep at least 80 of the 100.
  1. Writer San Francisco, CA · enterprise AI platform
    1

    They are staffing the exact layer you sell, so the build-or-buy question is open on their engineering team this week.

    Signal: Nov 3, 2026 Source
    Buyer: VP of Engineering or head of the integrations platform
    Why it’s ranked here

    A strong fit.

    • A product company whose product has to connect to its customers’ own tools or apps.
    • Its own job posting shows an integrations or agent-connectivity build under way.
    • An engineering organization big enough to have the executives your posting names.
    • Something dated happened in the last thirty days.
    • Its product needs user-authorized access, with permissions and credentials.
    • Not already on your customers page or in your case studies.
  2. Asana Vancouver, BC · work management software
    2

    Asana is putting a product lead on how agents reach its data, and every agent builder connecting to Asana needs the auth and permissions on the other side.

    Signal: Nov 5, 2026 Source
    Buyer: Head of Platform Product
    Why it’s ranked here

    A strong fit.

    • A product company whose product has to connect to its customers’ own tools or apps.
    • Its own job posting shows an integrations or agent-connectivity build under way.
    • An engineering organization big enough to have the executives your posting names.
    • Something dated happened in the last thirty days.
    • Its product needs user-authorized access, with permissions and credentials.
    • Not already on your customers page or in your case studies.
  3. Lattice Remote, US · people management software
    3

    The posting describes an integrations team that has already shipped an MCP server and is widening into ingesting data from other tools, which is the next set of connections to maintain.

    Signal: Nov 5, 2026 Source
    Buyer: Head of Engineering, Integrations
    Why it’s ranked here

    A strong fit.

    • A product company whose product has to connect to its customers’ own tools or apps.
    • Its own job posting shows an integrations or agent-connectivity build under way.
    • An engineering organization big enough to have the executives your posting names.
    • Something dated happened in the last thirty days.
    • Its product needs user-authorized access, with permissions and credentials.
    • Not already on your customers page or in your case studies.
  4. Braze New York, NY and other US cities · customer engagement platform
    4

    A new AI product has its own integrations team, and each customer data source it connects needs credentials the customer controls.

    Signal: Nov 9, 2026 Source
    Buyer: Director of Engineering, Decisioning Studio
    Why it’s ranked here

    A strong fit.

    • A product company whose product has to connect to its customers’ own tools or apps.
    • Its own job posting shows an integrations or agent-connectivity build under way.
    • An engineering organization big enough to have the executives your posting names.
    • Something dated happened in the last thirty days.
    • Its product needs user-authorized access, with permissions and credentials.
    • Not already on your customers page or in your case studies.
  5. Zendesk San Francisco, CA · customer service software
    5

    The posting lists auth, pagination, rate limits and schema drift as the job, which is the maintenance load a connector layer takes off an engineering team.

    Signal: Nov 5, 2026 Source
    Buyer: Director of Engineering, AI data layer
    Why it’s ranked here

    A strong fit.

    • A product company whose product has to connect to its customers’ own tools or apps.
    • Its own job posting shows an integrations or agent-connectivity build under way.
    • An engineering organization big enough to have the executives your posting names.
    • Something dated happened in the last thirty days.
    • Its product needs user-authorized access, with permissions and credentials.
    • Not already on your customers page or in your case studies.
  6. Genesys California · customer experience platform
    6

    Their CRM integration platform already covers three large systems and is hiring a lead, so more providers and more auth flows are coming.

    Signal: Nov 5, 2026 Source
    Buyer: Head of Engineering, CRM and Integrations
    Why it’s ranked here

    A strong fit.

    • A product company whose product has to connect to its customers’ own tools or apps.
    • Its own job posting shows an integrations or agent-connectivity build under way.
    • An engineering organization big enough to have the executives your posting names.
    • Something dated happened in the last thirty days.
    • Its product needs user-authorized access, with permissions and credentials.
    • Not already on your customers page or in your case studies.
  7. OpenAI San Francisco, CA · AI lab and platform
    7

    The agent platform team lists integrations as part of its scope, so how tools reach users’ accounts is a live engineering question there.

    Signal: Nov 5, 2026 Source
    Buyer: Head of Agent Platform Engineering
    Why it’s ranked here

    A strong fit.

    • A product company whose product has to connect to its customers’ own tools or apps.
    • Its own job posting shows an integrations or agent-connectivity build under way.
    • An engineering organization big enough to have the executives your posting names.
    • Something dated happened in the last thirty days.
    • Its product needs user-authorized access, with permissions and credentials.
    • Not already on your customers page or in your case studies.
  8. Sprout Social Chicago, IL · social media management software
    8

    The posting says Sprout is moving off one-off integrations to a platform model, which is the shift your product makes for a team.

    Signal: Nov 4, 2026 Source
    Buyer: VP of Product, Platform and Integrations
    Why it’s ranked here

    A strong fit.

    • A product company whose product has to connect to its customers’ own tools or apps.
    • Its own job posting shows an integrations or agent-connectivity build under way.
    • An engineering organization big enough to have the executives your posting names.
    • Something dated happened in the last thirty days.
    • Its product needs user-authorized access, with permissions and credentials.
    • Not already on your customers page or in your case studies.

Your new AE’s first 100 accounts, in 10 days

The first 25 are above, and they’re yours either way.

Email Kash

We build a handful of these a month, for founders hiring now.

10 days

from kickoff to your team running it

  • 100 accounts you approve, each with the reason
  • Drafts to the first five, in your voice
  • Your team runs it without us
  • Any account you cut, we replace

How does Nango sell?

An outside read from your LinkedIn posts, your site, your customer stories and your posting, built to be corrected: tell us anything that’s wrong. Tap a clip to play it from that moment.

In your posts and interviews10 quotes
  1. Who buys
    “We want developers to ship an integration and get back to building their product.”
    Your 1,000+ APIs post on LinkedIn, October 16
  2. Who buys
    “We want Nango to be the default starting point for developers connecting agents to their users’ apps.”
    Your GitHub stars post on LinkedIn, November 5
  3. The problem
    “Your integration can be ready while your OAuth app is still weeks away from approval.”
    Your OAuth apps post on LinkedIn, October 29
  4. The problem
    “When a provider changes its auth flow six months later, that should be our problem, not yours!”
    Your 1,000+ APIs post on LinkedIn, October 16
  5. The problem
    “Not every API has an official MCP server. And even when one exists, it may not expose the action your agent needs.”
    Your 10,000 tools post on LinkedIn, October 27
  6. Why you win
    “They want control over customer data and credentials.”
    Your self-hosting post on LinkedIn, October 20
  7. Why you win
    “Nango runs in their cloud, and we manage it for them.”
    Your self-hosting post on LinkedIn, October 20
  8. Why you win
    “Developers should be able to read the code, change what they need and host it themselves.”
    Your GitHub stars post on LinkedIn, November 5
  9. When a store moves
    “Agents are changing the economics of integrations.”
    Your pricing post on LinkedIn, October 13
  10. When a store moves
    “With agents, integrations are easier to consume and used at much greater scale.”
    Your pricing post on LinkedIn, October 13
What your customers sayFrom Account Executive (Founding) posting, nango.dev/platform/mcp, nango.dev/customers
  1. NNango
    “Sell to engineering, product, AI, and executive teams.”
    Nango · Account Executive (Founding) posting
  2. NNango
    “connects AI agents to the 1,000+ systems where work happens, providing a critical connectivity layer for the AI stack.”
    Nango · Account Executive (Founding) posting
  3. NNango
    “Your users authorize once; credentials stay encrypted inside Nango. Your agent authorizes with Nango and never sees real credentials.”
    Nango · nango.dev/platform/mcp
  4. NNango
    “Hundreds of fast-growing companies use Nango to power their core integrations.”
    Nango · nango.dev/customers

Words you use

  • “integrations for agents”
  • “Managed auth”
  • “pre-approved OAuth apps”
  • “bring-your-own-cloud”
  • “10,000+ pre-built tools”
  • “the system where work happens”
  • “permissions handled”

How the list learns your calls

In the first session you react to accounts like these: keep or cut, and why, the way you’d tell a cofounder. Each reason becomes a rule you can read, the pool re-scores, and ten more show whether it learned. Keep eight of ten and the hundred is built on your rules.

  1. You cut one on the call, and say why
  2. It becomes a rule
  3. The pool re-scores
  4. Ten more test it

Which questions can only you answer?

Your posts and your site say who builds on Nango, not which companies you would never spend an evaluation on, or what has to be true before an engineering team stops building integrations itself. About 30 minutes of you reacting to real accounts answers these.

  1. 1

    Is a company that already ships an MCP server a faster call than one that has not started?

    Rows 2 and 3 already run an MCP server or lead its roadmap; rows 14 and 15 do not mention one.

  2. 2

    Does the buyer sit in engineering or in product?

    Rows 2, 8 and 11 post product-manager roles; rows 1, 4 and 5 post engineering roles.

  3. 3

    Do very large companies belong in a founding AE’s first week, or only teams inside them?

    Row 7 (OpenAI) and row 5 (Zendesk) are very large; row 15 (Lovable) is much smaller.

  4. 4

    Does a company that builds connectors for its own product still buy, or only a company that wants to stop?

    Rows 22 to 25 build integrations as their product or in-house.

What does your Account Executive (Founding)’s first morning look like?

Without

The CRM you have now. The early weeks go to learning which accounts you’d call, and why.

With · Account Executive (Founding), first morning

  • WWriterDraft written
  • AAsanaDraft written
  • LLatticeDraft written
  • BBrazeDraft written
  • ZZendeskDraft written

A hundred accounts you approved, the rules behind them and drafts to the first five, so their time goes to buyers.

From week two, your mornings too: one brief, drafts to approve, every message sent by you.

How the 10 days run

What happens in the ten working days?

November 16, 2026 to December 1, 2026. About a day of your time in total.

  1. Before by November 16

    You send the customers you’d clone and three deals that went wrong, plus 10 to 20 emails or posts you wrote. “How you sell” is drafted from your talks and posts.

    You: 20 minutes
  2. Day 1 November 16

    The playbook session: we fill the gaps and correct the draft together. Your CRM is connected.

    You: 2 hours
  3. Day 2 November 17

    Your first rules are written; a few hundred companies are scored against them.

    You: none
  4. Day 3 November 18

    You review the first 25 (talking it through is fine).

    You: 30 minutes
  5. Day 4 November 19

    Your reasons become rules; you see the re-score and judge 10 more. First touches are written in your voice to the accounts you kept, and you read ten. Touches start logging to the CRM.

    You: 30 minutes
  6. Day 5 November 20

    The hundred is built. The research tool is set up; you test it on three accounts you know.

    You: 15 minutes
  7. Day 6 November 23

    The morning run is set up; your first morning, with us.

    You: 30 minutes
  8. Day 7 November 24

    You review all hundred, and any cut is replaced. Team training, session one.

    You: 1 hour 20 minutes
  9. Day 8 November 25

    Your first morning on your own. Training session two, hands-on for each person.

    You: 1 hour plus your morning
  10. Day 9 November 30

    Your second morning on your own. Each person on your team runs the morning alone.

    You: your morning
  11. Day 10 December 1

    Your third morning on your own. A week of touches is in the CRM. Handover sign-off.

    You: 30 minutes plus your morning
Kash Badami

Who builds it?

The person in the video does the work with you, from the first session to the handover.

$100M+in deals sold in a single year
$0 to $10MARR in 12 months, for a company I built
  1. “Kash and I built ERT Credit together in 2021. He took my MVP and turned it into a SaaS that hit $10M ARR in twelve months.”

    Jordan Anderson, CEO, PayStreetgobridgehead.ai/about

  2. “Analytical in approach, technologically-knowledgeable, and earnest in conviction, Kash was able to drive pipeline in a notoriously challenging tech region.”

    JBJason Brandt, Managing Director, Sales, ePlus inc.LinkedIn recommendation, April 2020

Where does this go from here?

Three options. Each one is fine.

Not a fit

Say so in a line, and that’s the end of it.

Not now

Keep the 25 and the read on how you sell, and share them. When the role fills, the offer stands.

Talk with Kash

Ask Kash to call you, or email him. He calls to set up a 30-minute strategy session. Bring your cofounder or your sales leader.

Your new AE’s first 100 accounts, in 10 days

The first 25 are above, and they’re yours either way.

Email Kash

We build a handful of these a month, for founders hiring now.

10 days

from kickoff to your team running it

  • 100 accounts you approve, each with the reason
  • Drafts to the first five, in your voice
  • Your team runs it without us
  • Any account you cut, we replace

Nango sales playbook, in brief

Nango (YC W23) “connects AI agents to the 1,000+ systems where work happens,” and sells it to engineering, product and AI teams building products that act on their users’ apps.Account Executive (Founding) posting, nango.dev

The founding Account Executive role is Nango’s “first enterprise seller,” working directly with the founders from first conversation through technical validation, close and expansion.Account Executive (Founding) posting

Bastien Beurier says “Agents are changing the economics of integrations,” and that customers want “control over customer data and credentials,” which is why Nango offers bring-your-own-cloud.Your GitHub stars post on LinkedIn, Your self-hosting post on LinkedIn

The first 25 accounts for the new AE are companies whose own job postings show an integrations or agent platform build under way, each scored on six rules: fifteen strong fits, six in the middle and four edge cases that test the rules.

Prepared by at Bridgehead · November 9, 2026 · Every source

Questions founders ask

Can’t my AE build this when they start?

They can. But wouldn’t you rather they were selling? Reps spend 28% of their time selling, and the average new AE takes 6.2 months to ramp. This replaces the weeks they would spend building the list and learning what you already know.

28%: Salesforce, State of Sales (7,700+ sellers, 2022) · 6.2 months: Bridge Group, 2026 AE report (158 companies)

How much sooner does my new AE get to work?

From day one, because the accounts you approved and the first drafts are waiting. The average new AE takes 6.2 months to ramp, and at a $200K median OTE that is about $103K paid before they are fully productive. Only 48% of AEs hit quota.

6.2 months: Bridge Group, 2026 AE report (158 companies) · $103K: arithmetic ($200K median OTE × 6.2 months ÷ 12); Bridge Group, 2026 AE report (158 companies) · 48%: Bridge Group, 2026 AE report (158 companies)

We tried an outreach tool and it sounded like a robot. How is this different?

Nothing goes out on its own. Every account on the list is one you approved, every draft is written to one person, and you send each message yourself. It learns your voice from what you’ve written and from every edit you make.

How much of my time does it take?

About a day, spread across the ten working days: the 2-hour session on how you sell, short list reviews you can talk through, two training sessions and your first mornings. The hours your AE gets back go to selling, where reps spend just 28% of their time today.

28%: Salesforce, State of Sales (7,700+ sellers, 2022)

What happens after you leave?

It keeps learning. Each week it proposes rule changes from what your cuts, replies and silences showed, and you approve or reject each in a line.

Where does my data live?

In your own accounts: your Claude, your CRM, your files. Nothing runs on anyone else’s side, and any rule can be changed in plain English.

How is it priced?

The first engagement is one fixed price for the ten days. It depends on how many people we train and which systems we connect, so Kash quotes it on a short call. After handover, you can keep us on a retainer to keep supporting your sales process and refining it, if you choose that route.

The research behind this page 10 sources · 3 postings · 6 customers · 25 stores looked at

Your talks and posts

  1. nango.dev
  2. nango.dev/platform/mcp
  3. nango.dev/customers
  4. Your GitHub stars post on LinkedIn, November 5, 2026
  5. Your self-hosting post on LinkedIn, October 20, 2026
  6. Your pricing post on LinkedIn, October 13, 2026
  7. Your OAuth apps post on LinkedIn, October 29, 2026
  8. Your 10,000 tools post on LinkedIn, October 27, 2026
  9. Seed round record (Crustdata via treg), March 23, 2026
  10. Your 1,000+ APIs post on LinkedIn, October 16, 2026

Your open roles

  1. Account Executive (Founding), first posted November 9, 2026
  2. GTM Engineer (Founding), first posted October 30, 2026
  3. Growth & Marketing Lead (Founding), first posted September 28, 2026

Your customers

ServiceNow · Replit · Motion · XY.AI Labs · Plain · Lago (santehq.com/customers and your posts). Customer photos are from santehq.com/customers.

How the 25 were picked

25 stores found and scored on 6 rules; the 25 chosen to teach: 15 strong, 6 middle, 4 at the edges. Logos are from each store’s own site.

  • Sources: each company’s own job board (Ashby or Greenhouse API) or a job-posting record from TheirStack via treg, pulled November 9, 2026. The posting URL is on line 1 of every saved file in research/nango/accounts-raw.
  • Customer check: nango.dev/customers shows about 100 logos as images. The logo wall was rendered and read by eye on November 9, and none of the 25 appears on it. The five case studies and the two names in the posting are also not on the list.
  • Greenhouse boards give a last-updated date, not a posted date, so rows from Greenhouse (Asana, Lattice, Cresta, Attentive, Braze, Vercel, Workato, Fivetran, Glean) date to that update.
  • Where a posting does not say how a company connects to its customers’ tools, rule 2 scores low. That means the posting is silent, not that the company does not build it.