How One Creation Flow Handles Every Experience

A backyard BBQ and a competitive padel tournament have almost nothing in common — except that both should be easy to set up on the same platform.

This is one of the hardest problems in building Sledge. We don't just handle events. We handle experiences — and experiences vary wildly. A Sunday potluck needs a location, a time, and a headcount. A multi-round tournament needs teams, brackets, scheduling, and scoring. A pasta masterclass needs skill levels, equipment, and session formats.

If we gave every host the same 40-field form, most of them would abandon it before finishing. If we gave them a stripped-down form, competitive hosts wouldn't be able to describe what they're running.

So we built something different.

The Spectrum Problem

Think about the range of things people actually do together in real life:

• Casual gatherings — a BBQ, a park hangout, a board game night. Pick a place, pick a time, show up.
• Structured sessions — a cooking class, a yoga workshop, a photography walk. There's a format, a skill expectation, maybe equipment involved.
• Competitive events — a tennis ladder, a padel tournament, a chess round-robin. Teams, brackets, scores, standings.

These aren't different products. They're different depths of the same thing: people coming together around a shared activity.

The question we had to answer was: how do you build one creation flow that handles all of them — without being overwhelming for the simple cases or insufficient for the complex ones?

Progressive Depth, Not Progressive Complexity

The core insight behind our approach is that activities have a natural depth of commitment. Some activities are self-describing — you say "BBQ" and everyone knows roughly what to expect. Others require layers of detail before they make sense to a potential participant.

Instead of building separate flows for different types of experiences, we built a single flow that adapts based on what you're creating.

Here's how it works in practice:

Layer 1: The universals. Every experience on Sledge starts with the same core questions: What are you hosting? Where is it? When is it happening? How many people can join? These are always relevant, regardless of whether you're running a BBQ or a tournament. They form the foundation.

Layer 2: The activity shapes the form. Once you select an activity — say, Padel — the form adapts. Padel has concepts like skill level, competition format, and team size that a potluck doesn't. The system knows this, and it surfaces the right fields. You don't see irrelevant questions, and you don't miss important ones.

Layer 3: The format deepens it further. Within an activity, the format matters. A casual padel session needs a court and a time. A padel tournament needs groups, brackets, match scheduling, and score tracking. Selecting "Tournament" as the format unlocks that deeper layer — but only when it's relevant.

Layer 4: Follow-ups fill in the details. Some choices trigger follow-up questions. If you say equipment is required, we ask what kind. If you set a recurring schedule, we ask about end conditions. These aren't pre-loaded — they appear only when your earlier answers make them necessary.

Why This Matters for Hosts

The practical result is that the form meets you where you are.

If you're hosting a simple gathering, you'll see a short, clean form that takes a couple of minutes. If you're organizing a competitive event, the form will guide you through the additional structure — team sizes, brackets, scoring rules — without making you hunt for settings in a separate "advanced" menu.

This isn't about hiding complexity. It's about revealing it at the right moment.

A few examples of how this plays out:

• Backyard BBQ — Select "Cooking" as the activity, pick your time and place, set a headcount. Done. The form doesn't ask about team sizes or competition formats because they don't apply.
• Pasta Masterclass — Select "Cooking", then choose "Workshop" as the format. Now the form asks about skill level, session duration, whether participants need to bring equipment. The activity is the same, but the format changes what's relevant.
• Padel Tournament — Select "Padel", choose "Tournament" as the format. Now you're into team configuration, group stages, knockout brackets, court assignments. The deepest level of the system — but only because this specific combination requires it.

Six Dimensions, One System

Sledge organizes all activities across six broad categories — what we call the SLEDGE framework: Sports, Learning, Education, Development, Growth, and Empowerment. Each represents a dimension of real-life experience, from competitive athletics to personal development workshops to community volunteering.

The creation flow works the same way across all six. Whether you're setting up a 5-a-side football match (Sports), a weekend photography course (Learning), or a neighborhood cleanup drive (Empowerment), the system adapts. Different activities surface different fields, but the underlying flow is consistent.

This means we can support an enormous range of experiences without building separate tools for each one. One system, one flow, one learning curve for hosts — regardless of what they're creating.

What's Next

We're actively building this out across iOS, Android, and Web. The creation experience is live today, and we're continuing to refine how the form adapts — making it smarter about which questions to surface, when to ask follow-ups, and how to present complex options without overwhelming new hosts.

The goal hasn't changed: make it as easy to set up a tournament as it is to plan a BBQ. Not by dumbing down the tournament, and not by overcomplicating the BBQ. By building a system that understands the difference.

One platform. Every kind of experience.
The form adapts — so you don't have to.