How we price projects

How a quote comes together

Every price starts with a conversation. You tell us what you want to achieve, who will use the result, and what you already have in place. We ask questions until we understand the problem well enough to plan the work.

After that short call, we write it all down. You receive a plan that describes what we will build, a fixed quote for that work, and a timeline. The plan lists what is included and what is not, so both sides know exactly what the price covers.

Nothing starts until you have read the plan and agreed to it. If something in it does not match what you had in mind, we change the plan before we start, not halfway through the work.

What a quote includes

A quote from us covers the whole job, not just the build. Unless the plan says otherwise, it includes the planning workshops, the design of the screens or pages, the build itself, testing, and the launch.

It also covers the work that is easy to forget. Setting up hosting, connecting your domain, configuring analytics, moving existing content or data, and handing over documentation are all listed in the plan when they are needed.

Where a project depends on paid tools, such as a hosting plan, a booking system, or a premium plugin, the plan lists them separately. Those fees are paid to the provider, and we say which ones you will need before you agree to anything.

If you already have part of the work done, such as a design, content, or a working system to connect to, the quote reflects that. You only pay for what is left to do.

Why we quote a fixed price

A fixed price gives you certainty. You know what the work costs before it begins, and you can plan your budget around it. It also keeps both sides focused on a clear scope and a clear result.

Fixed prices work when the scope is clear. That is why we spend time on the plan first. The clearer the plan, the more accurate the quote, and the fewer surprises later.

For large projects, a single fixed price for everything would hide too much uncertainty. Instead, we split the work into stages. Each stage has its own scope, its own quote, and its own result you can see and use. You decide whether to continue after each one.

What the typical ranges mean

The table above shows where most projects land for each of our fifteen services. The left column is a typical smaller project for that service. The right column is a typical larger one.

These ranges come from the kinds of projects we deliver most often. They are a planning guide, not a price list. Your quote depends on your scope, and it can sit below, inside, or above a range.

The top end of every range ends with a plus sign. Large projects have no natural ceiling, so we quote them on their own merits, usually in stages.

What moves a price up or down

A few factors affect almost every project, whatever the service.

Scope is the biggest. The number of screens, pages, features, user roles, and integrations decides how much work there is to do. Cutting a first version down to what matters most is the most effective way to lower a price.

Existing systems matter too. Connecting to tools that have clear, documented interfaces is quicker than working around old or closed systems. Moving data from spreadsheets or an old system adds work, especially when the data needs cleaning.

Content and design add to the scope when we create them. If your words, images, and brand are ready, the project moves faster.

Security and compliance needs add care and review. Systems that hold health, financial, or personal data need stronger controls, and that work is never worth skipping.

Speed can matter as well. A fixed deadline that is tighter than the normal timeline may need more people working in parallel.

How we keep timelines short

Short timelines come from focus, not from cutting corners. We agree a clear first version, design it before we build it, and build it in short rounds you can review. Each round ends with something working, so problems surface early, when they are cheap to fix.

We use proven components for common needs such as sign-in, payments, file storage, and notifications. That saves time and is safer than building them from scratch. It also leaves more of the budget for the parts that make your project different.

When the scope changes

Projects learn as they go. Sometimes a new idea is worth adding. Sometimes a planned feature turns out to be unnecessary.

When the scope changes, we say so in writing. We describe the change, what it affects, and what it costs, before any of that work begins. You decide whether to go ahead. Small swaps of similar effort often need no change to the price at all.

That way the fixed price stays meaningful. You never receive an invoice for work you did not agree to.

What you own

When the work is finished, the result is yours. You own the code, the designs, the content, and the data. Accounts for hosting, domains, and app stores are set up in your name.

That matters for price as well as for control. You are never locked in to us to make changes, and any capable team can pick up the work later.

After launch

Software, websites, and apps need care after launch. Platforms release updates, security fixes need applying, and people find better ways of working once they use something every day.

Before launch, we agree in writing how the result will be looked after: who handles updates and fixes, how quickly urgent problems are answered, and what that costs. Some clients prefer to look after things themselves, and we hand over everything they need to do that.

How to get a quote

Use the contact page to tell us what you want to do, in your own words. You do not need a specification. A few sentences about the problem, the people involved, and the result you want are enough to start.

We will reply to arrange a short call, and then send a written plan with a fixed quote and a timeline.