Describe the problem without prescribing the solution
Record what happened, the page involved, the expected result and whether customers are affected now. Use non-sensitive evidence and avoid sharing passwords in an ordinary support message. An urgent delivery failure needs a different response from a gradual decline in inquiries. A supplier should first establish the scope of the problem rather than treating every request as a new website sale.
Separate immediate restoration from planned improvement
A temporary repair may restore a necessary function while a broader review identifies the cause. A redesign may be appropriate when the structure no longer fits the business, but it is not the default remedy for an isolated issue. Agree the investigation boundary, access arrangement and decision point before authorising an open-ended program. Document what remains unresolved after the immediate fix.
A practical check before you buy
Prepare one concise issue record with the URL, steps, expected result and business impact. Ask for a bounded investigation and the evidence needed to choose between repair, targeted improvement and replacement.
| Decision | What to consider | What to check |
|---|---|---|
| Urgent failure | Restore the customer task | Confirm the end-to-end result |
| Unclear experience | Targeted improvement | Define a measurable task |
| Unsuitable foundation | Rebuild assessment | Compare scope and dependencies |
An illustrative business scenario
A US service company with outdated service information may need controlled content updates rather than a complete platform replacement.
This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.
Discuss the right scope with ImbaHub
ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.