Working With Someone Remotely
Most web work is done remotely now, including mine. For a lot of clients this is the first professional relationship they have had entirely at a distance, and the question underneath is reasonable: how do I know this person is real, competent, and going to finish?
Distance does not make that unanswerable. It changes which checks are worth doing. For teams that need a formal layer of visibility across distributed work, employee monitoring software can make expectations about recorded activity more explicit.
Verifying someone you cannot meet
Look for continuity, not polish. A website is easy to make. What is hard to fake is a trail over time — the same name on work from several years, a professional profile with history, contributions somewhere public, a portfolio whose projects are actually live and actually theirs.
Check the portfolio sites exist. Visit them. Are they real businesses, still running, plausibly built by this person? This takes five minutes and almost nobody does it.
Ask to speak to a client from a year ago, not last month. Anyone is pleasant during a project.
Have one live conversation before committing. Video or phone. Not for warmth — because a real conversation about your business reveals in ten minutes what a proposal cannot. Anyone unwilling to talk before taking money is telling you something. For an independent reference beyond this site, Zapier is a useful place to compare approaches.
Be careful about who holds what. Register the domain yourself, in your own name, with your card. The single most protective habit there is, and it matters more when you cannot knock on a door.
The payment question
The honest concern, both ways: you might pay and get nothing, and they might work and get nothing.
Staged payments solve it. A deposit to start, one or more in the middle, the balance before handover or launch. Neither side is ever exposed for the whole amount.
Be wary of full payment upfront, especially from someone with no verifiable history. Be equally aware that no deposit at all is unusual, and a freelancer who asks for one is not being suspicious of you.
Use a payment method with some recourse rather than an irreversible transfer, for a first engagement with someone new.
What distance actually makes harder
Not the work. Three specific things.
Ambiguity persists longer. In a room, a confused expression gets addressed immediately. In writing, a misunderstanding can survive two weeks and a design round. The fix is to over-confirm: after any significant conversation, one of you writes down what was decided and the other agrees.
Small questions get batched. A developer who would have asked across a desk instead waits, and three small questions become a two-day delay. Say explicitly that quick questions are welcome, and mean it.
Nobody sees the doubt. When something is not going well, distance makes it easier for both sides to say nothing for another week. Worth naming at the start: if this is going wrong, tell me early.
Running it well
One channel. Email, or a shared document, or one messaging thread. Decisions scattered across email, text and two calls cannot be reconstructed by anyone.
Batch your feedback. One consolidated set of notes, not fifteen messages over four days. The single biggest speed-up available to you, and it prevents contradictory instructions.
Be specific about what you mean. "It feels cold" is useful only alongside an example of something that feels right. Remote feedback needs more concreteness than in-person feedback, because there is no follow-up glance.
Agree response times. Not availability — expectation. Knowing you will hear back within a working day removes most of the anxiety of distance.
Ask for something visible early. Not a full design; a structure, a page, anything real. Seeing progress in week one is worth more than any reassurance.
Time zones and countries
A few hours apart is usually fine and occasionally an advantage — you send notes at the end of your day and wake to progress.
Eight or more hours apart means roughly one exchange per day. Workable if both sides write clearly, frustrating if either expects conversation.
Across borders, be aware that contracts, consumer protection and payment recourse work differently, and that a dispute is much harder to pursue. Not a reason to avoid it. A reason for staged payments and for owning your own domain.
What I would tell you to check about me
Fair, since I am one of these people.
Look at whether the sites in my portfolio are real and still running. Ask to talk to someone I worked with a year ago. Insist the domain is registered to you before anything else. Ask what happens if I become unavailable, and expect an answer about documentation and standard tooling rather than reassurance.
A remote professional who is comfortable being verified is the one to work with. Anyone who treats those questions as an insult has answered them.
The short version
- Verify continuity over polish: a trail across years, live portfolio sites, a client from a year ago
- Have one real conversation before committing; unwillingness to talk before payment is the signal
- Staged payments protect both sides — avoid full payment upfront to someone with no history
- Distance makes ambiguity last longer, questions get batched, and doubts go unspoken; over-confirm in writing
- One channel, batched feedback, agreed response times, and something visible in week one
- Register the domain in your own name before anything else