Software built to a scope agreed in writing before the sprint starts, and shipped with the repository, the tests and the deploy. You do not need a specification: the first conversation writes one. Everything below can be opened today.
Each one began as a problem somebody had. The label says what it is today: live is the product itself in production, demo is a sandbox of it.
The problemKnow which funds opened, added to or exited a position the day the 13F lands, without anybody reading a filing.
What I builtA watcher on SEC 13F filings for a list of funds: every holding parsed, the history kept, and position changes sent to Telegram the day a filing lands, with a dashboard over the lot.
Open it →Leave an email, get a link back. Read-only; filings to 1 June 2026.
The problemTurn a public disclosure regime that publishes loose forms into a dataset somebody can actually query.
What I builtA pipeline that ingests House and Senate trade disclosures, keeps the raw filings, maps every asset to a ticker and turns the lot into a dataset somebody can query.
Open it →Free 45-minute trial with your email. Read-only, data frozen 12 September 2026.
The problemA finished browser strategy game in the Eufloria lineage — no engine licence, no bought assets, and it has to be playable, not just runnable.
What I builtA complete strategy game that runs in a browser tab, written from scratch: no engine, no bought assets, procedurally grown trees and shareable seeded maps.
Open it →The whole game, no sign-up. Opens 60 seconds into a match.
Three steps, and you can stop after the first one with something useful in hand.
Thirty minutes on a call, then a written page: what the thing actually is, the shortest version that solves the problem, and what it would take. Yours whether or not we go further.
Two to six weeks against a scope agreed in writing — named deliverables, a date, and a price on the deliverable, told to you before you commit.
It ends deployed and running, not as a prototype. You get the repository, the tests, the deploy and a walkthrough, and you own all of it.
Not offered: open-ended retainers, or maintaining someone else’s codebase. What the offer includes
No preparation and no specification: bring the problem the way you would describe it to a colleague.
Rather write? Send a brief and get a written reply. Send a brief