Illustration, not the real app (NDA)
CashoutReady
- Company
ChainComply- Type
- B2C web app
- When
- 2026
- My role
- ProductEngineeringDesign
- Industry
- Crypto, Regtech
Tech stack
- React
- TypeScript
- Stripe
- Turborepo
- Vite
- MUI
KendoReact- TanStack
- Axios
- pnpm
Playwright- OpenAPI
- i18n
- GitHub
- GitHub Copilot
- Cursor
- OpenAI Codex
- Claude Code
- MCP
- JavaScript
- CSS
Overview
ChainComply's source-of-wealth analysis for individuals: people hand over their exchange accounts and wallets, ChainComply reconstructs how their wealth was built, and they get a claim their bank can read. I own it as its product manager, and designed and built it too.
- Three steps, and only the first is theirs: people hand over their sources, ChainComply reconstructs their wealth story, and they approve the claim before their bank sees it.
- Fixed-price packages paid through Stripe, from a simple check to a white-glove service where a case lead takes the whole file.
- Sources come straight from exchange accounts, wallets and DeFi activity, or from partner crypto tax calculators such as Kryptos.
- A Source-of-Wealth Claim their bank can read: a written report and an interactive map.
- And more proprietary features I can't share publicly.
How I built it
Part of our pnpm, Turborepo and Vite monorepo, on the same stack as the rest of ChainComply's apps. I built it in React and TypeScript: choosing a package and paying through Stripe, handing over the sources, and approving the claim once an analyst has reviewed it. I designed it too: low- and high-fidelity wireframes on paper, in Figma or in Miro, quick proofs of concept in StackBlitz, then the final design in code.
Product decisions
The problem
ChainComply's source-of-wealth analysis was only open to businesses, through their analysts. People who had to show their bank where their crypto wealth came from had no way to get that report themselves.
What I changed
Scope. I decided what individuals need from the platform: the Connect flow for bringing their data in, plus what's new for them, from choosing a package and paying to receiving it.
Built on what we'd learned. CashoutReady builds on the feedback from the Analyst Workspace and Connect, so we didn't start from scratch: we already knew what people needed, and I carried those lessons into the scope.
Requirements and delivery. I write the requirements, work with the developers day to day, and answer the questions that come up along the way.
My role
Our CPO set the direction: offer individuals the service our analysts get. I own it from there, from scope and requirements to delivery. The team brings its questions to me, and I report progress to him and check legal and privacy questions with him.
Outcome
Launching soon; results to follow.
