Define the delivery that a price is meant to cover

A price is meaningful when the work it covers is clear. A catalogue enquiry with one product reference has different requirements from a request that supports amendments, staff approval and provider reconciliation. The number of visible pages alone does not express that difference.

We discuss the intended result, review the project circumstances and identify the information needed for a proposal. A website description is not a fixed quote or a reserved delivery slot.

Scope follows the decisions and relationships

For a catalogue, the work may include product structure, content preparation, enquiry context and editing instructions. For an order workflow, it may also include state changes, role permissions and correction history. Each added relationship needs a rule and an acceptance example.

Separate the first useful delivery from later ambitions. A request-and-review process can be complete without automated payment collection if that is the agreed boundary. Adding another provider later requires review of its arrangement and a fresh assessment of the affected work.

Investigation has a different result from implementation

When a fault is not understood, an assessment can establish its evidence and recommend a boundary. The deliverable may be a reproducible example, findings and a repair proposal. That is different from promising that every reported symptom will be corrected within the assessment.

The agreement should explain how further work is proposed after the finding. Unknown access, missing source material or an unavailable provider test environment can affect what conclusions are possible. Those limits should remain visible in the commercial discussion.

Include preparation and transition

Product data may need correction before it can support a reliable catalogue. Spanish and English content require review. Moving to a new system can involve retained links, open requests, staff permissions and reconciliation of transferred relationships.

Identify who supplies each input and what quality is expected. A proposal that assumes clean product records is not equivalent to one that includes preparing them. The hidden-cost exercise helps distinguish recurring clarification from the work a change will create.

Keep ongoing responsibilities explicit

Hosting, provider subscriptions, maintenance, incident investigation and new features should be identified as included, separately priced or outside the agreement. Support response arrangements are stated only where agreed; a handover document does not create continuous coverage.

For a useful comparison, ask each proposal to demonstrate the same customer and staff task, including an interrupted case. Then compare the dependencies, handover and limits as well as the amount. Send the task and the circumstances to begin defining that boundary.