# Example: one original article into social posts

Source: Odd Rule Lab’s own website-change estimating guide. AI-assisted sample; no client work or results claimed.

## Post 1 — classify first
A booking widget request arrives halfway through a website build. Before estimating it, compare it with the agreed scope: a defect, an included revision, a new feature, or an unclear request. The category determines the next conversation.

## Post 2 — include the hidden work
A small visible change can involve clarification, implementation, testing and handoff. In a fictional example, five hours at USD80 with 20% contingency gives USD480 before applicable taxes. These are illustrative assumptions, not a pricing rule.

## Post 3 — record the decision
For an addition, state what is included, what is excluded, the required inputs, fee and calendar impact. Let the client approve, defer or discuss a substitution. Record that choice before starting.

## Newsletter opener
The visible edit is only part of a website change. This week’s guide shows how to classify a request, include the hidden tasks and give the client a clear decision.

## Claim check
No customer outcome, guaranteed savings, income claim, quote attribution or unsupported statistic was added.