Use cases / Freelancers & agencies
Shopify for Freelancers and Agencies: Deliver Custom, Bill Better
The uncomfortable arithmetic of Shopify freelancing is that your income is capped by how many theme builds fit in a month, and clients keep asking for custom work at template prices. Both halves of that problem are the same problem: the build takes too long relative to what it is worth.
Theme work bills by the hour and does not scale
Most Shopify freelance work is not the interesting part of the job. It is a custom section, a restyled product page, a layout the theme's settings do not cover. Each one is billable and each one costs a day you cannot get back, so growing means either raising rates until clients balk or working more hours. Meanwhile the client who wanted 'something custom' has a budget shaped by what a premium theme costs.
Compress the build, keep the margin
Generation changes the ratio rather than the rate. A custom theme that was a two-week engagement becomes a first draft in an afternoon, and the rest of the week is refinement and client conversation, which is the part they are actually paying for. You can keep the project price and take more projects, or drop the price and win the clients who were choosing a template.
Iterate live, in front of the client
The slowest part of client work is the review cycle: send a mockup, wait, receive vague feedback, rebuild. Being able to change the real store while they watch collapses that loop. 'Make the product page tighter, move reviews above the fold' becomes a thing you do on the call rather than a revision round.
Hand off code, not a dependency
Every theme is standard Shopify 2.0 Liquid you can download as a ZIP. Clients keep working files rather than a proprietary runtime, which makes the handoff clause easy to write and removes the objection about being locked to whoever built it. If they later hire someone else, that person opens normal theme files.
Spend your hours where you are irreplaceable
Nothing generates brand direction, art direction, or the judgment that comes from having shipped fifty stores. Those are the things clients remember and the things that justify a rate. Letting the build compress means more of the engagement is that work and less of it is writing the same hero section for the ninth time.
Where this stops
This does not replace knowing Shopify. The output still needs someone who can read Liquid, spot a bad schema, and tell a client when their request is a bad idea. It replaces typing, not judgment, and clients who cannot tell the difference were never the good clients.
FAQ
Can I use Clyro for client work?
Yes. Themes generated for a client are standard Liquid you download and install on their store, and they own the files. Check the current plan for theme limits if you run many client stores in parallel.
Can I white-label the output?
The theme files carry no branding and no runtime dependency, so what you deliver is a Shopify theme like any other. What you should not do is misrepresent how the work was done if a client asks directly; in practice the ones who ask care about the result and the ownership terms, not the tooling.
Does it work with a client's existing theme?
Yes. Upload their current theme and edit it in plain English rather than starting over, which is the common case for retainer work and incremental changes.
How do I price work that takes an afternoon?
The same way designers priced work after Figma made mockups faster: on the outcome, not the hours. If a custom storefront was worth $4,000 to the client last year, it is worth that this year. What changes is how many of them you can deliver well.
Other use cases