40% at the start
Once the scope and proposal are agreed, the initial payment puts the project plan into motion.
PRICING
A clear scope. A proposal you can understand.
Projects do not all need the same pages, content or functionality. We price the work your project actually requires. The proposal sets out the delivery scope, payment arrangement and items that need separate consideration.
WHAT SHAPES THE PROPOSAL
What determines the price?
Page scope and design expectations are the starting point. Content readiness, product or service management, languages and integrations also affect the amount of work. Two websites that look similar may have very different development requirements.
- Page scope and the amount of content on each page
- Brand identity, design direction and visual requirements
- Catalogue, online shop or custom software functions
- Languages, external systems and existing data migration
SCOPE CLARITY
Know what is included from the start.
A service is not automatically included if it has not been specified in the proposal. Domains, hosting, paid licences, purchased images and third-party services are discussed separately when required. Revisions and delivery terms are clarified in the same way.
- Pages and functions to be delivered
- Content, design and development responsibilities
- Revision scope and review stages
- Third-party costs and post-launch services
PAYMENT ARRANGEMENT
Two stages: project start and delivery.
Our current payment approach is 40% of the total project fee at the start and 60% at delivery. Project-specific terms are confirmed in the written proposal. If an online payment link is offered, its method and conditions are shared separately.
- 40% at the start
- 60% at delivery
- Total scope and fee confirmed in the written proposal
- Separate assessment and approval for additional work
CHANGING REQUIREMENTS
Make new requests visible before adding them.
A new page, function or integration may become necessary as the project develops. We first compare the request with the agreed scope. If additional work is needed, we explain its effect on price and timing before it is added to the implementation.
- New requests compared with the current scope
- The additional development or content requirement explained
- Any effect on price and timing communicated
- The work plan updated after agreement
INFORMATION THAT HELPS US QUOTE
Describe your priority, not just a feature list.
Sharing a budget range does not mean asking for enough features to fill it. Knowing which problem should be solved first helps us choose an appropriate scale. By separating essential functions from optional requests, we can define a practical first delivery together.
For example, a site that explains services and receives enquiries may be enough for the first stage. If you want a customer panel later, we can note that separately. Unless it is defined in the initial proposal, it is not part of the starting scope; its cost and schedule need their own assessment.
Content readiness, language requirements and how products will be managed are concrete factors in pricing. Sharing them before the conversation helps us distinguish requests that look similar but require different amounts of work.
- The main need the first delivery must address
- Essential functions and those that can wait
- Available content versus content to prepare
- Budget range and any fixed timing requirement
BEFORE YOU DECIDE
Read the proposal through these practical questions.
Comparing only the total cost of two proposals can be misleading. One may cover the interface alone, while another includes content preparation, development or migration. If the deliverables differ, the figures do not represent the same work. First check whether the scopes are genuinely comparable.
The number of pages or page types, working functions and approval process should be clear. Check who is responsible for images, translations, paid tools and post-launch services. Clarifying an uncertain item before work begins gives everyone a better basis for decisions.
Payment terms for the start and delivery are confirmed in the project proposal. The same document defines delivery and how additional requests will be assessed. These explanations do not replace the written proposal for your project.
- Defined pages, functions and delivery scope
- Responsibility for content, licences and third-party costs
- Revision boundaries, approvals and timing conditions
- Payment arrangements reviewed alongside delivery terms
60% at delivery
The delivery payment is completed according to the written proposal and the agreed delivery terms.
The project fee is quoted for the defined scope. The proposal states separately whether domains, hosting, licences and third-party services are included.
FAQ
Useful answers
Why not publish one price for every project?
The work changes with the page, content and functional needs. Instead of a general price for all situations, we clarify your project’s scope and fee in a written proposal.
Are domain and hosting costs included?
Unless the proposal explicitly includes them, domains, hosting and other third-party costs need separate consideration. We also review whether your existing services can be used.
Can the project be split into phases if our budget is limited?
We can define a first scope around the essential need and leave later functions for separate phases. The proposal states what is included in the first delivery.
Is an online payment link available for every project?
No. The payment method is agreed during the project discussion and in the proposal. An online payment link is used only when that option is offered and its conditions have been shared.
Let’s Discuss Your Project
Let’s give your next project a clear direction.
A new website, a refresh of an existing platform or software for a specific workflow: tell us what you want to achieve, where you are now and what matters most. We can start the conversation with a practical scope.