Most studios hand over a repository. We keep the keys. Everything on this board is software we wrote and a business we operate — storefronts, a carrier integration on Amazon's network, a publication, and the automation that keeps all of it moving while we sleep.
Content engineAI articles, creative and cataloguePRIVATERunning
Client deploymentsNamed under NDAPRIVATERunning
SEO AutopilotGenerate, validate, publishPRIVATEIn build
What we run
The ones we own, and the ones we cannot name.
Three of these carry our own money, which is a very different incentive from a launch date. The fourth is client work — described here, named on a call. Either way, the detail below is what is built, not what is on a roadmap.
Commerce · owned brandRunning
Mom & Zoey
A GOTS-certified organic kidswear label we own and operate — design, catalog, theme, checkout, ads and fulfilment. Three storefronts, one brand, and an edge worker that puts every shopper on the right one.
Custom Shopify theme shared across all three stores
Country detection at the edge, no third-party redirect script
COD and UPI in India, Markets pricing abroad
Server-side events feeding Meta, GA4 and our own store
Shopify app · Amazon Shipping IndiaRunning
Shipping Perfection
Buy Amazon Shipping labels for Shopify orders on your own rate card. We integrate; we never resell freight, so the Amazon contract stays with the merchant. Built because we needed it for Mom & Zoey first.
Rate, buy, cancel and re-buy labels — PDF, PNG or ZPL
COD taken from the order balance, then reconciled against remittances
Failed deliveries answered before they turn into returns
Tracking and fulfilment written back to Shopify automatically
Publication · Next.js + SanityRunning
Parenting Beyond Perfection
An editorial platform for parents, with an embedded CMS, moderated comments, newsletter and a research-to-draft pipeline. Our earlier site, yourparentingtips.com, now redirects into it rather than competing with it.
Work we do for other companies, running under their own brand. We do not list names or addresses here — if you would want your project kept off a studio website, so does everyone already on it. We will walk you through the relevant ones on a call.
Carrier, ERP and payment integrations with the failure paths handled
AI content and agent systems with approval gates in front of them
Measurement, edge infrastructure and workflow automation
The layer underneath
Content, search, measurement and automation — as one system.
None of these were bought off a shelf and bolted on. They were built because a store we run needed them, which is why they talk to each other instead of sitting in seven browser tabs.
AI article pipeline
Running
A conversational writer built on the Claude Agent SDK. It researches the topic, drafts in brand voice, calls its own validators, fixes what fails, and publishes with the metafields already set.
Claude Agent SDK
Self-correcting
Publishes to Shopify
Creative and catalogue generation
Running
Product photography, lifestyle scenes, ad creative and short-form video generated through Higgsfield against our own brand token sheet — then turned into full catalogue and listing sets rather than one hero image.
Higgsfield
Product + listing sets
Brand-locked
SEO Autopilot
In build
The same writing pipeline as a Shopify embedded app, so a merchant can regenerate or write an article without leaving admin. Seven validation gates run before anything can be published.
Shopify app
Bedrock
7 gates
Search and answer engines
Running
Classic SEO — schema, internal linking, index health, Search Console triage — plus GEO: writing so that answer engines quote the page instead of skipping past it.
JSON-LD
GSC triage
GEO / AEO
Realtime order alerts
Running
A custom Shopify pixel watches the storefront and checkout as it happens and pushes each event straight into a notification channel. You hear about the order, or the checkout that stalled, while it is still happening.
Custom web pixel
Live channel
Checkout signals
First-party event relay
Running
Storefront events go to our own subdomain instead of a tracker domain, get enriched at the edge with country, network and an authoritative timestamp, and fan out from there. The raw IP is never forwarded.
Cloudflare Worker
sendBeacon
No IP forwarding
Measurement you can trust
Running
Pixels and tags placed once and audited: GA4 and GTM, Meta Pixel with the Conversions API behind it, Clarity for session replay. Deduplicated, so one purchase is one purchase.
GA4 · GTM
Meta CAPI
Clarity
Automation fabric
Running
A self-hosted workflow runner holds the joins between systems: chat and RSS triggers into research and drafting, storefront events into analytics, order routines, and the alerts that tell us when something stops.
n8n
Webhooks
Scheduled runs
Social publishing
Running
Scheduled social and paid creative produced against the same written brand system, then read back against what actually performed rather than what looked good in the deck.
Scheduled posting
Meta Ads
Performance readback
Geo routing at the edge
Running
A worker resolves the visitor country before the page renders and puts them on the storefront priced in their currency — no third-party redirect script, no flash of the wrong store.
We take the work we have already had to do ourselves.
Mobile, web, desktop and cloud engineering are all on the table. These four are where we can show you the running version rather than a case study.
Commerce systems
Shopify themes and apps, multi-country storefronts, Markets pricing, checkout and catalog work, and the operational plumbing behind them.
Three live storefronts on one shared theme
Carrier and back-office integrations
OAuth into a carrier or ERP, rate and label APIs, webhook ingestion, reconciliation, and the failure paths nobody demos — cancelled labels, failed deliveries, unmatched payments.
Amazon Shipping India, end to end
AI and agent systems
Agents that do real work and check themselves: tool use, structured output, validation gates, human approval before anything spends money or ships.
Claude Agent SDK in production
Measurement and automation
Server-side events, pixel and tag hygiene, edge workers, n8n orchestration, and dashboards that answer a question rather than display a number.
Edge relay + n8n running daily
How we work
Four steps, and the last one is the long one.
The numbering is the order, not a ranking — each step needs the one before it.
What the business actually needs to move, what the current systems can and cannot do, and what we will measure to know it worked.
1–2 weeks
02
Design and de-risk
Interface design, data model and API contracts, plus a prototype of whichever part we are least sure about — usually the third-party one.
2–4 weeks
03
Build and launch
Weekly increments behind automated checks. It goes live when the whole loop closes, not when the happy path renders.
4–10 weeks
04
Run it
Monitoring, iteration and the unglamorous operational work. We do this on our own products, which is why we are willing to do it on yours.
Ongoing
Start here
Tell us the part that keeps breaking.
A stalled checkout, a carrier that will not integrate, content nobody finds, numbers that disagree with each other. Send us the specific one and we will come back with what we would do about it — not a capabilities deck.