SuryanshChourasia
All work

Mine · 2026

CredoGrid

I designed a warm-introduction marketplace around escrow, confirmation, and a published dispute rule.

Frontend developmentInterface design in codeFull-stack implementation

A warm-introduction marketplace fails when one party says the introduction happened and the other says it did not.

The interface needed to explain when credits were locked, what confirmed delivery, and how a dispute would be resolved before either person committed. Trust depended on the transaction rule being visible, not on adding more feed activity.

CredoGrid

The story is on the left. The decisions behind it are below.

The decisions that made it work

01

Dual party escrow

Credits lock when the intro is requested and release when the requester confirms it happened. Neither side can move the money alone.

02

A published dispute rule

Disputes default to a documented 75/25 split rather than a case by case judgement. Publishing the rule up front is what makes people willing to transact at all.

75/25

dispute default split

append only

credit ledger

0

ghost intros tolerated

Built withNext.jsHonoDrizzlePostgresRedux Toolkit
Next projectHelioIT consultancy, APAC
Want one like this?Landing pages from $999, live in about 10 days.Start a project