Every project is different, but most follow a similar path. Knowing the stages helps you plan your time and see where your input matters most.
1. Discussion and scope
You explain the problem, the users and the goals. The developer asks questions, then writes down what will be built, what will not, and roughly how long it will take. Your job here is to be clear about priorities.
2. Quote and agreement
The scope becomes a quote or proposal with price, timeline and terms. Read it carefully and ask about anything unclear. Changes are easier to agree before work starts.
3. Design
Screens and layouts are sketched or mocked up before any code is written. This is the cheapest time to change your mind. Give feedback on the mock-ups from the view of the people who will use the product.
4. Building
Developers build the product, often in steps, so you can see progress and test early versions. Quick, clear feedback during this stage keeps the project on schedule.
5. Testing
The product is tested on different devices and with realistic data. You test it too, using the tasks your real users will do.
6. Launch
The product goes live. Plan the date with your team, and decide who handles questions from the first users.
7. Support and improvement
After launch there are fixes, updates and new ideas. Agree in advance who looks after hosting, security updates and small changes, and how that is priced.
The biggest cause of delay is usually slow decisions and changing scope part-way through. A clear brief and one person who can approve work keep things moving.
What you need to provide at each stage
- Discussion: clear goals, users and priorities.
- Quote: questions and a decision.
- Design: quick feedback on mock-ups and your brand files.
- Building: text, photos and answers to questions as they come up.
- Testing: time to try the product with real tasks.
- Launch: a decision on the date and who handles first questions.
Why projects run late
- Slow replies to questions or approvals.
- Content that arrives late.
- Many people giving different feedback.
- New features added part-way through.
- Unclear goals at the start.
Keeping the scope under control
Write down what is included in the first version. When a new idea appears, put it on a list for a later version unless it replaces something else. This keeps the first launch on time and gives you real user feedback to guide the next one. See also what to prepare before you ask for a quote.
Frequently asked questions
How long does a project take?
It depends on size. A simple website can take a few weeks, while a larger system can take several months. Ask for a timeline in the quote and what you need to provide to keep to it.
Can I change my mind during the project?
Small changes are normal. Bigger changes affect price and time, so agree how changes are handled before the work starts.
Who owns the finished work?
This should be written in your agreement. Ask for it to state clearly who owns the design, the code and your data when the project ends.
Planning a project? You can message us on WhatsApp at +92 345 9081781 or send a note through the contact page, and we will tell you what we can do.
