Five builds documented end to end — the brief, what we decided, what we shipped and what happened after launch. Screenshots go in the frames; send them over and we drop them in.
Many threads, one launch date.
Design, build, content, integrations and QA run as separate tracks that have to meet at one point. Every case below is that convergence, documented.
Laydo Classifieds
A classifieds platform for Pakistan: listings, category search, in-app chat between buyer and seller, and paid promotion slots.
Listing feed
Chat thread
Promotion checkoutLaunch a marketplace where a seller can post in under a minute from a mid-range Android phone on a slow connection.
Node and Postgres behind a React front end, image compression on the client, search built on indexed category and city columns rather than a separate engine.
Posting flow down to four screens. Paid promotion runs as a self-serve purchase, no admin step in the middle.
React
PostgreSQL
S3 + CDN
Primearz
Our own commerce platform, live in production and the place we test every checkout, catalogue and performance decision before it reaches a client build.
Storefront
CheckoutRun our own store on our own code, so client advice comes from a system we operate rather than a demo.
Catalogue, cart and order pipeline with local payment methods, plus an admin that non-technical staff use daily without training.
Every checkout change ships here first. Client stores inherit patterns already tested against real orders.
WooCommerce
Custom theme
Local gateways
Bechify POS
Point of sale for food and restaurants: table map, kitchen tickets, offline-first sales and end-of-day reporting.
Table map
Order screen
Daily reportKeep taking orders when the internet drops mid-service, and reconcile without a manager doing arithmetic at closing.
Local-first data with background sync, printer routing per kitchen station, and a shift report that closes in one tap.
Service continues through outages; sales appear in reports once the connection returns.
IndexedDB sync
ESC/POS printing
Postgres
Restaurant ordering assistant
A WhatsApp Cloud API assistant that answers menu questions, takes bookings and hands the thread to a human when it should.
Conversation
Handover inboxStaff were answering the same six questions all evening while orders waited.
Grounded the assistant in the live menu and policy documents, with strict rules on price and availability, and a one-tap route to a human.
Routine questions resolve in the thread. Staff time goes to the conversations that turn into orders.
Node.js
Retrieval over docs
Webhooks
Subscription billing plugin
Recurring payments for a WooCommerce store: renewals, failed-payment recovery and a customer portal for pausing and switching plans.
Plan settings
Customer portal
Dunning emailOff-the-shelf subscription plugins could not express the client's pricing, and support was chasing renewals by hand.
A purpose-built plugin on Woo's own order model, with retry schedules, proration on plan change, and a portal customers can use unassisted.
Renewals run unattended. Failed payments recover on schedule instead of turning into cancellations.
PHP
Stripe
WP Cron
Buraqstore multivendor app
A Shopify marketplace app: vendor onboarding and portal, order splitting, commission tiers and automated payout statements.
Vendor dashboard
Commission & payouts
Storefront listingRun a marketplace on Shopify without giving every vendor access to the store admin, and settle earnings without a spreadsheet.
An embedded app with a separate vendor portal: product submission with operator approval, per-vendor order routing, commission tiers and payout statements built from settled orders.
Vendors self-serve listings and fulfilment; monthly reconciliation is a report rather than a week of work.
Admin GraphQL API
Polaris
Webhooks + queues