How Do I Work With You Remotely During Development?
By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.
Published: · Last technical review:
I work remotely from Blanes (Girona) with direct contact across Spain. You contact me via the form, email, or WhatsApp, I reply within 24-48 business hours and, after agreeing on scope and timeframe in writing, you view and test real functional progress from your computer or mobile phone.
I sign a contract with you before starting.
Criteria: what you need to be able to do during development
Working remotely should not leave you with an explanation you cannot verify. To assess coordination, I suggest reviewing who answers your inquiry, how you can raise questions, and what opportunity you have to test what is being developed.
My published working terms specify direct contact. You work directly with me, without account managers or intermediaries between your explanation and the person coding the tool. The conversation is with me, and functional progress is shown so that you can test it from your browser or mobile phone.
Furthermore, receiving a message saying the project is progressing is not the same as opening a link and testing for yourself how a screen or record works. An explanation serves to place progress in context; a test allows you to review a specific action. They are not automatic substitutes, nor do they prove on their own that the entire project is completed.
Own proof: the channels and progress updates I publish
On my website, I explain that I work remotely from Blanes, Girona, across Spain. You can speak directly with me by email at info@buangh.com, via WhatsApp, or through the form. The initial inquiry serves to explain what workflow or website you need to resolve.
I also state that I code your web application, PWA, or lead generation website communicating directly with you and showing you functional progress. You can test them in your browser or mobile phone. That is the evidence from my process that I can transfer to this article.
I do not add a mandatory meeting frequency or a specific tracking platform. Those details do not appear as published terms. If you require a specific form of coordination, it is best to raise it to review how it fits into the project, rather than assuming that any arrangement is included.
Initial response does not mean continuous availability
I reply within 24-48 business hours when you send your inquiry via the form. That is a response time to assess your case, not a development delivery timeframe. Nor should it be interpreted as a guarantee of immediate support for any incident.
Deliverables, timeframe, and budget are defined in writing before starting development. Therefore, an initial response and project planning have distinct roles: the first opens the conversation; the second defines the work we agree upon.
A guide to testing a functional progress update
The following guide is an editorial review recommendation, not a documented contractual protocol. I suggest choosing a task related to the scope and describing how you expected to perform it. Then observe the behaviour and note down what you need to clarify.
| What you review | How to describe it | What you must not conclude |
|---|---|---|
| Action you are testing | What you were trying to do | That the entire tool has been reviewed |
| Observed outcome | What appeared or what happened | That a doubt implies a known technical cause |
| Expected outcome | What you needed to achieve | That every preference was an agreed feature |
| Context | Browser or mobile phone you are testing from | That you must share private data to explain yourself |
In a hypothetical example, if a query does not display the information you expected, describe the action and the difference. You do not need to diagnose the code or propose a technical solution for the question to be useful. Describing the behaviour allows us to discuss something concrete.
If what you want now differs from what was agreed, you can also point it out. Separating a question, a possible bug, and a new requirement helps explain the request. It does not impose a change request process; it ensures that scope does not disappear from the conversation.
Limits: when you should NOT assume standard coordination
You should not choose remote work assuming physical on-site presence at your premises. My offering is presented as remote development across Spain. If your need depends on a different condition, it must be reviewed explicitly and not inferred from my location.
Nor should you understand «functional progress updates» as unrestricted access to any environment or information. During the project, I provide you with access to view and test functional progress in your browser or mobile phone; technical server or administration access is agreed separately according to scope. In your initial inquiry, you can explain what you need without sending passwords or third-party data.
If you expect a specific project management tool or meetings at a particular cadence, state it as a requirement to review. I do not publish it here as an already available condition. Direct communication does not automatically imply any channel, availability, or format you might imagine.
How to prepare an exchange that helps you decide
I suggest separating three types of information: your requirement, the observed behaviour, and the question you want to resolve. If you mix all three into a broad statement such as «this does not work», it will be harder to determine which part needs review.
It is also useful to keep the reference to the deliverable you were testing. Linking each comment to the deliverable you are testing allows you to explain any question quickly without needing to use technical jargon. The goal is for you to be able to explain a question without having to translate it into programming language.
Before sending me your initial inquiry, note down what deliverables you expect to review, what target date you have in mind, and whether you already use existing tools or data that we should evaluate.
Coordination proof must correspond to your project
A reference from in-house software can help you get to know my work, but it does not replace your functional progress updates. Evaluating a reference and reviewing your commissioned project serve different purposes. Keeping them separate prevents interpreting a screenshot as approval of a feature you need to commission.
When you tell me about your case, also clarify who will be able to test the progress updates and what workflow they need to review. That is helpful information for understanding operations, not a promise about a schedule of meetings. The specific agreement must correspond to the scope we define.
How we start working together remotely
The first step is to write to me via the form, at info@buangh.com, or through WhatsApp explaining what workflow or website you want to resolve. I reply within 24-48 business hours with an initial assessment.
Before starting development, we agree in writing on the concrete deliverables, timeframe, and quote with VAT explicitly stated, so that throughout the project you can test each functional progress update against a clear benchmark.
Frequently asked questions
How do we communicate directly?
You can communicate directly with me by email at info@buangh.com, via WhatsApp, or through the form. I work remotely from Blanes across Spain. When you submit your inquiry via the form, I reply within 24-48 business hours; that timeframe is for the initial response, not for the delivery of a website or application.
How do you test functional progress updates?
During development, I show you functional progress updates so you can test them in your browser or mobile phone. To prepare your feedback, I suggest describing what you were trying to do, what you expected, and what you observed. This is a review guide, not a meeting schedule or an acceptance procedure not detailed in the source.