Pricing & engagements
One automation, a new website, or a longer-term engineering partner. Start with the work you need—not a package you have to grow into.
01 / Find your fit
Choose a starting point.
We’ll help define the details.
Fixed-scope quote
Start with the repetitive task slowing your team down. An invoice workflow, a reporting task, or a disconnected tool is a useful place to begin.
Price, timing, and deliverables are agreed before work begins. This guide is not an instant estimate.
02 / Larger engagements
Published options for deeper discovery, ongoing leadership, and complex delivery. These are not the minimum price for every project.
A focused review of your current systems, constraints, and delivery risks, resulting in a documented technical direction and prioritised roadmap.
Ongoing senior technical leadership combined with engineering delivery. We help manage architecture, development priorities, infrastructure decisions, and stakeholder communication.
For established teams that need a custom platform or commerce application designed, built, documented, and transferred to their internal team.
Published prices are planning references in USD. Taxes, third-party services, travel, and out-of-scope work are quoted separately. Your signed proposal and service agreement take precedence.
03 / Before we start
No two briefs are identical. These are the decisions we work through together.
What is included, what is excluded, and what a successful handover looks like.
An agreed sequence of work, review points, and acceptance criteria.
Project fees, third-party costs, access, documentation, and ongoing support terms.
Yes. A single automation, a defined website, or a focused integration can be scoped as a standalone project. Share your brief and planning budget so we can discuss a practical starting point. The larger engagements on this page are not the minimum price for every project.
No. A fixed-scope project may be a better fit for a defined task or first release. A retainer is considered when the work is ongoing and you need agreed engineering capacity or technical leadership. The model and terms are confirmed in your proposal.
Scope, data quality, integrations, design needs, security requirements, testing, and handover all affect the estimate. We clarify these before agreeing the price and delivery stages. Changes outside the agreed scope are discussed separately.
Third-party infrastructure, software licences, developer accounts, and usage-based API fees are identified separately and, where practical, billed directly to accounts owned by your organisation. Your proposal explains what is included.
We choose the stack around content workflows, integrations, security, performance, and who will maintain the system. That can include WordPress, a headless CMS, Next.js, or another appropriate platform.
Choose “Help me scope this” on the enquiry form. Describe the problem and what you want to change. We can discuss scope and priorities before you choose an engagement; submitting an enquiry does not commit you to a project.
