Scope & Additional Work

Every project has a defined scope. Here's how to understand what's included and what happens when needs evolve.

What's in scope

Your proposal and service agreement define exactly what's included in your engagement. The deliverables, revision rounds, and timeline are all documented there. If you're ever unsure whether something is included, check your proposal or just ask.

What's outside scope

Anything not listed in your original proposal is considered additional work. Common examples:

New pages beyond the original page count
New automation sequences or pipelines
Additional integrations with third-party tools
Functionality that wasn't part of the original plan
Ongoing content creation (beyond what's in your monthly plan)

This isn't about saying no. It's about making sure additional work is scoped, quoted, and approved before it starts, so there are no surprises on either side.

How change requests work

If you need something beyond the original scope during a project:

Describe what you need. As specifically as possible.
We'll scope it. You'll receive a description of the work, timeline impact, and cost.
You approve or decline. No pressure. If it's not the right time, it can be added later.
Work begins after approval. Nothing is built until the change order is agreed to.

ℹ️

Ideas that come up during a build are normal. Seeing work in progress often sparks new ideas. That's a good thing. The change request process just makes sure everything is documented and agreed to before work starts.

After delivery

Once a project is delivered and you're on a monthly plan, new requests follow the same process. Your plan may include certain types of updates (refer to your proposal). Anything beyond that is scoped as an add-on.

A note on timing

Scope changes during an active build may affect the delivery timeline. The impact is communicated as part of the change request so you can make an informed decision.