Svelte and SvelteKit consulting

When you have a Svelte or SvelteKit team and just need a senior pair of hands for a specific question. Not a sprint. Not a hire.

I do consulting two ways: a 1-hour live session ($149) for one specific question, or ongoing async access ($349 per month) when the questions keep coming.

Both go through me directly. No agency layer, no "let me forward this to our SvelteKit specialist." If you've got a question about Svelte or SvelteKit, I'm the person you're talking to from the first email.

Two cadences

Real-time consulting

A single 60-minute video call for one specific question or piece of stuck code. You send context ahead of time (a Loom, a repo, an error message, whatever's clearer). I show up prepared. We use the hour. It gets recorded so you can rewatch.

• $149 per session

• Live on Google Meet or Zoom

• You send context ahead of the call

• Recorded so you can rewatch

• One specific question or piece of stuck code per session

• Booked via Stripe link, scheduled within a few days

Best for: a tricky bug you've spent a day on, a "should I do it this way or that way" architecture question, an audit on something you're about to ship.

Asynchronous consulting

Ongoing, $349 per month. Reach out whenever, with whatever's blocking you. I write back with code, screenshots, or recordings, depending on what's clearer. Plus one live hour per month included.

• $349 per month

• Async via email, Discord, or Slack (your call)

• I aim to reply within one business day

• Code, screenshots, or recordings, whichever's clearer

• One live hour per month, splittable into up to three 20-minute slots

• Cancel any month, no notice required

Best for: ongoing projects where questions keep coming, teams without senior Svelte experience that want a backstop, founders pre-launch who'd rather text-message-pace than book a call every time something comes up.

What I help with

• Architecture decisions: load function vs. server endpoint vs. form action, how to split your route tree, when to reach for Durable Objects vs. a queue.

• SvelteKit performance: bundle size, hydration cost, server-side rendering edge cases, streaming responses.

• Migrations: Svelte 4 → 5, SvelteKit 1 → 2, headless WordPress → Statamic, "we wrote this in Next.js and want to port it."

• Tricky bugs: hydration mismatches, "works locally fails in prod", weird interactions between SvelteKit, Cloudflare adapters, and auth.

• Auth flows: Lucia, Better Auth, custom JWT, OAuth, session storage on edge runtimes.

• Headless CMS integration: Statamic, Strapi, Sanity, Payload. I've migrated apps off DatoCMS and onto Statamic recently and have opinions.

• Database and ORM choices for SvelteKit: Drizzle, Prisma, Cloudflare D1, Postgres, and when to reach for which.

• Code review: I'll read a PR, point at the load-bearing decisions, and tell you what I'd change and why.

If you don't see your thing on the list, ask. The list is the common cases, not the boundary.

How a real-time session works

You book through the Stripe link. I send a calendar invite within the day, plus a short prep email asking for context: what you're stuck on, what you've already tried, a Loom or repo if it helps.

The call itself is one focused hour. We share screens, dig into the code, try things in real-time. Most sessions end with the problem either solved or scoped clearly enough that you can finish on your own.

You get the recording within an hour of the call ending. Rewatch as many times as you want.

How async works

Onboarding takes a 10-minute exchange. You email me what you're working on, I send back a brief that explains how I work async, and we agree on the channel.

After that, you reach out whenever. A question, a code snippet, a screenshot, a "is this approach right?", whatever shape your question takes. I aim to reply within one business day, faster if the question is short.

The monthly live hour can stay as a single hour or get split into up to three 20-minute slots. Useful for spreading attention across the month, or for "I have three small questions this week."

You can cancel at any month boundary. No notice, no exit interview.

What's not in scope

• Building features for you. That's a sprint.

• Long-term retainer-style availability. Async is responsive, not on-call. If you need someone pinged on every PR, you need a hire.

• Non-Svelte stacks. I won't pretend to be a senior React, Vue, or Solid consultant.

• Code I write inside async sessions. I'll send code snippets, examples, and refactor suggestions, but I won't quietly build features on async time and bill them.

• Emergency on-call. If your prod is down at 2am, I might be asleep in Cape Town. Sprints come with deployment ownership; consulting doesn't.

Pricing

Real-time: $149 per session. Paid upfront via Stripe. One 1-hour call. Recorded. No subscription.

Async: $349 per month. Paid upfront via Stripe. Cancel any month, no notice required. Includes one live hour per month, splittable into three 20-minute slots if you'd rather.

There's no contract for either. There's no minimum engagement. If a single real-time call solves your problem, that's the right answer.

Ready?

If you're not sure which fits, send me a paragraph about what you're working on. I'll tell you which cadence makes sense, usually within a few hours.