Frequently asked questions.

One clearly defined change on one template or feature — a bug fixed, a section added, an app configured, a layout adjusted. If your request turns out to be two tasks, we tell you before you pay for either.

Full page builds, theme migrations, custom app development and checkout customisation. Anything that needs a discovery call to define isn't a task either. Those get a written quote instead of being squeezed into $99.

Ask anyway. The catalogue covers the 100 things people file most, not the only 100 things we do. Describe what's bothering you and we'll tell you whether it's a task, two tasks, or something bigger — before you pay anything.

That's a different service and we'd rather be honest about it — we don't do audits. If you know what's bothering you, we'll fix it. If you don't, an audit from a CRO agency is money better spent than a task from us.

Yes. One task, one payment. No hourly billing, no line items added later, no surprise invoice. If it turns out to be two tasks, you hear that before you pay for either.

No. Buy a 5- or 10-pack and the credits sit there until you use them. They're tied to one store and aren't transferable between stores.

Yes, and most people do exactly that — submit one task first to see how it goes, then buy a pack once they know they'll be back.

No. Nothing renews, nothing auto-bills, nothing to cancel. That's deliberate.

If we can't deliver what was agreed, yes. If the work matches the agreed scope and you've changed your mind, the included revision round is there to adjust it.

Never. Describe the problem and we'll tell you what it is before money changes hands.

Most tasks ship in under 24 hours; 48 is the ceiling. The clock starts once scope is confirmed and store access is in place — not at checkout.

Submit whenever. The queue moves overnight and across weekends. Turnaround is measured in hours from scope confirmation, not business days.

Sometimes, and we'll say so when we scope it. We won't promise same-day up front because it depends on the queue and on how fast store access comes through.

You hear about it from us, not by wondering. Pack holders sit at the front of the queue.

No. We request Shopify collaborator access, which you approve and can revoke at any time. We never ask for account passwords, and we'd tell you to be suspicious of anyone who does.

All work happens in a duplicate theme first, so your live store is never the test environment. Rollback is one click, not one apology.

No. We do the task, send the receipt, and go back to minding our own business. If we spot something else worth fixing we'll mention it — we won't fix it and bill you.

Only if you leave it in place. Revoke it whenever you like; it doesn't affect the delivered work.

Native theme code, not an app. No monthly app fee, no third-party script slowing the page down, and nothing to un-install later.

Minor updates are fine. A major theme version change may need a re-apply, and we'll say so upfront if that's likely for your task.

Yes — fonts, colours, button styles and spacing are matched to your theme. It should look like it was always there.

One revision round is included with every task. If the delivered work doesn't match the agreed scope, we fix it at no cost.

Before-and-after screenshots on desktop and mobile with every delivery. You never have to take our word for it.

Senior developers only. No juniors learning on your store — everyone here has shipped hundreds of these and knows which Liquid file not to touch.

BORING is a productised service, backed by Mudcy. Same people, different shape: fixed price, fixed scope, no retainer and nothing to negotiate.

Someone else picks it up. Tasks belong to the queue, not to an individual — which is the main thing a productised service fixes about hiring a freelancer.

By email, any time. Not by scheduled call — that's the one thing we genuinely don't do, and it's why the price stays where it is.