Palash Sarkar's client relationships span three continents, and every one of them has been managed entirely remotely from Dhaka. A remote design process that actually works reliably requires more structure than working with a client down the street — here's how Palash Sarkar built his.
Over-Communicate Rather Than Assume
In person, a raised eyebrow or a pause in a meeting signals confusion instantly. Remotely, that signal is easy to miss entirely. Palash Sarkar builds in more explicit check-ins than an in-person relationship would need — written summaries after every call, explicit confirmation before moving to the next stage — because remote work removes the informal signals that catch misunderstandings early.
Async-First, Meetings as the Exception
Live calls across a nine or ten-hour time difference are expensive for both sides. Palash Sarkar structures most project updates as detailed async written reports and Figma comments, reserving live calls for genuinely complex discussions that benefit from real-time back-and-forth — kickoffs, key decision points, and final walkthroughs, not routine status updates.
Tools That Remove Ambiguity, Not Just Enable Chat
WhatsApp handles fast, informal communication; email carries anything that needs a paper trail; Figma comments keep design feedback attached directly to the relevant screen instead of scattered across a separate thread. Palash Sarkar deliberately matches the tool to the type of communication, rather than funneling everything through one channel regardless of fit.
Key Takeaways
A reliable remote design process isn't just working the same way with a screen in between — it requires more deliberate structure around communication than an in-person relationship needs. That structure is what's let Palash Sarkar deliver consistent, premium work for clients he's never met in person.
Book a free consultation with Palash Sarkar at palashsarkar.com/book-a-call — he works with startups, agencies, and global brands from Dhaka, Bangladesh.