Flaire.

Context

I co-founded Flaire with two partners and lead product and technology. We connect creators and brands around short-form campaigns. My work covers product direction, architecture, hiring, interface design, and implementation.

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.

Constraints

We are a small, early-stage team. Research, design, engineering, and operations share the same people. Each release needs to be useful now without making the campaign model harder 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.

Pivotal decisions

Build around the campaign, not separate dashboards

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.

Keep the public promise concrete

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.

Keep product and engineering decisions close

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.

Outcomes

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.

I remain responsible for both the product decisions and the code that puts them into practice.