Software Engineering
Softwarethatstayssafetochangeasthebusinessgrows.
We design, build and sustain native mobile, responsive web, desktop and point-of-sale applications in a deliberately narrow set of stacks — organised so each change has a knowable blast radius.
- TypeScript
- C#
- Python
- Java
- Go
- Dart
- Rust
- TypeScript
- C#
- Python
- Java
- Go
- Dart
- Rust
Who this is for
The situation that makes this urgent
The mandate and boundaries below come directly from the approved service catalogue.
A business-critical application is expensive to change because every feature crosses multiple layers.
A mobile or point-of-sale product must behave safely when connectivity disappears.
Release confidence depends on manual testing and the knowledge of a few individuals.
Three ways to engage
Assess, Transform, Operate
Each package has a defined duration, retained outputs, commercial model and objective exit criterion.
Assess
Application and delivery baseline.
Transform
Product build and modernisation.
Operate
Application managed service.
Capability detail
The technical substance, on the page and not behind a form
The operating capabilities and controls that define this practice.
Applications
iOS, Android, responsive web and desktop
Point of sale
Retail, hospitality, fuel and agency banking
Core stacks
TypeScript, C#, Python, Java, Go, Dart and Rust
Quality
Unit, integration, contract and load testing
Accessibility
WCAG 2.2 Level AA, automated and manual
Observability
Logs, traces and business-event telemetry
Technical standard
Requirements that apply to every engagement
Must and should requirements from the board-approved practice standard, made visible before a conversation.
Meet WCAG 2.2 AA for every client-facing interface, verified automatically and with assistive technology.
Define explicit offline and degraded behaviour for every mobile and point-of-sale application.
Organise new code by logical feature module, never by technical layer.
Block merges when unit, integration, contract or load tests fail.
Version published interfaces and maintain producer-consumer contract tests.
Instrument structured logs, distributed traces and business-event telemetry.
Run secret, static security and dependency scans on every commit.
Target median merge-to-production time below one day for Tier 2/3 and three days for Tier 1.
Keep branch coverage above 80% for modules handling financial, clinical or personal data.
Localise currency, date, number and telephone formats for every served market.
How we work
Four phases. Objective exit criteria.
A gate passed on assertion has not been passed. One exit criterion per gate is shown here; the full set sits on each practice page.
Discover
Workload profile, dependency map and recovery objectives written down and signed off by the client owner.Design
Target architecture reviewed against the vendor-supported pattern for the engine in question; failure modes enumerated.Deliver
Recovery tested from backup within the stated RTO, evidenced by a timestamped test record.Operate
Runbooks in place, rota published, first quarterly service review held with measured figures.
The boundary
What we do not do
A capability list without explicit limits is only marketing.
Out of scope
Embedded firmware, real-time control, safety-certified avionics or medical-device software.
Not delivered
Game engines, real-time 3D products, or permanent staff augmentation.
Independent assurance
Independent review of our own software is assigned to an external provider.
Evidence
The artefacts that make the claim testable
Evidence replaces unqualified promises and unattributed metrics.
Feature module map
Published boundaries and dependencies make a change's blast radius visible. Measurement method and review date accompany the delivered record.
Release evidence
Passing accessibility, contract, load and security results attached to the release. Measurement method and review date accompany the delivered record.
Get started
A two-week baseline shows what is safe to change, what is not, and the sequence that reduces risk first.
You keep the written baseline whether or not we continue together.