Our first client was ourselves.Seven self-hosted systems, in production
Systems live
7
Delivered to clients
3
Custom site modules
134
Languages in production
10+
All seven
What each one actually does
DTC storefront automation
Two storefronts built from scratch with 134 custom site modules between them, with content, support, product imagery and 10+ languages running on one connected line. This is also the only page on this site where every number has a stated source.
- Two self-written themes, structure shown
- Seven measured numbers, each with its source
- Why building the site ourselves is what made the automation possible
An email system wired into the loop
Email isn't a piece of software here, it's a node in a process. Incoming mail arrives already matched to the customer and order, with a reply drafted; outgoing mail is triggered by business events. Address count isn't priced per person, and the send button stays with a human.
- Three things an off-the-shelf inbox can't do
- The same message, before and after
- Three rules we don't bend
Affiliate and dealer network
Creators and dealers share one underlying system: per-partner tracking and commission rates, store and service-point maps, after-sales capability matching. Off-the-shelf affiliate platforms only cover the online half — this one also settles what happened in a physical store.
- Why an off-the-shelf platform didn't fit
- Attribution for offline visits
- What keeps settlement day from becoming an argument
Three-tier partner management
Head office, region, partner — people spread across the country, with every fact previously travelling upward by self-report. The entry point is the messaging tool they already use daily: nothing to install, nothing new to learn. Delivered and deployed on the client's own servers.
- The risk isn't technical, it's that nobody uses it
- Duplicate records caught as they happen
- The keys stay with the client
Marketing content pipeline
Product photography goes in; scene imagery, short-form video, copy and hashtags come out, packaged and pushed to the person who publishes, with a publishing log and platform data flowing back. Work that used to pass between three roles now runs end to end with one. Also deployed on the client's own servers.
- A good-looking image isn't enough — it has to be your product
- Produced but never published is the usual failure
- The module clients ask about most is the one that tracks spend
Multi-department rollout
A retailer running physical stores alongside its own storefront. One order used to travel between seven departments as screenshots and group messages, with somebody retyping it at every handover. Finance, people, engineering, sales, e-commerce, design and store management now sit on one foundation, sharing one knowledge base and one permission model. Delivered onto the client's own servers, and new roles are added by them.
- What each of the seven departments handed over
- Why this page carries no figures at all
- After handover, they're the ones adding to it
Our own visual production desk
One service for images, another for cutouts, another for video, another for voice — output scattered across their back offices, prompts with nowhere to accumulate, no single gate on spend. So that layer is ours: twelve workbenches, eleven job types on one queue, five domains each with its own recipe system, and a daily spend ceiling that prices every call before it runs. It isn't delivered to clients; it's what we use daily.
- Seven decisions that haven't changed since
- Why the model never sets type on an image
- Three pages here mention imagery — which covers what
Before you read these
One thing said up front
The measured figures in these case studies are our own results, not a promise about yours. The same piece of work can be several times larger at a different company, so using somebody else's numbers to model your payback doesn't help you.
Next