Know what you are buying
Three different kinds of cost.
Build and launch
The initial implementation: understanding the operation, reviewing a prototype, building the agreed functions, testing and preparing the rollout. The proposal defines the deliverables and payment milestones.
Monthly maintenance
Our ongoing service for the delivered system. We document operating responsibilities, support coverage and defect handling, including the hosting, monitoring and backup activities covered by your proposal.
Further development
New features, significant integrations or larger process changes. These are estimated separately or covered by an explicitly agreed development arrangement.
What changes the estimate
Complexity matters more than headcount.
A small company can have demanding workflows. A larger one can start with a narrow first release. We use the work the system must do to define its scope, rather than assuming every employee adds the same implementation effort.
| Factor | A more focused scope | A more involved scope |
|---|---|---|
| Workflows | One clearly defined job process | Several service types with different rules and approvals |
| Integrations | A bounded data handoff with a documented interface | Several systems with two-way synchronisation and exception handling |
| Existing data | A consistent dataset to import | Duplicates, historical records and reconciliation across sources |
| Field access | Connected mobile use | Offline work, synchronisation conflicts or specialised devices |
| Service needs | Agreed support during defined hours | Extended coverage or demanding recovery requirements |
After the implementation
Know what our maintenance service covers.
We define the maintenance service with you before signing: the support channel, service hours, priority definitions and response commitments. We distinguish correcting agreed functionality from developing a new capability, so both teams understand how a request will be handled.
We document included services and separately charged usage in your proposal. Running costs can depend on cloud resources, storage, text messages, mapping, AI usage and external software licences. We identify these cost drivers and any agreed allowances; unlimited usage or development is not assumed within maintenance.
- What is monitored, backed up and maintained?
- Who investigates a failed integration?
- How are urgent issues raised and prioritised?
- Which changes need a separate estimate?
Compare the full decision
Look beyond the monthly software bill.
Compare implementation, maintenance, external usage and expected changes over the same period. Include your team's time for data preparation, training and acceptance. A custom solution is worthwhile when the operational improvement justifies that total investment; it is not automatically cheaper than an existing app.
Growth can change the workload, data volume or support needs. Agree which events can change the recurring fee and how those changes are communicated. Do not assume that a particular employee count guarantees a price or that the price never changes.
Get a useful estimate
Bring one workflow you want to improve.
Describe the current process
Tell us what you do, the people and systems involved, the recurring problem and what a better result would look like.
Define the first release
Work through the important rules and dependencies. A prototype helps confirm the scope before the full build is agreed.
Review the proposal together
We set out deliverables, exclusions, implementation costs, maintenance, external fees and acceptance. Before the build, we also agree data access, code rights and the arrangements if the service ends.
FAQ
Questions worth asking
Can you give us a price before we describe the workflow?
We can discuss fit and budget, but a reliable implementation quote needs an understood scope. The cost of mapping the process and preparing a prototype is clarified before that work begins.
Are new features included in maintenance?
We separate maintenance from development in your proposal. We state any included changes, limits and approval process explicitly, and estimate additional capabilities before you decide to commission them.
Will every additional technician increase the price?
There is no public per-technician tariff on this site. The commercial terms for your system specify the fee and any usage or scope limits. Adding people can change operating needs, so agree the actual cost drivers in advance.
What happens if we stop using the maintenance service?
Before the build, we agree the exit arrangements with you in writing: data export, access, rights to the commissioned software and the reusable foundation, and handover. Those terms define what continues and what ends with the service.