Software engineering · Brook, Ashford, Kent
Scoped. Built. Supported.
Software rarely fails during the build. It fails at handover, when the people who wrote it leave and nobody can change it. We write the scope down first.
How an engagement runs
Four fixed points
A scope, in writing
Two weeks. £1,500. What ships, what is excluded, what could go wrong. The document is yours whether or not we build it.
Ten-day milestones
Working software every fortnight, on an environment you can open yourself. A wrong turn costs two weeks.
Your accounts, your code
Repositories, cloud accounts and domains sit in your company's name from day one. We hold access, not ownership.
Written for your next engineer
Each project closes with a runbook and a recorded walkthrough. Support afterwards is a choice, never a dependency.
Rates
What we are engaged to do
Select the lines that apply. They carry into the enquiry form below.
Discovery & written scope
Two weeks. Interviews, a data model, a costed build plan. Ends in a go or a no-go; both are acceptable.
Web & product build
Customer-facing applications and internal products, built to the scope. First release usually lands between eight and sixteen weeks.
Workflow automation
The spreadsheet that three people maintain by hand, replaced by something that runs itself and logs what it did.
Systems integration & API work
Accounting, CRM, payments and stock made to speak to each other. With retries and an audit trail, not a nightly export.
Cloud & infrastructure
Migration, hardening and cost review across AWS, Azure or Hetzner. Data stays in UK or EU regions unless you instruct otherwise in writing.
Managed support
Monitoring, patching, backups and a named engineer who already knows the system. Four-hour response during UK business hours.
Retained engineering
Days booked against your backlog, minimum three months. For teams that have the direction and need the hands.
Figures are a starting point. Each one is confirmed in the scope document, in writing, before any invoice is raised. Fixed-price work is quoted as a single figure, not an estimate.
How we are set up
Ten working days, maximum
No milestone runs longer than a fortnight. A wrong turn costs two weeks.
The people who scope it, build it
Discovery is not a sales call handed on to a delivery team you have never met.
Quoted once
What the scope document says is what the invoice says. Changes are priced before anything moves.
A runbook, every time
Each system ships with a written runbook and a recorded walkthrough, addressed to whoever comes after us.
The practice
A small practice, deliberately
Software should outlive the people who wrote it. Almost none of it does.
Pared Limited was registered in 2025. The engineers behind it have been building production systems since 2014: payments, logistics scheduling, clinical records. The unglamorous middle of other people's businesses.
One of those systems worked well for four years. Then the client needed a VAT rate changed and found that nobody could do it. The team had gone; nothing had been written down. That afternoon is the reason for the scope document, the ten-day milestone and the runbook at handover.
We work from Brook, a few miles outside Ashford. Discovery happens on site. Most of the build does not.
The engineer who set the rules
Callum Reeve joined in 2025. Before that: eleven years on systems that are not permitted to fail — first a card authorisation switch handling roughly 1.4 million transactions a night, then four years on rota software for an ambulance trust.
The trust job is the one that changed him. A release went out at 04:10 on a Tuesday and a rota covering 900 staff came back empty. He found it in nine hours. The fix was one line. What stayed with him was not the line — it was that nobody in the building could say what the rota was supposed to do, so there was nothing to check the behaviour against.
He writes the specification first now. Every engagement. He is the reason discovery is a separate, paid piece of work here instead of something we give away to win the build, and the reason a runbook ships with the code.
He is also the one who will tell you, on the first call, that your idea is three products rather than one.
What we decline. No build price before the scope exists. No retainer shorter than three months. No engineer on a project who was not in the scoping. If you need a team assembled next week, we are the wrong practice, and we will say so on the call.
Why we work this way
Simple can be harder than complex: you have to work hard to get your thinking clean to make it simple.Steve JobsBusinessWeek, 1998
Which is why the first thing we hand over is a document, not code.
Next step
Start with the scope, not the estimate.
Thirty minutes, no charge. If the work does not suit this practice we will say so on the call, and name someone it does.
Enquiries
Book a consultation
- [email protected]
- Telephone
- +44 7868 236 612
- Registered office
- Lavington House, Naccolt Road,
Brook, Ashford, TN25 5NY
United Kingdom - Open in Maps ↗
- Hours
- Monday to Friday, 09:00–17:30
Enquiries answered within one working day.