CARA A. BROWN, MBA • DESIGN STRATEGIST + SERVICE DESIGNER
CARA A. BROWN, MBA • DESIGN STRATEGIST + SERVICE DESIGNER
A service platform that coordinates brands, venues, bartenders, and patrons — turning promotion spend into a closed-loop engagement and feedback system.
Dwinker was developed within Foster Brand, a marketing agency. The visual identity shown throughout pitch materials reflects Foster Brand's brand language and is included here for context. The service design, ecosystem model, business model, journey logic, and prototype were my work.
Beverage and spirit brands spend heavily at venues — events, activations, free pours — but consistently lack a reliable way to capture patron insight, preference feedback, or post-event re-engagement signals tied to that spend. Money went out. Nothing came back.
The problem wasn't the spend. It was that the promotion model wasn't designed to produce value for anyone except the venue getting foot traffic in the moment. Brands had no data. Patrons had no continuity. Bartenders had no incentive to participate. The system was leaking value at every handoff.
The three core breakdowns the platform was designed to solve — inefficient spending, lack of data, and stakeholder disconnection.
Connected to promotions — not disconnected from them. Every activation produces data and a follow-up channel.
A reliable pipeline for brand-sponsored events and specials, without ad-hoc coordination.
An incentive to participate authentically — their service becomes a measurable part of the experience.
Real value for engagement — not a loyalty points scheme. Immediate, tangible, experience-first.
The ecosystem diagram — who participates and how value moves across the system.
Ecosystem design isn't about building an app. It's about designing the rules of engagement so multiple parties can coordinate sustainably — and each one wins by participating.
Discover specials and brand-sponsored events at participating venues. The entry point is value-first — no account required to see what's available.
Capture intent and create a measurable pre-visit signal. This is where the data collection begins — before the patron walks in the door.
Phone-based redemption at the bar. The bartender is part of the system — their participation is acknowledged and rewarded, not ignored.
Follow-up offers — a second drink, an off-premise coupon — close the loop. The re-engagement signal is what makes the brand's original spend measurable.
The minimum end-to-end flow the prototype demonstrated — from discovery to closed-loop re-engagement.
Alcohol distribution in the US operates under a three-tier legal structure — producer, distributor, retailer — that constrains who can offer what to whom. The service model had to be designed around these constraints, not against them. Legal realities determined MVP scope before any technical decisions were made.
Not every part of the value exchange could be brokered by the platform — some elements required direct brand relationships, others required venue coordination outside the app. The platform's job was to facilitate, standardize, and measure what happened in between. Knowing where the platform's responsibility began and ended was a core design output, not an afterthought.
Industry structure, legal constraints, and promotion budgets — the real-world factors that shaped the service model and MVP scope.
Customer segments and revenue logic aligned to the platform ecosystem — built to reflect how each stakeholder creates and captures value.
Prototype walkthrough — demonstrates the end-to-end patron journey from browse through re-engagement. Click-through fidelity, not launch-ready code.
The challenge: Three breakdowns — inefficient spending, lack of patron data, and stakeholder disconnection. The problem framing that anchors the pitch.
Ecosystem / value exchange: How each participant gains value — and how those gains are structurally connected so the system is self-sustaining.
Platform positioning: How the service model differs from existing mechanisms in the space — and why existing alternatives don't solve the core problem.
MVP flow: Browse → RSVP → Redeem at bar → Re-engage. The minimum end-to-end journey the prototype needed to demonstrate.
Industry constraints: Legal structure, promotion budgets, and operational realities — the feasibility layer that shaped platform scope before any UI decisions.
Business model: Customer segments, revenue streams, and value creation logic — built to reflect how each stakeholder creates and captures value across the ecosystem.
Competitive landscape: Context against the existing alternatives in the space — and the gaps that make the Dwinker model structurally differentiated.
Competitive advantages: Why the model is designed to be durable — each stakeholder's gain depends on the others' participation, creating a self-reinforcing system.
The design challenge wasn't the app. It was coordinating four stakeholders with different incentives so each one gains value by participating — and loses value by opting out. That's an ecosystem problem, not a product problem.
Every touch in the journey was designed to generate a measurable signal. RSVP = intent. Redemption = visit confirmation. Re-engagement = preference and loyalty data. The loop was the value proposition — not an add-on.
Legal structure, promo budgets, and operational realities were mapped before any prototype decisions were made. Feasibility isn't a later-stage concern — it's a design input. The platform model reflects what the industry can actually support.
This project is often described as a startup concept — it's more accurately a service architecture problem. How do you design a system where four parties with different incentives all gain enough value to sustain their participation? The prototype was a communication tool. The real work was the ecosystem model: who participates, under what rules, in exchange for what, and how the platform holds the system together without owning every interaction.
How I Work →