Development partnership / Monthly
A plan for your store's growth.I own the technical side.
For growth-stage and Shopify Plus brands. I propose the architecture and the approach for each change, keep the roadmap and plan the work with you. Your team can launch campaigns and change offers itself, or leave them to me.
An enquiry first, nothing booked. I review the fit and availability.
- From 25 hours a month
- Cancel anytime
- Monthly review
- Up to four partnerships at a time
Who it's for
- Someone on your side decides and reviews
- Development continues: offers, markets, connected systems
- On Shopify Plus, or Plus is on the table
Nobody to decide or review, or nothing continues after delivery? A project fits better. Explore projects & builds
What you have, month after month.
A roadmap, and someone who owns it.
I propose the architecture, keep the roadmap and plan each month's work with you.
Megasplet ↗Changes shipped every month, reviewed before release.
Built and tested on staging. Your team approves each one before it goes live.
Feelrooty ↗A store your team can run, or leave to me.
Campaigns, offers and translations from Shopify admin, when your team wants to.
Feelrooty ↗Apps that keep up with Shopify.
When Shopify changes its checkout or discount APIs, I update your apps to match.
Megasplet ↗One person who answers.
Priority replies in Slack, usually the same day, or within 24 hours on a working day.
What growing brands build next.
Some features need Shopify Plus. I say which during planning.
Funnels and campaigns
Several funnels, each with its own offers.
Separate journeys for different audiences or channels, each with its own landing page, offer and path to checkout.
Landing pages that match the ad.
Each campaign gets its own page, built from sections your team fills in, so the visitor finds what the ad promised.
Discount journeys tied to the ad.
One link applies the offer and lands on the matching page. Nobody types a code, and the page confirms the offer.
Campaigns scheduled in advance.
Your team sets the banner, page, offer and dates once, and the campaign starts and ends on time.
Bigger baskets
Spend thresholds and gifts.
Free shipping, tiered savings or a gift, shown as progress in the cart and applied at checkout.
Bundles and build-your-own packs.
Fixed bundles, or packs customers put together, priced by rules kept in one place.
Subscribe and save.
Repeat delivery for products customers run out of, in your design.
Personal to each customer
Offers and content by segment.
First-time buyers, VIPs, lapsed customers and wholesale buyers each see what fits them.
“Pairs well with” suggestions.
Accessories and refills beside each product and in the cart, chosen by your team.
Local prices, currency and language.
Each market sees its own prices, products and language.
Testing and measurement
A/B tests on pages and checkout.
Try a change on part of your traffic before everyone sees it.
Offer and price tests.
Compare offers by what they earn per visitor, not only by conversion.
Tracking that respects consent.
Every step from product view to purchase reaches your reports and ad platforms.
From ad to order.
Each order tied back to the campaign that started it, so spend goes where it sells.
One loop, every month.
Requests, decisions and recorded hours are documented in Console, where your team can follow them.
Plan
We take the next change from the roadmap.
Build
I build and test it on staging, a copy of the live theme.
Review
Your team checks it before release.
Run
It goes live, and your team puts it to use.
Every month, back to plan
Every term
- From 25 hours a month, billed hourly, no rollover
- Monthly, cancel anytime
- Reviewed at least monthly; the first month sets milestones and access
- Extra hours and design fees agreed first
- You keep the code and documentation
- Up to four partnerships at a time
Before we start.
Is this just standard Shopify?
The foundation is, on purpose. Your products, rules and translations sit in the structures Shopify itself maintains and extends with every release, so you gain new Shopify features instead of fighting them. The custom part is what customers see and what your team works with: the storefront, the offers and the journeys built on top.
Can you take over from our current developer?
Yes. I review the store, the code, where each rule lives and the open work with your team. Then we agree access, handover and the first milestones.
We already have designers or developers. Where do you fit?
Around them. I give technical direction and review, or take specific builds, and for premium brands I usually work in Figma with your designer. We agree who owns each part first.
Who holds the code and how do releases work?
Your team can access the GitHub repository. You review each change on a staging theme, a copy of the live theme, before I merge it. The setup guide shows the workflow ↗
Can a partnership start with a new build?
Yes. A substantial build can be the first milestone. A headless storefront starts only with a partnership.
Want to check the approach before you write? The whole plan is free.Get the decision plan ↗
What should your store do better?
Tell me about the store, your team and the work ahead. You can bring a problem or an idea; you do not need a technical brief.
Check partnership availabilityI reply by email, usually within a day or two. No call or work is booked by sending an enquiry.