Venu
CRM built for aesthetic clinics
I spent weeks talking to aesthetic clinics in Barcelona before writing a single line of code (well, almost).
Here's what I found:
The real pain:
Every clinic I called manages WhatsApp manually. Between patients. No system. No automation. One owner told me: "sometimes I see the message 3 hours later and the client already went somewhere else."
Estimated cost of not responding in time: €1,200–1,600/month in lost appointments.
What I built:
Venu is a CRM built specifically for aesthetic clinics that automates the WhatsApp layer: identifies whether the person messaging is a returning patient or a new one, responds differently in each case, and books appointments automatically.
No contracts, no complex setup. €149/month flat.
Stack: Next.js + Supabase + GPT-4o + Z-API + Stripe.
What I learned from the process:
1. Pain is confirmed in the first 60 seconds of a call
2. The most common objection: "will the AI understand my clients?" — which led to building the returning vs. new patient detection as a core feature
3. Price isn't the friction — trust is
Where I am now:
MVP in production as of today. Two hot leads. 6 clinics that validated the pain waiting to see the real product.
This week: demos, feedback, first paying customer.
Has anyone gone through a similar B2B outreach process in local niches? What worked for closing the first one?
I'm building Venu, an AI agent for aesthetic clinics in Spain that handles WhatsApp leads automatically: qualifies them, follows up, books appointments.
The MVP is done. Dashboard, kanban pipeline, conversation inbox, appointment calendar, billing with Stripe, multi-tenant RLS, onboarding wizard. 885 lines of agent logic. The whole thing.
And I realized something uncomfortable this week.
Nobody asked for the CRM.
I talked to 6 clinic owners in Barcelona before writing a single line of code. Every single one of them complained about the same thing: WhatsApp chaos. Leads coming in while they're with a patient. No time to respond. Appointments lost because someone didn't follow up in 20 minutes.
Not one of them said: "I need a better pipeline view."
Not one said: "I need a kanban board for my leads."
So why did I build all of it?
Because I'm a developer. And developers build systems. Complete systems. Systems with dashboards and settings tabs and CSV imports. Systems that look like software.
The truth is: the CRM exists to make me feel like I built something serious. The WhatsApp agent exists to solve their actual problem.
What I actually built vs. what matters
The AI agent that responds to WhatsApp leads in under 60 seconds? That's the product. The automatic follow-ups at 12:00 every day for leads that went cold? That's the product. The booking flow with human confirmation? That's the product.
The kanban pipeline, the 5-tab settings panel, the CSV import for treatments, the KPI dashboard, weeks of work on features that aren't the reason someone pays €149/month.
They're not useless. The CRM gives the agent context, stores the data, makes the product feel legit. But I built it in the wrong order.
I should have shipped the agent first. Put it in a WhatsApp thread. Charged for that. Then added UI around it as clients asked for it.
Instead I built the full SaaS upfront and now I have two self-inflicted security blockers standing between me and my first beta clinic: a hardcoded Google Calendar ID and two unauthenticated API routes I never cleaned up.
Weeks of kanban work. Two stupid bugs blocking production.
The lesson I keep learning and forgetting
The product is the outcome, not the interface.
Clinic owners don't want a CRM. They want to never lose a lead again while they're with a patient. The CRM is just the container I built around the thing that actually does that.
Where I am now
MVP: complete
Paying customers: 0
Beta leads: 14 validated in Barcelona
Next step: fix the two blockers, onboard the first clinic, find out what I actually got wrong
Building in public from Barcelona. Happy to answer questions about the agent architecture, the WhatsApp integration, or the multi-tenant Supabase setup.
What's the most "obvious in hindsight" mistake you made on your first SaaS?
-
1
This one's sharp, especially "the product is the outcome, not the interface." Easy to write, hard to actually live by when building feels productive.
My own obvious-in-hindsight one: I kept treating "finish the product" as the goal, when the real wall was getting it in front of the few people who'd actually pay. Building got faster every month, but a good narrow tool can still sit invisible because one builder can't out-market the big platforms. That gap is basically why I'm building AppGild, an early marketplace for focused apps and AI agents aimed at small businesses and solo pros. If you ever want one more place for Venu to be found as it grows, happy to share the link. Either way, good luck onboarding that first clinic.
Comment