What I can build in 1, 3, or 8 hours
You buy hours, not packages — so the fair question is "what does an hour actually get me?" Here's an honest answer. A single session caps at 3 hours, and a week at 20, so bigger builds happen across a few sessions. Nothing here is a fixed quote; it's a feel for the unit. I'll always scope your exact thing before you spend.
1 hour — one clear thing
An hour gets one specific item off your list, or tests whether a bigger idea is worth building.
- A bug fixed or a broken flow repaired.
- One automation — say, a script that pulls your orders into a sheet.
- A single landing section, or a contact form wired up properly.
- A data cleanup plus one chart.
- A rough prototype of one small idea, just to see if it has legs.
3 hours — one real feature, shipped
Three hours is a full session — the most I'll take in one sitting. Enough to ship one working thing end to end.
- A single-page site, live.
- One feature working start to finish — e.g., a booking form that takes payments.
- A small internal tool: one screen that does one job well.
- A dashboard view pulling your real numbers.
- A messy spreadsheet turned into a simple, usable app.
8 hours — a small project
About three sessions, usually over a week or two. A working first version you can actually use, not a finished, scaled product. We'll scope the rest from there.
- A basic D2C storefront you can take real orders on (v1).
- An internal tool with a few connected screens.
- A kid's game with a real mechanic — and a lesson tucked inside.
- A multi-view dashboard wired to your data.
- An automation pipeline that runs without you.
Not sure which bucket your idea is in? Book a consultation and I'll tell you straight. Or start free and drop it on your backlog.