15 months as JonnyDo’s on-call tech team, billed by the hour.

Pricing structure came before the checkout.

Daniel had three plans with multiple package combinations. Our first sessions were strategy: pricing, packaging, and how Stripe would model the whole thing. We mapped his pricing into something Stripe could handle cleanly. Which tier maps to which Stripe product. Which package maps to which add-on. How proration would work. Without that work, the checkout would have been a structural mess from day one.

The Webflow build matched the designer’s Figma exactly.

Daniel’s local designer handed us pixel-perfect Figma files. Our Webflow build kept them pixel-perfect. The visible site looks exactly like what was designed. The invisible engineering went into the Stripe integration: multi-tier subscriptions, proration, add-ons, and edge-case handling that took most of the hours.

After launch, hourly packages matched the reality of the workload.

JonnyDo’s post-launch workload was steady but unpredictable. Some months a new subscription tier needed building. Some months a single Stripe webhook tweak. Hourly packages let Daniel buy time only when the work demanded it. He kept a tech team on call without a fixed monthly bill.

15 months of compounding work without changing teams.

The same dev team that launched JonnyDo’s website kept showing up for 15 months. Every Stripe edge case we’d already worked through stayed in the team’s head. Every workflow Daniel cared about, we already knew. No rehiring, no re-onboarding, no relearning his pricing model.