Knowing the stages of a project helps you plan your own time. You are needed at certain points, and your quick answers there are what keep the schedule.
1. Discovery
We go through your requirements together and turn them into a written scope: pages, user roles, functions and connections to other systems. Open questions are settled here, because a question answered now costs minutes and the same question during development costs days.
Your part: explain how your business works, answer questions, and approve the scope.
2. Structure and design
For a website, we propose the structure of the pages and then a visual design, usually of the home page and one inner page first. For software, we prepare screen layouts of the main workflows. You see how it will look and work before anything is programmed.
Your part: give consolidated feedback. Say what works and what does not, and why. "Make it pop" is hard to act on; "the phone number should be visible without scrolling" is easy. The quotation states how many rounds of design changes are included.
3. Development
The approved design is built into a working system: pages, forms, the admin area, the database, payments and messages. Work is done on a development address that only you and we can open. For larger projects, we deliver in stages, so you can try finished parts while the rest is being built.
Your part: send the final texts and pictures, and look at each stage when we ask.
4. Content
Texts and pictures are placed, either by us or by you through the admin area after a short introduction. Search-engine basics are set up at the same time: page titles, descriptions and readable addresses.
5. Testing
We test on phones, tablets and computers, in the common browsers, and we test every function: forms, sign-in, orders, payments, emails and permissions. Then it is your turn.
Your part: use the system as your customers and staff would. Place a test order, fill in each form, try to do what you are not supposed to be able to do. Send all findings in one list, with the page and what you expected to happen. We correct them and you check again.
6. Launch
When you approve, we go live:
- the system is moved to the live hosting;
- the domain is pointed to it and the security certificate is issued;
- email addresses are set up or checked;
- old addresses are redirected to the new pages, so that search engine rankings and bookmarks survive;
- analytics and the search console are connected;
- a backup routine is put in place.
We choose a quiet time for the switch and watch the site afterwards.
Your part: be reachable on launch day, and check the live site once more.
7. Handover and training
You receive the logins, a short guide or a training session for the admin area, and the source files where the agreement includes them. Change the passwords we used during the project.
8. Support after launch
Every project includes a support period, stated in the quotation, during which we fix faults at no charge. After that, a maintenance plan covers updates, backups, small changes and monitoring. See the article on care after launch.
How we stay in touch
- A named contact on our side.
- Regular updates at the rhythm agreed at the kickoff.
- A project ticket in the client area, where files, decisions and approvals are kept in one place. Decisions made on the phone are confirmed there in writing.
Payments
The price is divided into stages, for example at the start, on design approval and before launch. Each stage has an invoice in your client area. Work on the next stage begins when the invoice for it is paid.
What moves a deadline
- Material that arrives late.
- Feedback that takes weeks.
- New requirements in the middle of development.
- Access that is missing: a domain login, a payment gateway approval.
We tell you at once when the date is at risk and what would bring it back.
What keeps it on time
One decision maker, complete material at the start, feedback within two or three working days, and the discipline to put new ideas on a list for the next version instead of into the current one.