DTL Solutions Page

Solutions overview · /solutions · built section by section

Solutions page

Same header, lead form and footer as the homepage. Solutions is marked as the current menu item and “All solutions” in the Solutions panel now lands here. Pick a hero in the bar below (six options), then options for sections 2 to 7 further down. All seven sections are now built. Section 3 has a remark: it isn’t needed if hero F or section 2 F is picked. The eight solution pages come after this overview.

Proposed page structure (tell me what to add, drop or reorder)

This page · /solutions

  1. Hero
  2. The eight services, grouped Build · Run · Spend
  3. Where to start: pick your problem, get the service
  4. How an engagement runs: Assess → Plan → Deliver → Run
  5. Clouds and credentials (AWS, Azure, Google Cloud)
  6. Proof: numbers and client stories
  7. FAQ
  8. Lead form + footer (from the homepage)

Then one page per service · /solutions/<slug>

  1. Cloud migration
  2. Managed cloud services
  3. Cloud cost optimisation (FinOps)
  4. Resource augmentation
  5. DevOps & CI/CD automation
  6. Generative AI & data
  7. Cloud security & compliance (its 12 sub-pages are phase 2, not in the menu)
  8. Backup & disaster recovery

Held back as on the other pages: no “24/7” or “SLA” wording until confirmed. Numbers used are the homepage proof numbers you supplied.

Section 1 · Hero pick one · A is my suggestion

Talk to an engineer
Section 2 · The eight services pick one · A is my suggestion

The eight services

From the first move to the monthly bill.

Grouped the way the work happens: build it, run it, then keep the spend in check. Start with one service or hand us all eight. The same engineers stay with you either way.

Help me choose
Section 3 · Where to start pick one · A is my suggestion

Remark If the team picks hero option F (Problem picker) and/or section 2 option F (Service explorer), this section repeats them and isn’t needed. Drop it and the page goes straight from the eight services to how an engagement runs.

Where to start

Not sure which service? Start with what’s going wrong.

Most teams come to us with a problem, not a service name. Pick the one that sounds like you and see where we’d start and what you’d get first.

Tell us your problem
Section 4 · How an engagement runs pick one · A is my suggestion

How an engagement runs

Four steps. No surprises in any of them.

Every service follows the same path: we look first, agree the plan in writing, do the work in small steps, then stay on or hand over. You always keep your accounts, your access and the runbooks.

Start with step one
  • Your accountsEverything runs in cloud accounts you own.
  • Your accessWe work with named, logged access you can remove.
  • Your runbooksWritten down as we go and handed to you.
Section 5 · Clouds and credentials pick one · A is my suggestion

Badge rules Each partner badge is shown as supplied, on a white well, never recoloured or cropped. AWS allows one AWS badge per page, so every option shows the AWS Advanced Tier badge once (the header’s Partner Ecosystem panel also shows it when opened, as on the other pages). Your project files also include AWS SMB Competency, AWS Generative AI Competency, Microsoft Infrastructure (Azure) and AI Business Solutions badges. Tell me which DTL currently holds and I’ll add them as text.

Clouds and credentials

AWS, Azure or Google Cloud. Certified on all three.

We don’t push one cloud. We work where your workloads already are, or recommend the best fit and explain why. The same eight services, run by engineers certified on each platform.

Ask which cloud fits
Section 6 · Proof pick one · A is my suggestion

Sample content The five team numbers are the homepage proof numbers you supplied. All eight client stories are dummy samples, one per service, tagged “Sample”, the same way as the homepage. Replace them only with verified figures and the client’s written consent, then remove the tags.

Proof

Less talk. More proof.

The numbers behind the team, and what changed for a few clients. Ask and we’ll introduce you to one in your industry, with their consent.

Ask for a reference

Stories marked “Sample” show the format only. Real client stories replace them before launch.

Section 7 · FAQ pick one · A is my suggestion

Answers Every answer reuses what the page already says in sections 1–6, nothing new. Your team should confirm three: whether the full assessment is charged, the contract terms (“month by month”), and multi-cloud / hybrid. The page also carries FAQPage structured data for Google.

FAQ

Questions teams ask before they call us.

Straight answers on where to start, what it costs, who owns what, and how we work with your team.

Ask your own question