All thoughts
Behind the Scenes1 min read
That Mumbai Client Trip
Three days, one whiteboard, way too much filter coffee. Here's what actually happens on an on-site architecture sprint.
Three days, one whiteboard, way too much filter coffee
Back in May 2025, right before joining Gohil full time, I flew to Mumbai for an on-site architecture sprint with a freelance client. Most of my work until then had been remote, so this was a different kind of pressure.
Turns out, architecture decisions hit different when you're in a room with the people who have to live with them. No Slack lag, no 'let me check and get back to you'. Just a whiteboard, a marker running out of ink, and a client asking hard questions in real time.
- Mapped out the entire system architecture from scratch, in person, in a day
- Learned that remote habits don't always translate to in-person sprints
- Realized how much faster trust builds face to face than over email
Survive three days of back-to-back architecture discussions
Not oversell what could actually be built in the timeline
Try the local food between meetings
That trip ended up shaping how I approach client conversations even now, less about the perfect stack, more about aligning expectations before a single line of code gets written.
1 view
Comments (0)
Loading comments...