How to Build a Tutoring Platform App with Bubble

Before Bubble, building a tutoring platform that handled profiles, booking, payment, and live sessions required a development team and months of runway. Most edtech founders either chose an existing platform and accepted its limitations or shelved the idea.

Building a tutoring platform app with Bubble makes the full two-sided marketplace model accessible without code. Here's what it takes to build it correctly.

Key Takeaways

• Bubble supports the full marketplace model: Tutor profiles, student discovery, booking, payment, sessions, and reviews are all buildable without writing code.
• Booking and scheduling is the hardest part: Availability management requires careful data modeling to prevent double-bookings and timezone conflicts.
• Stripe Connect powers tutor payouts: Split payments and automatic payouts require Stripe Connect, not the standard Stripe plugin.
• Video delivery needs an integration: Bubble doesn't host video natively. Whereby, Daily.co, or Zoom connect via plugin or API for live session delivery.
• MVP scope matters enormously: A booking-and-payment MVP is weeks. A full marketplace with reviews, analytics, and tutor onboarding takes months.

Bubble App Development

Bubble Experts You Need

Hire a Bubble team that’s done it all—CRMs, marketplaces, internal tools, and more

Let's talk

What Is a Tutoring Platform App — and Why Build It with Bubble?

A tutoring platform connects students with tutors, manages booking and scheduling, processes payment, delivers live sessions, and handles post-session reviews and notes.

Edtech founders, tutoring businesses, schools building internal tools, and subject-matter experts building personal brands all have reasons to build a custom tutoring platform. The common problem is that existing tools, Wyzant, Preply, Superprof, take large commission cuts and offer no customization over the booking experience, payment terms, or platform branding.

Two-sided marketplaces are among the most ambitious apps you can build with Bubble, and tutoring platforms are a well-matched use case. The platform's core operations, including profile discovery, session booking, payment split, and review collection, map directly to Bubble's workflow and database capabilities.

Building on Bubble means you own the platform, the data, and the economics. No per-session commission to a third-party marketplace.

What Features Should a Tutoring Platform App Include?

A tutoring platform has two user types with distinct feature needs. Build for both from the start. An incomplete tutor experience means no supply, which means no student demand.

Prioritize booking and payment above everything else. Those are the two workflows that determine whether the platform functions as a business.

• Tutor profiles: Each tutor has a profile with subjects taught, bio, credentials or qualifications, hourly rate, availability windows, and verification status. Only verified profiles appear in student search results.
• Student discovery and search: Students filter tutors by subject, price range, rating, and available time slots. Results display as a Repeating Group sorted by relevance or rating. Session history with a tutor surfaces on repeat visits.
• Session booking with availability calendar: Students select an available time slot directly from the tutor's calendar. Booking creates a Session record and marks the selected AvailabilitySlot as booked, preventing double-booking.
• Stripe Connect payment: Students pay the platform at booking. Funds are held by Stripe until the session completes. Stripe then transfers the tutor's share (minus the platform fee) to their connected bank account automatically.
• Video session delivery: Live sessions run inside the platform via an embedded Whereby or Daily.co room. The video room URL is generated when the session status changes to "live" and displayed to both participants.
• Session notes and resources: After each session, tutors can add session notes and attach resources. These are visible to the student in their session history and serve as a record of progress.
• Review and rating system: After session completion, students receive a prompt to rate their tutor and leave a review. Reviews are published (immediately or after admin moderation) and factor into tutor search ranking.
• Tutor earnings dashboard: Tutors see a breakdown of completed sessions, payment amounts, platform fees, and payout status. Pending and completed Stripe transfers are displayed with dates.

How Do You Structure the Database for a Tutoring Platform App in Bubble?

The tutoring platform data model is one of the more complex in edtech. The AvailabilitySlot type requires particular care. It's what prevents double-bookings and powers the calendar UI.

Design the full model before building. The booking workflow depends on every field in this structure being correct.

• User: Fields include role (student, tutor, admin), name, email, and Stripe customer ID (for students) or Stripe Connect account ID (for tutors). Role drives all routing, privacy rules, and dashboard access.
• TutorProfile: Fields include linked User, subjects list, bio text, credentials, hourly rate, profile photo URL, rating average, session count, and verified status (boolean). Verified status must be true for the profile to appear in search results.
• AvailabilitySlot: Fields include linked tutor (User), day of week, start time, end time, and booked status (boolean). Tutors create multiple AvailabilitySlot records to define their weekly availability pattern. When a session is booked, the matching slot is marked booked. This prevents double-booking at the data layer.
• Session: Fields include linked student (User), linked tutor (User), session date, start time, duration in minutes, status (scheduled, live, completed, cancelled), video room URL, price, and session notes text. One record per booked tutoring session.
• Payment: Fields include linked Session, total amount charged, platform fee amount, tutor payout amount, Stripe payment intent ID, Stripe transfer ID, and payment status (pending, held, transferred, refunded). Split payment tracking requires both the intent ID and the transfer ID.
• Review: Fields include linked Session, reviewer (User), star rating (1-5), comment text, published status, and published date. One review per session per student. Hidden until published status is set to true.

How Do You Build the Core Workflows for a Tutoring Platform App in Bubble?

The booking and payment workflows are the most critical. Every other workflow is secondary. Build those two first, test them with real Stripe test mode transactions, then build everything else.

Never build on top of untested payment workflows. A broken Stripe Connect flow discovered after launch is an operational and financial problem, not just a technical one.

• Tutor onboarding: Tutors fill out their profile form, which creates a TutorProfile record with verified status set to false. Admins review the profile in a management dashboard and set verified to true when approved. Until verified, the profile is invisible to students.
• Student booking: When a student selects a time slot on a tutor's calendar, the workflow first checks that the matching AvailabilitySlot has booked status = false. If available, it creates a Session record, sets the AvailabilitySlot to booked = true, and initiates the Stripe payment flow. If the slot is already booked (race condition), it displays an error and asks the student to select another slot.
• Stripe Connect payment: The student pays via Stripe Checkout, creating a payment intent. The funds are captured and held by Stripe. A Payment record is created in Bubble with the payment intent ID. When the session status changes to "completed," a backend workflow calls Stripe's Transfer API to release the tutor's share to their connected account, minus the platform fee percentage. The Payment record is updated with the transfer ID.
• Video session delivery: A scheduled backend workflow monitors Session records where date equals today and current time is within five minutes of start time. It sets session status to "live" and generates (or displays the pre-assigned) Whereby or Daily.co room URL. Both the student's and tutor's dashboards show the "Join Session" button when status is "live."
• Post-session flow: When session status changes to "completed," a backend workflow creates a blank session notes record linked to the session, sends a SendGrid review request email to the student with a link to the review form, and updates the TutorProfile's session count field.
• Tutor payout tracking: When a Stripe Transfer webhook fires confirming the transfer, a backend workflow (triggered via Bubble's webhook listener) updates the linked Payment record's status to "transferred" and logs the transfer date. The tutor's earnings dashboard reflects this status change in real time.

What Security and Data Requirements Apply to a Tutoring Platform App?

A tutoring platform handles personal data, financial data, and potentially minor users. All three categories require specific, deliberate access controls.

Session data, payment records, and student safety controls all start with Bubble's security configuration applied at the data layer. Building these rules after the platform is live is more complex and riskier than building them in from the start.

• Payment data isolation: The Payment data type must have a strict privacy rule: "This record's session's student equals current user OR this record's session's tutor equals current user." Neither students nor tutors can see the other's raw payment or payout amounts. Admins see all Payment records for financial oversight.
• Session record access: Set a privacy rule on Session: "This record's student equals current user OR this record's tutor equals current user." Session notes, video URLs, and payment status are accessible only to the two participants.
• Review moderation: Set Review published status to false on creation. An admin can review and approve, or set up an automatic publish trigger after a defined time window with no admin flag. This prevents abusive or fake reviews from going live immediately.
• Tutor verification gate: The TutorProfile search query should filter to only profiles where verified = true. Use Bubble's search constraints, not just UI filtering, to ensure unverified profiles cannot be accessed directly by manipulating URL parameters.
• Minor user safety: If the platform serves students under 18, parental consent workflows, additional profile verification for tutors working with minors, and session recording consent must be addressed. These are policy requirements that Bubble's role and verification system can technically support but won't implement automatically.

What Plugins and Integrations Does a Tutoring Platform App Need?

Tutoring platforms have a more complex plugin stack than most education tools because they combine marketplace, booking, payment, and video delivery in one application.

Prioritize Stripe Connect and the video integration. These are the plugins most likely to require non-trivial configuration.

• Stripe Connect plugin: The Stripe Connect plugin (distinct from the standard Stripe plugin) handles split payments, tutor account onboarding, and automatic transfers. Tutors complete Stripe's Connect onboarding flow to link their bank account. Students pay through Stripe Checkout. Transfers happen via Stripe's Transfer API called from a backend workflow.
• Whereby or Daily.co plugin: Embeds video rooms directly inside the Bubble app. Whereby's API allows room creation and custom room naming. Daily.co offers more configuration options for room size, recording, and access controls. Both have Bubble-compatible plugins in the marketplace.
• SendGrid plugin: Sends booking confirmations, session reminders (24 hours before), and post-session review request emails. Use transactional templates with dynamic fields for tutor name, date, time, and video room link.
• Air Date/Time Picker: Provides the date and time selectors in the tutor availability configuration form and the student booking interface. Critical for accurate timezone handling. Ensure the plugin stores times in UTC and displays in the user's local timezone.
• Full Calendar plugin: Renders the tutor's availability calendar as a visual weekly or monthly calendar view. Students see available slots highlighted; booked slots are greyed out. The plugin integrates with AvailabilitySlot records to display real-time availability.
• Chart.js or Bubble Charts plugin: Powers the tutor earnings analytics dashboard: session volume over time, earnings by subject, peak booking days. Pulls from Session and Payment records filtered by the current tutor user.
• Bubble's Repeating Group: Renders tutor search results, session history lists, and review feeds natively. Sort by rating, price, or availability dynamically based on student filter selections.

How Long Does It Take and What Does It Cost to Build a Tutoring Platform App with Bubble?

Tutoring platforms are one of the more ambitious Bubble builds in the education space. The combination of marketplace logic, Stripe Connect, video delivery, and booking prevents this from being a short project regardless of who builds it.

Scoping the first phase tightly is the difference between a successful Bubble MVP development and a build that never ships. An MVP that covers profiles, booking, and Stripe Connect payment is a complete and marketable product. Video, reviews, and analytics are phase two.

The Growth plan is required for scheduled backend workflows (session status updates, payout triggers) and the API call volume generated by Stripe Connect webhook processing. High-traffic platforms or teams with multiple builders need the Team plan. Whereby and Daily.co have their own usage-based pricing separate from Bubble's plan costs.

Conclusion

Bubble enables tutoring marketplace platforms when the AvailabilitySlot data model and Stripe Connect integration are built correctly from the start.

Build profiles, booking, and Stripe Connect first. Weak availability logic creates double-booking failures that are expensive to fix once the platform is live.

Bubble App Development

Bubble Experts You Need

Hire a Bubble team that’s done it all—CRMs, marketplaces, internal tools, and more

Let's talk

Need Help Building Your Tutoring Platform on Bubble?

Tutoring platforms combine Stripe Connect split payments, AvailabilitySlot-based booking logic, and video room access control. Each of these requires precise backend architecture. Errors in any one layer create financial or operational failures that are difficult to patch post-launch.

• Data architecture: We design your data types, option sets, and privacy rules before writing a single element on the canvas.
• Workflow engineering: We build backend workflows, scheduled jobs, and API integrations with proper logic and error handling.
• Plugin configuration: We select and configure the right Bubble plugins for your feature set without unnecessary bloat.
• Role-based access: We implement privacy rules at the database level, not just conditional UI visibility.
• Integration setup: We connect your Bubble app to Stripe, SendGrid, Twilio, and other services correctly from day one.
• Pre-launch testing: We test against real data before deployment so every workflow performs correctly under live conditions.
• Post-launch support: We stay involved after go-live to optimize as real usage data shapes the app.

We have built 350+ products for clients including Coca-Cola, American Express, Sotheby's, and Medtronic. We know exactly where Bubble builds fail and we address those problems before they surface.

If you want your Bubble app built correctly from day one, let's scope it together.