Founder Work
Founder Marketplace Architecture AI Merchant Intelligence MVP · Salon Vertical

Mighty Coupons —
Coupon-Driven Local Service Marketplace

New local businesses face a structural cold-start problem: no prior signal, no review history, no mechanism to earn local trust quickly. I designed Mighty Coupons as a decision architecture problem — structuring how authority, trust, and AI-bounded intelligence operate across a two-sided marketplace to make the first merchant-consumer exchange reliable by design.

My Role Head of Design & Product Innovation
Marketplace architecture · Consumer decision flows · Merchant tooling · AI boundary design
Team 6-person founding team
Founder (PhD, Google) · Engineer (PhD, Microsoft) · 2 Engineers (TikTok) · Marketing Lead
Platform Type Two-sided Local Marketplace
Merchant dashboard (desktop-first) · Consumer app (mobile-first)
Stage Beta · Salon vertical
Early merchant users in testing · Category expansion planned
Executive Summary
  • Market volatility raises the cost of early customer acquisition for new local businesses. Mighty Coupons addresses this structurally — coupon-driven discovery gives merchants a measurable, low-cost entry point into local consumer awareness.
  • The platform is a two-sided marketplace: a desktop-first merchant dashboard for coupon campaign management and booking operations, and a mobile-first consumer app for nearby deal discovery and direct service booking.
  • Three interlocking mechanisms define platform integrity: verified merchant identity, a standardized "control variables" offer schema for comparability, and an AI layer that surfaces operational and coupon strategy insights to merchants.
  • MVP is deliberately scoped to the Salon vertical — a category chosen for its appointment density, promotion sensitivity, and repeat-visit frequency. Early merchant beta testing is underway.
01 / 08

Project Overview

Mighty Coupons originated from a structural observation: market volatility has made the earliest phase of local business growth — attracting the first wave of customers — disproportionately difficult. Established businesses have brand recognition and prior engagement signals that feed discovery algorithms. New businesses enter with no prior signal, no review history, and no structural mechanism to earn local trust quickly.

The platform's response is a coupon-driven discovery model. Promotional offers serve as the entry point — they give consumers a concrete, low-risk reason to try an unfamiliar business, while giving merchants a measurable and controllable mechanism for early customer acquisition. The surrounding infrastructure — verification, booking, and AI intelligence — ensures that exchange is reliable and structurally sound for both sides.

"The coupon is not a discount mechanism. It is a structured entry point — a controlled offer that gives consumers a reason to try a business they have not encountered before."

Team
Head of Design & Product Innovation My role · Full platform design scope
Founder PhD · Google background
Engineer PhD · Microsoft background
Engineer TikTok background
Engineer TikTok background
Marketing Lead Growth & merchant acquisition

Operating context: No dedicated product management layer exists in this team. All product strategy, design architecture, and cross-functional coordination between engineering and marketing runs through my role. The scope is structural, not positional.

02 / 08

Market Context

The problem Mighty Coupons addresses is structural, not cyclical. New local businesses face a compounding set of conditions that make the early customer acquisition phase disproportionately expensive and unreliable regardless of service quality.

Condition 01
Market Instability Increases Consumer Risk Aversion
Economic volatility makes consumers more selective about where they spend. Spending defaults to familiar, trusted providers. New businesses — regardless of service quality — face an elevated trust deficit precisely when they most need discovery volume.
Condition 02
Discovery Channels Are Structured for Established Brands
Paid advertising rewards budget scale. Algorithmic discovery rewards prior engagement signals. Review aggregators require a volume of past customers that new businesses do not yet have. None of these channels solve the structural cold-start problem.
Condition 03
Promotional Offers Exist Without Booking Closure
Merchants create promotional offers but distribute them through channels with no appointment-booking infrastructure. Consumer intent is generated but not captured. The conversion loop is structurally open — awareness without a path to a confirmed service visit.

Design implication: The correct intervention is not a cheaper ad product or a better directory. It is a platform that connects standardized promotional offers from verified merchants to proximity-based consumer intent — and closes the loop with a booking system that converts discovery into a confirmed service appointment.

03 / 08

Product Vision

The platform is built around three structural mechanisms that define how trust, comparability, and merchant intelligence operate. These are architectural commitments — not features — that determine what kind of exchange the platform can reliably facilitate.

Mechanism 01
Verified Merchant Identity
Consumer trust in a local marketplace depends on knowing that listed businesses are real and operating. Verification is an identity confirmation — not a quality rating. Unverified merchants are structurally absent from consumer-facing discovery. This is an architectural constraint enforced at the data layer, not a policy filter.
Mechanism 02
"Control Variables" Offer Standardization
Offers across the platform share a standardized schema — service type, discount format, duration, and redemption conditions. This structure makes offers inherently comparable for consumers and measurable for AI analysis. It also creates the consistent data substrate that supports platform-level intelligence over time, as offer volume scales.
Mechanism 03
AI Merchant Intelligence Layer
AI is scoped to the merchant side of the platform — where data asymmetry is highest. Merchants can observe their own bookings; they cannot see platform-wide demand patterns or comparative offer performance. The AI layer closes that gap: surfacing analysis of coupon strategy effectiveness, service demand signals, and operating model recommendations derived from the standardized offer data structure.
04 / 08

Platform Architecture

The platform is structured around three interdependent systems, each designed for the operating context of its primary user.

The Consumer System is mobile-first — discovery and booking happen close to the point of service, on the move. Consumers search for verified merchants nearby, browse and compare standardized promotional offers, discover deals, and complete service bookings without leaving the app. The interface is structured as a decision flow — proximity, offer comparison, and direct booking as a sequential low-friction path — not a passive directory.

The Merchant System is desktop-first — managing coupon promotions, tracking service demand, evaluating promotion performance, and controlling booking schedules is a deliberate operational task requiring a full-surface interface. A merchant verification system gates platform access: only confirmed, legitimate businesses are permitted to publish listings and appear in consumer-facing discovery. Verification is enforced at the data layer — not as a policy filter, but as an architectural prerequisite.

The AI Intelligence Layer sits on the merchant side, where data asymmetry is highest. Merchants can observe their own bookings; they cannot see platform-wide demand patterns or comparative offer performance. The AI layer closes that gap — surfacing coupon strategy analysis, service demand signals, and operating model recommendations derived from the platform's standardized offer data structure. Scope is explicitly bounded to decisions the data can support.

System Architecture · Two-Sided Marketplace
AI Layer Platform Core Actors
AI
Layer
Platform
Core
Actors
Supply Side Desktop
Merchants
Local businesses · Salon MVP
  • Create & manage coupon promotions
  • Set availability and booking schedules
  • Review demand analytics dashboard
  • Receive AI-generated strategy recommendations
Demand Side Mobile
Consumers
Nearby deal discovery
  • Search for nearby verified merchants
  • Browse & compare standardized offers
  • Book services directly in-app
  • Generate demand signal data through behavior
Fig. 01 Three-layer marketplace architecture. Hover any platform component for function, purpose, and marketplace impact. Value flows from merchants through the platform core to consumers; demand signals feed back through analytics and AI to inform merchant strategy.
Marketplace Growth Loop Self-reinforcing flywheel · Salon MVP → category expansion
01
Consumer Discovery Consumers find nearby verified deals via mobile app
02
Booking Volume Confirmed appointments generate demand signal data
03
Merchant Adaptation AI insights guide merchants to adjust promotions
04
Better Offers Higher-quality, more relevant deals appear on platform
05
Platform Growth More consumers join → loop compounds
Consumer Experience Flow

Hover each node to see how the step functions within the full consumer decision path.

Step 01
Search Nearby Deals
Location + service intent triggers proximity-based discovery.
Hover for detail
Step 02
Deal Discovery
Comparable offers surface ranked by proximity and relevance.
Hover for detail
Step 03
Booking Service
In-app booking converts intent into a confirmed slot.
Hover for detail
Step 04
Service Experience
Consumer visits the merchant and redeems the coupon offer.
Hover for detail
Step 05
Review / Feedback
Post-visit signal enriches merchant trust and platform learning.
Hover for detail
Merchant Operations Flow

Hover each node to understand the merchant-side workflow and how each step generates platform data.

Step 01
Create Promotion
Standardized schema structures offer for cross-merchant comparability.
Hover for detail
Step 02
Coupon Strategy
First-visit discounts and seasonal offers drive early acquisition.
Hover for detail
Step 03
Booking Management
Desktop dashboard controls schedules and prevents double-bookings.
Hover for detail
Step 04
Demand Analytics
Booking patterns reveal service demand and offer performance.
Hover for detail
Step 05
AI Recommendations
Bounded insights surface where data can support a recommendation.
Hover for detail
Platform Role — Mighty Coupons Engine

Hover each cell to understand the platform function and why it is structurally necessary.

Input
Consumer Demand
Location-aware intent from consumers searching nearby services and promotions.
Hover for detail
Discovery Layer
Deal Discovery Engine
Surfaces verified, standardized offers ordered by proximity and relevance.
Hover for detail
Shared Infrastructure
Booking Infrastructure
Converts discovery intent into confirmed appointments; closes the consumer loop.
Hover for detail
Trust Gate
Verified Merchant Layer
Architectural prerequisite — unverified merchants are structurally absent from discovery.
Hover for detail
Merchant Intelligence
Merchant Analytics
Aggregates booking and offer data into actionable demand and performance signals.
Hover for detail
AI Layer
AI Insights Engine
Scoped to merchant-side decisions — strategy, demand timing, operating model improvements.
Hover for detail
05 / 08

MVP Focus: Salon as the Initial Wedge Market

The MVP is scoped to a single service vertical — the Salon category — before expanding to additional business types. This is a deliberate product strategy decision, not a resource constraint. Two-sided marketplaces carry an inherent cold-start risk: without sufficient merchant supply, consumer demand does not materialize; without consumer demand, merchants see no reason to participate. Launching across multiple categories simultaneously amplifies this risk and produces a thin, low-trust experience on both sides. Focusing on one category allows the platform to validate its core mechanics in a controlled environment — building sufficient depth in a single vertical before the expansion model is activated.

Business Reasoning for the Salon Wedge
  • 1
    Single-category launch reduces cold-start risk. Marketplace cold-start is a structural problem: supply without demand and demand without supply are both inert. Concentrating the initial merchant acquisition effort and consumer discovery surface on one vertical builds liquidity in a focused area rather than spreading thin across many categories. A dense, trusted Salon supply is more valuable to early consumers than a sparse multi-category listing.
  • 2
    Appointment-based and promotion-sensitive by category default. Salon services run on scheduled appointments, which maps directly to the platform's booking system. Consumers in this category already expect and actively search for promotional offers — first-visit discounts, seasonal deals, and service bundles are category norms. The coupon-driven discovery model fits without requiring a change in consumer behavior.
  • 3
    High consumer search frequency for nearby salon deals. Salon services are among the most actively searched categories in local deal and coupon contexts. Consumers regularly search for nearby salon promotions — particularly for first-time visits to an unfamiliar provider. Consumer intent is structurally present; the platform intercepts it with verified, comparable offers and a seamless booking path.
  • 4
    High repeat-visit frequency creates compounding platform value. Salon services are not one-time transactions. Consumers return on a predictable cycle — haircuts, coloring, nail care, skincare treatments. Repeat behavior generates longitudinal data on coupon effectiveness and consumer preference patterns, which feeds AI intelligence quality as the platform scales.
  • 5
    Validates the full platform loop in one category before expansion. Constraining the MVP to Salons means coupon-driven discovery, verified merchant listings, appointment booking, and AI insight delivery can all be verified as a working integrated system — before adding the structural complexity of additional verticals with different offer schemas, booking cadences, and consumer intent patterns. A single-category MVP produces a clean, unconfounded validation signal.
Merchant Testing Stage

The platform is currently in merchant testing with early salon businesses. This phase validates the offer creation flow, verification onboarding, and booking system under real merchant operating conditions — before consumer-side scaling begins. The objective at this stage is structural validation: confirming that the systems work as designed in the hands of actual users, establishing that the core mechanics are sound, and identifying friction points before the consumer surface is opened at scale.

Marketplace Growth Loop

The Salon vertical is designed to activate a self-reinforcing loop: as more verified salon merchants join the platform, the deal inventory grows richer, which improves consumer discovery quality, which attracts more consumers, which generates more bookings, which increases merchant revenue and confidence in the platform. This loop — once validated in a single category — becomes the replicable engine for expansion into adjacent verticals. Each new service category inherits the same structural mechanics, with category-specific offer schemas and booking cadences layered on top.

More Merchants More Deals Better Discovery More Consumers More Bookings Merchant Revenue More Merchants

Expansion model: The Salon vertical is the proving ground for the platform's core mechanics. Successful validation of the discovery → verification → booking loop in one category creates the replicable template for expansion into adjacent service verticals — each with its own offer schema, booking pattern, and consumer intent profile.

06 / 08

Trust & Verification System

A local marketplace built on promotional offers carries a specific trust risk: consumers cannot distinguish real businesses from illegitimate listings without structural intervention. Verification resolves this at the architecture level — before any offer surfaces in the consumer-facing interface.

System Design
Verification as Architectural Gate, Not Policy Filter
Unverified merchants are structurally absent from consumer discovery — not filtered or ranked lower. This is enforced at the data layer. A policy filter can be applied inconsistently or overridden; an architectural gate cannot.
Scope Boundary
Verification Confirms Identity, Not Service Quality
The verification system answers one question: is this a legitimate, operating business? It does not rate service quality or predict customer satisfaction. Conflating these two functions would undermine both — a common failure mode in marketplace trust design.
Consumer Signal
Verified Status as Persistent Trust Signal
Verified merchant status appears on consumer-facing listing cards as a persistent ambient signal — not a certification badge requiring consumer interpretation. The signal communicates platform responsibility for the businesses it surfaces.
AI Onboarding Entry
Verification Entry via AI-Assisted Merchant Onboarding
The verification flow is accessed through the AI-assisted merchant onboarding system at onboarding.mighty.coupons. The AI guides merchants through qualification and identity confirmation before platform publishing access is granted.

"A local marketplace that surfaces unverified listings is not building consumer trust. It is distributing liability to consumers who have no way to perform their own verification."

07 / 08

My Role

As Head of Design & Product Innovation, this role functions as the platform's primary product intelligence layer — holding full design scope from marketplace system architecture through interaction design, while coordinating across engineering, marketing, and the founder. No dedicated product management layer exists on this team. Product strategy, platform architecture, and cross-functional alignment all run through this function. The scope is structural, not positional — every decision at the product level is owned and operationalized here. I designed the platform mechanics that coordinate value exchange between consumer decision flows and merchant operating workflows — ensuring discovery, booking, verification, analytics, and AI recommendations function as one coherent system.

  • 01
    Marketplace System Design
    Defined the structural logic of the two-sided exchange — what merchants offer (verified promotions, standardized schema), what consumers receive (trusted deals, frictionless booking), and the infrastructure that keeps both sides in equilibrium. This modeling determined verification requirements, offer schema design, and the "control variables" standardization approach that enables cross-merchant comparability.
  • 02
    Consumer Decision Architecture
    Designed the mobile-first consumer system as a structured decision flow — not a listing directory. The interaction model is built around how consumers make local service choices: proximity, offer comparison, and direct booking as a sequential, low-friction path. Intent-matching drives discovery rather than keyword search or passive browsing.
  • 03
    Merchant Dashboard Experience
    Designed the desktop-first merchant system — coupon campaign creation, promotion performance evaluation, demand trend tracking, and booking schedule management with conflict prevention. The dashboard is designed to reduce merchant operational overhead while generating the structured data that feeds AI intelligence quality over time.
  • 04
    Coupon Promotion Mechanics
    Designed the offer creation system and standardized promotion schema — the "control variables" approach that structures coupon offers into comparable, measurable units across all merchants. Offer standardization is not a UX constraint; it is the data foundation that makes platform-level AI analysis and consumer-side comparison both possible.
  • 05
    AI-Assisted Insights & Onboarding Logic
    Defined the scope and output structure of the AI intelligence layer — coupon performance analysis, demand pattern signals, and operating model recommendations scoped to decisions the data can support. Also designed the AI-assisted merchant onboarding flow at onboarding.mighty.coupons, which guides merchants through qualification and identity verification before platform access is granted. Boundary design is architectural — incorrect scope produces advice the underlying data cannot support and erodes merchant trust in the system.
  • 06
    Product Innovation Brainstorming with the Founder
    Work directly with the founder to pressure-test platform assumptions, stress-test category expansion logic, identify structural gaps before engineering handoff, and align product direction with the long-term marketplace model. This collaboration is where MVP scope decisions — including the Salon wedge strategy — are stress-tested against both product integrity and market feasibility.
  • 07
    Collaboration with Engineering & Marketing
    Coordinate with engineers on component specifications, data model constraints, and implementation feasibility — translating architecture decisions into buildable requirements. Coordinate with marketing on merchant acquisition messaging, onboarding entry points, and how verification and promotional mechanics are communicated to prospective merchants. Cross-functional alignment is not a separate workstream — it is built into how every product decision is formulated and handed off.
08 / 08

Strategic Contribution

The following reflects the architectural and organizational contribution of this engagement, scoped to what is structurally observable at the current stage of the platform.

Platform Architecture
Two-Sided Marketplace Designed as One Coherent System
Consumer and merchant layers share infrastructure constraints by design — verification state, booking logic, and AI data flow across both sides architecturally, not through integration bolted on after the fact.
Trust Infrastructure
Verification as Structural Prerequisite, Not Moderation
Positioning verification as an architectural gate — not a moderation feature — defines the quality floor of merchant supply without requiring consumer-side enforcement or behavioral change. The design is invisible to consumers and structural to the platform.
MVP Strategy
Single-Category MVP Produces Clean Validation Signal
Scoping the MVP to the Salon vertical allows the full platform loop — discovery, verification, booking, AI insights — to be validated as an integrated system before category expansion introduces structural complexity and confounding variables.
AI Design
AI Positioned at Maximum Leverage Point in the System
AI is scoped to merchant-side decisions — where platform data asymmetry is greatest. Explicit scope boundary design prevents the system from generating recommendations it cannot reliably support, preserving long-term trust in the AI layer.
Role Scope
Principal-Level Product Function in a Technical Founding Team
Designed and held the full product function — marketplace architecture, consumer flows, merchant tooling, and AI boundary design — inside a six-person engineering-led team with no dedicated product management layer. The operating mode is the contribution.

"Platform integrity is not a feature set. It is an architecture — trust enforced at the data layer, a booking system that closes the discovery loop, and AI that operates only within the scope the data can support."

Project Summary

The work on Mighty Coupons focuses on structuring value exchange between merchants and consumers — designing the offer schema, verification system, booking infrastructure, and AI intelligence layer as a coherent platform rather than a collection of features. The project's central challenge is marketplace dynamics: how to create sufficient trust and supply-demand equilibrium at launch, and how to validate the platform's core mechanics before introducing the complexity of additional service categories. By executing a controlled category launch in the Salon vertical — a category naturally aligned to appointment scheduling, promotional discovery, and repeat consumer behavior — the platform builds the architectural foundation and operational evidence needed to expand into additional service verticals with confidence and without confounding the learning signal.