Tandem
Get matched with providers who fit your style, your goals, and your schedule.

- Role
- Solo builder
- Status
- Prototype, built in under 24 hours
- Category
- Two-sided marketplace
- Stack
- Bolt.new, Supabase
Context
Tandem began as a rapid prototyping experiment. I wanted to see what I could build in a single day using no-code tools, starting with a simple question: what kind of product could solve a real-world problem and make money quickly?
After exploring different ideas, I focused on a common pain point: finding a coach, tutor, or specialist who truly fits your style and goals. Most platforms are built around task-based transactions. Very few prioritize long-term relationships, personal growth, and fit.
With that in mind, I built Tandem as a lightweight matchmaking tool. It helps users find providers who align with their goals, while giving providers an easy way to manage clients, track progress, and grow their business.
- Target audience
- Individuals seeking personal growth, independent service providers.
- Purpose
- To explore how quickly I could go from idea to prototype using no-code tools while solving a real-world problem with clear monetization potential.
Tandem was built to help people find the right kind of support, whether physical, mental, or educational, by simplifying how we connect with coaches, tutors, and service providers. It focuses on removing friction, building trust, and making human connections feel more accessible.
Problem statement
Finding the right service provider is frustrating and time-consuming. Whether someone is searching for a fitness coach, a tutor, or a wellness expert, the current options are fragmented, overwhelming, and often impersonal. Most platforms prioritize transactions instead of trust, leaving users with too many choices and not enough clarity. Providers are also left without the tools they need to build long-term client relationships.
Tandem solves this by offering a simple and personalized matchmaking experience that connects people to providers who align with their goals, style, and preferences.
Mock KPI goals
- Time to match. Help users find and message a provider in under 5 minutes
- Provider engagement. At least 50 percent of providers log in weekly and respond to messages
- Conversion rate. 20 percent of site visitors complete the client intake form
- Provider satisfaction. 75 percent or higher satisfaction from a quick dashboard feedback prompt
- Prototype build time. Launch a working version of the platform within 24 hours
Since this is a prototype, mock KPIs and results are represented as part of this case study.
Approach
Research and analysis
In exploring the opportunity to build a simple and scalable matchmaking platform, I began with a focused objective: create a lightweight MVP that could deliver immediate value, prove demand, and open pathways for monetization. With time as a constraint and clarity as the priority, the approach centered around rapid ideation, user-focused problem definition, and iterative no-code development.
Evaluation of the market landscape
To determine the best starting point, I assessed the current landscape of service discovery tools. Platforms like Thumbtack, TaskRabbit, and Yelp offer broad provider access but often prioritize volume over personalization. These platforms are optimized for transactional, one-off tasks, and lack tools for relationship-based services such as coaching, tutoring, or personal development. Many also carry high barriers to entry for new providers, require steep fees, or lack trust-building tools for users.
This evaluation revealed a clear gap in the market: an approachable, trust-first solution for users seeking consistent support, and a lightweight business toolkit for providers working independently or in small teams.
Product strategy and framing
With the target problem identified, I outlined a product strategy focused on speed to value and expandability. The first version of Tandem would focus on fitness and tutoring as early verticals, while establishing a foundation that could scale to include other services like wellness coaching, language instruction, and creative skills training.
- Starting with a two-sided structure, giving both users and providers tailored experiences
- Prioritizing core user journeys like onboarding, matching, and communication
- Using a no-code toolset (Bolt.new and Supabase) to reduce build time and increase flexibility
- Including basic analytics and communication features to simulate real business utility for providers
- Designing a brand and name flexible enough to grow beyond the initial niche
UX and functional priorities
- A "Match Me" form that collects user preferences across goals, experience level, and availability
- A provider sign-up and dashboard experience that includes a schedule view, client list, and quick messaging access
- Smart, AI-assisted matching logic that pairs users with appropriate providers based on multiple data points
- A clean, modern UI that reflects approachability and professional trust
The initial prototype of Tandem was developed and deployed in under 24 hours. The app includes a functional onboarding flow, basic two-sided matching, a working provider dashboard, and a plan for multiple monetization paths. The process validated that real, usable tools can be created in compressed timeframes when guided by clear goals and user needs.
Strategy
Vision: to simplify the way people discover and connect with service providers by creating a human-centered platform that emphasizes personalization, trust, and ease of use. Tandem aims to empower individuals in their personal growth journeys while giving providers the tools to build sustainable, client-focused businesses.
- Personalized matching. Design a smart intake and matching flow that connects users with providers based on goals, availability, preferences, and communication style.
- Two-sided experience. Build parallel experiences for users and providers, with tailored features that support discovery, communication, and ongoing engagement.
- Provider tools. Develop a lightweight dashboard for providers that includes appointment scheduling, client management, basic analytics, and messaging.
- Trust and simplicity. Create an intuitive, accessible interface that builds user confidence and lowers friction during onboarding and engagement.
Solution
Tandem was designed to help users find service providers who align with their goals, preferences, and lifestyle. The platform streamlines discovery, communication, and client management for both sides of the marketplace.
Backend
- Scalable no-code stack. Supabase provides user authentication, database storage, and real-time updates, enabling rapid development while leaving room for growth.
- Two-sided architecture. Separate logic and database schemas for users and providers support different onboarding flows, dashboards, and interaction modes under one experience.
- Smart matching logic. Intake responses are matched to provider profiles based on availability, service category, goals, and preference tags. Matching can later be enhanced with AI.
- Integrated messaging. Built on Supabase's real-time capabilities, providers and clients message directly through their dashboards, with attachment uploads and a record of every interaction.
Frontend
- Clean, modern interface. A minimal, welcoming design system built in Bolt.new that keeps users focused on their next step.
- Provider dashboard. Upcoming appointments, client lists, messages, and analytics showing client activity and income trends.
- User intake flow. A dynamic form that collects preferences, goals, and availability, building trust through a personalized approach.
- Quick actions menu. A floating bar that lets providers switch between messaging, schedule, and client details.
Challenges and iterations
- Designing for two audiences in one platform. Parallel but clearly defined interfaces using conditional logic, with shared components like messaging and scheduling reused with role-specific labels. Ongoing user testing informed adjustments to flow and layout.
- Matching without advanced AI. The intake form was refined to capture more structured inputs, enabling smarter tag-based filtering. Plans were documented for a conversational assistant that could assess learning styles, personality fit, and goals.
- Real-time messaging in a no-code stack. Supabase real-time subscriptions sync messages instantly in the Bolt interface, with Supabase storage handling attachments.
- Business tools without building a CRM. The provider dashboard ships with just enough: a weekly schedule, income tracker, and client list, with feedback and booking history planned.
- A brand that can grow. An early barbell icon made the product feel narrowly focused. The logo was reworked around connection and duality, and the palette shifted from bold fitness tones to greens and neutrals that signal growth and trust.
Mock results and learnings
Time to match
Users completed the matchmaking flow and sent a first message in about 4 minutes
Goal: Find and message a provider in under 5 minutes
Provider engagement
Simulated tracking suggested 60% of active providers returned in week one and replied to a new client
Goal: At least 50% of providers log in weekly and respond
Conversion rate
Early testing with simulated traffic indicated a projected 26%
Goal: 20% of visitors complete the intake form
Provider satisfaction
Initial usability tests showed 78% positive response
Goal: 75% or higher on a dashboard feedback prompt
Results are mock or simulated, as this was a prototype.
Lessons learned
- Design for dual audiences from the start. Planning for both roles early avoided rework and delivered value on both sides of the marketplace.
- Balance simplicity with flexibility. Lightweight intake and dashboard tools felt approachable while leaving room for deeper customization.
- Build fast, then refine. Launching an MVP in under 24 hours showed the power of rapid prototyping, and the importance of iterating on feedback rather than aiming for perfection upfront.
- Plan for scale beyond one industry. Flexible branding, architecture, and matching logic position Tandem to expand without major changes.
- Don't overbuild the first version. Staying focused on matching, messaging, and dashboards avoided scope creep and kept the build achievable.