PROJECT PRICING

Built around your business.
Priced around your requirements.

The price follows the work: the systems involved, the complexity, the data and the outcome you need. Start with a project assessment, then agree the scope and commercial terms.

CHOOSE THE RIGHT APPROACH

Clarity before
commitment.

The engagement model is agreed for your project. No blanket package price applies to every business.

DEFINED REQUIREMENTS

A scoped project quote

For well-defined work, agree a quotation after the requirements, integrations, deliverables and acceptance criteria have been reviewed.

EXPLORE THE UNKNOWNS

Discovery before a build

When the unknowns are material, we can propose a separately priced discovery stage. Its deliverables and fee are agreed before it starts.

CONTROL THE BUDGET

Time-based work with a cap

For evolving work, we can agree rates, progress reporting and a spending limit. Further work beyond that limit needs approval first.

WHAT GOES INTO A QUOTE

Understand the work.
Then set the boundaries.

  • The business problem, users and intended outcome.
  • Systems, integrations, access and source data.
  • Deliverables, exclusions and acceptance criteria.
  • Dependencies, review responsibilities and delivery dates.
  • Support, handover and operating requirements.
  • Third-party costs, applicable taxes and payment milestones.

Software subscriptions, connector licenses, hosting and usage charges are identified separately where relevant. The proposal makes clear what is included and what the customer supplies.

WHEN REQUIREMENTS CHANGE

Agree the change.
Before the work.

Additional requirements need a clear decision, not a surprise invoice.

We assess the extra work and explain its effect on price, timing and dependencies. The revised scope and cost are agreed before the additional work begins.

Payment milestones are set for the actual deliverables in your proposal. They are not a preset schedule published for every project.

Read how a project is scoped and reviewed

PROJECT QUESTIONS

Before you commit.

Can you give a price before seeing our systems?

We can discuss the approach, but an agreed quote needs enough information about the requirements, integrations, data and responsibilities. We identify what must be checked before committing.

What if we do not know the full scope yet?

We can propose a bounded discovery stage or an agreed time-based engagement with a spending limit. The approach, fee or rate, deliverables and approval checkpoints are agreed first.

Can requirements change during a project?

Yes. We document the requested change, assess the effect on cost and timing, and obtain agreement before doing the additional work.

Are support and running costs included?

The proposal states the support period, handover items and operating responsibilities. Third-party software and usage costs are identified separately where relevant.

MAKE THE NEXT STEP USEFUL

Tell us what you need to improve.

Share the task, the tools you use and the outcome you want. We can identify the information needed for a tailored proposal.

Start a project conversation