Website Maintenance Plans

Cost factors

• • Number of distinct user roles and the permission rules between them
• • Third-party systems to integrate, and how well documented their APIs are
• • Whether existing data has to be migrated, and what condition it is in
• • Depth of custom design versus adapting an established design system
• • Compliance or audit requirements that change how we build and test

We quote after a scoping call, itemised by module, so you can see what each part costs and drop anything you do not need.

Typical timeline

Timelines follow scope, so we give you one at the end of discovery rather than before it. What we can commit to up front is the shape of the schedule:

• • Discovery and a written scope before any build work starts
• • Working software demonstrated on a fixed sprint cadence, not just at the end
• • A dated delivery plan you approve before we commit to it

What you own

• • Full copyright in the source code we write for you, assigned on final payment
• • The repository, its history, and the deployment configuration
• • Database schemas, migrations and technical documentation
• • Accounts and infrastructure registered in your name, not ours

Third-party libraries keep their own open-source licences, and any commercial component is listed in the quote before you sign.