A clear project price starts with a clear scope.
A one-off cost can describe the development project, but domains, hosting and future changes do not disappear. We help define a website and prepare a concrete project proposal. Prices, payment and rights belong in the actual agreement.
From one-off amount to reviewable project
Scope
Describe the initial delivery concretely.
Boundary
Separate development from operations and future work.
Approval
Test agreed tasks before handover.
Define the first delivery’s job
A project becomes understandable when pages, content, editing and functionality have a clear scope. Comparing page counts alone is insufficient: forms, migration and languages can change the work considerably. Identify what must exist at handover and what belongs in a later phase.
An illustrative small consultancy might begin with a central service, company introduction and working inquiry route. A manufacturer may need substantial data work. The same word, website, can describe different projects. We begin with tasks the customer and editor actually need to complete.
Separate construction from continued use
A defined development delivery can be compared separately from ongoing services. Registration, hosting, external licenses and support still need an owner and a cost description. Investigate unclear items rather than assuming they are included or free.
We can structure a proposal to distinguish project work from continuing decisions. Third-party services have their own conditions. One development invoice does not automatically grant unlimited rights to every image, component or external service.
| Cost area | Clarify |
|---|---|
| Development | Agreed initial delivery and approval |
| Domain and hosting | Account holder, owner and recurring costs |
| Licenses | Resources and actual usage conditions |
| Changes and support | Commissioning process and separate scope |
Handle changes without vague expectations
Describe how preview feedback is handled and distinguish defects from new requests. A broken link in agreed functionality is different from adding an entire booking system after design approval.
Base acceptance on observable tasks. Can a customer understand the service, submit an appropriate inquiry and reach the intended recipient? Can the editor complete agreed changes? These checks clarify delivery without suggesting future development is already included.
Choose around the way the site will be used
Stable core needs may suit a defined project. A team running frequent campaigns and design changes also needs an ongoing work plan. One-off development and continuing maintenance need not be opposites. Share your current website, planned content and editing needs. ImbaHub can prepare a reviewable scope before commissioning, without invented prices or promises that no future costs can arise. Clarify operational contacts and ownership alongside the proposal so the project remains understandable after handover.
Questions, answered
Does one-off mean everything after launch is free?
No. Domains, hosting, licenses and further work are separate decisions that should be explained.
Do we automatically own the entire solution?
Rights, files and access need to be specified. A payment model does not settle every license and handover question.