Showcare
"One platform. Every event workflow."
Associations and non-profits running events, membership and sponsorship programs were managing registration, marketing and onsite execution across fragmented systems, each requiring its own manual upkeep.
How to read this case study: what I owned, what shipped and the verified outcome (My Role, What Shipped and Impact below) are factual. The surrounding strategy, vision, alternatives and metrics framework are interview-ready framing built on those facts, how I'd talk through the product thinking, not a claim that every metric or GTM motion was formally run at the time.
Challenges & baseline.
Challenges
Associations running events needed registration, marketing and membership tools that worked together, not a set of separate systems each needing its own manual upkeep, with onsite execution suffering when they didn't. Fragmentation across registration, marketing, onsite and reporting tools is a recognised problem in enterprise event technology generally.
Baseline
Event operations before a unified platform: fragmented systems across registration, marketing and onsite support, standardised on a per-client basis.
What the customer actually needed.
Insight
Associations don't really buy event management software, they buy confidence that a high-stakes event will actually work when thousands of people arrive. That means reliability, deadlines and services matter as much as feature breadth, and events introduce a constraint most SaaS products don't have: the deadline cannot move. A feature delivered two weeks late is annoying in most software; a registration capability arriving two weeks after the customer's conference is worthless.
Job to be done
When my association is running a major event, give me one connected system for registration, marketing, sponsorship and onsite execution, so I'm not manually reconciling several tools while thousands of people are arriving.
Vision, mission & the bets we made.
Every association runs events on one connected platform instead of a patchwork of separate tools.
Pair association-focused technology with expert services so event, membership and sponsorship growth doesn't depend on stitching systems together in-house.
Consolidate fragmented registration and event-management systems into one platform per client; standardise workflows so onsite execution doesn't depend on tribal knowledge; keep the squad shipping against real client event calendars, not just a backlog.
Ship and maintain the registration and event-management product a squad owns within Showcare's platform; support onsite execution across association client events; keep delivery paced against clients' live event calendars.
Strategic bets
- Consolidate fragmented registration and event systems into one platform per client instead of leaving associations to stitch tools together themselves
- Standardise the repeatable 80% of the workflow while configuring the differentiated 20%, so the product doesn't collapse into bespoke agency work
- Standardise workflows across clients so onsite event support doesn't depend on one person's tribal knowledge
- Pace squad delivery against clients' real event calendars, since a missed deadline shows up live at someone's conference, not quietly in a backlog
Alternatives considered
The alternative to consolidation was letting every client's workflow stay bespoke, more flexible per client, but it turns the business into an agency rather than a platform. The alternative to standardisation was full customisation for every association, but that breaks at scale and puts event-day risk on tribal knowledge. The direction that held up was standardising the repeatable 80% of the workflow while configuring the differentiated 20%, enough consistency to ship reliably, enough flexibility for enterprise associations to actually use it.
What I owned.
Squad Lead, led a product and engineering squad within Showcare's platform team.
What shipped.
Showcare's platform gives associations a single system for event registration, marketing, sponsorship and membership, backed by a services team for onsite support, used across medical, science, education, government and trade-association clients.
How it got built.
Worked with clients to map their existing, fragmented registration and event workflows before consolidating them onto the platform
Led the squad's delivery cadence against live client event calendars, where a slip is visible onsite, not just in a backlog
Standardised workflows across association clients so onsite execution didn't depend on one person's memory
Coordinated with Showcare's services team so platform changes matched what they needed to support events in person
How this reaches customers.
Land: registration around one major event, the highest-stakes, most visible workflow an association runs. Expand: registration into onsite support, then marketing, then sponsorship, then the broader membership platform, a classic enterprise land-and-expand motion, sold consultatively rather than self-serve given the operational stakes involved.
North star metric.
Supporting metrics
- Recommended North Star going forward: percentage of events successfully operated without a critical platform failure, rather than client-sector count alone
- Registration completion rate and check-in success rate
- On-time readiness ahead of each event date
- Client retention and platform adoption across the registration, marketing, sponsorship and membership modules
Guardrails
- Support incidents per 1,000 attendees
- Event-day uptime
- Registration conversion rate
The verified bottom line.
Gave associations a platform that consolidates registration, marketing and membership instead of a patchwork of separate systems, with a squad shipping against clients' live event calendars, not just a backlog.
What I'd do differently.
Shipping against a backlog and shipping against someone's live conference date are different disciplines, a slipped ticket is invisible, a slipped feature onsite isn't. Standardising workflows across clients mattered less for consistency's sake and more because it's what let the squad actually hit those dates without depending on one person's memory. The broader lesson: roadmap priority isn't just business value versus development effort, time itself can be a product constraint, a feature delivered after an immovable customer event has effectively delivered zero value.
More proof, more products.
See every product shipped and business built.