Skip to content

E‑commerce & marketplaces

Your store, or your marketplace. We find the money it leaks.

One senior team for single-brand stores and multi-vendor platforms — design, engineering, payments, ads and retention in one room. The people rebuilding your product page are the people reading your payout data.

Get a free auditSee where it leaks

We work in

  • Shopify Plus
  • Hydrogen
  • Next.js
  • Stripe Connect
  • Multi-vendor
  • Algolia
  • Klaviyo
  • GA4 + server-side
  • Meta Ads
  • Google Ads
Shop2

Thermal Bottle 600ml

4.8 · 128 reviews

$89.00Free shipping
Buy now

[01] Who we build for

Two kinds of commerce, one team.

Selling your own products and running a platform other people sell on are different businesses with different failure modes. Pick the one that sounds like yours.

  • Single-brand store

    You sell your own products.

    DTC brands and retailers on Shopify, Shopify Plus or headless.

    One catalogue, one checkout, one P&L. Growth comes from traffic, conversion rate, order value and repeat purchase — and from a store fast enough to deserve the traffic you are paying for.

    • Product page, cart and checkout rebuilds
    • Ads and server-side tracking that finally agree with each other
    • Lifecycle, subscriptions and loyalty
    • Headless only when the theme has genuinely run out
    Where stores leak

  • Multi-vendor marketplace

    Buyers and sellers both live on your platform.

    Founders and CEOs of marketplaces, aggregators and multi-seller platforms.

    You are not running a store, you are running an economy: supply, demand, commission, payouts, disputes and trust. Half the roadmap is seller software nobody outside the building ever sees — and it is the half that decides whether sellers stay.

    • Seller onboarding, KYC and seller dashboards
    • Commission, split payments and payout runs that reconcile
    • Search, ranking and catalogue quality across thousands of listings
    • Trust, safety, fraud and dispute handling
    • Ops tooling, so your team stops living in the database
    Marketplace engineering

[02] The maths

Store revenue only moves four ways.

Traffic × conversion rate × average order value × repeat purchases. Every idea we bring you maps to one of these — and if it doesn’t move one of them, it doesn’t make the roadmap. On a marketplace the same four apply twice, once to buyers and once to sellers, with take rate on top.

  • Traffic

    Qualified sessions

    Visits from people actually in the market — not raw numbers that flatter a dashboard.

    • Technical, collection and product SEO
    • Meta, Google and TikTok campaigns
    • Structured creative testing
    • Core Web Vitals, because speed is ranking and revenue
    • Marketplaces: listing pages that can rank at catalogue scale

  • Conversion rate

    Orders per session

    The cheapest growth you own: the same traffic, more orders, no extra ad spend.

    • Product page and checkout rebuilds
    • Reviews, photo UGC and trust signals
    • Search, filtering and navigation
    • A/B tests run long enough to mean something
    • Marketplaces: ranking and the quality of the first screen of results

  • Average order value

    Revenue per order

    Every dollar added here drops almost straight to the bottom line — you already paid to acquire the customer.

    • Bundles, sets and volume breaks
    • Cart and post-purchase upsells
    • Free-shipping thresholds that are actually tuned
    • Recommendation logic worth clicking
    • Marketplaces: multi-seller carts and cross-seller recommendations

  • Repeat rate

    Orders per customer

    The number that decides whether you can afford to keep buying traffic at all.

    • Email, SMS and WhatsApp lifecycle flows
    • Subscriptions and one-tap reorder
    • Loyalty and referral mechanics
    • Segmentation, win-backs and replenishment timing
    • Marketplaces: seller retention, because your supply churns too

[03] What we do

Four ways we grow your store.

Most brands have to hire a design studio, a dev shop and a media agency, then referee the three of them. This is all of it, in one room.

01

Product & Store Design

Three screens decide most of your revenue — collection, product, checkout. We rebuild those first, around the questions shoppers actually have, and leave you a design system your team can keep extending.

  • Objection-first product pages: fit, delivery, returns, proof
  • Checkout and cart flows stripped to the shortest honest path
  • Mobile-first templates, built to an image and font budget
  • Collection pages that merchandise instead of just listing
  • A design system in Figma and in code, not a one-off mockup

What you get

  • UX audit
  • Figma prototypes
  • PDP & checkout redesign
  • Design system

Tech we use

Figma · Liquid · Hydrogen · Tailwind · Storybook

02

Ads & Acquisition

Campaigns run by the same team that owns your tracking and your theme. No media agency blaming the developers, no developers blaming the pixel — one group accountable for the number.

  • Meta and Google performance campaigns, including Shopping and PMax
  • Server-side GA4, Meta Conversions API and Consent Mode v2
  • Creative testing with a written hypothesis, not vibes
  • Merchant Center feed quality — titles, attributes, exclusions
  • Reporting on blended MER and contribution, not just in-platform ROAS

What you get

  • Account audit
  • Campaign structure
  • Creative test plan
  • Tracking rebuild
  • MER dashboard

Tech we use

Meta Ads · Google Ads · GA4 · Server-side GTM · Merchant Center

03

Features & Engineering

The things the app store can’t sell you — built natively, so they lift order value without adding three more scripts to every page load. And when traffic spikes, the store stays up.

  • Shopify and Shopify Plus builds, plus headless on Hydrogen or Next.js
  • Checkout extensibility and Shopify Functions for discounts, shipping and payments
  • Subscriptions, loyalty, referrals and bundle builders
  • AI product recommendations and an AI shopping assistant that knows your catalogue
  • ERP, inventory, 3PL and fulfilment integrations that stay in sync
  • App-bloat audits: replace the critical ones, delete the rest

What you get

  • Architecture plan
  • Storefront build
  • Custom features
  • Integrations
  • Handover docs

Tech we use

Shopify Plus · Hydrogen · Next.js · Node.js · Stripe · AWS

04

Growth & Retention

Acquisition you rent; retention you own. We build the lifecycle program and the reporting around it, so you can see which cohort, channel and flow is actually paying for itself.

  • Collection and product SEO, with product structured data
  • A CRO backlog ranked by impact against effort
  • Welcome, post-purchase, replenishment and win-back flows
  • Abandoned cart and browse recovery across email, SMS and WhatsApp
  • Dashboards your whole team can read without a call

What you get

  • Tracking plan
  • CRO roadmap
  • Lifecycle flows
  • SEO fixes
  • Dashboards

Tech we use

Klaviyo · GA4 · BigQuery · Looker Studio · Search Console

[04] Marketplaces

The marketplace work nobody shows you.

Buyers see maybe a third of your product. The rest is seller tooling, money movement, catalogue quality, trust and ops — and that is where multi-vendor platforms actually get stuck.

01

Seller onboarding & seller tooling

Your sellers are users too, and they are the side that leaves first. Onboarding, verification, listing tools and a dashboard that answers “how am I doing?” without a support ticket.

  • Self-serve onboarding with KYC and document verification
  • Bulk catalogue ingest — CSV, feeds and API — with validation that explains itself
  • Seller dashboard: orders, payouts, fees, returns, performance
  • Seller scorecards and SLA tracking, with consequences that apply themselves
  • Role-based access for teams inside a single seller account
  • Seller messaging and support that doesn’t land in your founder inbox

What you get

  • Onboarding flow
  • KYC integration
  • Seller portal
  • Catalogue ingest
  • Scorecards

Tech we use

Next.js · NestJS · PostgreSQL · Stripe Identity · Redis · AWS

02

Payments, commission & payouts

The part that quietly kills marketplaces: money in from buyers, money out to sellers, the right cut retained, and every line reconcilable twelve months later.

  • Split payments and escrow on Stripe Connect or a local equivalent
  • Commission and fee engines — per category, per seller, per campaign
  • Payout schedules, holds, adjustments and instant payouts
  • Refunds, chargebacks and partial returns across several sellers in one order
  • Tax, GST/VAT and per-seller invoicing across regions
  • A ledger and reconciliation reports your accountant will accept

What you get

  • Payment architecture
  • Commission engine
  • Payout automation
  • Ledger & reconciliation

Tech we use

Stripe Connect · Node.js · PostgreSQL · Webhooks · Queues

04

Trust, safety & disputes

One scam seller costs you more than ten good ones earn. Trust is a product surface: verification tiers, fraud scoring, review integrity and a dispute flow that doesn’t need a human reading every thread.

  • Seller verification tiers and progressive trust
  • Fraud scoring on accounts, orders and payouts
  • Review and rating integrity — verified purchase, abuse detection
  • Dispute flows with evidence, deadlines and an audit trail
  • Content moderation with AI triage and human review where it matters
  • Policy enforcement: strikes, suspensions, delisting

What you get

  • Risk rules
  • Verification tiers
  • Dispute flow
  • Moderation console

Tech we use

Node.js · PostgreSQL · Claude / OpenAI · Queues · Admin tooling

05

Ops tooling & marketplace economics

Most marketplaces can’t answer “which sellers and which buyer cohorts make money?” without an analyst and a week. That is the question your board asks, so it should be a page, not a project.

  • An admin console for the work your ops team currently does in SQL
  • GMV, take rate, contribution and cohort LTV on one dashboard
  • Supply and demand balance by category and region — where you are short
  • Seller cohort retention next to buyer repeat rate
  • Unit economics per order, per category, per fulfilment path
  • An event schema and warehouse, so the numbers stop being arguable

What you get

  • Admin console
  • Metrics dashboard
  • Event schema
  • Warehouse models

Tech we use

BigQuery · Looker Studio · Next.js · GA4 · PostgreSQL

[05] Diagnostics

Where commerce revenue usually leaks.

These are the patterns we run into most. If two or three of them sound like you, we already know where to start looking — and we’ll tell you before you pay us anything.

If you sell your own products

  • 01

    Traffic is fine. Orders are flat.

    Usually because

    Almost always the product page: thin copy, one angle of photography, no answer to the obvious objection, and a sizing or delivery question the shopper has to go hunting for.

    What we do

    Objection-first PDP rebuild, reviews and photo UGC in place, and an A/B test behind the change so you know what it was worth.

  • 02

    Mobile converts at half the rate of desktop.

    Usually because

    A desktop-first theme, a hero image that blocks first paint, and a cart drawer that opens onto a five-step checkout with no express payment in sight.

    What we do

    Mobile-first templates against a performance budget, express wallets above the fold, and a checkout that asks for the minimum.

  • 03

    Ad costs climb every quarter.

    Usually because

    Client-side-only tracking, so the platforms optimise on partial data after iOS and consent loss — plus creative that never gets tested in a way that can be read.

    What we do

    Server-side GA4 and Meta CAPI with Consent Mode, a clean product feed, and a creative cadence with one variable at a time.

  • 04

    Carts fill up, then get abandoned.

    Usually because

    Shipping cost and delivery date revealed at the last step, forced account creation, too few payment methods, and a recovery email that goes out too late to matter.

    What we do

    Shipping and ETA shown on the product page, guest checkout, wallets and BNPL, and recovery flows across email and SMS.

  • 05

    Everybody buys once.

    Usually because

    Nothing happens after the order confirmation. No segmentation, no replenishment timing, no reason to come back before the customer forgets the brand.

    What we do

    A full lifecycle program, one-tap reorder and subscriptions where the category suits it, and cohort reporting to prove it works.

  • 06

    Thirty apps installed, and the site still feels slow.

    Usually because

    Every app injects its own script, and the theme carries years of dead Liquid, duplicated CSS and tracking that nobody owns any more.

    What we do

    App and script audit, native rebuilds of the ones you can’t live without, and a Core Web Vitals budget enforced on every deploy.

If you run a marketplace

  • 01

    We have sellers. We don’t have sales.

    Usually because

    Supply grew because adding it was free, demand didn’t, and nothing in the product makes a new buyer’s first search look good. Classic cold-start: the two sides are out of balance, and your category pages show it.

    What we do

    Narrow to the categories where supply is already deep, fix search and ranking there first, then build the demand side — listing-page SEO, paid on the queries that convert, and retention so a first order isn’t the only one.

  • 02

    Payouts and commission are reconciled by hand every month.

    Usually because

    Payments were built for a single-seller store and then stretched: fees calculated in application code, adjustments kept in spreadsheets, multi-seller refunds handled manually. It holds until volume — or an auditor — arrives.

    What we do

    A real ledger: a commission and fee engine with rules you can read, automated payout runs with holds and adjustments, and reconciliation reports that tie to the cent.

  • 03

    Our best sellers are leaving.

    Usually because

    Payouts are slow, the seller dashboard can’t answer basic questions, listing tools hurt at scale, and support runs through your inbox. Sellers churn for operational reasons far more often than over take rate.

    What we do

    Treat sellers as users: faster payouts, a dashboard with orders, fees and performance, bulk listing tools, scorecards they can act on, and self-serve support.

  • 04

    Search returns junk, so buyers go back to the big guys.

    Usually because

    Thousands of third-party listings with inconsistent titles, missing attributes and duplicates, ranked by something close to recency. No amount of UI work fixes a catalogue problem.

    What we do

    Taxonomy and attribute normalisation, AI enrichment across the catalogue, duplicate detection, and ranking that weighs relevance, seller quality and fulfilment — measured on search-to-order rate.

  • 05

    Fraud, fake listings and disputes are eating the team.

    Usually because

    Verification is one-size-fits-all, risk checks are manual, and every dispute is a human reading a thread with no evidence trail and no deadline.

    What we do

    Progressive seller verification, automated risk scoring on accounts, orders and payouts, AI triage on moderation, and a structured dispute flow with evidence and an audit log.

  • 06

    Every sale day we fall over, and every release is a gamble.

    Usually because

    One monolith, no load test against a realistic traffic shape, N+1 queries on the busiest pages, and staging data that looks nothing like production. Peak day finds all of it at once.

    What we do

    Profile the hot paths, cache and queue what should never be synchronous, load-test the real traffic shape before the sale, and put releases behind CI, feature flags and a rollback you have actually practised.

  • 07

    Our dev team ships exactly what we ask — and never what we should have asked for.

    Usually because

    They’re paid to deliver tickets, not outcomes. So nobody tells you an idea is expensive, a feature is a trap, or that the thing you asked for last quarter is being used by eleven people.

    What we do

    A written recommendation every cycle: what we’d build next, what we’d stop, what we’d delete. It’s the cheapest part of our work and it saves the most money.

  • 08

    We can’t say which sellers or which buyers make money.

    Usually because

    Events were never designed, so analytics answers volume questions and not margin questions. GMV goes up and nobody can tell whether contribution moved with it.

    What we do

    An event schema and warehouse, then GMV, take rate, contribution and cohort LTV by seller, category and region on one dashboard your board can read.

  • 09

    We spend a lot on development and can’t point at what changed.

    Usually because

    Hours billed against a backlog nobody ranked by impact, progress reported as tickets closed, and no metric agreed before the work started.

    What we do

    A scope with a success metric in writing, a weekly demo of working software instead of a status email, and measurement in place before launch — so the result isn’t a matter of opinion.

[06] Why founders pick us

Most agencies bill you. We’re paid to have an opinion.

Plenty of shops will take thousands a month and never once tell you what to stop doing. That is the gap we were built in — and these are the eight things clients actually say they stayed for.

  • Clean code you can hand to anyone

    Typed, reviewed, tested and documented, with the architecture decisions written down. Hire an in-house team tomorrow and they can read it on day one. Nothing is a service only one person understands.

  • A commerce network to borrow judgement from

    Our extended network is engineers and operators whose careers run through commerce at scale — Meta, Google, Amazon, eBay, Alibaba, Shopify and other commerce businesses. We use it mainly for one thing: knowing what not to build. That has saved clients more than anything we shipped.

  • Transparency, including the bad news

    What’s going wrong arrives in writing, weekly — including when it’s our estimate that slipped or our idea that lost its test. You will never discover at the end of a quarter that a month was wasted.

  • We suggest. We don’t just invoice.

    Every cycle you get a written recommendation: what we’d build next, what we’d kill, what nobody is using. Argue with it — that’s the point. It’s the part of the job most teams never do for you.

  • A team that actually likes commerce

    Checkout edge cases, catalogue data, payout reconciliation, fraud rules. Our engineers chose this work — it isn’t the project they’re stuck on between app builds. It shows in how fast the second opinion arrives.

  • Faster, and below agency rates

    No layer between you and the engineers: no account manager relaying questions, no four-week discovery before anything ships. You pay for the work, and the first useful thing lands in weeks, not quarters.

  • Your timezone, your hours

    Cover across India, Australia and the United States, so stand-ups happen when you’re awake and someone is reachable around the clock — including the launches, migrations and sale days when an hour of downtime is real money. We put the hours in the contract instead of leaving it as a slogan.

  • We work like it’s our platform

    You own the repo, the cloud, the ad accounts and the data from day one — nothing sits behind our logins. And we take your view of the P&L: if a feature won’t pay for itself, we’ll say so before we quote it.

What you’re used to, and what you get

  • A pitch deck, then a four-week discovery phase.

    A specific list of what we’d fix first, within days.

  • Tickets closed, reported as progress.

    A weekly demo of working software, and the metric it moved.

  • Silence until the invoice.

    Written updates, including the parts going badly.

  • Builds whatever you ask for.

    Tells you what not to build, and why — in writing.

  • An account manager between you and the engineers.

    You talk to the people writing the code.

  • Work that only keeps running while they hold the keys.

    Your repo, your accounts, documented handover.

  • One timezone, nine to five, answers tomorrow.

    India, Australia and the US — someone awake when you are.

  • Big-agency day rate for mid-level work.

    Senior work, priced under the agencies you’re comparing us to.

[07] Proof

Don’t take our word for it. Take the cheap test.

We won’t put invented case studies, invented numbers or invented quotes on a website — if you see those elsewhere, ask how they were measured. Here is what you can verify instead, before you commit a budget.

  1. 01

    Start with a free audit

    Send a store URL or a marketplace walkthrough. You get back a prioritised list: what we’d fix first, what it’s likely worth, and what it takes to do. Yours to keep, whether or not we build any of it.

  2. 02

    Read the code before you commit

    We’ll walk you through a repo we’ve written — the tests, the docs, the decision records — and you can ask the engineers who wrote it anything you like.

  3. 03

    Buy a small piece first

    A fixed-scope sprint with a written success metric. If we’re wrong about the outcome, you found that out for the price of one sprint, not one year.

  4. 04

    Talk to engineers on the first call

    No SDR, no sales script, no “let me bring in a technical person next week”. The people who would do the work are on the call where you decide.

  5. 05

    References on request

    We’d rather connect you with people we work with than print a testimonial nobody can check. Ask on the call.

  6. 06

    Nothing is held hostage

    Repo, cloud, ad accounts, pixels, data warehouse — yours, documented. Leaving us should be boring, and that’s deliberate.

[08] Platforms & stack

The stack we actually work in.

No learning on your budget. This is the tooling we’re in week to week — and the integrations that usually decide whether a build is simple or painful.

  • Storefront & build

    • Shopify and Shopify Plus
    • Liquid themes and theme architecture
    • Hydrogen + Oxygen
    • Headless Next.js on the Storefront API
    • WooCommerce and BigCommerce
    • Headless CMS for content-heavy catalogues

  • Marketplace & multi-vendor

    • Multi-vendor architecture on Next.js and NestJS
    • Seller portals, admin consoles and role-based access
    • Commission, fee and payout engines
    • KYC, identity and document verification
    • Catalogue ingest: CSV, feeds and seller APIs
    • Moderation, risk and dispute tooling
    • Multi-seller order routing and split shipments

  • Checkout & payments

    • Checkout extensibility and UI extensions
    • Shopify Functions: discounts, shipping, payments
    • Stripe, Stripe Connect and Shopify Payments
    • Split payments, escrow and payout schedules
    • Apple Pay, Google Pay and Shop Pay
    • Afterpay, Zip and Klarna
    • Multi-currency, multi-region, GST and VAT

  • Data & measurement

    • GA4 with a documented event schema
    • Server-side GTM
    • Meta Conversions API
    • Google Consent Mode v2
    • BigQuery and Looker Studio
    • Blended MER, CAC and cohort LTV
    • GMV, take rate and contribution reporting

  • Acquisition

    • Meta Ads
    • Google Search, Shopping and Performance Max
    • Merchant Center feed management
    • TikTok Ads
    • Technical and collection SEO
    • Product structured data and rich results

  • Retention & lifecycle

    • Klaviyo flows and campaigns
    • SMS and WhatsApp messaging
    • Subscriptions and reorder flows
    • Loyalty and referral programs
    • Reviews and photo UGC
    • RFM segmentation and win-backs

  • AI in the shopping journey

    • AI shopping assistant trained on your catalogue
    • Recommendations and personalised merchandising
    • Size and fit guidance
    • Review summarisation on product pages
    • Support deflection for order and delivery questions
    • Catalogue enrichment and seller-listing clean-up at scale

  • Operations & integrations

    • ERP and inventory synchronisation
    • 3PL and warehouse APIs
    • Carrier and fulfilment integrations
    • Accounting and finance sync
    • Returns and exchange flows
    • B2B and wholesale channels

[09] Ideas board

Ideas we’d bring to your platform.

A sample of the experiments we often start with. Which ones fit depends on your category, your margins and your data — we’d rather argue about that on a call than guess here.

  • Conversion

    AI size & fit assistant

    Recommends the right size from a few questions, so fewer orders come back as returns.

  • Retention

    One-tap reorder

    Lets repeat customers buy their usual again in a single tap, straight from an email or their account.

  • AOV

    Bundle builder

    Shoppers build their own sets, with a bundle price that rewards adding one more item.

  • Sellers

    Instant seller payouts

    Money reaches sellers in hours instead of weeks — the single most common reason good supply stays.

  • AOV

    Post-purchase upsell

    A relevant one-click add-on on the thank-you page — no new checkout, no new shipping cost.

  • Sellers

    Seller scorecards

    Shows each seller where they rank on delivery, cancellations and reviews — and exactly what to fix.

  • Retention

    Back-in-stock alerts

    Captures demand for sold-out lines and brings shoppers back the hour stock lands.

  • Conversion

    Duplicate listing collapse

    Folds the same product from many sellers into one page with a clear best offer.

  • Conversion

    Reviews with customer photos

    Real photos on product pages answer the questions your copy can’t.

  • Trust

    Buyer–seller messaging

    Pre-purchase questions answered in-platform, with a record if it ever becomes a dispute.

  • Conversion

    Smart search with typo tolerance

    Search that understands misspellings and synonyms, so no query ever hits a dead end.

  • GMV

    Make-an-offer flow

    Lets buyers negotiate inside rules you set, instead of leaving to find a cheaper listing.

  • AOV

    Free-shipping progress bar

    Shows exactly how close the cart is to free shipping, with the right product to close the gap.

  • Trust

    Verified-seller tiers

    Visible trust levels earned through verification and performance, not bought.

  • Conversion

    Delivery date on the product page

    A real estimated arrival date before the cart, instead of a surprise at step four.

  • GMV

    Seller-funded ad placements

    Sellers pay to promote listings — a revenue line that grows with your supply, not your spend.

  • Retention

    WhatsApp order updates

    Order and delivery updates where customers actually read them — and can reply.

  • Trust

    Dispute resolution centre

    Evidence, deadlines and an audit trail, instead of a support thread and a judgement call.

  • Conversion

    Personalised homepage

    Collections and products ordered by what each visitor has been browsing.

  • Retention

    Replenishment reminders

    Timed to how long the product actually lasts, per customer, not a fixed 30 days.

  • Traffic

    AI catalogue enrichment

    Fills missing attributes and rewrites seller titles across thousands of listings.

  • Traffic

    Core Web Vitals clean-up

    Find and fix what slows your pages down, for shoppers and for search rankings.

  • Conversion

    Exit-intent offer

    A well-timed, well-targeted offer for visitors about to leave — and only for them.

  • Traffic

    Feed enrichment for Shopping

    Better titles, attributes and exclusions, so Google spends your budget on the right products.

[10] First 90 days

How a first 90 days could look.

Fix the measurement, ship the cheap wins, then scale what the data backs. In that order — scaling spend or supply on broken measurement just buys you expensive noise.

  1. 01

    Days 1–14

    Audit

    We go through the storefront, the seller side, the analytics, the ad accounts and the codebase, then agree a prioritised plan with you — effort against impact, in writing.

    • Buyer and seller journey walkthrough
    • Tracking, attribution and event-schema check
    • Core Web Vitals, performance and SEO audit
    • Payments, payouts and ad account review
  2. 02

    Days 15–45

    Quick wins

    The high-impact, low-effort fixes ship first, so you see movement while the bigger builds are still being scoped.

    • Checkout, product page and search fixes live
    • Server-side tracking rebuilt and verified
    • First A/B tests running
    • Abandoned-cart, welcome and seller-activation flows on
  3. 03

    Days 46–90

    Scale

    With data you can trust, we scale the channels, features and categories that earn it — and cut the ones that don’t, including our own ideas.

    • Campaigns scaled on blended MER
    • Custom features and seller tooling shipped
    • Full lifecycle and retention program running
    • Reporting your team owns, not a monthly PDF

[11] How to start

Four ways to work with us.

Start as small as you like. Most clients begin with the audit and decide from there — it costs you nothing and you keep it either way.

  • No cost · ~1 week

    Free audit

    We review the store or platform, the data and the spend, and come back with a prioritised list: what to fix, what it’s likely worth, and what it takes to do.

    • Buyer and seller journey walkthrough
    • Tracking and attribution check
    • Performance and SEO report
    • Payments, payouts and ad account review
    • Roadmap ranked by impact against effort

    Yours to keep, whether or not we build any of it.

  • Fixed scope · 4–8 weeks

    Growth sprint

    One outcome, shipped and measured. A checkout rebuild, a search overhaul, a payout engine, a tracking rebuild — scoped up front, demoed weekly.

    • Written scope and success metric
    • Design and build in one team
    • Weekly demo of working software
    • Measurement in place before launch
    • Documentation and handover

    Good when you know exactly what you need next.

  • Fixed scope or retainer · 8 weeks+

    Marketplace build or rescue

    A multi-vendor platform built properly from the start, or an existing one taken off the floor: money movement, search, trust, performance and the ops tooling your team is missing.

    • Architecture and data-model review
    • Payments, commission and payout design
    • Seller onboarding and seller portal
    • Search, ranking and catalogue quality
    • Admin and reporting your ops team owns

    Good when the platform is the business.

  • Monthly retainer

    Growth partner

    A standing squad across design, engineering, ads and lifecycle, working a shared roadmap — the closest thing to an in-house team without the hiring.

    • Shared roadmap, reviewed monthly
    • Continuous CRO and experiment program
    • Ads and lifecycle managed end to end
    • Feature development each cycle
    • One dashboard both sides read

    Good when growth is the job, not a project.

True of every engagement

  • You own the code, the repo and every account
  • You talk to the people doing the work
  • A weekly demo, not a weekly status email
  • A written recommendation each cycle — including what to stop
  • Everything documented and handed over
  • Cover across India, Australia and the US

[12] Portfolio

Work we’ll walk you through.

Stores and marketplaces we’ve built and grown. On a call we’ll screen-share the real thing: code, dashboards and all.

[13] Reviews

In our clients’ words.

Quotes from clients, on the record. Ask on the call and we’ll put you in touch with people we work with.

  • “Zaggee has done so much work with Headless platforms, and we knew the Zaggee team was incredibly well-versed in that space.”
    Kelsey OliverManaging Director, Auzzie TurfRead about Auzzie Turf
  • “What’s particularly impressive is their ability to think beyond just the immediate project, sharing knowledge that benefits our company as a whole.”
    Silas GregoryCEO, OrevaRead about Oreva

Send us your store or marketplace. We’ll send back what we’d fix first.

No pitch deck and no 40-slide proposal — a short, specific list from the people who would do the work. Free, and yours to keep.

Get a free auditEmail usCall us