Engagement models & pricing
A specific task, a complete project or ongoing technical support. Choose the model that fits your requirement; we’ll review the scope before preparing an estimate.
Custom development is quoted after scope review. Numerical rates and packages have not been published.
Start with how you want to engage
For a defined fix, feature or small integration that can be assessed as a focused piece of work.
For custom plugins, themes, websites, applications and integrations with a wider delivery scope.
For maintenance and recurring development needs with an agreed scope or allocation.
For white-label projects, specialist tasks and ongoing technical collaboration.
What shapes an estimate
We look at what needs to be built, what it connects to, and what dependable delivery requires.
Business rules, user roles, custom interfaces and edge cases.
Code quality, plugin dependencies, hosting and access requirements.
API availability, data mapping, migration and authentication.
Testing scope, approval stages, documentation and handover.
The proposed timeline and the support or maintenance you need.
How the quote takes shape
Your goal, website or stack, current challenge and preferred timeline.
Review dependencies, assumptions and the result you expect.
Discuss deliverables, milestones, fees and any separate provider costs.
Confirm responsibilities, payment terms, revisions and support coverage.
Your proposal should distinguish development fees from hosting, paid plugins, licences, API usage and other provider costs. Changes beyond the agreed scope are reviewed separately. Payment schedules, revisions and support are confirmed in the relevant agreement.
Pricing questions
Custom work varies with the setup and requirement. We review scope before quoting rather than presenting a price that may not cover the work you need.
Share your budget range with the requirement. We can discuss priorities and scope before deciding whether the engagement is a fit. A specific budget does not guarantee acceptance.
Inclusions are specified in your proposal. Hosting, licences, subscriptions and model or API usage should be identified separately unless explicitly included.
The number or scope of review rounds and acceptance criteria are agreed in the project document. New requirements outside that scope are assessed separately.
Payment milestones, currency, taxes and due dates are set out in the written agreement. This page does not assume a standard deposit or payment schedule.
Support coverage is defined in the proposal. Ongoing maintenance and additional development can be discussed as a separate arrangement.
Yes. Share the delivery model, workload and responsibilities you have in mind. Visit our Partnerships page to explore the options.
Start with the requirement
Share your project, task or ongoing support needs.
