Client work pays the bills. Products recycle the pain.
I did not wake up in Karachi with a “SaaS vision board.” I kept hitting the same sharp edges on Shopify and AI projects — metafield bulk edits that should have been a spreadsheet, admin clicks that begged for a Chrome extension, visa document questions that needed structured guidance. Those edges became MetaGrid, BulkFix, and VisaChamp. The lesson is portable: spot the repeated pain, ship a thin tool, do not wait for a platform.
The radar is the retainer
If you do client delivery long enough, patterns announce themselves:
- Three merchants curse the same admin workflow
- You write the same private script twice
- A kickoff question repeats so often you build a calculator for it
That radar is an unfair advantage agencies and freelancers waste when they treat every engagement as disposable. I treat repeated friction as product research that someone else already funded.
MetaGrid: spreadsheet truth for metafields
Shopify metafields are powerful. Editing them at catalog scale inside the default admin is not.
MetaGrid is a Shopify app for spreadsheet-style bulk metafield editing — spot gaps, find/replace, undo safely across the catalogue. It exists because “just export CSV and be careful” was not a serious answer for merchants who live in metafields for differentiated PDPs.
The product insight was not “build an app store empire.” It was: meet merchants in a mental model they already trust (the grid), and make undo non-negotiable. Undo is how you earn the right to bulk-edit.
BulkFix: thinner wedge, same wound
Before — and beside — a full app, there is room for a lighter wedge. BulkFix is a Chrome extension for bulk metafield editing inside the Shopify admin when you need a lightweight, in-browser workflow.
That is the shipping-small lesson applied to the same pain: meet the user where they already work, keep auth surface smaller, learn which features matter before you solemnize them in an app listing.
Not every product should start as an app. Some should start as an extension or a static utility and graduate when sync, roles, and undo history demand it.
VisaChamp: structured guidance, not vibes
VisaChamp is an AI visa assistant web app — structured guidance for travellers navigating visa requirements. It sits in a different domain than Shopify, but the engineering ethics rhyme with support bots and document QA: refuse when you lack the right section, prefer structure over chatty guesswork, treat wrong answers as expensive.
Cross-pollination matters. Patterns from VisaChamp (document attention, field extraction, confidence) show up in Shopify support bots. Patterns from metafield tools (validation, bulk safety) show up in how I scope AI catalog pipelines. Products teach the consultancy; consultancy feeds the products.
Do not wait for a platform
The failure mode I see in other builders (and in my own older notes) is waiting for:
- A perfect brand
- A full design system
- A multi-tenant architecture
- Certainty about monetization
- “When client work calms down”
Client work does not calm down. Platforms built in the abstract tend to solve imaginary jobs. Thin tools that steal a real job can grow into platforms later — or stay thin and still be useful. Both outcomes beat vapor.
The Playbook calculators follow the same rule: AI API cost, agent ROI, RAG cost, Shopify build cost, page speed revenue. Each one is a productized answer to a repeated kickoff question.
A practical loop you can copy
- Notice — write down the friction the same day you feel it
- Count — if it appears on a second project, it is a candidate
- Thin — in-browser or extension if possible; happy path + undo/safety
- Publish — a URL beats a private repo
- Listen — edge cases in your inbox are the roadmap
- Graduate or archive — promote when sync/auth/collab is demanded; archive without guilt
I keep the loop weekly so side projects survive client weeks — one hour: metrics, one ship, one cut. Products die from neglect more than from competition.
What I refuse to invent
No fake user counts. No fabricated ROI case studies. MetaGrid, BulkFix, and VisaChamp stand as shipped tools with real jobs. The Playbook explains how I work; it does not cosplay as a vanity metrics dashboard.
That constraint makes writing slower and more trustworthy. It also keeps product decisions honest: if a tool cannot be described by the job it steals, it is not ready.
How client scoping changed after shipping products
I estimate metafield work differently because I have felt bulk-edit failure modes firsthand. I estimate AI document features differently because VisaChamp taught me where confidence breaks. I estimate “small utilities” differently because I know an evening build can remove a recurring support tax.
Products are not a distraction from consultancy when they are born from consultancy. They are compounded judgment.
Time zones as a product constraint
Building from Karachi for global users means support and shipping expectations have to be designed in. Thin tools that run in the browser need less on-call. Apps with webhooks need alerting that does not assume you are awake. I bias early products toward architectures that tolerate async — same bias as client kickoffs across timezones.
That constraint sounds limiting. It is actually a filter for better MVPs: fewer moving parts, clearer jobs, less pretend 24/7 coverage.
What “thin” still owes the user
Thin is not careless:
- Explain what the tool will not do
- Prefer undo or dry-run on anything bulk
- Do not harvest paste data when local processing will do
- Write a one-page README before you tweet the launch
VisaChamp owes travellers careful refusals. MetaGrid owes merchants undo. BulkFix owes admin users a small surface that does not fight Shopify’s UI. Calculators owe transparent assumptions. Different products, same respect.
Saying no to the wrong product
Not every repeated pain should become your product. Sometimes the market is a feature inside Shopify you cannot outrun. Sometimes the only buyers are two agencies including you. Sometimes legal exposure (especially in visa or medical-adjacent advice) demands a shape you are not ready to staff.
Archive the sticky note. Keep the lesson. Use it to scope client work better. That is still a win from the radar.
If you only remember one thing
Spot the repeated pain. Ship the thin tool. Let the platform earn its way into existence.
I am Faraz Hussain — Shopify developer, web engineer, and AI automation consultant based in Karachi. MetaGrid, BulkFix, VisaChamp, and this Playbook are what it looks like when client weeks are allowed to leave tools behind. If you are sitting on a private script you have run for two merchants already, give it a name and a URL next.