MODULE 03 — The Raising Club

Events and community programming

Classes, open play, workshops and ongoing series — online or in person, free or paid, run by The Raising Club or by partner organisations.

See it live at theraisingclub.com
“They delivered on time and were very proactive in recommending new capabilities for the marketplace.”
Ara VazquezFounder, The Raising Club
Client
The Raising Club
Sector
Childcare · Marketplace · EdTech
Built
2026
Timeline
First commit 29 May 2026 · five-module platform in production 2 July 2026
The public events browser — age, format, price and style filters over live listings.

What it does

Capabilities

  • Four event styles — guided class, open play, workshop and ongoing series — each with sessions, locations, instructors and capacity.
  • Filtering by child age from newborn to twelve-plus, online versus in person, location, price band, attendance type and date range.
  • Registrations record which children are attending, with waiver acceptance captured per registration.
  • Paid events run through the same Stripe checkout and webhook as courses and subscriptions — one payment path, three revenue lines.
  • Organisations host their own events under their own profile, with attribution on the listing.
  • Automated reminders, plus an event credits ledger for cancellations.

How people use it

The journeys it was designed around

A parentBook a Saturday class for a two-year-old

  1. Filters events by the child’s age, online or in person, location, price band, who attends (children with an adult, children only, adults only), date range and event style.
  2. Opens an event to see sessions, location, instructor, capacity and price.
  3. Registers, selecting which of their children are attending — the platform already knows the children from their profile.
  4. Accepts any waiver the event requires; the acceptance is recorded against that registration, not just the account.
  5. Pays through Stripe if the event is paid, or confirms immediately if it is included in their membership.
  6. Receives automated reminders before the session, and finds it under their own events list.

An organisationRun programming under its own brand

  1. Creates an event under the organisation profile, with its own locations and instructors.
  2. Sets the style, age range, capacity, price and session schedule, including ongoing series with multiple sessions.
  3. Publishes it into the same public browser as first-party events, attributed to the organisation on the listing.
  4. Manages registrations and messages attendees from the event record.

How it is built

Implementation and the rules real users find

Under the hood

  • Events, sessions, locations, instructors, categories, resources, saves, registrations and per-child registration rows are separate tables — a recurring series is sessions under one event, not duplicated events.
  • Waivers are versioned documents with their own acceptance records, so it is always answerable which text a given parent agreed to and when.
  • Paid events reuse the same Stripe checkout session and the same webhook as courses and subscriptions; fulfilment confirms the registration and fires a notification.
  • An event credits ledger holds value back when something is cancelled, rather than forcing an immediate refund path.
  • Reminders are scheduled records rather than ad-hoc jobs, so what was sent and what is pending is inspectable.

The rules real users find

  • Capacity is enforced server-side at registration time — two parents registering the last place simultaneously cannot both succeed.
  • A registration knows which children it covers, so an event with a per-child price and a family with three children resolves correctly.
  • “Included” events show as included rather than as $0, because the two mean different things to a member.
  • Organisation-hosted events carry attribution on the listing, so a parent always knows who they are actually booking with.

The screens

Taken from the live product

Click any shot to enlarge.

The rest of the platform

All 5 modules

These were built on one schema and one permission model, which is the only reason all 5 of them could ship together.

Who built this

Senior engineering, not an account manager

SigmaticAI is led by Ketan Khamgaonkar — an IIT Roorkee M.Tech who went on to PhD research at IIT Bombay before spending four years building AI automation, agentic systems and full web and mobile products. On every project you talk to the person writing the code.

  • M.Tech, IIT Roorkee
  • PhD research, IIT Bombay
  • 4+ years shipping production software

Need a events and community programming of your own?

No pitch deck. Tell us what you are trying to ship and we will tell you the fastest honest path to live — including if that path is smaller than you thought.

Read the full case study

Tell us about it

Name and email are all we need — the rest helps us come back with something useful.