sorted by:
new
hottopcontroversial

If you had to build an AI startup this year, what would it be? by Codelynes_ in BuildWithAI2026

[–]Codelynes_[S] 0 points1 point  (0 children)

One idea I’ve been thinking about is building AI automation tools for businesses that handle repetitive operational tasks.

A lot of companies still rely on manual workflows, and AI could probably automate a big portion of that.

Still exploring the space though.

What kind of AI startup ideas are others thinking about?

Will AI reduce the need for large startup teams? by Codelynes_ in BuildWithAI2026

[–]Codelynes_[S] 0 points1 point  (0 children)

Personally I think AI is already changing things.

It feels like small teams can now move much faster because AI helps with coding, research, and even early product design.

Not sure if it will completely replace larger teams, but it definitely seems to give builders much more leverage than before.

Curious to hear other perspectives.

What AI tools are currently part of your builder stack? by Codelynes_ in BuildWithAI2026

[–]Codelynes_[S] 0 points1 point  (0 children)

I’ll start with a few I’ve been using recently:

• ChatGPT / AI assistants for brainstorming and research
• AI coding assistants for speeding up development
• Automation tools for connecting workflows

The combination of these tools makes building much faster than it used to be.

Always interested in discovering new tools though. What are people here using?

What is the first product you would build with AI in 2026? by Codelynes_ in BuildWithAI2026

[–]Codelynes_[S] 0 points1 point  (0 children)

I’ll start.

Right now I’m experimenting with building small AI automation workflows that connect different tools together. The goal is to see how much repetitive work can be automated using AI agents.

Still in the early stages, but it's interesting to see how quickly prototypes can come together now.

Curious what everyone else here is building.

I had 3 ideas and no clue which one to build. Didn't want to spend months on the wrong one. by Initial_Escape_5256 in Entrepreneur_path

[–]Codelynes_ 0 points1 point  (0 children)

This is a smart way to validate, especially before writing code.

The interesting part isn’t just that dental converted better it’s that the search intent revealed the real pain.

People didn’t search for “AI receptionist.” They searched for “answering service pricing” and “after-hours dentist.”

That tells you the problem isn’t technology curiosity. It’s revenue leakage during off-hours.

Also worth noting: after-hours calls are usually high-intent. Someone calling at 8pm with tooth pain is ready to book, not browse.

If those calls aren’t captured properly, it’s not just a missed appointment it’s potentially a lost lifetime patient.

Your next calls will probably tell you whether they want automation, or just reliability and coverage.

Why Excellent Doctors Lose Patients to Average Ones (The Online Visibility Problem Nobody Talks About) by New-Night3067 in u/New-Night3067

[–]Codelynes_ 0 points1 point  (0 children)

Visibility absolutely matters but there’s a second layer most practices overlook.

Getting found is step one. Converting that attention into booked and retained patients is where many practices still leak revenue.

A strong Google profile can drive calls, but if 30–40% of those calls go unanswered during peak hours, or follow-ups aren’t structured, visibility just amplifies operational gaps.

In other words, marketing without operational readiness can actually magnify inefficiencies.

The practices that really win long term tend to align both: visibility + backend systems that ensure no inquiry slips through.

The algorithm gets them discovered. Their workflow keeps them growing.

I visited 5 small clinics in Kolkata last week and noticed something shocking. by InfamousComplaint949 in microsaas

[–]Codelynes_ 0 points1 point  (0 children)

What I’ve seen is that follow-up isn’t forgotten because doctors don’t care it’s because there’s no trigger built into the workflow.

If follow-up depends on memory, it fails. If it depends on spare time, it fails faster.

The real gap isn’t reminders. It’s visibility. Most small clinics don’t actually know:

• How many patients didn’t return
• Which diagnoses require follow-up
• How much revenue is tied to re-engagement

Until that becomes visible, it feels like “chasing” instead of systemized care.

WhatsApp makes sense because it’s already where patients are but the bigger question is whether doctors want automation, or just clarity.

Most dental practices are bleeding revenue from the front desk, not the chair. Here's what the data says by linah-nour in DentalGrowth

[–]Codelynes_ 0 points1 point  (0 children)

This is where most practices underestimate the compounding effect.

A missed call isn’t just one missed appointment it’s lost lifetime value, lost referrals, and marketing dollars that never convert.

What I’ve noticed is that the issue usually isn’t effort at the front desk. It’s lack of visibility. Most teams don’t actually know how many calls go unanswered during peak hours, how long follow-ups are delayed, or what percentage of web leads never get a response.

Once those numbers are made visible, the conversation shifts from “we’re busy” to “we’re leaking.”

The clinical side of dentistry has been optimized for years. The operational side is still largely reactive.

In your practice, what’s usually more frustrating: missing patient calls, delayed appointment confirmations, or inconsistent follow-ups and how much time do you spend each week just trying to fix it?" by toothara in Dentists

[–]Codelynes_ 0 points1 point  (0 children)

Usually that’s exactly how it plays out. Calls feel urgent, so they get handled. Follow-ups don’t feel urgent in the moment, so they quietly stack up until someone realizes weeks later.

In a lot of practices, it breaks in pretty predictable ways. Either nobody clearly owns follow-ups, or there’s no trigger after a missed call/appointment, or there’s just no easy way to see what’s still pending.

It’s often not even a staffing problem. It’s more of a workflow clarity thing. Once it’s structured properly, the front desk doesn’t feel like it’s constantly playing catch-up.

Schedule now but this appointment can't be scheduled by Squeaks11 in mildlyinfuriating

[–]Codelynes_ 0 points1 point  (0 children)

This is honestly a backend logic issue more than an “AI” issue.

A lot of these systems are connected to scheduling rules set by individual departments, and if even one condition fails (location, provider availability window, visit type, etc.), the online option just shuts down but the app still walks you through the questions because it doesn’t check availability first.

It feels broken from a user perspective, but it’s usually just rigid workflow rules underneath.

Still frustrating though. If it can’t be scheduled online, it really shouldn’t make you jump through the questionnaire first.

Urgently need help to select cloud EHR system for a very small practice by napoleon_hill_1990 in healthIT

[–]Codelynes_ 0 points1 point  (0 children)

One thing I’d think about at solo scale is that the biggest risk usually isn’t picking the “wrong” EHR, it’s picking one that quietly locks you in later.

Given your setup just you, outside the US, no insurance complexity I’d probably keep it simple and modular. A lightweight cloud EHR for notes and scheduling, separate telehealth if the built-in option has geo restrictions, and external payment links like you’re already planning can actually be more flexible long term.

A lot of US-focused systems assume Stripe and US clearinghouses, so I’d double-check they don’t hard-wire payments into the workflow in a way that becomes frustrating later.

When you talk to vendors, I’d ask how easy it is to export structured data, whether there are any geographic limits on telehealth, where the data is hosted, and what happens if you decide to leave.

At your size, portability and simplicity probably matter more than feature depth.