Portfolio

Systems I built, and the decisions behind them

Three projects. In each one the system is the proof, not the point: a revenue operations problem, a decision about how to run it, and software built so the decision would hold.

Case 01 · Own build, in production

Radar · Personal CRM for the job search

01

A CRM of my own for the job search

811 applications migrated Plan to live history in 2 days 0 tables left in HubSpot

I ran my job search like a sales pipeline. When the tool got too heavy, I built my own: stages, a reason for every closed application, a 0 to 100 fit score per job, and a shutdown plan written on day one.

Next.jsSQLiteDockerGoogle OAuthClaude Code

Case 02 · Revenue layer, embedded

Axenya · B2B, Corporate health benefits

02

Auditable forecast in real time

4 to 5 days → real time 8 panels · 20 releases 1,000+ properties audited

They were rebuilding the forecast by hand in Excel, four to five days, every two weeks. I rebuilt it as a real-time platform where every chart shows the exact CRM fields behind the number.

HubSpot APIVercelGoogle AuthGitHubClaude Code

Case 03 · Built for a client

Commercial CRM · B2B

03

A commercial CRM shaped around one sales process

A B2B company replacing a generic CRM with one built around its own sales process. Published after the client’s announcement, with fictional data and no logo.

Coming soon