UK

United Kingdom · Technology and data · Principal/Manager (12-16 years)

Global Cloud Operations Assistant Manager

Here is the whole job, in plain words. What it is, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

See how AI is changing this job, and get the full read by email.

Start my free Automation Fluency module

As a Global Cloud Operations Assistant Manager, a good place to start on AIOps Strategy & Implementation is Planning Automation Across a Department, a free Future Fluency module at Level 5. You'd practise working out what in your department's work could be automated, what should not be, and what to recommend.

Free to start, no card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, the new skills it asks for, where it leads, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Your employer, or 'self-employed'

Leading a team? Try this with up to five of them for 14 days, free.

  • Experience bandPrincipal/Manager (12-16 years)
  • Direct reports10-25 reports
  • Reports toDirector, Global Cloud Operations
  • UK framework levelUsually someone running a function, or a director

Also advertised as Principal Cloud Engineer · Head of Cloud Operations · Cloud Infrastructure Lead (Manager)

Built on 43,079 real UK job descriptions we analysed · grounded in what real qualifications cover

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

EAL Level 2 Certificate In Engineering Technologies Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards
EAL Level 2 Diploma In Engineering Technologies Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards
EAL Level 2 Certificate in Engineering Operations (Knowledge) Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards
EAL Level 2 First Certificate in Engineering Technology Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards
EAL Level 2 Diploma in Engineering Operations (Knowledge) Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards
EAL Level 2 First Diploma in Engineering Technology Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 10 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Leading a team in Engineering EAL Level 2 Certificate In Engineering Technologies

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Data Fluency turning numbers into a decision
Automation Fluency building AI into how work runs
Sustainability Fluency building care for people and planet into the work
Systems Fluency seeing the whole picture

2AI and this work

Will AI change your work as a Global Cloud Operations Assistant Manager?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

  • AIOps Strategy & Implementation
  • Cloud Native Security Posture Management
Why each one is rising

The future skills this job leans on

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

What happens when you start

Next, a free account. We build your Global Cloud Operations Assistant Manager plan as you set up, starting with the free Automation Fluency module. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Ready to pay? Subscribe for £70 a month

Keep this read. One email with what AI is changing in this job, the new skills it asks for and where to start free. Nothing else follows unless you confirm your address.

3What this role really is

This job leads a team of cloud operations engineers and shapes how cloud infrastructure runs globally. It means owning the operational health of a business unit, managing budgets, and keeping systems stable, cost-effective and ready for growth. It suits someone who builds capable teams and resilient cloud platforms.

4What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Cloud Platforms (AWS, Azure, GCP) Strategic

Leading multi-cloud strategy, evaluating new cloud services for enterprise adoption, managing top-level billing and account structures. You'll be making decisions about which cloud services to use and how to best use them across your domain.

Monitoring & Observability (Datadog, Grafana, Splunk, ELK Stack) Architect

Defining the enterprise observability strategy for your domain, selecting and integrating platforms, and implementing AIOps for predictive monitoring. You'll ensure your team has the right tools to monitor and troubleshoot effectively.

Infrastructure as Code (Terraform, Ansible, GitLab CI, Jenkins) Strategic

Designing the enterprise IaC framework for your domain, including module registries, CI/CD integration, and policy-as-code (e.g., Sentinel, Open Policy Agent). You'll ensure our infrastructure is deployed consistently and securely.

Incident Management (PagerDuty, Opsgenie, Jira Service Management) Strategic

Owning the entire incident management process for your domain. This means managing on-call schedules and escalations at a global level, reporting on MTTA/MTTR to executive leadership, and driving continuous improvement in incident response.

Scripting & Automation (Python, Bash, Boto3/Azure SDK) Strategic

Driving the 'automate everything' vision within your team. Identifying major opportunities for operational efficiency through automation, and managing platforms like ServiceNow GRC for compliance automation. You'll ensure your team is building robust, scalable automation.

Executive & Planning (Anaplan, CloudHealth, Tableau Server, Power BI Premium) Expert

Managing cloud budgets and forecasting, presenting operational health metrics and strategic roadmaps to leadership. You'll use these tools to justify investments, track performance, and communicate effectively with senior stakeholders.

5What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing in Where you are nowThe step above
Cloud Architecture Changes Escalate all proposed changes to a Senior Engineer or Lead. Propose minor architectural changes within existing patterns; consult with Senior Engineers. Design and implement significant architectural changes within a workstream; inform Lead Engineer.
Budget Allocation (Cloud Spend) No authority; report any unexpected spend to supervisor. Identify cost-saving opportunities; propose changes to manager. Recommend budget optimisations for specific services (£5K-£10K impact); get manager approval.
Team Hiring & Performance No involvement beyond providing feedback on team culture. Participate in interview panels for junior roles; provide peer feedback. Interview candidates for junior and mid-level roles; mentor new hires.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Cloud Spend Variance
Keeping our cloud costs within the agreed forecast, identifying opportunities to save money without compromising service quality.
Target · Within 3% of the forecasted budget for your owned services.

If the Q3 budget for your services was £1.5M, you'd aim for actual spend between £1.455M and £1.545M. This means proactively rightsizing, managing reserved instances, and cleaning up orphaned resources.

P1 Incident Reduction
Reducing the number of critical, customer-impacting incidents that affect the services your team is responsible for.
Target · Decrease the number of P1 incidents by 20% year-on-year for your owned services.

If your services had 10 P1 incidents last year, we'd expect to see no more than 8 this year, showing real improvements in system resilience and proactive problem solving.

Team Performance & Development
The health and growth of your team, measured by retention and internal progression.
Target · Maintain a team attrition rate below 10% annually and promote at least two engineers within your team each year.

If you have a team of 15, you'd aim to lose no more than one person in a year, and you'd be actively working to get two of your engineers ready for their next career step, whether that's Senior Engineer or Lead.

Mean Time to Recovery (MTTR)
How quickly your team restores service after a critical incident, reflecting their efficiency and preparation.
Target · Reduce average MTTR for P1/P2 incidents by 15% year-on-year.

If the average time to get a P1 service back up was 60 minutes last year, you'd be pushing to get that down to 51 minutes this year through better runbooks, automation, and incident response training.

Strategic Influence & Collaboration
Your ability to shape the broader cloud strategy and work effectively with other departments.
  • You're regularly invited to high-level planning meetings with Product and Engineering leadership. Your input is actively sought when major architectural decisions are being made. Other teams see your group as a partner, not just a service desk. You're able to get buy-in for your team's initiatives, even when they require effort from others.
Operational Excellence Culture
Fostering a culture of continuous improvement, blameless post-mortems, and proactive problem-solving within your team.
  • Your team consistently conducts thorough, blameless post-mortems that lead to concrete action items. They're actively proposing and implementing automation to reduce 'toil'. There's a clear focus on root cause analysis rather than just quick fixes. They're sharing knowledge and best practices internally and, where appropriate, externally.
Talent Development & Mentorship
How effectively you're growing the skills and capabilities of your direct reports.
  • Your team members feel supported and challenged. They have clear development plans and are making measurable progress. You're regularly providing constructive feedback and creating opportunities for them to take on more responsibility. You're seen as a trusted advisor and mentor within the team and the wider organisation.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy
Building High-Performing Teams

You'll spend a good chunk of your week coaching, mentoring, and developing your direct reports. This means regular 1:1s, helping them navigate tricky technical problems, providing career guidance, and celebrating their successes. You'll also be involved in hiring and onboarding new talent, shaping the future of your team.

You'll be working with a junior engineer to help them understand the nuances of a complex incident, guiding them through the RCA process, and giving them the confidence to present their findings to a wider audience.

Strategic Impact & Ownership

You'll be defining the roadmap for your operational domain, deciding which automation projects get prioritised, how we approach cloud cost optimisation, and what our incident response strategy looks like. You'll own the operational health of a significant part of our cloud estate, and your decisions will have real, measurable impact on the business.

You'll be presenting a proposal to senior leadership on a new multi-cloud disaster recovery strategy, outlining the technical approach, the budget implications, and the expected improvements in RTO/RPO.

Solving Complex Organisational Challenges

This isn't just about technical problems; it's about people, processes, and politics. You'll be navigating trade-offs between cost and reliability, convincing different teams to adopt new operational standards, and figuring out how to scale our operations efficiently as the business grows. It's often messy, but deeply rewarding.

You'll be mediating a discussion between a Development team that wants to deploy a new service quickly and a Security team that has concerns about its compliance posture, finding a solution that balances both needs.

What frustrates people
  • The constant tension between cost-cutting pressure and the business's demand for higher uptime and performance.
  • Dealing with legacy systems and processes that are hard to change, even when everyone agrees they're inefficient.
  • The 'blame game' during incidents, where you have to prove the infrastructure is stable before other teams will look at their code.
  • Managing underperforming team members, which is never easy, but essential for team health.
  • The sheer volume of administrative tasks that come with managing a team (HR processes, budgeting, reporting).
What this role does not give you
  • A purely hands-on technical role; your time will be split between technical leadership, people management, and strategic planning.
  • A quiet, predictable 9-to-5 job; incidents don't care about your schedule, and strategic challenges are always evolving.
  • The chance to avoid difficult conversations; you'll need to provide tough feedback, negotiate with senior leaders, and sometimes deliver bad news.

8Who you work with

This role directly shapes our organisational strategy and capability within cloud operations. You'll be accountable for the operational health, cost efficiency, and resilience of a significant business unit, influencing how we build and run services across the entire company. Your decisions here genuinely impact our ability to deliver on customer promises and maintain our market position.

Inside the business
  • SVP of Engineering
  • Executive Peers (e.g., Head of Product, Head of Security)
  • Finance Leadership
  • Other Cloud Operations Managers
  • Engineering Leads across various product teams
Outside the business
  • Key Cloud Vendor Account Managers (AWS, Azure, GCP)
  • Third-party service providers (e.g., Datadog, PagerDuty)
  • Industry bodies and compliance auditors

9What you need before you start

Not a wish list. The things you would be expected to already have.

  • Proven experience (12-16 years) in cloud operations or site reliability engineering, with at least 5 years in a leadership or management role.
  • Demonstrable experience managing a team of 5+ engineers, including hiring, performance management, and career development.
  • A track record of successfully managing significant cloud budgets (e.g., £500K+) and driving cost optimisation initiatives.
  • Deep, hands-on experience with at least one major cloud provider (AWS, Azure, or GCP) at an expert level, and strong familiarity with another.
  • Extensive experience in designing, implementing, and managing Infrastructure as Code (IaC) frameworks at scale.
  • Proven ability to lead major incident response efforts, conduct blameless post-mortems, and drive continuous improvement in operational processes.
  • Strong understanding of SRE principles and their practical application in a production environment.

10What to practise next

Where the job is going, and what to do about it starting this week.

Serverless Architecture Governance

More services are moving to serverless, and while it simplifies some operational aspects, it introduces new challenges around cost management, observability, and cold starts. You'll need to define the operational best practices for serverless deployments.

Serverless Cost Optimisation · Distributed Tracing & Observability · Event-Driven Architecture Patterns

  • This quarter: Deep dive into serverless best practices from AWS Lambda, Azure Functions, or GCP Cloud Functions.
  • Next quarter: Work with a development team to define operational standards for their new serverless application.
  • Month 6: Evaluate a new serverless monitoring tool and present its benefits to your Director.
  • Month 9: Lead a project to automate serverless deployment and rollback procedures.

Quick win: Encourage your team to experiment with serverless for internal tooling. Review existing serverless applications for cost and performance bottlenecks.

Sustainability in Cloud Operations

As environmental concerns grow, optimising cloud carbon footprint will become a critical operational metric. This means making choices about regions, instance types, and architecture with sustainability in mind, and you'll be leading that charge.

Carbon Footprint Measurement · Green Cloud Architectures · Workload Optimisation for Sustainability

  • This quarter: Read up on cloud provider sustainability reports and initiatives.
  • Next quarter: Identify one service in your domain with high resource usage and propose a 'green' optimisation plan.
  • Month 6: Integrate sustainability metrics into your operational dashboards and reporting.
  • Month 9: Lead a cross-functional initiative to establish company-wide cloud sustainability goals.

Quick win: Start by identifying and decommissioning orphaned resources. Encourage your team to use the most energy-efficient instance types for new deployments.

11Staying current once you are in

What people here do to keep up
  • Regularly attending industry conferences (e.g., AWS re:Invent, Azure Summit, KubeCon) to stay abreast of the latest cloud technologies and operational best practices.
  • Participating in leadership development programmes or executive coaching to hone your management and strategic thinking skills.
  • Engaging with industry groups and communities (e.g., FinOps Foundation, SRE communities) to share knowledge and learn from peers.
  • Contributing to open-source projects or writing technical blogs/articles, demonstrating thought leadership in cloud operations.

12The rising capability

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

AIOps Strategy & Implementation

Manual incident response and monitoring are becoming unsustainable as systems grow more complex. AIOps tools can drastically reduce MTTR, predict outages, and cut down on alert fatigue, but they need a strategic leader to implement them effectively and integrate them into existing workflows.

  • Event Correlation & Anomaly Detection
  • Predictive Analytics for Outages
  • Automated Remediation Workflows
  • Natural Language Processing for Incident Summaries

Cloud Native Security Posture Management

Traditional security models don't cut it in dynamic cloud-native environments. As we move more towards serverless and containers, the attack surface changes, and operations managers need to lead the charge in securing these new paradigms, not just react to security incidents.

  • Zero Trust Architectures
  • Container & Serverless Security
  • Cloud Security Posture Management (CSPM)
  • Identity & Access Management (IAM) at Scale

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • ITIL Framework (Strategic Application)
  • SRE Principles (Defining & Enforcing)
  • Cloud Cost Management (FinOps Strategy)
  • Infrastructure as Code (IaC) Governance
  • Disaster Recovery (DR) Planning & Ownership
  • System Hardening & Security Posture (Strategic)

14The pathway

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Senior Cloud Operations Engineer / Staff Cloud Operations Engineer

    3-5 years in previous role

    Skills to master

    • Deep technical expertise in cloud platforms and IaC, leading complex projects, mentoring junior engineers, and taking ownership of critical workstreams. You'd need to show you can handle non-routine situations with sound judgment and influence technical decisions.

    You're ready to move on when

    • Consistently leading P1/P2 incident responses and driving post-mortem action items.
    • Designing and implementing significant automation or IaC solutions that improve operational efficiency.
    • Effectively mentoring 2-3 junior engineers and contributing to their growth.
    • Demonstrating strong communication skills, especially when presenting technical solutions to non-technical audiences.
  2. 2

    Technical Lead, Cloud Infrastructure

    4-6 years in previous role

    Skills to master

    • Architecting solutions across multiple workstreams, defining technical strategy for a domain, and providing technical leadership to a small team. You'd need to prove you can handle novel problems and ambiguous situations, making strategic trade-offs.

    You're ready to move on when

    • Successfully architecting and delivering complex, multi-team cloud projects.
    • Consistently defining and advocating for technical best practices across a domain.
    • Being the go-to person for complex technical challenges and providing clear direction to others.
    • Demonstrating strong influence skills with peer leads and senior stakeholders.
  3. 3

    Cloud Architect

    5-7 years in previous role

    Skills to master

    • Designing large-scale, resilient, and cost-effective cloud solutions from the ground up. This involves deep expertise across multiple cloud services, security, and networking, with a focus on strategic design rather than day-to-day operations. You'd need to show you can translate business requirements into robust technical architectures.

    You're ready to move on when

    • Successfully designing and gaining approval for major cloud infrastructure projects.
    • Deep expertise in cloud architecture patterns, security, and cost optimisation.
    • Ability to articulate complex architectural decisions to both technical and business audiences.
    • Experience with multi-cloud or hybrid-cloud environments.

15Where this role leads

The long view: This work can lead to VP of Infrastructure and Operations, Chief Technology Officer, or Head of Platform Engineering.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Global Cloud Operations Assistant Manager is actually changing.

Where it leads

Roles this leads to

Also named as a next step, with no page in the catalogue yet:

  • Principal Cloud Architect / Principal SRE (Individual Contributor Path)

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Leading a team in Engineering, worked against Global Cloud Operations Assistant Manager.

Leading a team in Engineering Level 2

Applied to your work in Global Cloud Operations Assistant Manager

The objective of this unit is to equip learners with an understanding of the roles, responsibilities, knowledge, and skills required to effectively lead a team in an engineering environment. Learners will explore how to manage team workloads, allocate tasks, and contribute to achieving team goals through effective leadership practices.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 6 Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

See Your Progress Grow Illustration
Global Cloud Operations Assistant Manager
  • ITIL Framework (Strategic Application)
  • SRE Principles (Defining & Enforcing)
  • Cloud Cost Management (FinOps Strategy)
  • Infrastructure as Code (IaC) Governance
  • Disaster Recovery (DR) Planning & Ownership
  • System Hardening & Security Posture (Strategic)
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

16The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Global Cloud Operations Assistant Manager is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Director, Global Cloud Operations (Level 6)

    3-5 years in current role

    From managing a department/function to shaping a business unit (multi-year transformation).

    • Enterprise-level Cloud Governance Defining and enforcing cloud policies across the entire organisation.
    • Vendor Relationship Management (Strategic) Managing relationships with top-tier cloud providers at an executive level.
    • Global Operations Management Overseeing cloud operations across different geographies and regulatory landscapes.

  2. Principal Cloud Architect / Principal SRE (Individual Contributor Path)

    3-5 years in current role

    From managing a team to acting as the highest technical authority and individual contributor.

    • Advanced Cloud Engineering Mastering cutting-edge cloud technologies and designing their implementation.
    • Complex System Optimisation Diagnosing and optimising performance bottlenecks in the most complex, high-scale systems.
    • Strategic Technical Roadmapping Defining the technical direction for major cloud initiatives for years to come.
Working with AI on the job

Working with AI

Where AI is starting to help

As a Global Cloud Operations Assistant Manager, your time is gold. You're juggling strategic planning, team development, budget oversight, and still getting pulled into incidents. Frankly, there's not enough time in the day. But what if you could offload some of the heavy lifting and empower your team to be even more efficient? That's where AI comes in.

We're not talking about robots taking over your job. We're talking about smart tools that amplify your team's capabilities and give you the insights you need faster. Imagine your team spending less time digging through logs and more time building resilient systems, or you getting a first-draft incident report in minutes instead of hours. This isn't future tech; it's happening now, and we want you to lead the charge.

Automated Root Cause Analysis

Imagine AI tools like Datadog Watchdog or Dynatrace Davis sifting through mountains of logs, metrics, and traces during an incident. Instead of your team spending hours manually correlating data, the AI instantly highlights the most probable root cause. This means faster resolution, less 'toil' for your engineers, and quicker service restoration for our customers. You'll get to focus on the strategic fix, not the initial detective work.

Predictive Anomaly Detection & Cost Optimisation

AI models can analyse performance trends and identify subtle anomalies – like a slow memory leak or creeping disk usage – that predict future outages before they even trigger a hard alert. For you, this means fewer P1 incidents to manage. On the FinOps side, AI can spot underutilised resources or inefficient spend patterns, giving you actionable insights to keep your cloud budget in check without manual auditing. It's about being proactive, not reactive.

IaC & Script Generation (for your team)

While you're leading strategy, your team can use AI copilots like GitHub Copilot or Amazon CodeWhisperer to generate boilerplate Terraform configurations, Ansible playbooks, or Python automation scripts. This dramatically speeds up development, reduces errors, and frees your engineers to tackle more complex, interesting problems. You'll set the standards, and AI will help your team meet them faster.

Incident Report & Post-mortem Drafting

After a major incident, the last thing anyone wants to do is write a lengthy report. With AI, you can feed an LLM the incident timeline, relevant Slack conversations, and technical logs. It can then generate a comprehensive first draft of both the customer-facing incident report and the internal blameless post-mortem. You and your team can then review, refine, and ensure accuracy, saving hours of painful documentation work per incident.

Common questions

Common questions

How do you become a Global Cloud Operations Assistant Manager?

Common routes in include Senior Cloud Operations Engineer / Staff Cloud Operations Engineer (3-5 years in previous role), Technical Lead, Cloud Infrastructure (4-6 years in previous role) and Cloud Architect (5-7 years in previous role). Times vary with prior experience.

Where can a Global Cloud Operations Assistant Manager progress to?

This role can lead on to Director, Global Cloud Operations (3-5 years in current role) and Principal Cloud Architect / Principal SRE (Individual Contributor Path) (3-5 years in current role), depending on the skills you build.

What new skills matter most for a Global Cloud Operations Assistant Manager?

Increasingly, AIOps Strategy & Implementation and Cloud Native Security Posture Management. These are the skills our record of this role lists as growing.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Read the Zavmo manifesto to understand how you will be taught Meet your tutors

Or try another one

17Where to go from here

Other roles at Level 6

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

 More jobs in technology and data

Stay in the field you know and move sideways rather than up.
If you leave this industry

The skills built in this role apply across technical sectors. Cloud operations expertise is in demand in SaaS companies, financial services, e-commerce, and any organisation that depends on cloud infrastructure. This can lead to a similar leadership role in a different industry, or a broader technology leadership position.

This role profile is © 2026 Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Start my free Automation Fluency module What happens next: a free account, then we build your plan as you set up. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.