We teach your team to build it.
The tools that let a small team build its own internal software got good very quickly, and most businesses haven’t noticed yet. We teach your people to use AI coding tools and modern development workflows properly, so the next internal tool you need doesn’t require a purchase order or a consultant.
How it’s priced
Fixed price, against a written scope
Education is priced per engagement, because the right shape depends on how many people are being trained, what they can already do and whether there’s a real build attached. Final pricing is confirmed in writing before anything is booked, and we’ll tell you if training is the wrong answer for you.
Typical timeline
Agreed per engagement. Workshops are scheduled around your team; guided implementation runs for as long as the build takes.
The problem
Every small internal tool you need becomes someone else’s invoice.
A form that writes to a sheet. A report nobody has time to assemble. A tracker for one team’s process. None of them justify a development project, so they either never get built or they get bought as yet another subscription. Meanwhile the tooling to build exactly that has become dramatically more accessible, and the people in your business who understand the process best are the ones best placed to use it.
- Small internal tools priced as projects, so they never happen
- Another subscription for something a competent team could build in a week
- Dependence on an external firm for changes that should take an afternoon
- People who know the process best having no route to improve it
- A team that has heard of AI coding tools but is using them as a novelty
The solution
Capability you keep, rather than a dependency you rent.
We train your team on the same tools and workflow we use ourselves, on your own problems rather than a sample project. Practical training and workshops to establish the fundamentals, guided implementation while they build something real, then ongoing technical support for when they get stuck. The deliverable is a team that can build and maintain its own internal tools, and the judgement to know when something should be handed to us instead.
- Training on your real problems, not a tutorial project
- AI coding tools used as part of a workflow, with review and version control
- Guided implementation: they build it, we’re alongside them while they do
- Honest limits too: what to build in house, and what not to
- Ongoing technical support once the training ends
- Reduced reliance on subscriptions and on us
Exactly what lands in your hands
- Practical training sessions run on your own problems and systems
- Workshops covering AI coding tools, version control and review
- A working internal tool your team built, in production
- Written guidance and conventions your team can follow afterwards
- A documented view of what to build in house and what to outsource
- Ongoing technical support and code review where you want it
What this looks like in practice
Illustrative scenarios based on the kind of work this service exists to do. They’re examples, not client case studies.
An operations team that keeps needing small tools
Trackers, forms, dashboards and internal reports. Not big enough to justify a project each, collectively worth a great deal. We teach the team to build them.
A developer or two who want to move much faster
People who can already code, using AI tools casually and inconsistently. We cover the workflow properly: prompting, review, testing, version control and what not to trust.
The business owner who wants to stop being quoted for everything
Enough capability in house to handle the small things, and enough judgement to know which of the big things are genuinely worth paying for.
A team inheriting a system we built
We built it, you want to own it properly. We train your people on the codebase and the deployment, then stay available while they take it over.
Guided implementation of a first real build
Your team builds something that matters, with us reviewing the design and the code as they go. The training and the deliverable are the same piece of work.
How the engagement runs
- 01
Establish the starting point
Who is being trained, what they can already do, and which real problem they’re going to build against.
- 02
Practical training
Workshops on the tools and the workflow, worked through on your problems rather than a sample project.
- 03
Guided implementation
They build something real. We review the design and the code while they do it, and correct course early.
- 04
Ongoing support
Available for review and the hard questions once the formal sessions finish, for as long as it’s useful.
Fixed scopes, fixed prices
Education is priced per engagement, because the right shape depends on how many people are being trained, what they can already do and whether there’s a real build attached. Final pricing is confirmed in writing before anything is booked, and we’ll tell you if training is the wrong answer for you.
Team Workshop
Practical training on AI coding tools and a modern development workflow, run on your own problems.
- Sessions scheduled around your team
- AI coding tools used as part of a real workflow
- Version control, review and testing fundamentals
- Worked through on your systems and your problems
- Written conventions to keep afterwards
Guided Implementation
Your team builds something real and we’re alongside them while they do it.
- A real internal tool, chosen with you
- Design and architecture reviewed before the build
- Code review throughout
- Deployed to production by your team
- Handover notes your team wrote themselves
Ongoing Technical Support
A technical counterpart for a team now building its own tools, for when they get stuck.
- Code review on request
- A named technical contact
- Architecture and build-versus-buy advice
- Help when something breaks in production
- Escalation to a build with us when that’s the right answer
These are launch positioning prices, not quotes. Final pricing depends on scope, integrations and data quality, and is fixed in writing before any build starts. See all pricing.
We can build it for you, or teach you to build it
Different problems call for different answers. Here’s how to tell which one you need.
Hire us to build it
- Best when
- The system is business-critical, handles payments or personal data, or has to be right first time.
- You end up with
- A finished, deployed system, documented and handed over.
- Your team’s time
- A few hours a week for reviews, decisions and testing.
Learn to build it yourselves
- Best when
- You keep needing smaller internal tools, or you want to own and evolve a system without us.
- You end up with
- A team that can build, and a working tool they built themselves.
- Your team’s time
- Significant. They’re the ones doing the building, with us alongside.
The two combine well: we build the core system, then train your team to maintain and extend it. And if you aren’t sure which you need, that’s exactly what Consultancy & Strategy is for, even when the honest answer is neither.
Education & Enablement, answered
For the small work, yes, deliberately. We’d rather be the firm you call for the system that genuinely needs us than the firm you resent for invoicing a form and a report. Teams who can build their own small tools tend to arrive at the big problems with much better judgement, and those are the engagements worth having.
No, and we’ll be straight with you about what that means. A non-developer can reach a genuinely useful standard for internal tools with the current generation of tooling. They shouldn’t be building anything handling payments, personal data at scale or safety-critical decisions, and we teach that boundary as explicitly as we teach the tools.
No. We don’t run an accredited programme and we aren’t going to print a certificate that means nothing. What you get is a team that has built and deployed something real, and the artefact to prove it.
It’s priced per engagement and confirmed in writing before anything is booked, because the right shape depends on how many people are involved, what they can already do and whether a real build is attached. Tell us the team and the problem and we’ll come back with a fixed figure.
The ones we use ourselves on real builds, which currently means AI coding assistants inside an ordinary professional workflow: version control, code review, testing and deployment. We teach the workflow rather than one vendor, because the vendors will change and the workflow won’t.
Next step
Ready to build the capability in house?
Five short questions about the business, the problem and the budget. We’ll come back with a view on scope and cost.