Project configurator
Six questions to a price range and a project spec
Step 1 of 7
Project type
What are we building?
Choose an answer to continue.
Maintenance and the technical audit have fixed prices: Website maintenance Technical audit
Step 2 of 7
Scope
How many pages will the site have?
Count the distinct pages, not individual blog posts.
Choose an answer to continue.
Do you need a blog or a news section?
Choose an answer to continue.
How many products do you sell?
Choose an answer to continue.
Do products come in variations, such as size or colour?
Choose an answer to continue.
Do business customers need their own prices (B2B)?
Choose an answer to continue.
How do products get into the store?
Choose an answer to continue.
How many different user roles?
Admin, staff and customer are three roles, for example.
Choose an answer to continue.
How many main modules will the system have?
A module is one area of work: bookings, invoicing, stock or reports.
Choose an answer to continue.
Will customers or partners get their own access?
Choose an answer to continue.
What should the system do? (optional)
A few sentences are enough; they help the first conversation start from what matters.
Choose an answer to continue.
What are we redesigning?
Choose an answer to continue.
How large is the current site?
Choose an answer to continue.
Are you moving from another platform?
Choose an answer to continue.
Step 3 of 7
Languages
In how many languages?
Choose an answer to continue.
Step 4 of 7
Integrations
What should it connect to?
Tick everything you need, or move on if none of it applies.
Choose an answer to continue.
Step 5 of 7
Design
What kind of design do you need?
Choose an answer to continue.
Step 6 of 7
Start
When should we start?
Choose an answer to continue.
Step 7 of 7
Your spec
Your answers
- 01Project type
- –
- How many pages will the site have?
- Do you need a blog or a news section?
- How many products do you sell?
- Do products come in variations, such as size or colour?
- Do business customers need their own prices (B2B)?
- How do products get into the store?
- How many different user roles?
- How many main modules will the system have?
- Will customers or partners get their own access?
- What should the system do? (optional)
- What are we redesigning?
- How large is the current site?
- Are you moving from another platform?
- In how many languages?
- What should it connect to?
- What kind of design do you need?
- When should we start?
What is included
- A content model: clear relationships between pages and the content reused across them
- Editing built for your team: purpose-made blocks, no page builder
- A design system applied across every content type and screen size
- Final performance, accessibility and security checks before launch
- Training for the people who will edit the content
What is not included
- Copywriting and photography: you provide the content
- Hosting, domain and premium plugin licences
- Maintenance after launch, which is a separate monthly package
What is included
- Catalogue structure: products, variations and categories modelled on how customers actually choose
- A purchase path and checkout reduced to the decisions that matter
- Pricing, shipping and order rules fitted to how you sell
- Cart, checkout and order emails tested before launch
- Training for the people who will run the store
What is not included
- Copywriting and product photography: you provide the content
- Hosting, domain and premium plugin licences
- Fees of payment and courier services
- Maintenance after launch, which is a separate monthly package
What is included
- A domain model: business concepts, states and permissions turned into a clear technical foundation
- A workspace shaped around each role: dashboards and tools built on the decisions the team makes
- Role-based permissions and protection of sensitive data
- Delivery in phases, with documentation
- An architecture ready to grow with the business
What is not included
- Server, domain and third-party service costs, such as SMS, email or paid APIs
- Moving existing data, unless agreed as a separate item
- Further development and maintenance after delivery, agreed separately
What is included
- A review of the current site: content, structure, plugins and speed
- A new design system and editing built for your team
- A redirect map from the old URLs, so search engines do not lose pages
- Final performance, accessibility and security checks before launch
- Training for the people who will edit the content
What is not included
- Rewriting the existing content or new photography
- Hosting, domain and premium plugin licences
- Maintenance after launch, which is a separate monthly package