Launching RadiusHQ: A booking-first page for service businesses
Hey everyone 👋
Today I'm launching RadiusHQ.
Over the last few months, I've been talking to service businesses and noticed a common pattern.
Most of them were using a combination of:
Instagram or WhatsApp for customer acquisition
Linktree for links
Calendly for booking
Spreadsheets for managing appointments
The setup worked, but it created a lot of unnecessary friction.
The problem became even more obvious when teams were involved.
Imagine a salon.
Customers don't just want to book a service.
They want to book a specific professional.
A haircut with Sarah.
A nail appointment with Emma.
A consultation with Dr. Smith.
Most booking tools treat appointments as generic time slots, while many service businesses operate around people and expertise.
That's what inspired RadiusHQ.
What is RadiusHQ?
RadiusHQ is a booking-first page designed for service businesses.
Customers can:
Discover services
Choose a professional
View availability
Book appointments
Businesses can:
Manage team members
Assign services to specific professionals
Handle bookings from a single dashboard
Share a single booking page across Instagram, WhatsApp, Google Business, and more
Why I built it
I wasn't interested in building another website builder or another scheduling tool.
I wanted to simplify the journey between:
"I found your business"
and
"I've booked an appointment."
The fewer steps between those two moments, the better.
Who is it for?
RadiusHQ is built for businesses that sell time, expertise, or appointments.
Examples:
Salons and beauty businesses
Clinics and healthcare practices
Agencies
Consultants
Coaches
Freelancers
Fitness professionals
If customers need to choose a service, choose a professional, and book a time, RadiusHQ is designed for that workflow.
Current status
The product is currently free while I gather feedback and learn from early users.
I'd love to hear what you think:
Does this solve a real problem?
What would stop you from using it?
What feature would you want next?
Try it here:
Thanks for reading, and I'm happy to answer any questions in the comments.
I'd be careful with one thing.
The challenge may not be whether businesses need booking.
The harder decision could be whether they perceive the booking page itself as the product they're adopting.
That sounds subtle, but it can shape who adopts first, what they compare you against, and what convinces them to switch.
I wouldn't make that call casually in a thread.
Appreciate the perspective. I'm actively validating exactly this—whether businesses are adopting RadiusHQ for booking itself or for the customer-facing page experience.
That's exactly where I'd be careful.
The challenge isn't necessarily the validation itself.
It's the decision that ends up getting validated.
I wouldn't try to unpack that properly in a thread.
If you'd like the tighter version, drop your email and I'll put it together properly.
This comment was deleted 3 months ago
This comment was deleted 3 months ago