Mission
Make software behave the way it was specified.
We exist to remove ambiguity from software delivery: to state what will be built, build it, and provide the evidence that it works.
02
An engineering practice, described plainly.
PENCILL LTD is a software and systems engineering company. We build, integrate and maintain production software for organisations that need their systems to be understood, documented and dependable over time.
A
Company overview
We operate as a single accountable engineering team. Work begins with a written understanding of the problem, continues through reviewed increments, and ends with a system that another team could pick up and run. That sequence does not change with the size of the engagement.
Our services span custom software development, web applications, cloud infrastructure, integration, data engineering, quality assurance, security-oriented engineering, modernisation, architecture consulting, continuous delivery and long-term maintenance. All communication and documentation are in English.
Mission and vision
Vision
Systems that stay understandable as they age.
We want the systems we leave behind to remain legible and changeable long after the original engagement has closed.
B
Principles
- 01
Write it down first
A decision that is not recorded will be re-litigated later, usually at the worst moment.
- 02
Prefer the simpler structure
Complexity should be earned by a requirement, never adopted by default.
- 03
Make correctness observable
If nobody can check it, it is not a standard — it is a hope.
- 04
Own the consequences
The people who design a system stay close to it while it runs.
- 05
Be direct about risk
Uncertainty is stated, quantified where possible, and revisited.
- 06
Leave it maintainable
Every deliverable is judged by how easily the next engineer can change it.
C
Engineering culture
Code is read far more often than it is written, so we optimise for the reader. Reviews are expected, disagreement is welcome when it is specific, and the standard applies to everyone equally — including the person who set it.
We keep documentation close to the code it describes, prefer boring and dependable tools, and treat operational problems as engineering problems rather than interruptions.
D
Approach to collaboration
One conversation, not many
A single point of accountability on our side, so decisions do not get lost between contacts.
Visible progress
Work is demonstrated as it lands rather than described in status reports.
Shared vocabulary
We adopt the language of your domain so that specifications mean the same thing to both sides.
E
Quality standards
- Acceptance criteria agreed in writing before implementation starts.
- Peer review on every change, without exception for urgency.
- Automated tests layered by risk: unit, integration and end-to-end.
- Defects tracked to root cause rather than to the first fix that removes the symptom.
- Documentation updated as part of the work, not after it.
F
Security mindset
- Access granted at the narrowest useful scope and reviewed as systems change.
- Personal and sensitive data identified, minimised and handled deliberately.
- Dependencies monitored and updated as routine maintenance.
- Secrets kept out of source control and rotated on a defined basis.
- Incident response paths designed before they are needed.
G
Long-term partnership philosophy
A system's real cost appears after launch. We plan for that period from the first drawing: documented interfaces, predictable environments, and a support arrangement that treats maintenance as engineering rather than as clean-up. Where an engagement ends, it ends with a handover that leaves the client independent.
H
Company contact details
- Company
- PENCILL LTD
- [email protected]
- Website
- pencillgroup.com
- Language
- English
