About Towards The Cloud

We eliminate AWS complexity so you ship faster, spend less, and stay compliant.

Towards The Cloud is an AWS consultancy for B2B SaaS startups and scaleups. We bring a decade of hands-on AWS experience to teams that need senior engineering judgment without hiring a full platform team.

Every engagement starts with an assessment and the right fit, often a cost optimization or security review. When the issue is structural, we solve it at the root with a Landing Zone foundation you can rely on, not another patch on top of patches.

From there, we can maintain and operate your AWS infrastructure long-term, so your team focuses on shipping SaaS features instead of running infrastructure.

Danny Steenman, Founder & Cloud Engineer at Towards The Cloud

Danny Steenman

Founder & Cloud Engineer

Towards The Cloud

Our mission

Take AWS complexity off your team's plate, so they ship features.

For B2B SaaS startups and scaleups that need a production-grade AWS foundation, not a long agency contract. I build it once, maintain it continuously, and price it for the outcome, not the billable hours.

How this started

Why I built Towards The Cloud.

In 2013, while writing my research thesis, I stumbled into Cloud Computing and could not put it down. The shift from buying servers to renting them by the hour felt like cheating compared to the traditional hosting world I came from. That curiosity turned into a career.

Over the next decade, I worked my way up to Principal Cloud Consultant, leading large-scale AWS migrations and owning project lifecycles end to end. Across dozens of enterprises, I kept seeing the same pattern: architecture decisions that turned into expensive burdens, IAM policies layered with exceptions, AWS bills climbing faster than the products did, and engineering teams spending more time firefighting than shipping features.

In 2023, I founded Towards The Cloud to fix this differently. Not another audit firm, not another agency. A consultancy where one senior AWS engineer builds your foundation right the first time, then continuously maintains and evolves it, so your team can focus on shipping product instead of managing infrastructure.

Today I work with B2B SaaS startups and scaleups, including VC-backed teams, that need senior AWS judgment without the overhead of hiring a full platform team. The kind of teams that already know infrastructure matters, but cannot afford to grind their roadmap to a halt building governance from scratch.

What we stand for

Four principles behind every engagement.

These are not slogans. They are the operating defaults we fall back to when an engagement gets messy, scope changes, or a recommendation is uncomfortable.

One senior point of view

No junior handoffs and no account managers in the middle. You work directly with the engineer doing the work.

Outcomes over billable hours

Built right the first time, then maintained as your product grows. The model is priced for the foundation it produces, not for the hours it consumes.

Code over slides

Every engagement ships infrastructure as code, not a slide deck. You own and extend what we build.

Honest tradeoffs

If a service or pattern is wrong for your situation, we say so, even when it shrinks the scope of the engagement.

How it works

Assess, solve, and stay engaged for as long as you need.

Every engagement starts with an assessment of your current AWS foundation, then a fitting solution. Optional ongoing support keeps an AWS engineer embedded with your team, so the foundation stays secure and optimized as your product grows.

01

Assess the current AWS state

A direct review of your architecture, security, and cost shape. You leave with a clear picture of where the foundation needs work first.

02

Build the right fix

Implement the landing zone, remediation, or migration that the assessment surfaced. Shipped as infrastructure as code that you own end to end.

03

Stay engaged (optional)

Ongoing AWS engineering support that acts as an extension of your team for new platform work, reviews, and the next round of decisions.

First conversation

Book a Free Intro Call

In 30 minutes, we'll talk through your AWS environment and constraints, then recommend the right next step: an assessment, targeted remediation, or a deeper foundation conversation.

No commitment requiredRight next step recommended100% confidential