I work from Karachi. Most of my clients do not.
That is not a branding line — it is a scheduling constraint. Overlap with US East might be early evening for me. Overlap with UK is afternoon. Australia flips the day entirely. If I run kickoffs like a co-located agency, I lose sleep and the client still feels underserved.
So I redesigned kickoff as a system: async briefs first, short overlap calls second, trust artifacts always. This is how I run a client kickoff from Karachi without pretending we share an office.
What kickoff is for (and what it is not)
Kickoff is not a two-hour status meeting with screensharing trauma. Kickoff is alignment on:
- The outcome that counts as done
- The systems we will touch
- The access we need on day one
- The communication channel and response expectations
- The risks already visible in the brief
If those five are clear, the project can move while I sleep and while the client sleeps. If they are fuzzy, every timezone gap becomes a day of delay.
I would rather spend energy writing a sharp async brief than performing availability theatre.
The async brief I send before any call
Before we book overlap time, I ask the client to answer a short written brief — or I draft it from their RFP and ask them to correct it. Typical sections:
- Business outcome in one paragraph (not “make it modern”)
- Surfaces in scope: theme templates, apps, admin, AI pipeline, analytics
- Out of scope explicitly listed
- Success metrics they already track (conversion, support volume, publish time)
- Constraints: brand, legal, peak sale dates, frozen apps
- Access checklist: Shopify Collaborator, Git, analytics, staging, brand assets
- Decision owners: who can approve copy, design, and production deploys
I send this in Notion, Google Doc, or email — whatever they already use. The tool matters less than the written record. When someone joins mid-project, the brief is the onboarding.
Karachi advantage: I can prepare and revise this while US teammates are offline, then land a clean version in their morning.
Overlap hours: fewer, sharper, recorded
I protect overlap for decisions, not monologues.
A good first call from my side runs 30–45 minutes:
- Confirm the written brief (five minutes of corrections, not a live rewrite)
- Walk the risk list I already typed
- Agree on the first milestone and the definition of done
- Confirm channels: Slack or email, urgency rules, weekend expectations
- Book the next decision checkpoint, not a vague “weekly sync”
I record with permission or send a written summary within a few hours. People in other zones should not need to attend to know what changed.
If a stakeholder cannot make overlap for two weeks, we do not freeze. We decide what can proceed on async approval and what is truly blocked.
Trust without a shared office
Remote trust is built with artifacts, not vibes.
What I ship early on purpose:
- A living decision log (why we chose this theme approach / this model / this app)
- A credentials map that never puts secrets in chat history
- A staging URL with a simple QA checklist the client can click through
- Estimates written as systems (pipeline steps), not heroic hours
- Clear “I am blocked on X” messages instead of silent progress bars
Clients do not need to see me in an office. They need to see that work compounds while they sleep and that surprises are rare.
I am careful with overpromising timezone coverage. I do not market 24/7. I market predictable overlap plus strong async. That honesty filters the wrong retainers early.
Handling the awkward parts
Delayed replies are not disrespect
I explain my working window once, in writing. If a message arrives at their 4 p.m. and my midnight, it gets a thoughtful answer in my next block — unless we labeled it P0. P0 means production down or revenue-stopping bug, not “can we try a different blue.”
Design feedback across zones
I batch feedback. A Figma link with numbered comments beats a call where half the room is tired. When a call is required, I send options ahead of time so the meeting chooses, not brainstorms from zero.
Payment and contracts
International work needs clean SOWs, milestone billing, and clear revision rounds. Timezone friction gets worse when commercial terms are fuzzy. I settle that before deep build work.
A sample first-week cadence
- Day 0 (async): brief + access checklist sent
- Day 1: client returns comments; I revise scope
- Day 2: short overlap kickoff; staging plan agreed
- Days 3–5: foundations in staging; daily written updates in their morning
- End of week 1: recorded walkthrough or annotated Loom; decide go/adjust
Notice how few live meetings that is. The project still moves.
Tools I keep boring on purpose
People ask which stack I use for async kickoffs. The honest answer is whichever the client already opens daily. I have run the same process in Notion, Linear, email threads, and a shared Google Doc. Switching a client onto my favorite tool is not a deliverable.
What I standardize instead:
- One living brief document with a last-updated stamp
- One access checklist with owners and due dates
- One decision log with date, decision, and who approved
- One staging checklist the non-technical stakeholder can run without me on the call
If Slack is the channel, I still paste decisions back into the brief. Chat is for speed. The brief is for memory. Six months later, when someone asks why we disabled an app embed, the answer should not live in a collapsed thread from a Tuesday night.
Working with agencies and internal teams
Sometimes I am the only external builder. Sometimes I sit beside an in-house marketer, a US designer, and another developer. Kickoff changes shape, not principles.
With mixed teams I add:
- A RACI-lite note: who drafts, who approves, who merely needs FYI
- A single source of design truth (Figma) and a single source of scope truth (the brief)
- Explicit “no parallel Slack DMs for scope” rule — scope changes go in writing where everyone can see them
Timezone gaps punish informal scope drift. Someone in New York agrees to a feature on a huddle; I am offline; a designer in Europe starts mockups; the brief never updates. Async-first kickoff is how I prevent that expensive social game.
A note on energy and boundaries
Working across zones can quietly turn into always-on. I treat that as a project risk, not a badge.
Practical boundaries I state early:
- Normal response window in writing
- P0 definition that is narrow
- No expectation of same-hour replies for non-blocking questions
- Scheduled deep-work blocks where I am heads-down even if Slack is green
Clients who need a follow-the-sun team with three overlapping seniors should hire that shape. Clients who need a senior builder with strong async habits and predictable overlap are a fit. Kickoff is where we discover which story is true — before resentment shows up in the timeline.
What I optimize for after six-plus years
I have shipped client work across enough zones to know the failure mode: heroic late-night calls that create the illusion of alignment while docs stay empty. The opposite works better — boring documentation, sharp overlap, and respect for both calendars.
If you hire from Karachi (or you are in Karachi hiring globally), design the kickoff for async first. The call is confirmation, not discovery.
That is the playbook I use so timezone is a constraint we plan around — not an apology we repeat on every standup.