How Do I Agree on Your Development Timeframe Without Promising a Universal Figure?

By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.

GitHub · LinkedIn.

Published: · Last technical review:

Replying to your inquiry and delivering a development project are distinct commitments. I reply to you within 24-48 business hours; the project timeframe is agreed in writing based on complexity and requirements. Before starting, we define deliverables, timeframe, and budget, without applying a universal figure to any website or application.

I sign a contract with you before starting.

Criteria: distinguish the initial conversation from the project

If you are looking for when you will have a tool ready, an answer that conflates initial assistance with development does not help you. The inquiry allows assessing your case. The commission timeframe requires a defined project and is not deduced from the speed with which you receive a message.

My published response time for the form is 24-48 business hours. I maintain that figure strictly as a response time. I do not turn it into a programming timeframe, deployment date, or incident resolution time. That distinction is important so that you can organise your decision without false expectations.

The development timeframe is agreed in writing based on the complexity and requirements of the project. I do not publish a universal duration for a lead generation website, a web application, or an evolution of existing PHP. My process requires assessing each project individually.

Proof of my own: what I agree on before starting development

On my website, I explain that we define concrete deliverables, deadlines, and budget in writing, with VAT explicitly stated, before starting development. That is why I never publish a generic fixed deadline before knowing the actual scope of your commission.

I also explain that during development, I show you functional progress updates so that you can test them in your browser or mobile phone. A progress update allows reviewing part of the work, but should not automatically be interpreted as a full delivery. This is a general technical distinction, not a new condition on your commission.

That is why, when you ask me about the timeframe, I need to understand what you want to resolve. Defining a new tool is not the same conversation as reviewing a requirement on an existing application. Launching a lead generation page does not require the same work as building a multi-property operational PWA or evolving an existing PHP application.

What information helps formulate the question about the timeframe

The following list is an editorial preparation guide. It does not establish an estimation formula or a delivery policy. Its purpose is to prevent «I need it soon» from being the only information available to describe your requirement.

Deliverables
What concrete screens, features, or outcomes you expect to review.
Starting point
Whether you are starting from an idea, a website, or an application already in operation.
Target requirement
Why you want to have the project up and running and what context makes that date relevant.
Existing data or tools
What would need to be analysed before agreeing on potential connections or transfers.
Pending questions
What decisions are not yet made and could alter the description of the work.

The complexity of a development does not depend solely on the visual appearance of a screen: its behaviour also matters. A behaviour may require decisions about data, users, or existing tools. I do not claim that those tasks are part of your budget: I explain why we need to describe them before promising a delivery.

The date you need is not an already accepted date

When preparing your inquiry with the checklist, you can indicate your target date alongside the deliverables you need and any existing data or tools we should analyse. You can raise it even if you do not yet know how it fits: it provides context for our conversation, not an automatic reservation or a commitment acquired by completing a self-assessment.

Connecting your timeline objective with the outcome you expect allows you to explain your requirement without pretending that all decisions are settled. If something remains pending, it is better to identify it than to hide it under an apparent estimate.

Limits: when you should NOT accept a figure without scope

You should not compare proposals based on an isolated duration if they describe different work. As a general recommendation, I would first check whether you can recognise the same deliverables and the same pending questions. Comparison requires context; a date on its own does not explain what you are contracting.

Nor should you interpret «custom development» as availability for any arbitrary schedule. I do not publish that guarantee. If a specific timeline requirement exists, you must raise it so it can be reviewed alongside the complexity and scope of the project.

If a new feature appears during the conversation, do not mentally add it to the previous timeframe. As a criterion of clarity, identify the change and ask how it relates to the scope. A new request must not be taken as included in the agreed deliverables, timeframe, or budget. This article does not establish a contractual change procedure.

How to read a progress update without anticipating delivery

Imagine that you can test one part of your tool, but other requirements are still to be reviewed. This is a hypothetical example to distinguish states, not an account of an actual project. The existence of a visible feature does not on its own answer all questions about the whole system.

I suggest noting down what you have tested, what doubt remains, and which deliverable it relates to. That way you can comment on the behaviour without turning it into a general conclusion about the entire project. You do not need to measure performance or provide a technical estimate to explain a doubt.

Similarly, a commercial reply does not mean that development has already begun. The published process places the written agreement prior to starting work. Maintaining that sequence helps distinguish initial interest from what we have actually defined.

Prepare a timeline inquiry that can be reviewed

I would start with a concrete sentence: what you need, what you have now, and why you want to get it up and running. Then I would add the timeline objective as a requirement to be analysed, not as a date that I have already accepted.

You do not need to invent an estimate for your inquiry to be useful. If you do not yet know the complexity, you can say so. My initial response serves to assess the case; the written definition of deliverables, timeframe, and budget belongs to the specific project.

How we establish your project timeframe in writing

Send me your inquiry via the form explaining what you need to resolve and whether you have a target date in mind. I reply within 24-48 business hours with an initial assessment of your case.

From there, we assess your project individually and establish in writing the concrete deliverables, the development timeframe tailored to its complexity, and the budget with VAT explicitly stated before starting.

Frequently asked questions

What causes the timeframe to vary?

The timeframe is agreed based on the complexity and requirements of each project. My website distinguishes between a lead generation page, an operational web application or PWA, and an evolution of existing PHP. To review your case, it is best to describe the deliverables and starting point, without applying a universal duration to all of them.

Where do we agree on it?

We define the timeframe in writing along with concrete deliverables and budget, with VAT explicitly stated, before starting development. If you have a target date, you can raise it as context. My reply within 24-48 business hours applies to the initial inquiry and does not replace that project agreement.

Web applications and PWAs

Web applications and PWAs

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

Lead generation websites

Lead generation websites

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

PHP maintenance and evolution

PHP maintenance and evolution

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

Related articles