Skip to content
Example engagements

How We Approach Real Problems

Anonymised, illustrative scenarios across healthcare, fintech, SaaS and e-commerce — the situation, how we would tackle it and what you would receive. No invented clients, no invented numbers.

Technology consulting team planning a project around laptops
Radiatus at a glance
  • Since 2021Independent studio
  • 31 servicesAcross 5 practices
  • 13 productsBuilt & run in-house
  • 24/7Managed support
Illustrative scenarios

Six Problems, and How We Would Tackle Them

Each scenario is a composite of common requests. They are written to show our method — what we look at first, the order we work in and what you keep at the end.

Anonymised examples, not named clients. We don't publish client names or figures without permission. During a consultation we can talk through relevant past work in more detail and, where a client has agreed, arrange a reference.
Illuminated circuit board representing cybersecurity engineering   Healthcare SaaS · Example

HIPAA-aligned cloud migration

The situation

A health-data product has outgrown a single server and needs to move to the cloud without putting protected health information at risk — and an enterprise customer is asking for security evidence.

How we'd approach it

  • Map PHI data flows and agree a target AWS or Azure architecture
  • Build landing zone, encryption, IAM and logging as Terraform code
  • Migrate in stages with rollback plans and parallel running
  • Produce control evidence mapped to HIPAA safeguards

What you'd receive

Target architectureTerraform repoMigration runbookHIPAA control matrix
Doctor using a healthcare app on a smartphone   Diagnostics & labs · Example

Lab-to-EHR HL7 interface

The situation

Lab results reach clinicians through manual uploads and a fragile point-to-point feed that fails silently. The organisation wants reliable, monitored HL7 delivery into its EHR.

How we'd approach it

  • Document message types, segments and edge cases with both vendors
  • Build Mirth Connect channels with validation and transformation
  • Add alerting, retry queues and an audit trail for every message
  • Test with real-world samples, then cut over with a fallback

What you'd receive

Interface specificationMirth channelsMonitoring & alertsSupport runbook
Software developers reviewing code together at a laptop   B2B SaaS · Example

GitOps delivery overhaul

The situation

Releases are manual, infrequent and stressful. Environments drift, and only one engineer knows how production is set up.

How we'd approach it

  • Capture current infrastructure as code and remove manual drift
  • Introduce CI/CD with automated tests, scans and approvals
  • Move workloads to Kubernetes with GitOps deployment
  • Train the team and hand over documented golden paths

What you'd receive

IaC repositoriesCI/CD pipelinesGitOps setupTeam playbook
Abstract 3D AI letters representing artificial intelligence and generative AI   Fintech · Example

Real-time fraud scoring

The situation

A payments team wants to score transactions for fraud risk as they happen, with explainable decisions, without slowing checkout.

How we'd approach it

  • Assess data quality and agree success measures with the risk team
  • Build a feature pipeline and a low-latency model-serving service
  • Add monitoring for drift, latency and false-positive rates
  • Set up a controlled retraining and approval workflow

What you'd receive

Data pipelineModel-serving APIMonitoring dashboardsModel governance notes
Server racks and network cabling in a cloud data center   E-commerce · Example

Peak-season readiness

The situation

A storefront slows down or fails during promotions, and the cloud bill rises every month regardless of traffic.

How we'd approach it

  • Load-test to find the real bottlenecks before peak
  • Introduce autoscaling, caching and right-sized capacity
  • Define SLOs and alerting so issues surface before customers notice
  • Review spend and remove idle or oversized resources

What you'd receive

Load-test reportScaling configurationSLOs & dashboardsCost review
Padlock on a laptop keyboard representing cyber security and compliance   Enterprise software · Example

SOC 2 readiness programme

The situation

A software vendor keeps losing time to security questionnaires and needs to prepare for a SOC 2 audit alongside normal product work.

How we'd approach it

  • Gap assessment against the relevant Trust Services Criteria
  • Write right-sized policies and implement missing controls
  • Automate evidence collection on a GRC platform
  • Run a readiness review before the independent auditor arrives

What you'd receive

Gap assessmentPolicy setControl & evidence registerReadiness review
The pattern

The Method Behind Every Engagement

Different problems, same discipline. This is what keeps scope honest and results provable.

Measure first

We baseline the current state — performance, cost, risk or control coverage — before changing anything.

Secure by design

Security and compliance requirements are scoped into the plan, not retrofitted before an audit.

Everything as code

Infrastructure, pipelines and policies are version-controlled, reviewed and reproducible.

Operate & improve

Hand over cleanly, or stay on under a managed service to keep improving cost, reliability and risk.

What you keep

Deliverables you own, not a black box

Whatever the engagement, the output is something your team can understand, audit and run. We write for the engineer who inherits the system — and for the auditor who will ask how it works.

  • Architecture diagrams and decision records
  • Infrastructure-as-code and application repositories in your accounts
  • Runbooks for deployment, incidents and recovery
  • Compliance evidence mapped to the framework you are working towards
  • A handover session and agreed support options

Want to see how this maps to cost? Our engagement models explain fixed-scope projects, managed retainers and staff augmentation.

Talk through your scenario
Engineering team workspace with laptops and planning notes
FAQ

Frequently Asked Questions

No. They are anonymised, illustrative scenarios based on the kinds of problems we are asked to solve. We do not publish client names or results without permission, and we will not invent numbers. They show how we scope and deliver, not a specific client outcome.

Where a client has agreed to act as a reference, we can arrange an introduction after an initial conversation. Ask on your discovery call and tell us which industry or problem is most relevant to you.

We agree measurable success criteria up front — for example deployment frequency, recovery time, cloud spend, control coverage or interface error rates — take a baseline before changing anything, and report against those criteria through delivery.

Everything we build for you: infrastructure-as-code repositories, application code, architecture diagrams, runbooks and compliance evidence. IP is assigned to you under the contract, and we document handover so your team can run it without us.

It depends on scope. Assessments and readiness reviews are usually measured in weeks; migrations, platform builds and compliance programmes in months. You get a milestone plan with your proposal before anything starts.

Recognise one of these situations?

Tell us the problem — we'll suggest an approach, success criteria and a path to production.

Talk to an engineer