Start with the work
that needs doing.

What the scope covers

Before work starts, the scope says what is included and what is not, what we deliver, what we need from you, which systems are involved, where a person reviews or approves the work, how we check that it is done, the price and payment schedule, and the expected schedule. There is no single price or timeline that fits every project.

What we need from you

• one person who can make or collect decisions
• access to the website, domain, software or data involved
• your logo, brand files, photos and existing content when they are relevant
• real examples of the forms, documents and messages the project has to handle
• time with the people who actually do the work being changed
• timely review of working versions

Who owns the work

After final payment, you own the code and content we create for your project. We keep our own tools, reusable components and methods, and third-party software stays under its own license. Your signed agreement has the final say.

How changes are handled

A change that fits inside the agreed scope is part of the project. If it adds a feature, an integration, a new kind of user or other real work, we explain the effect on cost and schedule first, and the change is approved in writing before that work starts.

What we leave out of a first version

• features with no clear first user or job
• edge cases a person can handle by hand while the main workflow is proven
• integrations that are not needed for launch
• automating high-impact decisions without a review step
• polish that delays testing without changing whether it works

If one of these becomes important later, it becomes the next scoped piece of work.