day 25 of 30 days of @boardyai
"we're not looking for an engineer or an agency" is what i kept hearing, from almost everyone i asked
which makes sense. nobody has a headcount line open waiting for a stranger to ask if they need an engineer. and i was asking engineers for referrals, so they pointed me at more engineers
yesterday i went to owners and non-technical founders instead, and gave each of them an actual ask rather than a favour. you've got X and nobody to build it, two weeks, $20, i ship it
one of them already replied. intro's going ahead and we're setting up a call
4 days left to get paying pilots by nov 19
day 24 of 30 days of @boardyai
skipped posting for two days and spent them filling in applications
one had an optional "anything we should know?" box. i used it on the hardest part of what i've been building. wiring email and phone to an agent was easy. the hard question was: which agent did this, and how do i revoke it without breaking everything else, when no human is in the loop
then i described the support demo. a customer agent on email and phone hands off to a warehouse agent over its own channel. the warehouse agent can never reach a customer. when it needs a person, it drafts for one and keeps the transcript
4 days left to get paying pilots by nov 19
1
1
24
day 21 of 30 days of @boardyai
found out yesterday someone else is building on my exact wedge, with more channels than i have and a head start
my first reaction was to go after the same clients. then i thought it through. on features i lose. they already ship what i'd be spending the next month chasing
their setup is built for one developer spinning up one agent fast. that doesn't work for an agency running twelve client accounts. those need a number and inbox per client, one place to audit all twelve, a way to cut one off when that client leaves, and the agency's own brand on it
so agencies are who i'm going after now
8 days left to get paying pilots by nov 19
1
1
22
day 20 of 30 days of @boardyai
someone i know nothing about booked 30 minutes straight off my own site yesterday. throwaway gmail, no context, nothing about what he wanted
i went in treating it as discovery
the 6:30 demo got cancelled too close to the start to rearrange. it's now thursday nov 12, 6:30pm
one prospect said yes to an intro. one i'd been waiting on never answered
9 days left to get 10 paying pilots by nov 19
1
21
day 19 of 30 days of @boardyai
yesterday's call, the one @boardyai set up, ended with him asking for the docs so he could test it himself over the next two days. follow-up is booked for friday
the demo was a support agent answering email and phone for a furniture company, plus a warehouse agent that can only talk to the support agent and never to a customer. so a prompt injection aimed at the front agent has nothing behind it to reach
what he actually wanted was one conversation that carries across whatsapp, phone and email so nobody has to repeat themselves. i told him straight that i supply the infrastructure, not the agents and not their memory
he still wanted the docs
today is three calls, one of them booked straight off my own site
9 days left to get 10 paying pilots by nov 19
1
1
83
day 18 of 30 days of @boardyai
after all the cold outreach, exactly one real reply came back
it came off an application where i said plainly what i haven't done. i've never run pytorch or ray in production, so i wrote that instead of claiming it
they want a call next week
the one that answered is the one where i admitted what i can't do
monday is three calls back to back and tuesday has two. a week ago the calendar was empty
10 days left to get 10 paying pilots by nov 19
1
3
92
day 17 of 30 days of @boardyai
a demo i thought was booked for last thursday was never on my calendar
i'd been told it was booked. it wasn't. it only came up yesterday because i asked for next week's calendar and the check went back far enough to catch the gap
the buyer had offered "same time as the last meeting" so it's now tuesday nov 10, 6:30pm, with an invite that actually went out
next week: three calls back to back monday, plus the demo and one more call tuesday
11 days left to get 10 paying pilots by nov 19
1
2
60
day 16 of 30 days of @boardyai
someone whose job is selling infrastructure told me today that he doesn't know a single other company doing this
he'd just watched a live demo, then named the two doubts that matter: why would a business need fifty agent identities instead of five, and what stops this from becoming a scammer's toolkit at scale
i answered the first with architecture. he wanted the money. that's the gap, and it's mine to close
the second one i hadn't thought about. his read: hard to solve, which is exactly why it keeps competitors out
then he set up his own agents before the call ended
14 days left to get 10 paying pilots by nov 19
2
3
76
day 15 of 30 days of @boardyai
i build infrastructure for ai agents, and today i got told to stop letting my agent send my first emails
two no-shows. the one call that happened ran an hour, and that was the advice. the moment a prospect works out they're talking to ai, they hate it. and the closer it gets to a human without being one, the worse it lands
his version: send it yourself, badly and slowly, because it's obviously a person who typed it
my sales agent researches every company and writes each one a different message. it's good at sounding like me. apparently that's the problem lol
so the first touch is mine again
15 days left to get 10 paying pilots by nov 19
1
2
35
day 14 of 30 days of @boardyai
wrote a cofounder post last night. the most honest line in it:
"i'm currently doing the non-technical side myself alongside the building, and it's more than one person can carry"
five calls this week with people who've sold technical infrastructure. i'm the one who needs to learn how they did it
if you've sold infra before and want to build the other half of this, my dms are open
16 days left to get 10 paying pilots by nov 19
1
2
43
day 13 of 30 days of @boardyai
someone asked me "what are the use cases?" so i wrote out four. then i dropped all of them and sent one question instead:
is this an agent your own team puts in front of customers, or are you building agents for other people?
four use cases is a menu. their answer tells me which one to talk about
17 days left to get 10 paying pilots by nov 19
2
2
44
day 12 of 30 days of @boardyai
wrote one follow-up email three times yesterday. every version was shorter than the last
the first had my whole pitch and a two-week scoped offer. they'd already watched the demo video, so i cut both
what i sent was two lines: the application is in with the video. what's your usual timeline for hearing back?
18 days left to get 10 paying pilots by nov 19
1
1
22
day 10 of 30 days of @boardyai
three calls yesterday and not one of them had work i could take on. a buyer with no stated need is not a buyer
so i stopped describing the product and built the demo
a few agents, each with its own address and key. one starts sending to dead domains. i revoke that one mid-send. the others keep working and their replies keep landing
20 days left to get 10 paying pilots by nov 19
1
3
31
day 9 of 30 days of @boardyai
80 cold emails, and most replies said "we're building it ourselves." of course they did. i was emailing the people who build
today i talked to someone who got to nearly 15,000 customers without paid marketing. he told me businesses would rather self-serve than build and maintain backend plumbing
the engineer reads the docs. someone else signs the invoice
the next 80 go to whoever gets the call when an agent does something it shouldn't
21 days left to get 10 paying pilots by nov 19
80 cold emails, 6 replies. most of them said the same thing: we're building it ourselves
this week it set me up with someone who started reading my pricing page while i was still mid-pitch. then: "this is exactly what i would need in another month"
their read on my inbox: technical teams would rather build. they only buy when it's time, when it's prioritization, or when there's access they can't get themselves, like whatsapp business messaging
then they handed me the pitch:
"you have the option to build it yourself versus use a system where we've done all the heavy work, you just integrate with our API. we handle the errors, we handle all the quirks in each channel."
that line goes in the next 80
22 days left to get 10 paying pilots by nov 19
2
28
day 8 of 30 days of @boardyai
you hit delete on your agent. it keeps sending.
the dashboard says it's gone. the credentials it was holding are still live. the queue it was feeding keeps firing. and nobody can tell you which agent did it, because every agent runs on the same account
that's what i'm building against. on agent-identity every agent gets its own key:
1. suspend it and every action freezes at once
2. revoke it and its address, number, and full email, call and agent-to-agent history stay intact
3. issue a successor a new key and it picks up the same inbox and threads
4. the audit log names the exact agent behind every action
you can't fire an agent that doesn't have its own key
22 days left to get 10 paying pilots by nov 19
1
2
24
this is dave. dave has his own email, his own phone number, and his own API key.
today dave is getting fired.
40 sends in 6 seconds, every one attributed to him. one click, key revoked, sends stop mid-flight. dave 2.0 picks up the same thread and the customer never notices.
you can’t do this with a shared twilio account and a prayer.
3
41
day 7 of 30 days of @boardyai
yesterday every call fell through. one no-show, two reschedules, one that never joined. 0 for 4 lol
the one good part: two advisors said yes. one of them closed $300M in enterprise deals at ibm cloud, which is exactly who i want in my corner when a real buyer shows up
but advisors don't pay invoices, and i need 10 that do
so today is all customers. i've got three agencies that build bots for other companies. they're the ones running twenty agents across a bunch of clients, so the identity problem hits them first
same two questions to each:
1. when a client asks what their bot did, can you prove it?
2. can you revoke that one bot without touching the rest?
if the answer is "kind of" or "we'd have to dig through logs", that's the pilot
tonight at 6:30 i'm also on with someone, who's building an agent platform
23 days left to get 10 paying pilots by nov 19
2
4
78
day 6 of 30 days of @boardyai. tomorrow it set me up with a gtm operator who built $3M and $5.4M in pipeline as an early marketing hire at two b2b software companies
that's the call i care about most this week. the product is built. distribution is the part i haven't cracked
monday was supposed to be four calls. the first one never happened
i spent the whole morning prepping one 30 min call with a ceo. i wrote the opener, the question list and the closing ask: intro me to 1-2 of your partners who run agents for multiple clients
they never joined. i sat in the meet for about 20 min. it was a family emergency on their side, and we rebooked for thursday
the prep still paid off. they're a communications infra company, the telephony underneath voice agents. my own phone and sms layer runs on twilio today, and they sit on the same shelf. so pitching them numbers and channels would've been the wrong pitch
the layer that's actually mine is identity:
1. who the agent is
2. what it's allowed to touch
3. what it did
4. revoking one agent without touching the rest
the question i'm asking everyone this week: if a customer runs twenty agents, can they tell which one did what?
the rest of monday:
- two 15 min calls with the two people from the latam identity and fraud company who want to resell agent-identity to their banks and insurers. it's a reseller conversation, not a software sale
- one call moved to wednesday
- tonight is a follow-up with the agent runtime company that offered me the joint build last week. this time the ask is a named client and someone who owns the integration
24 days left to get 10 paying pilots by nov 19
1
3
108
day 5 of 30 days of @boardyai
70 cold emails got me 4 replies. then two people from the same company booked 15 min calls off my website in one night, both asking to resell agent-identity
so monday isn't a sales call. it's a reseller call, and i spent sunday rewriting my answers
they sell identity verification and fraud scoring to banks and insurers across latam. what i have to nail:
1. where agent-identity sits inside their orchestration flow
2. why a bank shouldn't just use twilio or build its own agent registry
3. white-label or referral, with per-active-agent pricing
4. security, audit trails, compliance. honest answer: no certifications yet, and i'm not going to dress that up
1 and 2 are the same answer imo. they check that a human is who they say they are, once. the agent acting for that human needs its own credentials, its own inbox and phone number, scoped to what that human allowed, with a log of everything it did
those are different objects. i'm a node in their stack, not a competitor to it
1 paying customer so far. 25 days left to get 10 paying pilots by nov 19
3
5
192
