How we work
How we work
How a project runs from first call to handover, who owns the code, and the practices we follow while we build.
01 / How a project runs
How a project runs
Four steps, in this order. You know what comes next and what you will receive at the end of each one.
We ask what your organisation needs, who will use it and what already exists.
- What you do
- Tell us what the software needs to do, who will use it and what you use today. Share anything that exists already, such as spreadsheets, systems or notes.
- What we do
- Ask questions and listen, then write back what we heard so you can correct it. We say plainly if we are not the right people for the job.
You receive: A short written summary of what we heard
We write down what we will do, what we will not, and what it costs. Bespoke work runs on a master agreement and a statement of work.
- What you do
- Read the written scope, say what is missing or not needed, and agree it when it is right.
- What we do
- Write down what we will build and what we will leave out, split the work into stages, and give you a price in writing.
You receive: A written scope and a price
We deliver in short stages and show you the result along the way.
- What you do
- Try the working software at each stage and tell us what to change. Answer our questions when we need a decision.
- What we do
- Build in short stages, have a second person read each change, test the parts that matter most and show you the result as we go.
You receive: Working results you can check at each stage
We deliver the finished work and explain how to run it. For bespoke software, the code is yours once every sum due is paid in full.
- What you do
- Check the finished work against the written scope and tell us who will run it day to day.
- What we do
- Deliver the work, explain how to run it, hand over plain documentation and agree any support you want.
You receive: The finished work and plain documentation
02 / How we build
How we build
These are the practices we follow on every project. Ask us about any of them on a call.
From sketch to release
- 01
Written scope before code
Nothing is built until you and we have agreed in writing what it is.
- 02
Version control and review
Every change is recorded and read by a second person before it ships.
- 03
Automated tests
The parts that matter most are covered by tests that run on every change.
- 04
Accessibility checks
We check against WCAG 2.2 AA, including use with a keyboard and a screen reader.
- 05
Security checks
We review how data is stored and sent before release, and keep secrets out of code.
- 06
Plain documentation
You receive a short, readable guide to what we built and how to run it.
git switch -c add-invoice-exportgit commit -m "Add invoice export"pnpm testall tests passedpnpm buildbuild completegit push origin add-invoice-exportreview requested03 / Ways to work with us
Ways to buy
Three ways to buy from us. We do not publish prices. We quote in writing.
01 / 03
Subscription
A Scout Systems product, with support included.
Subscription
You subscribe to the finished product and we host and support it. Products are sold singly, bundled or as the full suite. We quote in writing.
- Suits you when
- You want finished business software that someone else hosts and supports.
- You receive
- The product, hosted by us, with support included.
02 / 03
Project or hourly
Bespoke or infrastructure work for an agreed scope.
Project or hourly
Bespoke software is set out in a statement of work with scope, milestones, acceptance criteria, price and a time or budget ceiling. Infrastructure work can be a project or hourly work.
- Suits you when
- You know what you need built or tested and want the scope and price agreed first.
- You receive
- A statement of work, then the finished work.
03 / 03
Retainer
An ongoing arrangement for infrastructure services.
Retainer
Cybersecurity and cloud work can be agreed as a retainer under contract. The contract states what the retainer covers.
- Suits you when
- You want cybersecurity or cloud work to continue under one contract.
- You receive
- The work the contract says the retainer covers.
04 / Contract and ownership
Contract and ownership
These terms are agreed in writing before work starts. Here they are in plain words.
- Who we sell to
- Businesses and public sector bodies for everything we sell. Individuals for bespoke software.
- The paperwork
- Bespoke software runs on a signed master agreement plus a statement of work for each project. The statement of work sets the scope, milestones, acceptance criteria, price, and a time or budget ceiling.
- Who owns the code
- You own the code once every sum due is paid in full. Until then Scout Agency owns it.
- What we keep
- Scout Agency keeps its own platform and its pre-existing components. If your software uses them, you use them under licence.
- Security testing
- No security test starts without your signed written authorisation. Testing a system without permission can be a crime under the Computer Misuse Act 1990.
05 / The first step
The first step is a short call.
A 30 minute call to hear what your organisation needs. You do not need to prepare anything. If we can help, we will write down a scope and a price. If we cannot, we will say so.