About us
An engineering company built around clarity, not ceremony.
REP & REFORM LTD designs, builds and maintains software for organisations that need dependable systems rather than disposable prototypes. We work across the full delivery path: product definition, interface design, application engineering, infrastructure, testing and long-term support.
Software delivered as a working system, documented and maintainable.
Our work covers custom business applications, customer-facing web products, internal tooling, integration layers and the infrastructure that runs them. Engagements range from a single well-scoped module to continuous development across several releases.
We prefer small, senior teams with direct client contact. Decisions are recorded, code is reviewed, and the architecture stays legible to whoever maintains it next — including teams that are not ours.
To make software that behaves predictably under real conditions — with sensible structure, honest estimates and no hidden complexity handed over at the end.
Predictability is a design decision. It comes from defined scope, small increments, automated verification and observability built in from the start rather than retrofitted after an incident.
We aim for systems a client can operate, extend and audit without depending on a single vendor.
Scope before code
Every engagement starts with the problem, the constraints and the definition of done. Unclear requirements are resolved in writing before implementation begins.
Small increments
Work is delivered in reviewable slices, each demonstrable in a running environment, so direction can change without discarding completed work.
Written decisions
Architectural choices, trade-offs and rejected alternatives are documented next to the code they affect.
No silent complexity
Dependencies, background jobs and manual steps are named explicitly and handed over with operational notes.
Explicit data models
Schemas, constraints and migrations are treated as first-class engineering artefacts. Data integrity is enforced in the database, not only in application code.
Boundaries that hold
Business logic is separated from transport and presentation, so an interface change does not require rewriting rules that govern the domain.
Automated verification
Unit, integration and end-to-end tests run in continuous integration on every change, with the failing case reproduced before a fix is written.
Operable by design
Structured logging, health checks, metrics and alerting are part of the feature, not a later project.
One accountable contact
Each engagement has a named engineer responsible for scope, sequencing and written status updates, so questions do not travel through several intermediaries.
Shared visibility
Backlog, branch state, test results and deployment history are visible to the client throughout, in the tools they already use where possible.
Asynchronous by default
Written summaries replace status meetings; scheduled calls are reserved for decisions that genuinely need discussion.
Definition of done
A change is complete when it is reviewed, covered by tests, documented, deployed to a staging environment and accepted against the agreed criteria.
Review discipline
All code passes peer review. Reviews check correctness, readability, security-sensitive paths, error handling and migration safety.
Accessibility and performance
Interfaces are checked for keyboard operation, contrast, semantic structure and payload size as part of normal delivery.
Repeatable releases
Builds are reproducible, environments are configured through code, and rollback paths are prepared before deployment.
The relationship continues after the first release.
Software degrades when dependencies age, platforms shift and usage patterns change. Ongoing support covers dependency and security updates, monitoring review, performance tuning, incident handling and planned feature work.
Support arrangements are agreed in writing and shaped around the system's actual risk profile. Where a client's own team takes over, we provide handover documentation, runbooks and a transition period of shared work.
Enquiries: [email protected]