The Thrive home page

Thrive Protocol: Product design for a capital allocation platform.

Role
Design Lead
Scope
Product designInformation architectureDesign systemsVerification flows
Period
Aug 2025 to Feb 2026
01Context

Thrive is a capital allocation and intelligence platform for investors and founders. It surfaces on-chain signals and human reviews so funders can make decisions backed by evidence. The concept narrative was Proof of Value.

I owned product and brand design end to end. This page covers the product work. The brand case study covers the rest.

Builders create impact. Guardians verify it. Ecosystems fund it.
The Power List itself. Verified projects, ranked, ready to invest in.
The program side. Every action is visible, including who approved what and when.
02The problem

Three things made this hard.

  • The data is dense and mixed. On-chain metrics can be verified. Off-chain claims cannot.
  • The people making the decisions are not analysts. They need conclusions, not raw tables.
  • Projects submit their own evidence. They have every incentive to inflate it.
03Structured intake

Scoring only works if evidence arrives in a shape we can score. I mapped the pipeline end to end. Data connects at the source, Guardians and agents verify it, intelligence turns it into scores, and the output is ready for a decision. Every submission maps to four signal categories: Capital Efficiency, Team Credibility, Revenue Quality, and Traction Velocity.

From raw data to decision-ready. Founders control who sees their data and at what level of detail.
04Missing data

A submission is rarely complete on the first pass. The platform tells a project exactly what is missing, what each item is worth, and how to fix it, without a human sending emails.

Each gap becomes a concrete next step: connect an API, send a document for review, verify a profile.

Gaps a project cannot fill become research tasks. Guardians pick them up, follow written steps, and file the missing signal. No chasing, no email threads.

05Verification and scoring

Guardians verify each claim against its proof. They are a vetted network of human experts and AI agents. Every signal has a 1 to 5 scale with a readable label, instructions for the reviewer, and the data required to back a score. A review walks the same steps every time, so two Guardians looking at the same project reach comparable results. Guardians earn Thrive points for the work, and points translate to tokens. Verifying impact carries financial upside.

Dense evidence, one step at a time. The reviewer sees the instructions and the data side by side.
06The decision layer

This is where an investor or reviewer makes a call. The Verification Terminal compresses a project into score, coverage and confidence, with the full report one click away. I mapped every approve and reject path before drawing screens.

The Verification Terminal, mid build in Lovable.
Approve and reject paths mapped screen by screen before any UI was final.
07Thrive Agent

The same discipline, turned toward founders. Thrive Agent locks a goal, pulls real data from the tools a company already runs, and challenges its own recommendations against that data before showing them. Claims that fail the check get dropped, visibly.

Clarify, connect, verify. Every recommendation traces back to a data source.
08Systems work

I restructured the app's information architecture, starting from the full project lifecycle: application, review, contracts, milestones, payment. I also built the design system: components, states, and the typography scale.

The lifecycle map behind the IA restructure. Every state a project can be in, and every way out of it.
09Shipping

I shipped production interfaces directly with Lovable. That cut the design to build loop from weeks to days. Decisions were tested in the real product, not in mockups. The Verification Terminal above still carries the build bar.

Let’s build something together.

Currently open to new partnerships.