What Do I Set Out in Writing Before Developing Your Website or Application?

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

GitHub · LinkedIn.

Published: · Last technical review:

Before developing your website or application, I sign a contract with you and define in writing the deliverables, deadlines, and budget, with VAT explicitly stated. Every project is assessed individually. I describe what you need to solve and what outcome must allow reviewing scope, without taking features for granted.

Criteria: from an idea to an understandable deliverable

«I want an application» describes a direction, but it does not let anyone know what behaviour you expect. As an editorial guide, I suggest explaining the problem first and then the outcome you need to be able to review. There is no need to start with names of technologies to define a task that your tool must resolve.

A concrete deliverable must be readable without having to mentally fill in what is missing. In any custom development, merely listing the names of screens is not enough to define what actions each user can perform or what rules the system must apply. If you need to consult records, it is best to describe who consults them, what information they view, and why they need it.

I do not present these examples as features included in your commission. They are questions to help write your inquiry more effectively. A requirement can be valid and, at the same time, require analysis before becoming quoted work. Maintaining that distinction prevents an exploratory conversation from looking like a list of accepted commitments.

Proof of my own: my published scope process

My website establishes that we define concrete deliverables, deadlines, and budget in writing, with VAT explicitly stated, before starting development. It also explains that every project is assessed individually and that the timeframe depends on its complexity and requirements.

That is the condition I uphold here. I do not add a mandatory contract form, a rigid approval system, or a change policy that the source does not detail. The published process supports prior agreement, but does not allow inventing all its documents.

During development, I show functional progress updates so that you can test them in your browser or mobile phone. To prepare for that review, I suggest writing down the deliverables so that you can recognise what you wanted to achieve. This is a recommendation for clarity, not an already documented acceptance protocol.

An editorial outline to organise your scope

Editorial outline, not a screenshot or accredited contractual process:

You can walk through it with a hypothetical example. Instead of «I need reports», describe what information you need to consult and for what purpose. Then identify what you do not know yet. Do not turn the example into a promise of integration, migration, or offline operation.

Preparation step What to write What to avoid
Problem A task you need to resolve A list of technologies without purpose
Users Who is involved and what they need to do Taking all permissions for granted
Deliverables What you expect to be able to review «Everything necessary» without definition
Starting point What tool or information exists Assuming that any transfer is included
Open questions What remains to be analysed or decided Presenting it as already approved work

Limits: when you should NOT finalise scope yet

You should not approve a description you do not understand just to start sooner. As a general criterion, if you cannot distinguish what is included from what remains to be reviewed, you need to clarify that part. The goal of the document is not to accumulate technical terms, but to make the work you are about to contract understandable.

Nor should you hide a dependency under a generic phrase. If you already work with spreadsheets, databases, or other tools, indicate this in your initial inquiry to assess whether they require prior analysis. Identifying that need does not mean that an integration or migration is part of the offer without prior analysis.

If you already have PHP/MySQL and need a change, separate maintenance from a new feature. My maintenance offering includes security updates, backups, and bug fixes; new features are quoted separately. Do not use an evolution request as if it were an automatically included fix.

What remains to be specified regarding changes

I sign a contract with you before starting. 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.

You can prepare a description of the change you want to inquire about. Indicate what behaviour you had planned and what you need now. This is a conversational guide; it does not attribute an as-yet undocumented contractual rule to my service.

What common agreements I would review with you

Ownership and hosting should not be resolved by analogy with another project. For websites, code and content belong to the client; for applications and other developments, I agree on ownership or licensing on a case-by-case basis. You may arrange your own hosting or have me manage it; the domain is defined in the scope.

To prepare those decisions before requesting a quote, note down your preferences regarding code ownership or licensing, hosting arrangements, domain management, concrete deliverables, and target date. Remember that my published figures are starting prices per service (custom web application or PWA from €3,500 + VAT*, lead generation website from €1,500 + VAT*, and PHP maintenance from €60/month + VAT*), and that the final budget is always established in writing after assessing your case. The self-assessment helps organise your inquiry; it does not replace project analysis or generate a binding quote.

How to turn your preparation into a useful inquiry

I would start with an explanation you can read straight through: what you have, what you need to resolve, and what you expect to achieve. Add your pending questions without attempting to answer them with assumptions. An incomplete but identified scope is far more useful for discussion than an extensive list of commitments that nobody has reviewed.

Then we can place the need in the corresponding service. You do not need to contract all services simply because several related questions appear. You can inquire about a new website, an application, or a PHP evolution; the scope must address the specific problem, not add options without justification.

What happens after you send me your inquiry

When you write to me via the form or WhatsApp, I reply within 24-48 business hours with an initial assessment of your case. If the project is a good fit, we draw up the scope with verifiable deliverables, ownership and hosting terms, timeframe, and budget with VAT itemised before writing code.

During development, I maintain direct contact with you from Blanes (Girona) across Spain and show you functional progress updates in your browser or mobile phone so you can check them against what was agreed.

Frequently asked questions

What deliverables do we agree on?

We define concrete deliverables in writing before starting development, along with deadlines and budget, with VAT explicitly stated. To prepare for that conversation, describe what you need to resolve and what outcome you expect to be able to review. I do not turn an example from this article into an included feature without analysing your project.

How do I handle scope changes?

If something different from the agreed deliverables arises during the project, I do not take it as included in the timeframe or budget; this article does not set a contractual change procedure. In PHP maintenance, any new feature is quoted in writing separately from bug fixes.

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

* Indicative starting prices, subject to conditions and change. VAT not included: charged separately at the applicable rate. The final amount is set in a written quote after reviewing your project and is binding only once accepted by both parties. Quotes are valid for 30 days. Full terms: General terms.