01
Plain language
Technical choices explained in terms of consequences — cost, risk, effort — rather than terminology.
About us
An engineering company focused on software that stays useful
SUPER ACCOUNTANTS LTD works in information technology: building custom applications, running them on dependable infrastructure, automating manual processes and connecting systems that were never designed to work together.
Our focus
What the company does — and does not do
The company's registered name is SUPER ACCOUNTANTS LTD. Its activity is IT services and software development. It does not offer accounting, bookkeeping, audit or tax services, and nothing on this website should be interpreted that way.
The work divides into building new software, improving software that already exists, and making the environment around that software predictable. In practice these overlap: a new application usually needs integrations, and an old application usually needs its deployment path repaired before anything else can improve.
No history, founding date, headcount or client list is published here, because this site deliberately avoids stating anything it cannot support. What can be described honestly is how the work is approached — and that is what the rest of this page covers.
Mission
Reduce the friction between a business and its software
Most organisations do not need more software; they need the software they have to fit the way they actually work. The mission is to close that gap — by building only what is missing, integrating what exists, and leaving systems that can be understood and changed by the people who depend on them.
Measure of success
A project has gone well when the client's own team can operate, explain and extend the result without needing the original authors in the room.
Values
Principles applied to every engagement
02
Proportionality
The simplest solution that solves the problem, including recommending an existing product over a custom build.
03
Maintainability
Code, configuration and documentation written for the person who inherits them.
04
Honesty about limits
No guaranteed outcomes, no invented credentials, no claims that cannot be supported.
05
Shared ownership
Clients hold their own repositories, accounts and credentials from the start.
06
Steady pace
Sustainable increments rather than heroic pushes that leave debt behind.
Engineering principles
How the software itself is built
Model the domain first
Data structures and state transitions are designed before interfaces, so the system stays coherent as features accumulate.
Prefer explicit over clever
Readable code with obvious control flow beats compact code that only its author understands.
Automate the repeatable
Builds, tests, migrations and deployments are scripted so they behave identically for everyone.
Keep environments comparable
Development, staging and production differ in data and scale — not in configuration philosophy.
Write the decision down
Architecture choices are recorded with their trade-offs, so they can be revisited rather than re-argued.
Leave the code better
Small refactors accompany feature work instead of waiting for a rewrite that never comes.
Collaboration
How we work with client teams
Engagements are set up so progress is visible without anyone having to ask. Work items live on a shared board, changes appear in a running environment, and each cycle closes with a short written summary of what changed, what is next and what is blocked.
Client involvement is concentrated where it matters: agreeing the problem, reviewing increments and deciding priorities. Technical detail is documented rather than delegated upward.
Where a client has an in-house team, the arrangement can be joint delivery, focused help on specific components, or review and advisory input — whichever leaves the internal team stronger.
Quality
What quality means in practice
Correctness
Business rules covered by automated tests, with defects turned into permanent regression checks.
Clarity
Consistent structure, naming and formatting enforced by tooling rather than argued case by case.
Operability
Useful logs, basic metrics and a documented way to diagnose a problem in production.
Reversibility
Every release has a rollback path, and every schema change has a migration.
Contact