SORRY IN ADVANCE.LTD

About us

An IT company that apologises in advance — and then does the work properly.

We help organisations build and maintain software that solves real problems, with honest communication at every step.

Purpose

Software should make work simpler — for the people using it and for the people who maintain it.

SORRY IN ADVANCE LTD exists to deliver technology that holds up over time. That means understanding the problem before writing code, choosing proven tools, and leaving behind systems that others can confidently change.

Our name is a small joke with a serious point: software projects involve trade-offs, unknowns and the occasional bad news. We would rather tell you early than surprise you late.

Approach to engineering

Understand first. Build small. Verify always.

Every engagement starts with questions: who uses this, what happens when it fails, and what will need to change next year. The answers shape architecture more than any trend.

We deliver in increments that can be reviewed and tested, write automated checks for important behaviour, and keep deployment repeatable.

Whiteboard sketch of a service-oriented software architecture drawn in green marker

Working principles

  1. 01

    Plain language

    We explain technical decisions in terms of cost, risk and outcome.

  2. 02

    Written agreements

    Scope, assumptions and changes are captured in writing.

  3. 03

    Proportional solutions

    The simplest design that meets the need — no more, no less.

  4. 04

    Visible progress

    Regular updates showing what changed and what comes next.

  5. 05

    Shared ownership

    You own the code, the accounts and the documentation.

  6. 06

    Respect for data

    Personal and business data is handled with care and minimised.

Laptops and sticky-note wireframes on a shared table during a planning session

Collaboration philosophy

We work with your team, not around it.

Good software comes from close collaboration with the people who understand the business. We adapt to your existing tools and rhythms, involve stakeholders early, and make sure knowledge is shared rather than locked inside our heads.

Commitment

Maintainable code. Clear communication. Every time.

Maintainability is a feature: consistent structure, meaningful names, tests and documentation that let your system evolve without fear.

Clear communication is a discipline: honest estimates, early warnings and summaries you can forward to anyone in your organisation.