About us
FRIEND HOMES LTD is an IT company working on software, cloud infrastructure, data systems and security practice. This page describes how we work — not what we would like you to assume about us.
01 — Company overview
What the company does
We build software and the infrastructure it runs on, and we help organisations understand and improve the systems they already have. Engagements range from a single application to a broader programme covering platform, data and security work.
Work is delivered by small teams that stay with an engagement from definition through to operation. We publish no client names, headcounts or awards on this site; the relevant question is whether our method suits your situation, and that is what these sections set out.
02 — Mission
To leave clients with systems they understand and can operate.
Software that only its original authors can maintain is a liability, however well it performs on the day it ships. Our measure of a finished engagement is whether the client’s own team can explain the system, change it safely and know where to look when it misbehaves.
Working principles
03 — Principles
- Scope in writing
- Nothing significant starts without agreed criteria for what finished means.
- One accountable team
- The people who define the work are the people who build it.
- Show progress early
- Working software in a shared environment beats status reports.
- Say what is uncertain
- Estimates carry their assumptions; unknowns are named rather than padded.
- Prefer removal
- Reducing a system is as valid an outcome as extending it.
- Leave a trail
- Decisions, trade-offs and runbooks are written down as work proceeds.
04 — Approach to technology
Tools chosen for the problem, not the trend
We keep a deliberately narrow default stack of well-supported languages, databases and cloud services, and we step outside it when a problem genuinely requires something else. New technology is evaluated against maintenance cost, hiring reality and how easily it can be replaced later.
The same restraint applies to architecture. Distributed designs are introduced when scale or organisational boundaries demand them, not as a default; a well-structured single service is often the more honest answer.
05 — Collaboration philosophy
Working with your team, in the open
We work inside your communication channels rather than behind a client portal. Progress, blockers and open questions are visible as they happen, and we expect direct access to the people who understand the domain.
Where your own engineers are involved, they review our changes and we review theirs. Knowledge transfer is continuous rather than a session booked for the final week.
06 — Quality standards
Quality defined before delivery, not after
Every piece of work carries acceptance criteria written in advance. Changes reach production through the same automated pipeline regardless of size: static analysis, tests, dependency checks and a review by a second engineer.
- Tests written around behaviour, not implementation detail.
- Releases staged so they can be rolled back quickly.
- Monitoring and alerting configured before launch, not after.
- Written incident notes and follow-up actions after any failure.
07 — Security and privacy principles
Least access, least data
We ask for the narrowest access needed to do the work, for as long as the work requires. Credentials are held in managed secret storage, never in code or shared documents, and are revoked at the end of an engagement.
Where client data is involved we prefer anonymised or synthetic datasets for development, encrypt data in transit and at rest, and keep our handling consistent with the commitments described in our Privacy Policy.
08 — Contact information
Reach the company directly
Enquiries and questions about this page are answered by email, in English.
- Company
- FRIEND HOMES LTD
- anniewatso89@gmail.com