Estimate the complete buyer route, not only the page count
A catalogue with twelve items can require more investigation than a website with fifty ordinary pages. The difference may be the relationships between variants, documents, provider systems and staff decisions. An estimate needs to describe those relationships well enough to define a reviewable result.
What the first engagement should answer
If the current system's capabilities are known, the first scope may be implementation. If they are uncertain, an assessment can establish whether the supported import, editing or permission model fits the task. The assessment should have a defined question and deliverable, such as a tested field map or a repair-versus-replacement decision.
We do not infer a fixed fee or delivery date from a service label. Bring the intended outcome, existing materials and any deadline so dependencies can be separated from development work.
Content preparation is part of the work
A product row may still need a clear description, confirmed characteristics, appropriate imagery and a document relationship. Twelve rows do not necessarily represent twelve ready-to-publish items. Some content may be shared at family level; some must be reviewed separately.
Identify who supplies and approves those materials. Czech translation and professional language review require an explicit arrangement. Technical claims, legal wording and commercial rules may need specialist reviewers whose availability affects the schedule.
Interfaces introduce their own scope
A provider may expose the required field only through a particular account, export or workflow. A receiving system may not distinguish an omitted value from an instruction to clear it. Resolving those limitations can be a material part of the project.
An integration estimate should include the representative trial, failure handling and operating instructions. A successful one-off transfer is not the same deliverable as an exchange your team can maintain.
Define acceptance before adding more options
For a catalogue, acceptance might cover identifying an exact item, asking about an unknown option and continuing the resulting request. A portal may also need permission, recovery and document checks. A mobile task may need device-specific behaviour and interrupted-work tests.
Additional filters, exports, roles and language versions introduce distinct cases. Discuss them as purposeful additions rather than treating them as small visual variations. The planning guide helps record what belongs in the first delivery.
Separate project costs from continuing commitments
Hosting, provider subscriptions, licensed assets, specialist review and ongoing support may be separate costs. The agreement should identify who purchases them and who owns billing and renewal. Client account control should remain clear even when a developer configures the service.
Post-delivery changes also need a route. Decide which editing tasks the team will perform, which updates are covered by support and how new development is estimated. Remote delivery does not imply unlimited response coverage.
A useful proposal explains what you will receive, what you must supply, how it will be checked and what remains outside the scope. Send a safe example to begin that discussion.