Looply (@looplyhqcom) header
Looply (@looplyhqcom) profile picture

AI agents that turn buying signals into booked meetings. Find the right buyers. Start better conversations. → https://xitter.gq/t.co/Al1G9YejIi

San Francisco, CA
Joined October 2026
Flai just raised $27M, and its revenue grew 20x in a year. At its 2025 seed it was 3 people. Now it's about 40. What got them there, per TechCrunch : → Referrals : dealers recommended Flai to other dealers. → Speed : the software can be live in a dealership 10 days after signing. → Focus : one market, car dealers. Now 10+ of the top 50 US dealer groups. Half of Flai's revenue now comes from new customers. The rest comes from the ones they already have. What I'm taking from it for Looply : → Make the first customers want to tell others. → Cut the time between yes and the first useful thing. @looplyhqcom starts from your website and suggests your ideal customer and the signals to watch. → Stay in one market until it's won. Ours is B2B outbound : founders, SDRs, sales teams and agencies. The CEO says he knows how hard the first customer was. That part never makes the headline.
6
3
1
15
652
LinkedIn messages sent to a CRM export vs. LinkedIn messages sent to a new hire:
1
5
11
370
Looply retweeted
3 signs a cold email will be ignored: → no reason it's you → no reason it's now → a calendar link in line 2
4
4
9
191
I've been stuck at €0 MRR since July. So I built this for fun. Building it makes me happier than staying at zero. @ShippedNews : breaking news for builders on X shippednews.com/?utm_source=… - Big tech racing to build AI assistants - Cloud deals between giants - Founders deciding what stays free Every story names its source and shows it. It's free.
7
4
4
11
1,132
Allo studied 72,339 cold calls placed through its power dialer, July to September 2026. What it found:
3
4
8
186
Looply retweeted
Encore AI raised $30M to turn sales calls into playbooks for AI agents 🤯 40+ enterprise customers, ARR up 5x since its seed (TechCrunch, July 2026)
2
4
7
278
How to write a business brief Claude Opus 5.5 can actually score against : "Companies that might need us" gives it nothing to check. "B2B SaaS, 20 to 200 people, in the US, hiring for RevOps in the last 30 days, never current customers" gives it three things it can check on every line. Fill it in once. Paste it into the first prompt. 1/ What you sell. One concrete product or service. 2/ Who it's for. Role, type of company, size or region limits. 3/ The problem, said the way a customer would say it. 4/ The signals that make you relevant. Hiring for X, a new head of Y. 5/ How recent. For example the last 30 days. 6/ Don't contact. Current customers first, then competitors, opt-outs, wrong roles. 7/ Proof you can share. Leave it blank if you have none. 8/ The first useful thing you can offer. A checklist, a teardown, a sample. Not sure who it's for or which signals to watch ? Paste your website into @looplyhqcom and it suggests your ideal customer and the signals to watch. Then add two rules to the prompt : "Apply every DON'T CONTACT rule, even when the score is high." "If something is missing, say so. Don't fill the gap." A blank proof line is fine. An invented one ends up in an email. Keep last week's brief next to this week's and change one line at a time.
10
5
14
506
6sense surveyed nearly 4,000 B2B buyers for its 2025 Buyer Experience Report. Here's what they found :
3
3
11
365
Looply retweeted
Looply writes the first email from the signal You approve each one, or let the campaign run
3
4
7
112
LinkedIn messages sent to a lead list vs. LinkedIn messages sent to a like:
3
5
9
445
Looply retweeted
Every outbound tool demo: "and here's the dashboard" 😅 Nobody signed up to look at a dashboard
2
4
8
241
Cold emails sent to a job title vs. cold emails sent to a new job :
11
13
224
49,433
Hi, I’m Benjamin. 28 years old, from Paris, France, and in January I launched @looplyhqcom as founder. The first question I wanted answered : how long does it really take to go from a first line of code to someone paying for it ? The building wasn’t the slow part. Everything around it was. The dates, as they happened : → January 7 : I stopped making iOS apps like MeetBase and PhotoBase. Apple’s payments reached me two months behind, and that was too much. I wanted Stripe, so I started a B2B SaaS. → March 30 : almost 3 months in, I was still choosing the name. Leadloop was taken, and comparing domains ate far too many hours before I settled on Looply. → End of May : our first paying customers, about €400 MRR. Small numbers, but people were actually paying. → End of July : back to zero. → September 7 and 8 : our first free guides, TEAM and SIGNAL, copy/paste prompts in Notion with a worked example. → October 21 : I hit my Claude session limit at 21:21 and had to wait until 22:10 to keep building. Read together, the dates say it : the product kept moving, and the hard part was getting it in front of people. With AI, it’s easier than ever to add another feature instead of doing the uncomfortable work of finding customers. Building from San Francisco doesn’t change that. Still going every week : our SEO, our own cold emails sent through Looply, our X and LinkedIn posts with the replies under them, and a new guide with each model launch since October 5. Still $0 on ads. My biggest takeaway as a founder : a paying customer tells you something that a thousand impressions can’t.
26
7
28
868
Cold emails sent to a database vs. cold emails sent to a funding round:
2
4
11
256
Looply retweeted
5 signals Looply watches 👀 → posts about your keywords, and who engages with them → who engages with a competitor's page → who engages with an influencer you pick → job changes into a role you sell to → companies that just raised
2
4
7
94
Looply retweeted
"Just bumping this to the top of your inbox" It was already at the top. That's why I archived it 🫠
2
4
4
65
Sales.co studied 2M+ cold emails and 61,770 classified replies from its own campaigns. Who replies, and who doesn't:
1
4
6
111
Looply retweeted
Inside Looply 🤖 Agents watching for signals, and one drafting replies for a person to check
2
4
8
136
Expandi studied 13.2 million LinkedIn connection requests and 6.7 million messages. What they found:
2
4
6
243
Looply retweeted
1 in 2 people we reached replied 🤯 267 reached, 133 replies. One LinkedIn campaign we ran ourselves, from buying signals
3
4
5
163