A support quote excludes the public file storage

What to change

Compare the proposed coverage with the actual public estate. Ask the supplier to trace a representative page, download and external dependency, then mark who supports each part. The practice should understand which failure would require another supplier or account owner. Clarify response coordination as well as technical coverage, because a visitor sees one website even when several contracts sit behind it. Record exclusions plainly before comparing headline support prices.

A worked example

Illustrative example

Illustrative test: A fictional failed download is routed to the correct responsible account owner.

How to check the result

The proposal explains who handles the full public journey and any excluded dependencies.

A mistake to avoid

A low monthly price may reflect a smaller estate rather than equivalent service.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordTrace important public files to their real storage provider.Map each component to the proposed support scope.Assign ownership for gaps and cross-supplier incidents.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.