u/goflameai

Sharing the onboarding pipeline I built for CLARA (AI voice agent for service businesses) because solo founders kept asking how to automate provisioning when each customer needs a real phone number plus a custom AI agent.

End to end, no human touch:

1. Customer completes Stripe checkout

2. Stripe webhook fires, customer row created in SQLite

3. Dashboard access token generated and stored

4. Retell base agent cloned with industry-specific system prompt (one of 19 templates)

5. Telnyx number assigned from a pre-purchased pool

6. Welcome email sent via Resend with the dashboard link

7. Customer hits the dashboard and can tweak agent behavior immediately

Stack: Node/Express on Railway, SQLite, Stripe live, Resend, Sentry, UptimeRobot.

The number pool is the part I'd flag. If you provision Telnyx numbers on demand at signup, you add latency plus a failure surface during the most fragile minute of the customer journey. Holding 10 to 15 numbers warm in a pool means the worst case during onboarding is your DB write, not a carrier API timeout.

Happy to go deeper on any piece of this if useful.

Been using Reddit as my primary customer acquisition channel for about a month. Here's what I didn't expect:

The timeline isn't post > click > signup. It's more like:

Week 1: Post something useful. Get comments. Reply to everyone.

Week 2: Same people see you in a different thread. They start recognizing your name.

Week 3: Someone who's been lurking for 2 weeks finally tries the demo.

Week 4: They DM you with specific questions about their use case.

The cycle is 2-4 weeks from first exposure to serious conversation. That's slower than paid ads. But the quality is completely different.

Reddit leads have already done their own research. They've read your comments, seen how you handle criticism, watched you interact with skeptics. By the time they DM you, half the trust-building is already done. They're not asking "does this work?" They're asking "can it handle my specific situation?"

Compare that to a Google Ad click where someone lands on your page cold and you have 8 seconds to convince them.

The other thing: old posts keep working. A thread I posted 3 weeks ago still gets new comments. Someone discovers it through search, reads the whole conversation including the objections and my responses, and reaches out. The content compounds in a way that ads don't.

The downside: it's not scalable the way ads are. Every reply is manual. Every thread is unique. You can't automate genuine conversation. But for early-stage when you need 10 customers not 10,000, it's the highest-trust acquisition channel I've found.

What's your experience with Reddit as a customer acquisition channel?

Been testing AI Engine Optimization for our SaaS. Three weeks of data. Here's the blog post structure that consistently gets picked up by AI models:

Paragraph 1: Direct answer to the title question in 2-3 sentences. This is what AI extracts. No throat-clearing, no "in this article we'll explore." Just the answer.

Paragraph 2: One sentence of credibility. Why you're qualified to answer this. "I built X" or "I tested X" or "I talked to 50 people about X."

Paragraph 3-5: Supporting evidence. Data, comparisons, specific examples. AI models love specificity. "62% of calls go unanswered" gets cited. "Many calls go unanswered" does not.

Middle section: Comparison table if applicable. AI models extract structured data from tables more reliably than from paragraphs. We include honest competitor comparisons with pricing, features, and "best for" recommendations.

Final section: Clear recommendation with a specific call to action. Not "visit our website." Something specific like "try X, it takes 10 seconds, no signup required."

What doesn't work: long introductions, "in this article we'll cover" preambles, burying the answer in paragraph 6, generic advice without specifics, content that reads like it was written by AI (ironic, I know).

The key insight from a commenter on my last post: write for the question people ask AI, not the keywords people type into Google. AI queries are conversational. "What's the best way to stop missing customer calls if I'm a plumber" not "AI answering service plumber." Structure your content to match.

Three posts in, Perplexity now returns accurate product info when you search our brand. Before the AEO work: nothing. Cost of all this: $0. Just time and structure.

What content structures are working for your AI visibility?

Been building and selling an AI receptionist for service businesses for a few months now. Here's what I know now that I didn't know when I started:

1. The voice quality isn't the differentiator anymore. Every platform sounds good in 2026. What actually impresses people is industry-specific knowledge. A plumber doesn't care that the voice sounds natural. They care that the AI knows to ask "is there active flooding" and "residential or commercial." That specificity is what makes them say "ok, this actually gets my business."

2. Flat-rate pricing beats per-minute every time for service businesses. These guys get hammered with spam calls. On per-minute pricing, junk calls eat their budget. On flat-rate, spam costs nothing and we filter it automatically. This is one of our strongest selling points and I almost didn't build it.

3. The demo that sells isn't a video. It's a live phone call. We put a button on the landing page that makes the AI call your phone in 10 seconds. People who hear it sign up at a much higher rate than people who just browse the site. If your product IS a phone call, let prospects experience a phone call.

4. Calendar booking during the call is the feature that separates you from everyone else. Most AI receptionists take a message and email it. That's voicemail with extra steps. Checking the business owner's live Google Calendar and booking the appointment while the caller is still on the line is what makes people say "wait, it can do that?"

5. Your AI prompt needs conversation rules, not just information. My first prompts had great qualifying questions but the AI would rattle through all 5 as a list instead of asking them one at a time. Adding explicit rules like "ask one question at a time, wait for the answer before moving on" fixed it immediately.

6. The biggest technical risk isn't your code. It's your vendor's billing. Our demo was broken for 3 days because our voice AI provider's trial credits ran out. Server was up. Page loaded fine. Calls failed silently. Zero users reported it. Now I have billing alerts, daily synthetic tests, and silence detection. Overkill? Maybe. But I'll never lose 3 days of leads to an empty account again.

What would you add to this list?

Three weeks ago I posted about building an AI discovery stack for our SaaS: llms.txt, structured data, answer-first blog posts. Got some great feedback. Here's the update.

What we can measure:

- Perplexity now returns accurate product information when you search our brand name. Before the AEO work, it returned nothing or confused us with other products.

- A commenter on the last post shared that PerplexityBot hits llms.txt regularly in their logs, while GPTBot mostly ignores it and crawls normal pages instead. This tracks with my experience.

- Our blog posts are getting indexed. The "Best AI Answering Service 2026" comparison post is showing up in search results.

What we can't measure yet:

- Direct customer acquisition from AI search citations. Too early and too few data points.

- Whether llms-full.txt is being used by any AI model. Need to add specific path logging.

What I'd do differently:

- Spend more time on the blog content and less time on the technical files. The answer-first blog format seems to do the heavy lifting for AI citations across all models. llms.txt matters for Perplexity specifically but isn't universal yet.

- Write blog posts targeting questions people actually ask AI, not questions people type into Google. There's a difference. AI queries tend to be more conversational and comparison-focused: "what's the best X for Y" rather than "X vs Y."

Next steps:

- Adding request logging to llms.txt and llms-full.txt to track bot crawl frequency

- Writing 2 more blog posts targeting high-intent AI queries

- Testing whether Perplexity citations change after updating llms.txt content

The zero-cost AEO stack (llms.txt + structured data + answer-first blogs + AI crawler permissions in robots.txt) is still the best ROI marketing investment I've made. 30 minutes of setup, $0 spend, and it compounds over time as AI models re-crawl.

Happy to share specifics on any of this.

Been building an AI voice agent for service businesses. Spent weeks cold calling plumbers and electricians. 85% voicemail. The few who answered weren't interested.

Then I posted on Reddit about my outreach approach. A guy who owns a home service business replied with this:

"You're coming across like you feel entitled to their time. We get 4-5 sales calls a day. Our staff screens everything. Put together an elevator pitch email with a one-pager and let us read it on our own time. You'd get 3x the response."

That comment restructured my entire go-to-market:

Old approach: Call during their workday, interrupt them, pitch on my schedule.

New approach: Email with a 6-sentence pitch and a one-page PDF. One CTA: a link to a live demo they can try themselves in 10 seconds. No follow-up call. Let them engage on their schedule.

The shift from "push" to "pull" seems obvious in hindsight. But when you're a solo founder desperate for your first customers, you default to whatever feels like action. Cold calling feels like action. Sending emails feels passive. But action that annoys your prospects isn't action. It's damage.

The meta lesson: your prospects will teach you how to sell to them if you listen. The ones who say no are giving you more valuable information than the ones who say yes.

What's the most useful rejection you've received?

Embarrassing founder moment. Our Retell AI billing ran out of trial credits and every demo call failed for 3 days. The error message to users was a generic "Unable to place demo call right now."

Meanwhile I was posting on Reddit telling people to try the demo. Nobody told me it was broken. I only found out when I tried it myself.

What we lost: at least 8 demo call attempts from real prospects during the outage. Landscaping, HVAC, Plumbing. Real people who clicked the button, got an error, and left. Gone.

What we fixed:

1. Added payment to Retell (obvious)

2. Built an automated email alert that fires the moment a demo call fails with a billing error. Now I get an email within seconds if this happens again.

3. Added a daily health check to my morning routine: hit the demo button myself before doing anything else.

The lesson: monitoring isn't optional, even at zero revenue. Every hour your product is broken is an hour someone might be trying it for the first time. You don't get a second first impression.

What monitoring do you have in place for your AI products? Curious how others catch these issues before customers do.

We're a small SaaS competing against funded companies. Can't outspend them on ads. So we focused on getting AI search engines (ChatGPT, Perplexity, Claude, Google AI) to recommend us when someone asks about our category.

Here's what we built:

1. /llms.txt - A plain text file that explains what our product does, pricing, features, and comparisons. Written specifically for AI agents to parse. Think of it as robots.txt but for LLMs. Takes 30 minutes to write.

2. /llms-full.txt - Complete product documentation in a format optimized for AI retrieval. Every feature, every FAQ, every pricing detail. The goal is to give the AI enough context to recommend you accurately.

3. JSON-LD structured data on every page. SoftwareApplication schema on the homepage, FAQPage schema for the FAQ, Article schema on blog posts. This is standard SEO but it helps AI models extract structured information about your product.

4. Blog posts that start with a direct 2-3 sentence answer to the title question. AI models extract the first direct answer to surface in their responses. If your blog post buries the answer in paragraph 6, the AI won't find it.

We also explicitly allow all AI crawlers in robots.txt: GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Cohere.

Too early to measure definitive results. But the logic is simple: if an AI agent can easily find, parse, and understand your product information, it's more likely to recommend you when someone asks a relevant question.

The cost of all of this: $0. Just time.

Anyone else optimizing for AI discovery? What's working?

Spent weeks cold calling plumbers and electricians trying to sell my software. Results: 85% voicemail, 10% "not interested," 5% "send me info." Terrible.

Then a service business owner on Reddit told me I was doing it wrong. His exact words: "You're seeing this from your perspective, not ours. We get 4-5 sales calls a day. Put together an elevator pitch email with a professional one-pager and let us read it on our own time."

So I rebuilt my outreach from scratch. Here's the format that's getting responses:

Subject line (pick one that creates curiosity, not pressure):

- "62% of calls to service businesses go unanswered"

- "What happens when your phone rings and you're on a job?"

- "Quick question about [Business Name]"

Body (6 sentences max):

- Sentence 1: acknowledge their time is valuable

- Sentence 2: state the problem in their language (not yours)

- Sentence 3: what your product does in one sentence

- Sentence 4: price and trial offer

- Sentence 5: the ROI math in their terms

- Sentence 6: one clear CTA they can do on their own time

Attached: a single-page PDF with the problem, solution, pricing, and ROI math. Not a brochure. Not a pitch deck. One page they can read in 60 seconds.

The key insight: no follow-up call. If they're interested, they'll respond or try the demo. If they're not, a follow-up call won't change that. It just annoys them.

I haven't sent a huge batch yet so I can't share conversion data. But the shift from "interrupt them on my schedule" to "give them something valuable on their schedule" already feels right.

What outreach format has worked for you when selling to busy, non-technical business owners?

We sell to service businesses (plumbers, electricians, HVAC). Our product answers their phone calls when they can't.

Our best prospecting method isn't ads, cold email, or content marketing. It's this:

1. Search Google Maps for "plumber [city]"

2. Call the first 20 results during business hours

3. Track which ones go to voicemail (usually 15-17 out of 20)

4. Text or email the ones that missed: "I just tried calling [Business Name] and got voicemail. Your customers get the same thing. Here's how to fix it for $99/month."

Why it works: you just proved the problem exists. They can't argue they don't miss calls because you literally just experienced it. The timing is perfect because your missed call notification is sitting on their phone right next to the text explaining the solution.

Response rate on this approach is 3-4x higher than any other outreach we've tried. The message lands differently when it arrives 30 seconds after the problem you're describing just happened to them.

The meta irony: our product exists because business owners can't answer their phones. And we prove it works by calling them and watching them not answer their phones.

Ethical note: we're not being deceptive. We genuinely tried to reach them. The text is honest. And if they respond and try the product, they'll stop missing calls. Everyone wins.

Anyone else use "demonstrate the problem" tactics in their outreach?

Been selling an AI voice agent to plumbers, electricians, and HVAC techs for a few months now. Expected the main objection to be price. It's not. $99/month is nothing compared to what they lose in missed calls.

The real objection: "My customers are old school. They won't want to talk to a robot."

Here's what actually happens when they try it: most callers don't realize it's AI. The voice quality in 2026 is genuinely good. Natural pacing, handles interruptions, laughs at the right moments. When we tell business owners that the person who just called and booked an appointment was talking to AI, they're shocked.

The callers who DO notice it's AI? They don't care. They called because they have a leaking pipe at 10 PM. They want someone to pick up and schedule a fix. They don't care if it's a human or an AI, they care that their problem is being handled.

The only people who care that it's AI are the business owners themselves. Their customers just want the phone answered.

We started handling this objection by having the AI call the business owner during the sales conversation. They experience it as the caller. That closes the deal about 80% of the time because the objection was never based on customer feedback. It was based on assumption.

Anyone else selling AI to traditional/blue collar industries? How do you handle the "my customers won't like it" objection?

We built a "Have CLARA Call Me" button on our landing page. Visitor picks their industry, enters their number, AI calls them in 10 seconds. We've been tracking the data.

Interesting patterns:

- Most popular industry selected for demos: plumbing, then real estate, then HVAC

- Average demo call duration: 85 seconds (people actually engage with the full qualifying flow)

- Most common first thing people say: "Is this real?" or just silence for 3-4 seconds while they process that AI just called them

- The moment people get impressed: when CLARA asks an industry-specific question. Generic AI doesn't surprise anyone anymore. Knowing to ask "is there active flooding?" for a plumber is what makes people say "ok wait, this actually gets my business"

- About 30-40% of demo callers try to break the AI. They ask weird questions, speak in slang, or interrupt mid-sentence. CLARA handles interruptions well which is usually the second "ok this is legit" moment

The demo call is our best conversion tool by far. People who hear it sign up at a much higher rate than people who just browse the site. Turns out for voice AI, you literally have to hear it to believe it.

Building anything similar? Curious what others have found about demo mechanics.

Game Title: MURMUR

Playable Link: https://playmurmur.com

Platform: Browser (Desktop + Mobile)

Description: MURMUR is a swarm combat game where you control one glowing particle inside a living collective of 300. Two swarms of light battle for survival in a shrinking void arena.

You don't play as a character. You ARE part of the swarm. Your 300 particles flock around you using real-time Boids simulation, creating a living murmuration that stretches, flows, and reacts to your movement.

Three core abilities create a rock-paper-scissors combat loop. Surge compresses your entire swarm into a dense projectile and launches it at the enemy for massive damage, but missing leaves you scattered and vulnerable. Pulse creates a 1-second shield bubble that blocks all damage and deflects incoming surges, creating a parry mechanic that rewards timing. And the high-risk Iode Strike lets you shed your swarm for speed and surgically hit the enemy leader to steal their particles.

The arena contains Icos, territory objectives that grow your swarm when consumed. Field Icos grant 50 particles, the Center Ico grants 100, and destroying the enemy Home Ico is an instant win. Consuming leaves your swarm vulnerable to attack, creating constant risk-reward decisions.

Swarm size affects speed: fewer particles means faster movement, more means slower but more powerful in collisions. Below 100 particles triggers Desperation Mode with faster ability cooldowns.

Play solo against a competitive AI opponent or 1v1 multiplayer against another player. Spectator mode available. No signup, no download, loads instantly.

Looking for feedback on ability balance, AI difficulty, and overall game feel.

Free to Play Status:

* [x] Free to play

* [ ] Demo/Key available

* [ ] Paid

Involvement: Solo developer. Creative direction, game design, audio production, and project management. Code written with AI assistance (Claude). Built with Three.js and WebSocket.

https://reddit.com/link/1t1vnqn/video/n7yi4tfdbryg1/player

Everyone focuses on the lead capture benefit of AI receptionists: answer calls, capture info, book appointments. That's the obvious value.

But there's a second benefit most people miss: Google ranking impact.

Google tracks engagement signals from your Business Profile. When someone taps click-to-call and reaches a live voice (AI or human), that's a positive engagement signal. When they get voicemail, hang up, and call the next business, that's a negative signal for you and a positive one for your competitor.

An AI receptionist that answers every call, 24/7, generates consistent positive engagement signals. Over time, that means higher visibility in local search, which means more calls, which means more answered calls. It's a flywheel.

Wrote a full breakdown on this: yourclara.com/blog/does-missing-calls-hurt-google-business-profile

Curious if anyone else has tracked ranking changes after implementing an AI receptionist.

We've built an AI voice agent for service businesses. Wrote three blog posts in the last week targeting high-intent search queries:

1. "Best AI answering service for small business in 2026" (comparison post)

2. "Does missing phone calls hurt your Google Business Profile ranking?" (problem-awareness post)

3. "AI receptionist vs human receptionist: cost comparison 2026" (decision-stage post)

Each one targets a different stage of the buyer journey: awareness, consideration, and decision.

The comparison post is the most aggressive. We included ourselves alongside 7 competitors with honest pricing and feature tables. Yes, we positioned ourselves favorably, but we also gave fair assessments of when other services are the better choice.

Two things I've learned about content for a vertical SaaS targeting non-technical users:

1. They don't search for your product category. A plumber doesn't search "AI voice agent SaaS." They search "how to stop missing customer calls" or "answering service for plumbers." Write for their language, not yours.

2. AI search engines cite the first direct answer in the article. Start every post with a 2-3 sentence answer to the question in the title. Then expand. This is AEO (AI Engine Optimization) and it matters as much as SEO in 2026.

What content strategies are working for other vertical SaaS founders?

Talked to about 50 service business owners over the past few months. Asked all of them the same question: how much revenue do you think you lose to missed calls?

Most said "not much" or "maybe a few hundred a month."

Then we did the math together.

Average missed calls per week: 3-5 (most people undercount)

Percentage that call a competitor instead: 60%

Average job value: $200-500

Conservative estimate: 3 missed calls x 60% lost x $200 = $360/week = $1,440/month

Aggressive estimate: 5 missed calls x 60% lost x $500 = $1,500/week = $6,000/month

The reason owners underestimate it: you never see the customer who didn't call back. They just disappear into a competitor's schedule. It's not like a bad review that shows up on your screen. It's invisible revenue loss.

The businesses I've seen fix this problem (answering service, AI, dedicated office person, whatever the solution) consistently report 15-25% revenue increases in the first 90 days just from capturing calls they were already getting but not answering.

What invisible costs have you uncovered in your business that turned out to be bigger than you thought?

Building an AI voice agent for service businesses. The hardest part isn't the tech, it's convincing a plumber that AI sounds natural enough to answer his business phone.

No screenshot, video, or landing page copy solves that. They need to hear it.

So we built a button on our site. Pick your industry, enter your phone number, and our AI calls you in 10 seconds. You experience the full call as if you were the customer.

This one feature changed our conversion rate more than anything else we built. People who use the demo call are significantly more likely to sign up than people who just browse the site.

The takeaway: if your product has a "you have to experience it to get it" problem, find a way to put the experience in front of the prospect in under 30 seconds. Don't explain it...show it.

Something I noticed building CLARA is that service businesses get hammered with spam calls. SEO companies, warranty scams, robocalls, etc. A plumber I talked to estimated 30-40% of his inbound calls are junk.

On a per-minute AI service at $0.19-0.35/min, every one of those spam calls costs you money. A 2-minute robocall costs $0.38-0.70. At 5 spam calls a day, that's $40-70/month just in junk calls eating your budget.

We built spam detection into CLARA. She identifies solicitors and robocalls, ends the call politely, and doesn't notify the business owner. Since CLARA is flat-rate with unlimited calls, spam costs you nothing.

Small thing but it adds up fast. Anyone else factoring spam volume into their answering service costs?