Already on Shopify
Keep what works and fix what holds it back: apps folded in, speed, editing and markets.
OptimiseExample: Čili Frik →Working together
Every store gets the same approach, built to Shopify Plus standards on any plan. What changes is how the daily work runs, and how often you need me.
An enquiry first, nothing booked. I review the fit and availability.
Fits if
Not for the lowest bid, a quick patch with no plan behind it, or one more app on top of the pile.
Typically three weeks to two months. A custom app can be a project of its own, and a store with a lot of messy data can start with hours instead.
Keep what works and fix what holds it back: apps folded in, speed, editing and markets.
OptimiseExample: Čili Frik →Move to Shopify with a plan agreed first. Magento, WooCommerce or Webflow, every important URL redirected.
MigrateA new store, built properly once: a custom theme or headless, one store or several.
New buildExample: SEOS AI →Afterwards your team takes it from there, or I keep running it.
What to keep, what to change and how the daily work will run.
Fixed and agreed in writing before work starts.
Dates assume content, access and decisions arrive on time
I build and test. Your team reviews on staging, a copy of the live store.
Corrections to the agreed scope are included · New requests priced for your approval first
Yours, documented, with onboarding for whoever runs it.
Code and hosting move to your accounts whenever you ask
In the review we list what your team does every week and pick the fastest way to run each job. Then the store is built around that map.
| Weekly job | By hand | In bulk | With AI | Automatically |
|---|---|---|---|---|
| Pages and campaigns | Yes | No | Yes | No |
| Prices and offers | Yes | Yes | No | No |
| New products | No | No | Yes | Yes |
| Translations | No | Yes | Yes | No |
| Stock | No | No | No | Yes |
| Orders and invoices | No | No | No | Yes |
An example store. Your map comes out of the review.
Your team runs each job, or I run it for you. Built on Shopify admin, import tools, Sidekick, ERP and PIM sync, and Shopify Flow.
On a partnership we agree goals in plain words and check them monthly. On a project, we build to your goals as agreed.
We take the next goal from the roadmap.
The first month sets milestones and access
I build and test it on staging, a copy of the live theme.
Extra hours and design fees agreed first
Your team checks it before release.
Reviewed together at least monthly
It goes live, and I refactor and keep it fast as I go.
Rolled back to the last working version if a release goes wrong
Every month, back to plan.Slack between releases, replies usually the same working day

Requests, decisions, approvals and hours are documented in Console, where your team follows them. Clients sign in at console.androja.dev.
The work is the same in each. What changes is whether your hours are reserved.
Reserved hours, every month.
For when you can't wait. I work as your fractional CTO: one person who owns your store's technical side part-time. Upkeep included.
From 25 hours a month, billed hourly, no rollover · Cancel anytime · Up to four at a timeHosting and updates for what I host.
Headless storefronts and custom apps. Hours kept for outages and for Shopify's API updates.
MonthlyNew work, when you need it.
For when you can wait while I'm on partnerships.
HourlyTell me about the store, where it runs now and the work ahead. A problem or an idea is enough.
Start a conversationI read every request myself and reply, usually within a day or two. Nothing is booked yet.
Not ready to talk yet? Get the decision plan ↗