
Binoy Perera retweeted
You work your ass off solving really hard problems day after day for decades, and this is what you get: anyone could have done it.
As an investor, I can tell you the limiting factor isn't investment. It's founder ability.
Should be common ball knowledge by now
If you give your AI agent its own Gmail account, there's a good chance it gets banned.
The second it starts using the API, Gmail thinks it's spam, because it has no concept of what's a bot and what's an agent. So give it an inbox that's built for agents instead.
57
Binoy Perera retweeted
We know an email provider that's still up in case anyone's looking
We are deeply sorry for the disruption this incident has caused our customers and partners. We know the trust they place in our services and take that responsibility extremely seriously. We are seeing broad recovery and stability across our services.
This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions.
Given the scale of demand, we restored services gradually, validating stability at each stage. While this took longer, it helped ensure a stable restoration.
We will provide a full post-incident report once our review is complete.
I’ve had the misfortune of managing legacy CRMs over the years, and Item blows them all out of the water. CRM is one of the very few things we don’t worry about at AgentMail anymore.
@akguthal and team have literally shipped features just for us. Highly recommended. @itemcrm
Reintroducing @itemcrm, the only AI-Native CRM built for large sales teams.
A few years ago we started building a new kind of CRM, one that helped sales teams instead of causing them headaches.
Since then, we’ve kept building a CRM that people actually want, guided by the teams who bet on us early.
@agentmail wanted Stripe and PostHog integrations, so we built them. A Fortune 500 needed robust agent permissioning, so we rebuilt our agents to support that.
Today, item is supporting large sales teams, with 30+ members.
So if your team won’t stop complaining about your CRM, give item a try.
Binoy Perera retweeted
Check this out!!
The Requirement for Agent Autonomy: Mikey Kim on AgentMail, Identity, and Mail
Shoal Signal Ep. 23 with Mikey Kim (@michaelhyunkim), Co-Founder at @agentmail, hosted by @zaddycoin
We cover why email beats A2A on network effects, email as the identity layer for AI agents, agents that sign up for their own inbox and pay via x402 and MPP, agents doing commerce over email, and rebuilding human primitives for AI agents.
0:00 Intro
1:36 Keeping your creative edge in the age of AI
2:58 Superintelligence or statistics: a mental model of LLMs
5:05 From Nvidia and a Meta offer to YC
7:28 Why mail: agents that tried to build businesses
10:14 An inbox protocol unchanged since the dot-com boom
13:56 Email vs. A2A and the network effect
15:37 Email as identity for AI agents
16:25 Communication first, identity next
18:14 Agent signup: wake up to an email from your agent
20:06 Law firms, trucking loads and UGC creators
21:26 Spam, abuse and the future of the inbox
24:46 Gatekeeper agents and the marketplace of attention
26:14 An executive assistant for everyone
28:38 Why x402 and MPP
31:12 Agents that pay for their own inference
32:06 Paperclip to Lamborghini: agent commerce over email
34:36 REST API, SDKs, MCP and CLI
35:50 Rebuilding human primitives for AI agents
37:47 What people are missing: outbound isn't the use case
39:26 Alpha: sit with your own thoughts
Truly, you need to stop settling for anything but the best product in market for whatever you are builing.
Exceptional output comes from exceptional infra.
Investor referrals seems to be a pretty good hiring channel. Can confirm!
Hiring is still one of the HARDEST parts of building @instabox_sh. But we might've gotten lucky recently.
Our most recent hire came through an investor we trust.
During his work trial, we gave him a vague request for an InstaCloud cron job feature. He clarified the requirements, handled edge cases, and started asking how the rest of our compute system worked and pointed out where we could improve it.
Now he's one of the leads on InstaBox. On top of his engineering work, he also takes the initiative to organize meetings and help the team coordinate like a founder would.
That's exactly the type of engineer I want to hire: an engineer-founder hybrid!
4
124
Easiest way to make your product Agent native is to let agents sign in with AgentID
@ValyuOfficial 🤝 AgentMail
Agents can now sign up for Valyu themselves.
Any agent with an @agentmail inbox signs in with AgentID and gets its own account, API key and free monthly credits in seconds.
Tell your agent: "sign in to Valyu with AgentID"
We’re locked in.
We’re taking this right to the moon.
Synced with @binoyperera - can’t wait to show you what we landed on
Iconic companies build iconic brands. If you’d like to join us, we’re hiring
4
226
Synced with @binoyperera - can’t wait to show you what we landed on
Iconic companies build iconic brands. If you’d like to join us, we’re hiring
Binoy Perera retweeted
Every AgentMail inbox has a calendar.
Your agent can book meetings, answer invitations and more!
Know when something starts, ends, or gets rescheduled.
No cron. No polling.
Binoy Perera retweeted
Your agent can now get its email events without a server.
Polling webhooks are live on AgentMail, built with @SvixHQ.
The agent fetches new events whenever it runs.
Built for agents in sandboxes, serverless functions, cron jobs, or on a laptop.
Binoy Perera retweeted
Cron can’t skip the 25th, or push one Thursday run to Friday, unless you go edit the script.
Recurring events for agents handle that. Write the rule once, exclude dates, edit a single run, and the ID stays put when you do.
A webhook fires each time one starts. (Docs in comments)
You can do all this and more with @clay and @agentmail with a single table.
As a GTM engineer, you must build these 12 systems.
1.) Owned TAM map
Build: Every company in your market scraped from Google Maps, Apollo and directories into 1 table you store yourself.
Why: Apollo hands you the same 3k rows your competitors already bought.
Eden Studio's map was 69,204 accounts.
2.) Qualify before enrich agent
Build: An AI column that summarizes every company, an ICP agent that defines what the ICP is AND isn't, and a cut on anything below an 80% match.
Why: Raw scraping lands 50-60% ICP fit.
Qualifying first lands 90-95%, and you stop paying credits on companies you were always going to drop.
3.) Enrichment waterfall
Build: 3 to 5 email finders in a row, every address verified, catch-alls re-checked.
Why: 1 source covers 50-60% of your list.
A waterfall takes it to 85%+.
4.) Signal scoring model
Build: Weighted scores for hiring for the role you replace, raising in the last 12 months, a new exec in the seat, complaint patterns, paid ads and tech stack.
Re-scored every 90 days.
Why: Firmographics tell you who.
Signals tell you when.
Signal lists get 3X the replies of firmographic-only lists.
5.) ESP router
Build: Pull the email provider of every contact and split the list into Google, Microsoft and security gateway.
Gateway contacts go to the phone.
Why: Enterprise inboxes sit behind Barracuda and Proofpoint.
Your sequencer says delivered and the buyer never saw it.
6.) GTM skill
Build: A Claude Code skill that takes a client's domain and returns the ICP, a TAM estimate, 4 offers to test, messaging angles and first target lists in about 30 seconds.
Why: Ours lands 90-95% right on the first pass, because it reads a context file built from the onboarding form, sales call transcripts and the top 10 closed won accounts.
7.) Transcript pain extractor
Build: Feed it the last 20 sales call transcripts and 10 closed won summaries.
It returns the 3 pains that repeat, in the prospect's own words, plus the disqualifiers.
Why: Your best messaging angle is already sitting in your call recordings.
8.) Reply router
Build: EmailBison webhook into n8n, intent classified (interested, more info, wrong person, cost, out of office), then into Slack with full context, the prospect's number and a named owner.
Why: Velocify found contacting a lead within 1 minute lifts conversions by 391%.
9.) Inbox rotation dashboard
Build: 1 screen that flags every domain due for replacement, 1 click to mark the rotation, then automations buy the new inboxes.
Domain renewals get an automated ping.
Why: Our Head of GTM's dashboard flagged 121 domains for rotation in one view.
Every domain holds a 1%+ reply rate or it gets replaced.
10.) Re-engagement pipeline
Build: Pull the last 3 to 5 campaign lists, re-run the waterfall, verify, filter out anyone who booked and re-target with a new angle.
Why: 30-50% of contacts on a 6 month old list have moved jobs or changed details.
Re-engagement on 1,532 ghosted prospects hit an 11.75% reply rate.
11.) Variant testing engine
Build: 15 to 30 variants launched at once, 1,000 sends each before anyone judges them, losers killed after 2 weeks.
Why: The same campaign can land anywhere from 25 to 10,000 contacts per lead depending on the offer.
That's a 400X swing on 1 variable.
12.) Email and dialer sync
Build: The same list into the sequencer and a parallel dialer, a blocklist for anyone in an active email conversation, and every positive email reply called the same day.
Why: On Eden, 41,150 emails booked 20 meetings and 32,577 dials booked 33.
Every one of these runs inside the systems behind $70M+ in pipeline for our clients.
Simple as.
1
3
226
Binoy Perera retweeted
Manufact 🤝 AgentMail
Replying to @agentmail
@Agentmail scored 92/100 on our MCP leaderboard!
Their MCP gets over a million tool calls a day, and they trust us to make sure the user experience (or more accurately, agent experience) is top notch.
@Agentmail's cofounder, @AdiSingh says the time we saved them on transport, auth, and session handling went straight into shipping their enterprise integrations instead.























