Software Lab.Platforms your operations can stand on for a decade.
We design, build and run custom platforms, web and mobile applications and the APIs that hold them together. Discovery is fixed-price, the architecture is written down before the code, and the same team stays to operate what it ships.
Build · Run · 24/7
01What we build
What the Software Lab builds.
Archetypes, named by what they do. Every engagement also carries the standards we apply in every lab.
- 01
Operations platforms
Internal systems that replace the spreadsheet and email layer: case management, scheduling, approvals and the audit trail behind them.
- 02
Customer portals and web apps
Authenticated portals, self-service accounts and transactional web apps that are fast on a mid-range phone and accessible to WCAG 2.2 AA.
- 03
Mobile apps
iOS and Android from one codebase where that fits and native where it does not, with offline states designed rather than discovered.
- 04
APIs and integration layers
Typed, versioned APIs with contract tests, so partners and internal teams can build on them without breaking each other.
- 05
Legacy modernisation
Ageing systems read, documented and replaced in stages, with old and new running side by side until the numbers match.
- 06
Commerce platforms
Headless and Shopify Plus storefronts wired into stock, fulfilment and finance, treated as software rather than a theme.
02Services
Services and deliverables.
Concrete scopes with named outputs, so you know what you will hold at the end of each stage.
Paid discovery
A fixed-price sprint that turns a brief into scope, architecture and a costed plan you can take to any supplier.
- Workshop outputs
- Architecture decision records
- Costed delivery plan
New platforms and MVPs
Production-grade first releases, delivered in fortnightly increments you can log in to and use.
- Working release every fortnight
- Test suite and CI pipeline
- Runbook and handover pack
Rebuilds and modernisation
Legacy code turned into a written specification first, then replaced module by module behind a stable interface.
- Legacy code specification
- Migration plan with rollback
- Parallel-run reconciliation
Run retainers
Hosting, monitoring, patching and feature work under one service level agreement, with named engineers.
- Service level agreement
- Monthly health report
- Reserved feature capacity
03Live tool: Scope-to-estimate configurator
Scope it in two minutes.
An indicative range, not a quote. Every assumption is visible, so you can challenge the ones that do not fit your project.
04Lab standard
The A* standard for this lab.
On top of fixed-price discovery, a named lead, code you own, test gates, observability, written decisions and an SLA-backed run retainer, this lab adds:
- 01
Legacy code turned into a written spec
Before anything is rewritten, current behaviour is documented and agreed, including the odd rules nobody remembers adding.
- 02
Contract tests on every API
Consumers and providers are tested against a shared contract, so a change that would break a partner fails in CI, not in production.
- 03
A performance budget
Page weight, response times and Core Web Vitals targets are set at the start and enforced by the pipeline on every change.
- 04
A post-launch SLO
Launch is followed by an agreed service level objective and error budget, measured from the first day in production.
05Human sign-off
Where people sign off.
Agents write and test a large share of the code, under hooks that block a merge when linting, type checks or tests fail. People make the calls that carry accountability.
- Product decisionsWhat to build, what to cut and what good looks like are decided with your product owner, never inferred by a model.
- ArchitectureA senior engineer signs each architecture decision record before work on it begins.
- ReleasesProduction deploys and app store submissions are approved by a named person once every automated gate is green.
06FAQ
Questions, answered.
How long does a typical build take?
It depends on scope, which is why discovery comes first. A focused first release is usually measured in weeks to a few months, and you see working software every fortnight from the first sprint.
Do we own the code?
Yes. You own the code, the infrastructure accounts and the documentation from day one. Nothing is held back to keep you tied to us.
Can you take over an existing system?
Yes. We start with a code and infrastructure review, write down how the system behaves today, and stabilise it before adding features.
Which technologies do you use?
Mostly TypeScript, React and Next.js on the front end, Node, Python and C# behind it, and Postgres for data. We choose for longevity and for your team's skills, not fashion.
08Contact
Tell us what has to work.
Your first call is with an engineer from the Software Lab, not a sales script. Bring the system, the deadline and the constraints.
hello@aurionlabs.io