unthinkable
Case study · A German outsourcing firm · call centre matching platform

Businesses are matched with the right call centre on a platform that ships new services faster and costs less to run.

A German outsourcing firm that connects businesses with more than 400 call centres wanted to keep improving its platform for them without cloud costs growing out of control.

What changed

15%lower cloud bills (as reported)
25%faster release frequency (as reported)
35%lower CPU use (as reported)
What stood in the way

What stood in the way.

What stood in the way
  • Testers launched EC2 instances for each test and left them running, adding cost for nothing.
  • The platform was a monolith, which made it hard to scale and to update one part without touching the rest.
What changed
  • 15%lower cloud bills (as reported)
  • 25%faster release frequency (as reported)
  • 35%lower CPU use (as reported)
What we built

What we built.

  • A Terraform setup that creates EC2, IAM, CloudWatch alarms and Lambda functions when a tester starts a Jenkins job.
  • A Lambda function that deletes an instance and its resources once logs, CPU and memory show it is idle.
  • The monolith containerised with Docker and run on Kubernetes through AWS EKS, Fargate and ECR, managed by Terraform.
  • Terraform
  • AWS Lambda
  • Jenkins
  • Docker
  • Kubernetes
  • AWS EKS
  • AWS Fargate
  • CloudWatch
What it shows

What this work shows about us.

Cost removed by design

Test environments exist only while someone is using them, so no one has to remember to switch them off.

Change one service, not the whole app

Microservices let the team update and release parts of the platform without touching the rest.

Want to cut your cloud bills with self-removing test environments? Tell us what you want to change. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with the right team.

Start your plan ↗
If we built it today

If we built it today, with AI.

This work came before today's AI. If the German outsourcing marketplace asked us now, this is what we would add, step by step.

Testing a change

An agent would start the right test environment for a change, run the tests and report back to the developer, then shut it down. Engineers still decide what ships.

Watching the bill

An agent would flag a resource that has been idle or oversized for days and propose removing it, for the team to approve.

Related

Where this work fits.

Facts and figures from the project records; nothing added.

Ask Unthinkable

Want this for your business?

Tell us what you run or what you're building. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with a senior AI engineer.

Send us a note instead

Required

Thanks. A senior AI engineer will reply to you.
u
Ask UnthinkableClarity first, then the right team
Your conversation

An AI agent. This prototype uses prepared answers and sends nothing.