A creator-brand campaign platform I co-founded and lead across product and technology.
Flaire connects creators and brands around short-form campaigns. I co-founded the company with two partners and lead product and technology. The role spans product direction, architecture, hiring, interface decisions, and the engineering work that benefits from direct founder context.
The public product is organized around three jobs: discover the right creator, turn an agreement into a clear brief, and pay for completed work. The interface has to make those jobs understandable to people entering from opposite sides of the same campaign.
Flaire is an early-stage product built by a small team. Product decisions cannot assume separate research, design, platform, and operations departments. Each release has to be useful now while leaving the data model and workflows clear enough to extend.
A creator marketplace also carries uneven information. Brands arrive with a campaign goal. Creators arrive with an audience and a body of work. The product has to translate both into a shared campaign without hiding the terms that matter.
The campaign is the durable object connecting discovery, briefs, deliverables, and payment. Organizing the system around that shared record keeps the product coherent as each side performs different work.
The product language stays close to the actual workflow: discover, brief, pay. That sequence is easier to evaluate than broad claims about creator marketing and gives the interface a clear order.
I stay involved from interaction design through implementation. When a workflow is confusing, the fix can reach the interface and the underlying data model in the same pass instead of becoming a visual patch over a structural problem.
The application uses React and TypeScript for the product surface, Supabase for the backend platform, and Postgres for campaign data. The technical work centers on keeping campaign state explicit, making permissions understandable, and shipping interface changes without fragmenting the workflow.
The website and product share one visual direction, but they do different jobs. The public site explains the operating model. The application carries the detailed creator and campaign work.
Flaire is live and remains the main product I operate. It now presents creator discovery, campaign setup, and payment as parts of one system rather than disconnected services.
The project also defines how I work: product decisions and production code are one responsibility, not two handoffs.