How we work
Choose the arrangement that matches how certain your scope is and how involved your own team wants to be. Below that: how a project runs, and straight answers on ownership, access and handover.
Draft engagement models. Confirm which arrangements are offered before launch. No rates or minimums are published.
Project-based delivery
A defined product or feature with a clear outcome, such as a map portal, a mobile app or a migration.
- How it works
- We agree scope, milestones and acceptance criteria up front, then deliver in short iterations you can review.
- You receive
- Working software at each milestone
- Source code in a repository you control
- Deployment and handover documentation
- Communication
- A named lead, a regular review call and a shared progress tracker.
- Scope changes
- Changes are discussed openly. We estimate their impact before work starts on them.
Dedicated team capacity
Ongoing product development where priorities change week to week.
- How it works
- Engineers work as an extension of your team, inside your tools and planning cycle.
- You receive
- Agreed capacity each month
- Work tracked in your backlog
- Regular delivery reports
- Communication
- Daily or weekly touchpoints that suit your team, with overlap across time zones.
- Scope changes
- You set priorities and we plan capacity around them.
Specialist consulting
A focused question: architecture review, choosing a GIS stack, a data audit or a migration plan.
- How it works
- A short, fixed engagement that ends in a written recommendation.
- You receive
- Findings and recommendations report
- Architecture or migration plan
- Walkthrough session with your team
- Communication
- Kick-off, interviews with your team and a final presentation.
- Scope changes
- Defined by the questions agreed at kick-off.
Maintenance and support
Systems already in production that need updates, monitoring and small improvements.
- How it works
- An agreed monthly allowance for fixes, dependency updates and minor features.
- You receive
- Security and dependency updates
- Issue fixes
- Monthly summary
- Communication
- A single channel for requests, with priority handling for outages.
- Scope changes
- Larger features are scoped separately as projects.
How a project runs
Discovery
We learn how your organisation works, who the users are and what data exists.
Scoping
We agree goals, priorities, constraints and what done looks like.
Design or prototype
Interface designs or a working prototype test the riskiest ideas first.
Iterative build
Short cycles of development, each ending in something you can review.
Testing and acceptance
Functional, data and performance checks against the agreed criteria.
Launch
Deployment to your chosen environment, with documentation and training.
Support
Monitoring, updates and improvements once the system is in use.
Ownership, access and handover
Confirm each answer matches your contractsWho owns the code and intellectual property?
Ownership is set in the contract for each engagement. Our usual approach is to work in a repository you own from the first day, so the source is always in your hands. Repository access and IP ownership are separate terms, and the contract states both.
How do you get access to our systems and data?
Your administrators grant access through named accounts with only the permissions the work needs. We do not ask for shared passwords, and access is removed when the engagement ends.
Who deploys, and where does it run?
We can deploy to your cloud or servers, or to hosting we set up in your name. Either way, deployment steps are documented so your team can repeat them.
How is work accepted, and how are changes handled?
Each milestone has acceptance criteria agreed before work starts. You review working software against them. Changes are estimated and agreed before we start on them, so scope never moves silently.
What do we receive at handover?
The source code, deployment and configuration notes, environment variables documented without secrets, data model notes and a walkthrough with your team.
What support is available after launch?
A maintenance arrangement covers fixes, updates and small improvements. Support hours and response times are agreed per contract. We do not offer a 24-hour uptime SLA unless one is written into your agreement.
How to begin
- Send a short description of the problem, the data you have and any deadlines.
- We reply with questions and arrange a call.
- You receive a proposal with scope, approach and the engagement model we recommend.
Have a project in mind?
Tell us what you are trying to achieve. We will reply with questions, an initial view on approach, and the next step.