Legacy systems under load
Software originally designed for a smaller organisation is now supporting the whole business. It works, but it groans. We stabilise it, document it, and modernise it in place without stopping the line.
Volume 01 — The Engineering Register
Engineered technology,
built to hold.
BLOCK AND RESERVE LTD is an independent technology practice. We design, build and operate the software, infrastructure and security systems that organisations depend on every working day — carefully, quietly, and for the long term.
Reserved for
- Operators of production systems
- Regulated and safety-critical work
- Teams modernising legacy platforms
- Founders building durable products
§ 01 — The house
A note from the practice
A practice, not a factory.
We are a small, senior team of engineers, architects and consultants working under a single roof. Each engagement is led by people who write code, review code, and remain accountable for the systems we deliver long after they enter production.
Our name is deliberate. Block refers to the units of infrastructure — servers, services, contracts, ledgers — that make a modern business function. Reserve is the discipline of leaving margin: margin for load, for change, for the unforeseen. Together, they describe how we work.
We do not chase trends. We do not resell hardware. We take on a small number of engagements at any time so that every one of them receives the attention it needs.
§ 02 — Capabilities
Twelve disciplines
01
Custom software architecture and engineering
02
Web and mobile application development
03
Enterprise systems and back-office platforms
04
Cloud infrastructure design and operation
05
Cybersecurity, hardening and incident response
06
System integration and middleware
07
Business process automation
08
Data platforms, warehousing and analytics
09
API design, versioning and integration
10
Infrastructure modernisation and migration
11
Technical consulting and architecture review
12
Ongoing technical support and maintenance
§ 03 — Problems we take on
What clients bring us
Fragmented data
Information lives in twelve spreadsheets, three databases and a filing cabinet. Decisions are slow because nobody trusts the numbers. We build reliable data pipelines and clean, queryable warehouses.
Security debt
Access is loosely controlled, secrets are shared informally, and there is no incident playbook. We introduce least-privilege access, encrypted operations, audit trails, and rehearsed response procedures.
Manual, repeated work
Skilled staff spend their days re-typing figures between systems. We identify the highest-value processes and automate them cleanly, with monitoring and human oversight built in.
Cloud spend without control
The cloud bill grows every month and nobody can say precisely why. We instrument workloads, remove idle infrastructure, and rebuild the parts that were designed for a different scale.
Product engineering capacity
The roadmap is longer than the team can deliver. We plug in as a senior engineering partner: writing code, reviewing pull requests, and mentoring rather than replacing your in-house engineers.
§ 04 — Sectors
Where we work
Software is now the substrate of every industry.
Our engagements cluster in industries where reliability, security and long time-horizons matter more than novelty.
Financial services & fintech
Insurance & risk
Healthcare & life sciences
Logistics & mobility
Industrial & manufacturing
Energy & utilities
Public sector & regulated bodies
Retail & e-commerce operations
Professional services
Media & publishing platforms
Property & construction technology
Education & research
§ 05 — Software
How we build
Software the way it should be written.
Small commits. Reviewed code. Thorough tests. Deployments that can be reversed in one command. We build systems that are boring to operate, because boring is what production software is supposed to feel like on a Tuesday afternoon.
- Application stack
- TypeScript, React, Node, Python, Go, Rust
- Data
- Postgres, ClickHouse, Kafka, dbt, Airflow
- Infrastructure
- Kubernetes, Terraform, AWS, GCP, Azure
- Delivery
- CI/CD, feature flags, observability by default
§ 06 — Cloud & Infrastructure
Built for uptime
Infrastructure as a discipline.
Every environment we design is expressed as code, version-controlled, reproducible, and instrumented from the moment it is provisioned. Nothing is configured by hand and forgotten.
- — Multi-region architectures
- — Disaster recovery drills
- — Immutable infrastructure
- — Cost observability
- — Zero-downtime deploys
- — Autoscaling & load shedding
- — Private networking, VPNs, mesh
- — Backup verification, not just backups
§ 07 — Security
Posture, not paperwork
Security treated as a property of the system, not a checklist tacked on later.
We assume the environment is hostile. That assumption drives every decision we make about identity, transport, storage, deployment and observability. We prefer boring, well-understood controls executed consistently over novel controls executed once.
Least
privilege access, revoked on offboarding
Encrypted
in transit and at rest, by default
Audited
structured logs, retained and searchable
Rehearsed
incident playbooks, tested quarterly
§ 08 — Integration & automation
Systems that speak
Making the parts of your business speak the same language.
Most operational pain is not caused by any single system failing; it is caused by systems that do not talk to each other properly. We build the middleware, the APIs, the event streams and the automations that turn a portfolio of tools into a coherent whole.
- — ERP, CRM and finance system integration
- — Event-driven architectures and message queues
- — Robotic process automation for back-office tasks
- — Scheduled data reconciliation and drift detection
- — Human-in-the-loop workflows with clear audit trails
§ 09 — Method
How an engagement moves
Phase 01
Discovery
One to three weeks of structured investigation. We read the code, interview operators, map data flows, and produce a written architecture brief before any implementation begins.
Phase 02
Design
We propose the smallest viable design that solves the problem completely. Trade-offs are made explicit; the option we did not choose is documented alongside the option we did.
Phase 03
Build
Short iterations, reviewed pull requests, thorough tests, continuous delivery to a staging environment your team can inspect at any time.
Phase 04
Harden
Load testing, failure injection, security review, and a written runbook covering every operational scenario we can reasonably foresee.
Phase 05
Operate
A defined support arrangement that keeps us close to the system while transferring ownership cleanly to your team on a timeline you set.
§ 10 — Technology
Working stack
Languages
- TypeScript
- Python
- Go
- Rust
- SQL
- Bash
Frameworks
- React
- Next.js
- Node.js
- FastAPI
- Django
- Express
Data
- Postgres
- ClickHouse
- Redis
- Kafka
- dbt
- Airflow
Platforms
- AWS
- GCP
- Azure
- Kubernetes
- Terraform
- GitHub Actions
§ 11 — Standards
Principles of practice
Quality is not a stage of the project — it is the way each hour of the project is spent.
Written work
Every architectural decision is recorded in writing. Every system we deliver has a runbook. Future engineers should never have to guess.
Reviewed work
No single engineer merges their own code into production. Peer review is a discipline, not a formality, and we practise it inside our own team as well.
Reversible work
Every change we ship can be undone in one command. If it cannot be undone, we build the migration path back before we build the migration path forward.
§ 12 — Reasoning
Why we are engaged
We take on few engagements at once
So the senior team is genuinely on your project
We write things down
So decisions survive the people who made them
We measure what we ship
So performance and cost are observed, not assumed
We hand off, not hostage
So your team can operate the system without us
We reserve capacity
So we can respond when something is genuinely urgent
We invoice for time, not tickets
So we can slow down when a decision requires care
§ 13 — People
A small team, kept close to the work.
Every engagement is delivered by senior engineers who remain part of the project from discovery through operation. There are no hand-offs to a delivery team you have not met.
§ 14 — Questions
Frequently asked
Questions that come up early in most conversations.
- What kinds of organisations do you typically work with?
- We partner with mid-market and enterprise teams that operate mission-critical software: financial operators, industrial and logistics companies, health and public-sector organisations, and product companies scaling engineering capacity.
- Do you take on both new builds and existing systems?
- Yes. Roughly half of our engagements are greenfield architecture, and the remainder are modernisation, integration or resilience work inside systems that already carry real production load.
- How do you approach discovery on a new engagement?
- We start with a short, structured discovery: reading the code and the runbooks, mapping data flows, interviewing operators, and producing a written architecture brief before any implementation begins.
- Can you work alongside our internal engineers?
- That is our default. We integrate into your workflow, pair with your engineers, review each other's code, and hand off documentation designed to outlast the engagement.
- How do you handle sensitive data and access?
- Every engagement begins with a written data-handling agreement, least-privilege access, encrypted transport and storage, audit logging, and clearly scoped credentials that are rotated on offboarding.
- What technologies do you specialise in?
- Our core stack spans TypeScript and Python for application work, Go and Rust for systems components, Postgres and event-driven data pipelines, and Kubernetes, Terraform and the major hyperscale clouds for infrastructure.
§ 15 — Correspondence
Write to us.
We reply to every serious enquiry, whether it becomes an engagement or not. A short note describing the situation you are working on is enough for a first conversation.
- Company
- BLOCK AND RESERVE LTD
- katherineclark1607@gmail.com
- Website
- blockandreserve.com
- Language
- English