BookSlot - Freelancer-First Scheduling With Built-In Payments and Session Types
Calendly was built for sales teams, not solopreneurs charging $200/hour for consulting sessions. BookSlot is a scheduling tool where paid sessions, custom meeting types, and instant rescheduling are table stakes — not $20/month add-ons.
Difficulty
beginner
Category
SaaS
Market Demand
Very High
Revenue Score
7/10
Platform
Web App
Vibe Code Friendly
⚡ YesHackathon Score
6/10
Validated by Real Pain
— seeded from real developer complaints
Freelancers widely report that existing scheduling tools are designed for sales teams and lack critical features like upfront payment collection, multiple meeting types with different prices, and client-driven rescheduling — forcing solopreneurs to hack together 3-4 separate tools to run basic paid bookings.
What is it?
Freelancers and solopreneurs lose real money every week stitching together Calendly, Stripe, and manual email follow-ups just to book a paid consultation. The pain is loud on r/freelance and IndieHackers: no single tool handles multiple meeting types, upfront payments, and frictionless rescheduling in one flow. BookSlot ships as a dead-simple web app where a freelancer sets up unlimited session types with prices, embeds a booking link anywhere, and receives payment before the meeting even happens. Clients self-serve rescheduling without emailing. Built on Next.js with Stripe Checkout and Cal.com's open scheduling primitives — shippable in 2 weeks because all heavy lifting is already solved by existing APIs.
Why now?
The April 2026 wave of solopreneur tooling is peaking — Cal.com's open API matured in 2025, making scheduling primitives free to compose without rebuilding calendar logic from scratch.
- ▸Unlimited paid session types with per-type pricing, duration, and availability rules.
- ▸Stripe Checkout upfront payment gate — client pays before slot is confirmed.
- ▸One-click client rescheduling via tokenized link without login.
- ▸Automated reminder and receipt emails via Resend with freelancer branding.
Target Audience
Freelance consultants, coaches, and solopreneurs charging for time — 4M+ in the US alone, active on IndieHackers, Twitter, and Slack communities.
Example Use Case
Marcus, a UX consultant charging $250/hour, sets up three session types in 10 minutes, shares his link on LinkedIn, and collects payment before every call — cutting no-shows by 80% and saving 3 hours of admin weekly.
User Stories
- ▸As a freelance coach, I want clients to pay upfront when booking, so that I eliminate no-shows entirely.
- ▸As a consultant, I want multiple session types with different prices, so that I can offer discovery calls and deep-dives from one link.
- ▸As a client, I want to reschedule without emailing the freelancer, so that I can adjust plans without awkward back-and-forth.
Acceptance Criteria
Payment gate: done when client cannot confirm slot without completing Stripe Checkout. Session types: done when freelancer creates 3 types with different prices and all render on booking page. Reschedule: done when client uses token link to pick new slot without logging in. Email: done when confirmation and receipt arrive within 60 seconds of payment.
Is it worth building?
$19/month x 80 users = $1,520 MRR by month 2. $49/month pro tier x 40 users = $1,960 MRR. $5k MRR realistic by month 5 with community-driven growth.
Unit Economics
CAC: $8 via community DMs and Twitter. LTV: $228 (12 months at $19/month). Payback: 1 month. Gross margin: 91%.
Business Model
SaaS subscription $19/month
Monetization Path
Free tier: 1 session type, 5 bookings/month. Pro $19/month: unlimited types and bookings. Agency $49/month: 3 booking pages.
Revenue Timeline
First dollar: week 2. $1k MRR: month 2. $5k MRR: month 5.
Estimated Monthly Cost
Vercel: $20, Supabase: $25, Resend: $10, Stripe fees: ~$30 (at $1k MRR). Total: ~$85/month.
Profit Potential
Sustainable indie business at $5k–$12k MRR.
Scalability
High — team booking pages, white-label, and marketplace of freelancers are natural V3 plays.
Success Metrics
Week 1: 150 waitlist. Month 1: 25 paid. Month 3: 80% month-2 retention.
Launch & Validation Plan
Post in IndieHackers Slack and r/freelance asking what scheduling tool they hate most and why — collect 50 responses before writing a line of code.
Customer Acquisition Strategy
First customer: DM 25 freelance coaches on Twitter/X who complain about Calendly payment limitations, offer 6 months free for public testimonial. Ongoing: IndieHackers posts, r/freelance, Twitter/X threads, ProductHunt launch.
What's the competition?
Competition Level
High
Similar Products
Calendly lacks native payments on base tier. Acuity Scheduling is complex and dated. TidyCal is one-time but misses recurring session types — BookSlot nails freelancer-specific paid session flows.
Competitive Advantage
Payment-first booking flow designed for freelancers, not enterprise sales teams — no upsell required for core features.
Regulatory Risks
Low regulatory risk. Stripe handles PCI compliance. GDPR data deletion endpoint required for EU users.
What's the roadmap?
Feature Roadmap
V1 (launch): paid session types, Google Cal sync, Stripe payments, reschedule tokens. V2 (month 2-3): Zoom auto-link, cancellation policy, coupon codes. V3 (month 4+): team pages, white-label domains, analytics dashboard.
Milestone Plan
Phase 1 (Week 1-2): booking flow, Stripe payment, Google Cal integration working. Phase 2 (Week 3-4): reschedule flow, email reminders, landing page live. Phase 3 (Month 2): ProductHunt launch, 25 paid users, coupon codes shipped.
How do you build it?
Tech Stack
Next.js, Stripe Checkout, Supabase, Google Calendar API, Resend for email, Cal.com API — build with Lovable for UI, Cursor for backend, v0 for booking widget
Suggested Frameworks
Next.js, Stripe, Cal.com API
Time to Ship
2 weeks
Required Skills
Next.js routing, Stripe Checkout, Google Calendar OAuth, Supabase auth.
Resources
Stripe Checkout docs, Cal.com API docs, Google Calendar API, Supabase quickstart.
MVP Scope
pages/index.tsx (landing), pages/[username]/book.tsx (booking page), pages/dashboard.tsx (session type manager), api/stripe-webhook.ts (payment handler), api/calendar.ts (Google Cal integration), lib/supabase.ts (DB client), components/SessionTypeForm.tsx, components/TimeSlotPicker.tsx.
Core User Journey
Sign up -> create session type with price -> share booking link -> client pays and books -> freelancer receives calendar invite.
Architecture Pattern
Client picks slot -> Stripe Checkout session created -> payment confirmed -> Google Calendar event created -> confirmation email via Resend -> reschedule token stored in Supabase.
Data Model
User has many SessionTypes. SessionType has many Bookings. Booking has one StripePayment and one CalendarEvent. RescheduleToken belongs to one Booking.
Integration Points
Stripe Checkout for payments, Google Calendar API for availability, Supabase for user data, Resend for transactional email, Vercel for hosting.
V1 Scope Boundaries
V1 excludes: team booking pages, video conferencing native embed, white-label domains, marketplace directory.
Success Definition
A paying freelancer books their first paid session through BookSlot without contacting support, and their client reschedules independently using the tokenized link.
Challenges
Competing with Calendly's brand recognition is brutal — distribution wins only by owning tight communities like IndieHackers Slack, Freelance Slack groups, and Twitter/X threads where payment frustration is loudest.
Avoid These Pitfalls
Do not build team features before 50 solo users validate the core loop. Do not undercut on pricing — freelancers who pay for tools have higher LTV. Finding first 10 paying customers takes longer than building — budget 3x more time for community outreach than development.
Security Requirements
Supabase Auth with Google OAuth. RLS on all booking and session_type tables scoped to user_id. Stripe webhook signature verification required. Reschedule tokens are single-use UUIDs with 7-day expiry.
Infrastructure Plan
Vercel for Next.js hosting, Supabase for Postgres and auth, Resend for email, Sentry for error tracking, GitHub Actions for CI on main branch deploys.
Performance Targets
Target 500 DAU at peak, booking page under 1.5s LCP, Stripe webhook handler under 300ms, slot availability check under 400ms.
Go-Live Checklist
- ☐Security audit complete
- ☐Stripe payment tested end-to-end in production mode
- ☐Sentry error tracking live
- ☐Vercel analytics configured
- ☐Custom domain with SSL live
- ☐Privacy policy and terms published
- ☐5 beta freelancers signed off
- ☐Rollback: Vercel instant rollback to prior deploy
- ☐ProductHunt launch post drafted.
How to build it, step by step
1. Run npx create-next-app bookslot with TypeScript and Tailwind. 2. Set up Supabase project with users, session_types, bookings, reschedule_tokens tables. 3. Add Google OAuth via Supabase Auth for calendar access. 4. Build session type creation form with Lovable and v0 components. 5. Implement Google Calendar free-busy check via API for slot availability. 6. Create Stripe Checkout session on slot selection and store pending booking. 7. Handle Stripe webhook to confirm booking and write to Supabase. 8. Create calendar event on confirmation and send Resend confirmation email. 9. Generate reschedule token and include in client email with self-serve rescheduling page. 10. Deploy to Vercel, set up custom domain, configure Stripe production keys.
Generated
April 5, 2026
Model
claude-sonnet-4-6