Both of these are my own products — public repos, public tests, real users. Client projects drop into the same slots as they ship, with the same three numbers: what the problem was, what shipped, what it changed.
Building the same form logic twice — once for validation, once for the UI — is where most of the time goes. FieldCraft resolves fields, conditional logic and multi-step flows from one JSON document, so the schema is the only thing you maintain.
Switching payment provider usually means rewriting the checkout. PayKit puts Stripe, Razorpay and PayPal behind one adapter interface, with webhook verification and retries handled, so changing provider is a one-line change and your keys stay on your server.
Name, one-line summary, two metrics, three tech tags, a link. Add an entry to the projects list to fill it.
Client work fits the same shape: the problem, what shipped, the measurable result.
In exchange for a public case study and a testimonial. That is how these cards get filled.
claim a slot →Auditable claims only. If a number here is wrong, the repo will tell you.
First reply inside 24 hours. Discovery call is free, 30 minutes, no deck.