How we work
Ways of working together
From a short AI pilot to a team that stays with your product for years. You can start small and change the arrangement as you go.
Discuss Your ProjectHow delivery works
One named lead, and the right people for the work
Bigger projects need more than one person, and that only works if somebody manages it properly: clear requirements, regular contact, checks on quality, and one person answerable for the result. That is the job of your named lead.
One person to talk to
A named lead who knows your business and is answerable for delivery. You never have to work out who to ask.
Quick answers
A question in the morning gets an answer that day, not at the end of the week.
Demos, not status reports
Every couple of weeks you see the software running. Progress reports are short and mention the risks as well as the good news.
Review and testing as we go
Code is reviewed and tested as it is written, not in a rush at the end.
Access limited to what is needed
People only get access to the systems they need, confidentiality terms are signed first, and your code stays in your repositories.
Ownership in writing
Who owns what, and who is responsible for what, is agreed in writing before work starts.
The options
Complete Project
You describe the outcome. We plan it, build it and hand it over.
Dedicated Team
A small team that works only on your product, with a named lead.
Team Extension
Our engineers join your team and work in your tools.
Specialist on Demand
A senior developer, architect, or AI or data specialist for as long as you need one.
Support & Maintenance
We look after your live applications.
AI Discovery & Pilot
A short, fixed-fee piece of work to test an AI idea before you commit to it.
| Model | Best for | Commitment | Pricing basis |
|---|---|---|---|
| Complete Project | A clear goal and no in-house developers | The length of the project | Fixed price, or paid by milestone |
| Dedicated Team | A product that will keep developing | Three months or more | Monthly fee for the team |
| Team Extension | More capacity without recruiting | Flexible, scaled up or down | Monthly or hourly |
| Specialist on Demand | A gap, a review or a short burst of expertise | Hours, days or weeks | Hourly or day rate |
| Support & Maintenance | Keeping systems healthy and improving | Rolling | Monthly retainer or block of hours |
| AI Discovery & Pilot | Trying AI with little risk | A few weeks | Fixed fee |
The process
From first call to live system
- 01
A conversation
You tell us what is going wrong, or what you would like to be possible. We ask a lot of questions.
You get: A short note of what we understood
- 02
Looking closer
We look at the systems, the data and the people involved, and find the quickest sensible win.
You get: Findings and a recommended first step
- 03
A proposal
A scope, a team, a timescale and a price, in plain language, usually with a couple of options.
You get: A written proposal you can take to anyone
- 04
Building
Work in short stages with a demo at the end of each, so you see progress and can change your mind.
You get: A demo every week or two
- 05
Going live
Testing, a security check, deployment, and handing over to your team.
You get: A tested, documented system
- 06
Afterwards
Monitoring, support, and whatever you want to do next.
You get: Support, and a short monthly report
FAQ
Questions people ask
We have never used AI. Where do we start?
With a conversation. We look at your processes and your data, tell you where AI is likely to help and where it is not, and suggest a small pilot before anything larger.
Can you work with the systems we already have?
Yes. Most AI work involves connecting to applications and databases that already exist, so integration is a big part of what we do. We would rather build on what you have than replace it.
Is our data safe if AI is involved?
That depends on how the system is built, so we agree it with you first: what goes to a model, where it is processed, who can see the results and how access is controlled.
Who will I actually be working with?
A named lead you can phone, supported by the rest of the team. They join the regular demos and report through the same channels. Who is responsible for what is written down at the start.
Who owns the code?
Intellectual property terms are agreed in writing before work starts.
Can we hire someone for just a few hours?
Yes. By the hour, part-time, for a project or for longer, depending on who is available when you ask.
How big can a team get, and can we start small?
As big as the work needs. A small team or a short paid pilot is a sensible way to begin, and you can grow from there.
How do we stay in touch day to day?
Through whatever you already use, such as Teams or Slack, plus regular stand-ups, demos and a named lead.
How long until we have something working?
For a focused first project, a working version is usually in front of real users within a few weeks. Larger systems are built in stages so that something usable arrives early.
What do you need from us to start?
A person who knows the process, access to the relevant data or systems, and a few hours of staff time in the first weeks. The proposal lists exactly what.
How does a pilot turn into a full system?
If the pilot's results justify it, we widen it in stages: more users, more document sets, more systems. If they do not, you have spent a small amount to find out.
Can we sign an NDA first?
Yes. We are happy to sign yours, or send ours, before you share anything sensitive.
How do you protect our data and code?
People get access only to what they need, confidentiality terms are signed first, and your systems and repositories stay under your control.
See also: flexible expertise and our technology.