Clear project scope. Transparent pricing. Support that fits your needs.
Know what you are paying for, what the project includes and who supports the software after launch.
We scope software around your business requirements rather than forcing every project into a generic package. Start with a focused prototype where suitable, agree the full project scope separately and choose ongoing support based on your operational needs.
- Fixed-price 14-day prototype pilot for suitable projects
- Project quotes based on agreed requirements and deliverables
- Three support tiers with clearly differentiated coverage
The price should follow the work—not an arbitrary package.
Different business problems require different levels of engineering effort.
An AI automation workflow, a custom application and a multi-system integration have different requirements. We assess the problem, systems involved, expected deliverables and technical dependencies before proposing a price. The objective is to make the commercial commitment understandable before implementation begins.
Defined deliverables
Know what the proposed engagement is expected to produce.
Visible assumptions
Understand which systems, access, data and third-party dependencies are required.
Agreed boundaries
Know what is included, what is excluded and how additional requests will be assessed.
Start with a fixed-price 14-day prototype pilot.
Test a focused idea before committing to a larger software project.
For suitable projects, we can define a fixed-price pilot to produce a working prototype in 14 days. The pilot is designed to test an important workflow, demonstrate an interaction or validate a technical assumption. Its scope is agreed in advance so both sides know what will be delivered and how it will be reviewed.
- One clearly defined problem, workflow or product assumption
- A written scope with deliverables and exclusions
- Agreed access, information and stakeholder dependencies
- Defined review points and acceptance criteria
- A working prototype to evaluate before deciding on the next phase
14-Day Prototype
Designed for validating core workflow hypotheses with real test data before committing to multi-month contracts.
A prototype is a focused validation step—not a finished platform.
Set the right expectations before the pilot begins.
The pilot is limited to the deliverables agreed in its scope. A production-ready system may require additional engineering, security review, integrations, testing, deployment preparation and operational documentation. Those requirements are assessed and quoted separately.
Potential pilot deliverables
The pilot may include: an agreed working prototype, selected workflow or interface, and review against defined acceptance criteria.
- Functional validation of core user or operational flow
- Working integration or interface using sample test data
- Review against agreed acceptance criteria
Separately scoped work
The pilot does not automatically include: a complete production platform, every requested feature, unlimited revisions, all third-party integrations, production deployment or ongoing support.
- Full production hardening & high-volume concurrency
- All external enterprise integrations & live webhooks
- Ongoing operational support & 24/7 on-call coverage
What determines the cost of a software project?
The quote reflects the actual complexity and responsibility involved.
Before preparing a proposal, we review the requirements and the work needed to deliver them. These are the main factors that can influence project investment.
Scope and functionality
The number and complexity of workflows, user roles, interfaces and business rules.
Existing systems and integrations
The number of systems involved, API capabilities, data quality, permissions and third-party constraints.
Design and user experience
The level of interface design, accessibility, responsive behaviour and user testing required.
Delivery and operational requirements
Testing, deployment, documentation, handover, security requirements and agreed support arrangements.
Choose the right starting point for the work.
The commercial structure should match the certainty and complexity of the requirements.
We discuss the engagement model after understanding the project. These paths describe the kinds of conversations we can have, not fixed packages with universal prices.
Prototype pilot
A fixed-price, tightly scoped engagement for validating a workflow or technical approach in 14 days where suitable.
Defined project
A separately scoped build with agreed deliverables, milestones, dependencies and acceptance criteria.
Ongoing development
Further phases or enhancements planned around changing business requirements and priorities.
After launch, support should be part of the plan.
Know where to report issues and what level of coverage your business has selected.
Software needs an agreed route for handling questions, defects and operational incidents after release. Our support options distinguish routine business-hours assistance from enhanced coverage and severe-incident on-call support. The appropriate tier depends on the importance of the system and the level of availability your business requires.
- Support scope is agreed separately from the initial development scope.
- Coverage and response expectations are documented before support begins.
- Support arrangements depend on the selected tier and agreed service terms.
Three support tiers. Different levels of coverage.
Choose the level of support that reflects your operational requirements.
The following descriptions explain the intended coverage. Exact response targets, service windows, escalation conditions, exclusions and fees must be agreed in the support arrangement.
Standard — Business-hours support
For routine questions and issues during agreed business hours. Suitable for businesses that can handle non-urgent issues within a normal working schedule.
Priority — Faster response and extended hours
For businesses that need faster attention and support coverage beyond standard business hours. Exact response targets and coverage windows are confirmed in the agreed terms.
Critical — Paid 24/7 on-call for severe incidents
For systems where a severe incident may require an on-call response at any time. This is a premium paid tier, not a free inclusion. It is subject to agreed incident definitions, escalation rules, coverage conditions and commercial terms.
Understand what ongoing support covers.
Support is not an unlimited development retainer.
Support arrangements address the agreed software and incident categories. New features, major changes, new integrations and substantial enhancements may require a separate project scope or commercial agreement. This distinction keeps support expectations clear for both sides.
- Agreed software and systems covered by the support arrangement
- Issue reporting and triage through the agreed channels
- Coverage hours and escalation conditions for the selected tier
- Clear distinction between incident handling and new feature requests
- Commercial approval for work outside the agreed support scope
Defect resolution, system accessibility triage, operational error reviews, and critical on-call incident handling (Critical tier).
New workflows, net-new API integrations, major schema overhauls, redesigns, and feature expansion.
Commercial clarity before work begins.
No vague scope. No assumed extras. No surprise commitments.
Before an engagement starts, the proposal should make the commercial arrangement understandable. You should be able to review the deliverables, exclusions, payment terms, dependencies and process for approving changes.
Written scope and deliverables
Clear documentation of what will be designed, coded and released.
Agreed project fee or pricing basis
Transparent commercial structure with no hidden fees or surprise additions.
Payment milestones and applicable terms
Staged milestone payments linked to tangible review checkpoints.
A process for reviewing and approving changes
Clear protocol for evaluating cost and schedule impacts before new work begins.
Getting a quote starts with a useful conversation.
A little context helps us assess the right next step.
Share the operational problem, the systems involved and what you want to improve. We can then discuss whether a prototype, a defined project or a separate support arrangement is the appropriate route.
Tell us what you need
Describe the workflow, business problem and intended outcome.
Review the requirements
Discuss users, systems, dependencies, scope and constraints.
Agree the proposal
Review the recommended approach, deliverables, commercial terms and next steps.
Pricing and support questions.
The details worth clarifying before you commit.
Project and support terms are confirmed in the relevant proposal or agreement.
Ask about pricing and supportGet a quote based on the work your business actually needs.
Tell us what you want to improve. We can discuss the right scope, whether a prototype is suitable and what ongoing support would make sense.
Start with a free 30-minute conversation. No need to prepare a complete technical specification before getting in touch.
- Discuss a software project or prototype
- Clarify support coverage and commercial requirements