Heritage accessories. 40 countries. 12,000 customers. Zero outside help.
zamani is a One Bit brand built from scratch. Every system on this page was built in-house: no agencies, no consultants. This is what’s running today — and what we replicate for clients.
What the brand looked like before we built anything
zamani launched as a WooCommerce store selling heritage-inspired smartwatch bands. The product was strong. The backend was not. Every order required manual intervention. No tracking, no automation, no organic discovery.
Before: the gaps
- Speed 11.5 second page load — losing customers before they see the product
- Tracking No server-side events. iOS 14+ blocking most pixel data
- Cart recovery Zero system. Abandoned carts = lost revenue, full stop
- Geography Selling to one country. Zero currency switching
- Organic traffic No SEO presence. 100% reliant on paid ads
- Operations Manual order management, no post-purchase automation
The core problem
Most e-commerce stores at this stage spend on ads before they’ve fixed the plumbing. Every dirham spent on traffic was landing on a store that loaded slowly, tracked poorly, recovered nothing, and converted at a fraction of its potential.
The answer wasn’t more ad spend. It was building the infrastructure that makes ad spend work.
We started with the foundations before touching anything visible.
Five systems. Every one still running.
These aren’t one-time fixes. They’re operational systems that compound over time — each one making the next more effective.
How: Bootstrap-native performance stack, image optimization pipeline, and a custom Cloudflare Worker that caches currency-specific HTML at the edge — so every visitor gets a fast, correctly-priced page without server round-trips.
How: WooCommerce webhooks feed into n8n, which sends matched events to the Meta Conversions API server-side. Deduplication logic prevents double-counting. The result: ad platform sees what actually happened, not what the browser reported.
How: n8n captures the cart abandon event from WooCommerce, waits the optimal delay window, then triggers a timed sequence — email first, then a WhatsApp message for high-value carts. The sequence stops automatically when a purchase completes.
How: WooCommerce Multilingual for currency management, a Cloudflare Worker for geo-detection and automatic currency assignment, and per-country shipping rules. Orders are validated against the visitor’s shipping country to catch currency mismatches before they become problems.
How: Product-level SEO optimization (title tags, meta descriptions, structured data), cultural keyword strategy for heritage search terms, dedicated landing pages for community-specific queries (Palestinian, Saudi, South Asian, Keffiyeh variants), and a content blog that builds topical authority over time.
The numbers, as of today
These are live metrics from a brand we still operate. Not a client case study from three years ago.
“We built zamani as a test of what a small team with the right systems can do. Every tool, every automation, every SEO page — it’s replicable. The same stack that runs here runs for clients. The only difference is that for clients, it’s already proven.”
Khaled Absi, One Bit
These aren’t custom solutions. They’re our standard stack.
We didn’t build one-off tools for zamani. We built reusable systems — and then we kept running them. Here’s what that means if you hire us.