How we operate

Every engagement begins with a structured discovery call led by a principal engineer — not a salesperson. We map the problem, constraints, existing systems, and the outcome you are accountable for.

You receive a written statement of work before any code is committed. It defines deliverables, milestones, assumptions, dependencies, and a fixed or capped price. Nothing starts until that document is signed by both parties.

We do not operate a sales layer or hand work to junior teams after the contract is signed. The people in your first call are the people writing your code, reviewing pull requests, and standing up your infrastructure.

• A single principal engineer is accountable for your engagement end to end.
• All code is peer-reviewed before it reaches a protected branch.
• Weekly written progress notes, with milestone demonstrations against the signed scope.

Each client runs in an isolated environment with its own repositories, secrets, and access controls. Changes flow through version control with reviewed pull requests, automated checks, and a staging environment that mirrors production before anything ships.

Work is invoiced against milestones defined in the statement of work, not open-ended hourly meters. You always know what the next payment unlocks, and scope changes are handled through a short written change order rather than surprise invoices.

You own everything we build. On completion you receive the full source repository, infrastructure-as-code, environment configuration, and a written handoff document covering architecture, runbooks, and how to operate the system. Optional care plans are available if you want us to continue maintaining it.

• Source code and commit history transferred to your organisation.
• Deployment, environment, and runbook documentation.
• A clean exit — no proprietary lock-in to Altnera tooling.

We work under a mutual non-disclosure agreement as standard and apply least-privilege access throughout. Details of how we store, transmit, and retire client data are set out in our Confidentiality & Data Protection document.