Next platform deadline: Amazon EKS Nov 26, 2026  

All 14 deadlines

Engagement examples

What a typical engagement looks like.

Illustrative situations, scopes, durations and outputs for common requests. They show how we would approach the work; they are not client stories and name no clients.

Illustrative engagement. Describes the typical situation, scope and output of this kind of work. It is not a client story and names no client.

Data & Databases

4 example engagements

Data & Databases services

Illustrative · Data & Databases

PostgreSQL fleet upgrade before Extended Support charges

Typical situation

A software company runs a few dozen Amazon RDS for PostgreSQL 13 and 14 instances. Standard support for 14 ends Feb 28, 2027 and Extended Support is billed per vCPU-hour after that.

Typical scope

  • Inventory of every instance, version, extension and parameter group
  • Extension and driver compatibility testing against the target version
  • Blue/green deployment rehearsal with measured switchover time
  • Wave plan grouped by risk and business window
Typical duration
Assessment 1–2 weeks; upgrade waves 4–8 weeks
Typical team
1 senior data engineer, plus your application owners for testing
Entry point
Upgrade readiness review (fixed fee)

What you hold at the end

  • Readiness report with a risk register
  • Tested runbook per wave, with rollback
  • Upgraded instances and a cost comparison before and after

Database Upgrades & End-of-Support

Illustrative · Data & Databases

Cassandra 3.11 and MongoDB 6.0 off end-of-life versions

Typical situation

A platform team still runs Cassandra 3.11 (end of life since Sep 2024) and MongoDB 6.0 (end of life since Jul 2025) behind customer-facing services.

Typical scope

  • Cluster health check: compaction, tombstones, repair, driver versions
  • Upgrade path without skipping majors (3.11 to 4.0 to 4.1; 6.0 to 7.0 to 8.0)
  • Rolling upgrade rehearsal in a production-like environment
  • Backup and restore proof before the first node is touched
Typical duration
Health check 1–2 weeks; rolling upgrades 3–6 weeks
Typical team
1 senior NoSQL engineer
Entry point
NoSQL health check & upgrade plan (fixed fee)

What you hold at the end

  • Health-check report with prioritized fixes
  • Rolling upgrade runbooks
  • Restore test evidence

NoSQL Engineering

Illustrative · Data & Databases

Redis to Valkey on ElastiCache

Typical situation

An engineering team pays for self-managed Redis and ElastiCache for Redis and wants to know whether Valkey is a safe, cheaper drop-in after the Redis licence change.

Typical scope

  • Command and module compatibility scan
  • Client library review and connection settings
  • Cost model: current spend against ElastiCache for Valkey rates
  • Cut-over plan with a dual-write or snapshot path
Typical duration
Review 1 week; migration 2–4 weeks
Typical team
1 senior data engineer
Entry point
Caching review & migration plan (fixed fee)

What you hold at the end

  • Compatibility and cost report
  • Migration runbook with rollback
  • Updated Terraform for the new clusters

Redis, Valkey & Caching

Illustrative · Data & Databases

WebLogic 12.2.1.4 to 14.1.2 before Premier Support ends

Typical situation

An enterprise runs line-of-business applications on WebLogic 12.2.1.4, whose Premier Support ends in December 2026, with a JDK 8 dependency.

Typical scope

  • Domain, application and JDK inventory
  • Deprecated API and library scan
  • Upgrade of one non-production domain as a proof
  • Wave plan for remaining domains
Typical duration
Review 1–2 weeks; upgrade sprint 4–10 weeks
Typical team
1 senior middleware engineer
Entry point
WebLogic readiness review (fixed fee)

What you hold at the end

  • Upgrade readiness report
  • Rebuilt domain scripts (WLST or WDT)
  • Cut-over and rollback runbook

Oracle & Middleware Modernization

Data Engineering & Analytics

3 example engagements

Data Engineering & Analytics services

Illustrative · Data Engineering & Analytics

Teradata warehouse to a lakehouse before a hardware refresh

Typical situation

An enterprise analytics team runs a Teradata warehouse with BTEQ scripts and nightly ETL feeding finance and operations reports. A hardware refresh is due and leadership wants a cloud option costed before signing.

Typical scope

  • Inventory of tables, BTEQ scripts, macros, ETL jobs and report consumers, with unused objects marked
  • Target choice between Snowflake and Databricks on the actual query mix
  • Pilot conversion of the most complex subject area with tooling plus engineer review
  • Reconciliation approach and wave plan by subject area
Typical duration
Readiness sprint 3–4 weeks; migration waves per subject area
Typical team
1 senior data engineer and 1 analytics engineer, plus your report owners for sign-off
Entry point
Migration readiness sprint (fixed fee)

What you hold at the end

  • Inventory and retirement list
  • Target architecture and wave plan with a fixed quote
  • Pilot conversion with a reconciliation report

Warehouse to Lakehouse Migration

Illustrative · Data Engineering & Analytics

Snowflake spend review after the bill doubled

Typical situation

A software company's Snowflake bill grew much faster than its data and users. Warehouses were shared across teams, auto-suspend settings varied and dbt models rebuilt full tables every hour.

Typical scope

  • Credits attributed to warehouses, teams and dbt models from account usage views
  • Warehouse sizes, multi-cluster settings and auto-suspend reviewed against real query load
  • The most expensive models moved to incremental builds and tested
  • Resource monitors, budgets and tags defined as code
Typical duration
Health check 1–2 weeks; optimization sprint 3–4 weeks
Typical team
1 senior data engineer
Entry point
Data platform cost health check (fixed fee)

What you hold at the end

  • Spend breakdown by team and workload
  • Savings register with each change and its measured effect
  • Guardrails as code and a monthly cost view

Snowflake & Databricks Cost Optimization

Illustrative · Data Engineering & Analytics

Change data capture from PostgreSQL and SQL Server into the lakehouse

Typical situation

An operations team relied on nightly full extracts from PostgreSQL and SQL Server. Reports were a day late and the extracts slowed the production databases.

Typical scope

  • Latency needs agreed per table: seconds, minutes or daily
  • Debezium connectors on Kafka with a schema registry and an initial snapshot plan
  • Bronze to silver merge in the lakehouse with deduplication and ordering
  • Lag, throughput and row-count reconciliation dashboards
Typical duration
Architecture review 2 weeks; build 4–6 weeks
Typical team
1 senior data engineer, plus your database owners
Entry point
Streaming architecture review (fixed fee)

What you hold at the end

  • Streaming architecture and decision records
  • CDC pipelines as code with monitoring
  • Reconciliation and replay runbooks

Real-time Streaming & CDC

Cloud & Platform Engineering

3 example engagements

Cloud & Platform Engineering services

Illustrative · Cloud & Platform Engineering

EKS clusters out of extended support

Typical situation

A company runs several EKS clusters on 1.31 and 1.32. Extended support costs more per cluster-hour and 1.31 extended support ends Nov 26, 2026, after which clusters are auto-upgraded.

Typical scope

  • Deprecated API scan across manifests and Helm charts
  • Add-on, CNI and ingress compatibility matrix
  • Blue/green node group strategy and control-plane upgrade rehearsal
  • GitOps changes so the next upgrade is routine
Typical duration
Readiness review 1 week; upgrades 2–6 weeks
Typical team
1 senior platform engineer
Entry point
Cluster upgrade readiness review (fixed fee)

What you hold at the end

  • Cluster inventory with support dates
  • Upgrade runbooks and rehearsal results
  • Pull requests in your repositories

Kubernetes & Platform Engineering

Illustrative · Cloud & Platform Engineering

VMware exit portfolio assessment

Typical situation

An infrastructure team faces a VMware renewal at a much higher cost and needs a defensible plan before the contract date.

Typical scope

  • Portfolio discovery from vCenter exports
  • Disposition per workload: rehost, replatform, refactor, retire or retain
  • Run-cost model for AWS, Azure, Google Cloud or OCI targets
  • Wave plan with dependencies and risks
Typical duration
3–5 weeks
Typical team
1–2 senior cloud engineers
Entry point
Migration assessment (fixed fee)

What you hold at the end

  • Portfolio assessment and business case inputs
  • Target landing zone outline
  • Migration wave plan

Cloud Migration & VMware Exit

Illustrative · Cloud & Platform Engineering

Cloud cost review for a multi-account estate

Typical situation

Finance asks engineering to explain a cloud bill that grew faster than revenue, including new AI and database spend.

Typical scope

  • Billing export and tagging analysis
  • Rightsizing, commitments and storage tiering opportunities
  • Database and AI inference cost drivers
  • Budget alerts and a monthly review cadence
Typical duration
2–3 weeks
Typical team
1 senior cloud engineer
Entry point
Cloud cost review (fixed fee)

What you hold at the end

  • Savings register with effort and risk per item
  • Tagging policy and dashboards
  • Quick wins implemented where agreed

FinOps & Cost Optimization

AI & Automation

2 example engagements

AI & Automation services

Illustrative · AI & Automation

RAG assistant from pilot to production

Typical situation

A team built a promising internal assistant over policy documents, but answers are inconsistent, permissions are not enforced and nobody can say whether it is good enough to launch.

Typical scope

  • Evaluation set built with your subject-matter experts
  • Chunking, hybrid search and re-ranking experiments, measured
  • Permission-aware retrieval tied to your identity provider
  • Guardrails, tracing and cost limits
Typical duration
Readiness assessment 2 weeks; hardening 4–8 weeks
Typical team
1 senior AI engineer, plus a data engineer when needed
Entry point
RAG readiness assessment (fixed fee)

What you hold at the end

  • Evaluation report with baseline and target scores
  • Production architecture and runbook
  • Code and evaluation suite in your repository

RAG & Knowledge Assistants

Illustrative · AI & Automation

An operations agent with human approval

Typical situation

An operations team wants an agent that triages tickets and runs routine runbooks, but security will not allow unsupervised write access.

Typical scope

  • Use-case and risk workshop
  • Scoped tools (for example through MCP) with least-privilege credentials
  • Human approval step for every change
  • Audit log and evaluation of agent decisions
Typical duration
Design sprint 2–3 weeks; build 4–6 weeks
Typical team
1 senior AI engineer
Entry point
Agent design sprint (fixed fee)

What you hold at the end

  • Agent design and threat model
  • Working agent in a sandbox, then production
  • Approval and audit trail your security team can review

AI Agents & Agentic Workflows

Recognize one of these?

Tell us what you run. On the free 30-minute review we will say how your situation differs and what a fixed-fee first step would cost.