Is the request care or new work?
A care plan covers only the responsibilities named in it. It may include certain updates or content tasks, but it does not automatically include new page types, integrations, or redesigned journeys. Those additions can affect content, design, development, and testing. They may need a separate scope.
Even a small edit can matter if it changes a legal claim, active campaign, navigation label, or form. We look at the effect of the change, not only the number of words or clicks involved.
What to send us
Share the page address or a screenshot, explain what you want changed, and tell us why it matters. Include any deadline or dependency. That gives us a way to identify the affected work and decide whether the request fits an existing agreement, needs a separate proposal, or should be planned for a later phase.
How are website changes after launch evaluated?
We look at the purpose of the request and the systems it touches. Replacing an outdated phone number is different from adding a new lead form. A new section may affect copy, layout, mobile behavior, navigation, tracking, and the way other pages link to it. If the request changes a key offer or regulated statement, your team may need to approve the exact wording before it is released.
We also need to know whether the live site is connected to active ads, email campaigns, booking tools, or other workflows. A change can be visually small but operationally important. The scope should say what will be edited, what will be checked afterward, who approves it, and whether there is a rollback path if an important feature fails.
Do I need a new project for every edit?
Not necessarily. Some changes may fit the written care plan or an agreed support arrangement. Others may be handled as a separately approved task. Larger additions can be grouped into a new phase so related design, content, and development decisions are made together. The right route depends on the contract and the effect of the change, not only how long it seems to take.
If you expect frequent changes, tell us what kinds of updates your team makes. We can discuss whether you need editorial access, training, a care arrangement, or a process for requesting new work. Clear ownership is more useful than sending every small change through an undefined support channel.
Your approved site remains yours to operate according to the terms of your project. We will not assume that a launch authorizes unreviewed future changes or that every new request is included in the original price.
Related reading on changes after launch
Next step for changes after launch
Send the change you have in mind and the outcome you want. We can discuss the appropriate scope and approval route.