Gerrit Mack · Wholebean
I'm Gerrit Mack. Under the Wholebean name I take ideas from a sketch to a live product: brand, interface, code, payments and launch. Here's what's live right now.
Brand → billing
one person, the whole stack
Written down
every decision, in the repo
Each one I took from nothing to a live domain myself: the name and brand, the product decisions, every line of the build, and the launch.
Plan the trip, not just the route.
Drop in a GPX and Packrouter assembles the rest of the expedition: weather at elevation, water, resupply, gear weight and a day-by-day plan for bikepacking, backpacking and packrafting.
Next.js · React · Vercel
Estimates your customers can approve, and pay a deposit on, in under three minutes.
A mobile-first estimating tool for HVAC contractors. Pick a job type, send one link, and the homeowner approves and pays a 30% deposit from their phone, with no app to install.
Next.js 16 · Tailwind v4 · Prisma · Supabase Postgres · Stripe · Resend · Vercel
One cog. No excuses.
A brand, an editorial site and a gear calculator for singlespeed mountain bikers: gear inches, skid patches, chain length and every cog that runs a "magic" gear on your frame.
Astro 7 · React 19 island · MDX · Vitest · Vercel
Most products stall at a handoff: design to dev, dev to launch. I do all of it, so nothing waits on anyone.
Turn an idea into a spec that can ship: who it's for, what v1 does, and what it deliberately doesn't.
Name, logo, brand kit and UI, written down as tokens and rules so the product stays consistent after launch.
Next.js or Astro, Postgres, auth and APIs. Server-rendered where it matters, tested where the maths is.
Stripe subscriptions and deposits, transactional email, domains, DNS and deploys. Live, not 'nearly done'.
It starts written down: the audience, the job, the constraints. QuoteDuct and Single Speed Society both began as a one-document spec.
Colour, type, components and voice are decided before the code, then become CSS tokens that no component is allowed to bypass.
Small, boring, fast technology. When I depart from the spec (a wrong formula, a deprecated library) the README says what and why.
Domain, DNS, deploy, payments, email, and a handover doc that says how to run it and what's left.
Because I'd rather take a product whole, from the first sketch to the first paying customer, than hand off half of it and hope.
I build for people I understand: riders planning a long self-supported trip, singlespeeders arguing about chain length, and tradespeople who would rather be on the job than on a laptop. The work tends to be opinionated and small, and every decision in it is written down.
I'm open to full-time and contract roles on product teams, and to building v1s for founders and small businesses.
For teams
Product engineer who can own a feature end to end: spec, design, build, ship. Happy in a codebase that already exists.
For founders & businesses
A branded, working v1 on your own domain, with payments if you need them, and a handover doc your next hire can pick up.
