Case study · Built by our founder
Bookvid
Bookvid (live at https://bookvid.com/) lets people book single or recurring video sessions with experts across music, politics, AI, and more, while hosts run their own pricing, series, and events from a dashboard, all tied together with calendar sync, Stripe, and in-session video.
The story
Bookvid predates Inseed as a company. Our founder built it as a full-stack engineer, leaning heavily to the frontend, on a direct-client engagement that arrived through a referral. It is founder-portfolio work rather than an Inseed-direct project, and the founder owned mostly the frontend plus a slice of the Python backend on a team.
The product sits between two groups. Experts want to monetize their time through paid video sessions; people want to book time with smart voices across domains like music, politics, and AI. For that exchange to feel effortless, three genuinely hard systems have to line up behind one booking button: availability and calendars, payments, and live video.
The catch is that the deceptively simple part, scheduling, is the part that quietly breaks marketplaces. Availability windows, recurring series, time-zone correctness, and calendar conflicts are all edge cases that off-the-shelf booking widgets tend to fumble the moment a real host with a real calendar shows up.
What we built
The build shipped both halves of the marketplace: a discovery and booking experience for attendees, and a host dashboard where creators set their pricing, spin up recurring series, and manage events. Our founder led the frontend across both surfaces in Next.js and contributed to the Python backend that stood behind them.
Scheduling was treated as a first-class problem rather than a plugin. The engagement integrated Cronofy for calendar sync and availability, then wrapped a custom scheduler around it to handle the booking and series logic a marketplace needs but a generic widget does not cover.
From there the work was about making a booked session flow cleanly from booking to payment to a live call. Stripe handled payments, and a third-party video and recording tool carried the session itself, all wired into the booking and dashboard frontends so the whole path felt like one product instead of four services taped together.
Architecture
The frontend is Next.js, covering both the attendee-facing marketplace and the host dashboard. The backend is in Python, which our founder contributed to alongside a broader team, so the frontend narrative here is the more complete one.
The most consequential architectural choice was not buying the scheduling problem off the shelf. Cronofy provides the calendar and availability integration, but a custom scheduler was built on top to model single and recurring sessions, keep time zones honest, and slot bookings into a host calendar without conflicts. That combination is what lets a host expose real availability and a series without the booking flow falling apart under real-world calendars.
Payments run through Stripe, and the live session uses a third-party video and recording tool. Rather than lean on a single off-the-shelf video SDK for everything, a good deal of the surrounding session experience was built in-house so booking, payment, and the call felt continuous. Database, auth, and hosting specifics are not documented in the founder notes, so they are left out here rather than guessed at.
Selected screens
Stack
One decision worth telling
Real scheduling is harder than it looks. Availability, recurring series, calendar sync, and conflict handling are all edge cases, and off-the-shelf booking widgets rarely fit the shape a two-sided marketplace needs once hosts bring their own calendars.
So the flow paired Cronofy for calendar integration with a custom scheduler built for the booking and series logic, then wired it into both the marketplace and the host dashboard. It is the clearest example of the engagement choosing to own the hard part instead of hoping a generic component would stretch to fit.
Outcome
“Inseed didn't just build a website; they brought our vision for Bookvid's session-based packages to life. Their innovative approach to user interaction and seamless execution has truly set us apart in the industry.”
What we would do differently
Most agencies skip this section. We include it because honest hindsight is the kind of credibility you cannot buy.
A lot of the session experience was built in-house around a third-party video and recording tool rather than settling on one clear off-the-shelf SDK up front. Locking that choice in earlier would have reduced the amount of surrounding plumbing that had to be hand-built to make booking, payment, and the call feel continuous.
Availability, recurring series, and calendar conflicts are the parts of a marketplace that quietly generate the most edge cases. Giving the custom scheduler its own hardening and test budget from day one, rather than growing it alongside the booking screens, would have paid back across every flow that touches a calendar.
With the founder mostly on the frontend, the database, auth, and hosting choices are the least captured part of this project after the fact. Writing those down as the build progressed would make the platform easier to reason about and extend later, instead of leaving gaps in the record.
Related work
Built by Inseed
Zero to App Store in under 4 months. Past 3,000 users in the next 3.
Read the case studyBuilt by Inseed
Vibe search shipped in 3 weeks. AI searches up ~200%.
Read the case studyTwo-sided marketplaces, calendar integrations, custom schedulers, Stripe, and video sessions. Tell us what you are shipping and we will tell you what the first four weeks can de-risk.
Book your audit