Knowledge hub · Project preparation guide
Prepare goals, users, data and acceptance criteria for a strong project start.
- 01
Goals and success criteria
Write a measurable goal, such as booking completion, order preparation time or support workload.
- 02
Content
Prepare sample content, products and user roles. Use sanitized examples instead of real personal data.
- 03
Dependencies and owners
Assign owners for domain, hosting and third-party connections. Limit access to the required scope and duration.
- 04
Pending approvals
Customer approval applies only to the reviewed preview version. Publishing is a separate staff step with recorded outcomes and history.
- 05
Budget and timeline
You do not need an exact figure; a range and a deadline are enough. Cost is driven mostly by the number of screens and roles, connections to other systems, the amount of content and languages, and the need for custom design. If the date is fixed we narrow the scope together; if the scope is fixed we set a realistic date.
- 06
What to bring to the first call
A few examples you like and dislike, the site or system you use today, who will make the decision and any dates that must not be missed make the first call productive. You do not need to share sensitive information such as passwords or customer lists in the first call; when access is needed, a separate secure route is set up.
- 07
How to write acceptance criteria
For each screen or feature, write in one sentence what shows the work is done: who should be able to do what, and what the result should be. A measurable sentence prevents a debate open to interpretation at approval time.
Related pages
Other articles in the knowledge base, and the page to reach us if a question is left over.
Let's talk about your project.
Tell us what you need; we will define the scope together.