Count the work spent reconciling product information

A catalogue can stay online while every useful enquiry requires a search through old attachments. The visible website may appear inexpensive to maintain because the cost has moved into sales, technical support and product review. Before commissioning a replacement, find out which work is repeated and why.

Observe a bounded sample

Suppose a fictional team reviews ten product enquiries during one week. Six require staff to identify the sheet the visitor used. Those six cases take an additional seven minutes each to locate the document and confirm its revision: 42 minutes in this sample.

That calculation describes observed handling work under the example's assumptions. It is not a promised weekly saving, an annual forecast or proof that a new catalogue would remove all of it. The enquiries could differ in complexity; some review would remain valuable even with clearer records.

Distinguish useful judgement from avoidable reconstruction

A technical specialist assessing compatibility performs necessary work. Searching three folders to determine which specification the customer saw may be avoidable reconstruction. Treating both as “manual work” can lead to automation that removes the judgement while leaving the confusion.

Ask staff to describe the decision and the evidence used. A change should preserve the qualified decision while making its inputs easier to find. For the sample, carrying a stable product reference and document revision into the enquiry might be more useful than an automatic answer.

Include preparation that a feature list hides

Product identifiers, variant relationships, approved translations and document ownership often need attention before development. A new catalogue cannot safely infer whether two almost identical sheets describe the same model. Someone must approve that relationship.

Also account for permission to publish, outdated links, replacement files, image descriptions and the receiving team's workflow. These are deliverable dependencies, not defects in a developer's efficiency. An estimate should say who supplies them and what happens when the evidence is incomplete.

Count the operating work after launch

A bilingual catalogue needs a change process. When a technical fact changes, which page, sheet, enquiry prompt and internal note must be reviewed? Who identifies the affected variants and signs off the Korean wording? The answer determines whether the system stays understandable after the first release.

Provider charges, hosting, access management and agreed technical care belong in the operating picture too. Avoid comparing a custom build's development price with an existing tool's monthly fee while ignoring the work both require from the organisation.

Evaluate a smaller change first

For the fictional sample, test a product-context improvement on a limited catalogue section. Record how often staff still need to identify the source document and whether the added context is correct. Watch for wrong references travelling confidently through the new process; fewer questions are not useful if the answer is based on the wrong variant.

Review the findings with the people doing the work. They may reveal that the primary difficulty is document control, language review or an unclear approval rule. Each suggests a different scope.

Pricing and scope explains how these dependencies enter a proposal. The workflow review guide follows the product question beyond the form, where many of these costs become visible.