Assessment
When you know something is inefficient or fragile, but not what to fix first.
- Map of the current workflow or system
- Bottlenecks and risks, in order of impact
- Prioritised recommendations and a scoped proposal
Priced from the agreed scope.
Pricing
Start with a clear scope, not an oversized project.
Scope and price are defined for each engagement and agreed in writing before work starts. Smaller, clearly defined workflows can suit a fixed scope; larger products and modernisation work may be delivered in phases.
Engagement types
Choose a starting point that fits the work.
Focused automation
One well-defined, repetitive process.
- The agreed automation and integrations
- Exception handling and testing
- Deployment and operating instructions
Priced from the agreed scope.
Internal tool or application
Teams that need a more structured operational system.
- Discovery and user workflows
- Application, data model and permissions
- Testing, deployment and handover
Priced from the agreed scope.
Product build or modernisation
A new product, or broader work on an existing application.
- Defined feature milestones
- Integrations, testing and release planning
- Ongoing support where it's agreed
Priced from the agreed scope.
Cost drivers
What affects the price.
Every quote is built from the same factors, and the proposal shows the assumptions behind it.
- The number of systems and integrations involved
- How many exceptions and edge cases the workflow has
- The quality of existing data and how much migration it needs
- Users, roles and permissions
- Testing, deployment and documentation effort
- Third-party licences and services
- Support after delivery
Before you commit
What the proposal answers.
- What am I buying?
- Concrete deliverables and boundaries, listed in the proposal along with what's excluded.
- How long will it take?
- The proposal includes a timeline once the scope, integrations and dependencies are known.
- What's included?
- Whatever the proposal lists, typically development, testing, deployment where included, and handover.
- What costs extra?
- Third-party licences, additional integrations, scope changes and ongoing maintenance, unless the proposal includes them.
- How do we pay?
- Payment terms are set out in the proposal before you commit.
- Who owns the work?
- Ownership of code, accounts, credentials, data and intellectual property is specified in the contract.
- What happens after delivery?
- Defect correction and any ongoing support are agreed as part of the proposal.
Want to know what your project would involve?
Describe the requirement and we'll explain the likely shape of the engagement and what the proposal would cover.