@benjaminprinter How are you tracing buyers back to the broad posts? Is that mostly what they tell you on calls, or can you see them moving from broad posts into the technical stuff?
@shannholmberg I used 40 curated emails in a playbook that the agent read before writing outbound. Worked really well. Could've given it all 10,000 emails I'd sent but I doubt it would've been much better.
SF doomers talk about whole industries getting replaced with AI, but i fully expect most ai native companies to just be existing companies that build the right ai-native culture, teams, software that run their businesses. bit by bit, ghost in the shell style.
A lot of what Iโm seeing work here is pretty familiar to engineers. It's just good software development. Wish there was a vibe coding in production book or something.
Been working w/ Retool's team, seen 100+ internal tools built by non-engineers.
Hereโs what sets the top 10% of builders apart (actually used, gets deployed company-wide, writes to important systems).
6/ They don't test in production.
Test records and emails to themselves first, including clicking twice, leaving fields empty, and disconnecting integrations. Breaking an important system early can kill the project.
Ampersand is hiring! I recently took some time to reflect on what I appreciate about our existing team members (or Ampersonians as I like to call them), and came up with our 6 cultural values:
- ๐๐ฟ๐ฎ๐ณ๐. We care about the details and the quality of our work.
- ๐๐๐๐๐ผ๐บ๐ฒ๐ฟ ๐ฒ๐บ๐ฝ๐ฎ๐๐ต๐. We are our customersโ extended team.
- ๐ข๐๐ป๐ฒ๐ฟ๐๐ต๐ถ๐ฝ. We take full end-to-end responsibility for our work.
- ๐ฉ๐ฒ๐น๐ผ๐ฐ๐ถ๐๐. We move fast without cutting corners.
- ๐๐ฑ๐ฎ๐ฝ๐๐ฎ๐ฏ๐ถ๐น๐ถ๐๐. We thrive in ambiguity and are always learning.
- ๐๐๐บ๐ถ๐น๐ถ๐๐. We are low ego, and are open to feedback.
I've been a part of companies where values were more for marketing than anything else, but these are ๐น๐ถ๐๐ฒ๐ฑ values exemplified by everyone that's on this journey with us. If you or someone you know resonate with these values, check out our open roles at https://t.co/Th2wNnzSJ9. We are hiring across eng + GTM (including our first Eng Manager and Sales Engineer!)
@laurenzlong@BessemerVP every time i use a new tool, i open up settings to get an API key for my claude and see if they have a salesforce/hubspot integration. I am disappointed 9/10 times, except when i use @11x_official or @withdefault (they use ampersand btw). They have great integrations :)
We raised $15M from @BessemerVP to solve integrations for enterprise agents.
The launch film we released yesterday detailed the hairy problem of building integrations with systems of record like CRMs and ERPs.
Today, I'm sharing a video I recorded about how Ampersand solves that problem.
MCP is not an integration strategy. We raised $15M from Bessemer to prove it.
If you are building an enterprise agent that needs to connect with your customersโ critical systems, simply integrating with the Salesforce MCP isnโt going to cut it.
1. MCP isnโt going to help you backfill millions of transactions from your customerโs NetSuite, or millions of accounts from your customerโs HubSpot. For that, you need robust sync infrastructure.
2. Enterprise customers do not use tools out-of-the-box. Their CRMs, ERPs, and all the legacy systems of record have custom objects, custom fields, and bespoke workflows. MCP will not help you navigate that complexity.
3. MCP is built for real-time querying. Some work is better done async, especially when you are dealing with strict rate limits that many SaaS products have. You need async workloads and smart retry logic.
Ampersand is the integration infrastructure for deeply connecting with your customersโ systems of record. Because the SaaSpocalypse didnโt happen. The world still depends on CRMs, ERPs, HRISs, and ITSMs.
@ayanb@WithAmpersand People need to stop building their homegrown SoRs and just integrate with them better. reminds me of @jerryjliu0
https://t.co/c7BmBOf86M
not sure i fully get this.
- i want my agents to use slack
- i don't want my agents to build a new slack
- i don't want to use slack's agent
i think every piece of software/system of record needs to become agent-native and not just human-native, which will benefit them because agent consumption will be exponentially higher than humans. but that doesn't necessarily mean turning into agents themselves
@ayanb@WithAmpersand Ayan don't think you're wrong... we've had massive challenges at G2 integrating our acquisition of Gartner Digital Markets having to bring together over 300 business systems including migrating CRM, AWS orgs, and financial systems and still took months of hard human labor ๐๐๐