UK

United Kingdom · Technology and data · Senior (5-8 years)

Senior Enterprise Architect

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 Senior Enterprise Architect, a good place to start on Prompt Engineering & LLM Integration 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 bandSenior (5-8 years)
  • Direct reportsNo direct reports
  • Reports toLead Enterprise Architect
  • UK framework levelUsually a manager, or the deepest specialist in a team

Also advertised as Senior Solution Architect · Lead Technical Architect · Domain Architect

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

Pearson BTEC Level 5 Higher National Diploma in Cloud Computing Pearson Education Ltd · Level 5 · covers 2 of 4 standards
NCFE Level 5 Diploma: Cloud Systems and Secure Networking NCFE · Level 5 · covers 1 of 4 standards
Qualifi Level 5 Extended Diploma in Cyber Security Qualifi Ltd · Level 5 · covers 1 of 4 standards
ATHE Level 5 Extended Diploma in Computing ATHE Ltd · Level 5 · covers 1 of 4 standards
NOCN Level 5 Diploma in Electronic and Communications Engineering NOCN · Level 5 · covers 1 of 4 standards
Qualifi Level 5 Diploma in Cyber Security Qualifi Ltd · Level 5 · covers 1 of 4 standards

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

The units you would start with

Cloud Architecture Design Pearson BTEC Level 5 Higher National Diploma in Cloud Computing
Cloud networking protocols, services and topologies NCFE Level 5 Diploma: Cloud Systems and Secure Networking
Security Strategy: Laws, Policies and Implementation Qualifi Level 5 Extended Diploma in Cyber Security
Cloud Native Solutions ATHE Level 5 Extended Diploma in Computing
Cloud Computing NOCN Level 5 Diploma in Electronic and Communications Engineering
Strategic Leadership Qualifi Level 5 Diploma in Cyber Security

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Data Fluency turning numbers into a decision
AI Governance Fluency using AI responsibly
Sustainability Fluency building care for people and planet into the work
Systems Fluency seeing the whole picture
Your Plan Illustration

Built for Senior Enterprise Architect

6 units that map to this job, from the qualifications that cover it.

  1. Cloud Architecture Design Pearson Education Ltd · covers 2 of 4 standards Level 5
  2. Cloud networking protocols, services and topologies NCFE · covers 1 of 4 standards Level 5
  3. Security Strategy: Laws, Policies and Implementation Qualifi Ltd · covers 1 of 4 standards Level 5
  4. Cloud Native Solutions ATHE Ltd · covers 1 of 4 standards Level 5
  5. Cloud Computing NOCN · covers 1 of 4 standards Level 5
  6. Strategic Leadership Qualifi Ltd · covers 1 of 4 standards Level 5
These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

2AI and this work

Will AI change your work as a Senior Enterprise Architect?

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

  • Prompt Engineering & LLM Integration
  • Sustainable Architecture Design
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 Senior Enterprise Architect 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

A senior enterprise architect designs how systems fit together across a part of the business and makes sure they get built properly. This means planning a significant chunk of the technology, checking everything works together, and following those plans through to delivery.

4What you'd actually use

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

Architecture Modeling (ArchiMate via Sparx EA, Archi, or similar) Advanced

Designing complex, multi-layer ArchiMate models from scratch for specific domains or workstreams. You'll also be mentoring others on modeling standards and best practices, ensuring consistency across the team.

Cloud Platforms (AWS, Azure, or GCP - deep expertise in at least one) Expert

Designing complex, multi-account/subscription architectures using advanced services (e.g., AWS Control Tower, Azure Landing Zones). You'll apply the Well-Architected Framework principles to ensure our cloud solutions are robust, secure, and cost-effective.

Enterprise Portfolio Management (LeanIX, ServiceNow APM, or Planview) Advanced

Actively using the tool to conduct application rationalisation analysis, identify technology redundancies, and create technology roadmaps. You'll model future-state scenarios and use the platform to inform your architectural decisions.

Collaboration & Diagramming (Miro, Lucidchart, Confluence) Expert

Facilitating complex design workshops using these tools, creating and maintaining the canonical architecture diagrams in Confluence. You'll be the one making sure everyone's on the same page visually and that our documentation is up-to-date and easy to understand.

API Management & Integration (MuleSoft Anypoint, Apigee, or Kong) Advanced

Designing the API strategy for a business domain, defining API contracts, and promoting API re-use across different systems. You'll ensure our systems can talk to each other effectively and securely.

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
Technology Selection (within domain) Proposes options, needs full approval from Senior Architect. Recommends and justifies, needs approval from Lead Architect. Makes and justifies decisions, informs Lead Architect of choice. Consults Lead for enterprise-wide impact.
Architectural Design (for a workstream) Designs components under direct supervision. Designs end-to-end for a single project, reviewed by Senior Architect. Leads design for complex workstreams/domain, presents to ARB, makes final technical decisions within scope.
Budget Allocation (for tools/training) Requests budget, no authority. Proposes small budget items (up to £2K), needs manager approval. Recommends and can approve up to £10K for domain-specific tools/training. Consults Lead Architect for larger amounts (up to £50K).
Technical Debt Prioritisation Identifies and reports technical debt. Proposes solutions for specific tech debt items. Identifies, proposes solutions, and influences prioritisation of significant technical debt within their domain, working with engineering leads.

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.

Component Reusability
Number of reusable services or components designed and adopted by other teams.
Target · Deliver ≥3 reusable services/components per year that are adopted by other teams.

You design a new customer authentication service that's then used by the mobile app, web portal, and partner API, counting as one reusable component.

Architectural Design Approval Rate
Percentage of architecture designs that pass the Architecture Review Board (ARB) on the first or second submission.
Target · Achieve 90% or higher first/second pass rate.

Out of 10 designs submitted to ARB in a quarter, 9 were approved within two rounds of feedback, meaning a 90% rate.

Technical Debt Reduction Contribution
Measurable reduction in technical debt within your domain, as identified by code quality tools or specific refactoring efforts.
Target · Contribute to a 10-15% reduction in critical technical debt identified within your domain annually.

Your refactoring design for the legacy order processing system reduces its cyclomatic complexity score by 12% and eliminates 5 high-severity code smells.

Time-to-Market Impact (Architectural Patterns)
Reduction in average project startup time for new initiatives that use your architectural patterns or reference architectures.
Target · Architectural patterns introduced reduce average project startup time by 15% within your domain.

Teams using your new microservice pattern for building customer-facing features report a 20% faster initial setup compared to previous projects.

Stakeholder Buy-in & Influence
How effectively you gain consensus and adoption for your architectural vision across different teams and leadership levels.
  • You're proactively invited to early-stage product planning meetings. Engineering leads seek your advice before starting new projects. Your architectural recommendations are consistently adopted without significant pushback. People actually use your reference architectures, not just pay lip service.
Mentorship Effectiveness
The growth and development of junior architects or senior developers you mentor.
  • At least one L1/L2 mentee is promoted or takes on significantly more architectural responsibility within 18 months. Mentees actively seek your guidance and provide positive feedback on your support. They're able to independently tackle more complex design challenges after working with you.
Architectural Documentation Quality & Accessibility
The clarity, completeness, and ease of understanding of your architectural artefacts.
  • New team members can quickly understand system designs from your documentation. Developers consistently refer to your diagrams and ADRs. Your documentation is regularly updated and accurately reflects the current state of systems. It's not just for the ARB
  • it's genuinely useful for everyone.
Proactive Problem Identification
Your ability to spot potential architectural issues, technical debt, or integration challenges before they become major problems.
  • You flag potential scaling issues during design reviews that prevent production outages months later. You identify integration conflicts between two new systems early on, saving weeks of rework. You're seen as someone who thinks several steps ahead, not just reacting to immediate needs.

7Would you like it

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

What people enjoy
Solving Big, Complex Puzzles

You love taking a messy, intertwined business problem and breaking it down into a clean, logical architectural solution. The bigger the tangle, the more excited you get.

When a new regulatory requirement comes in that impacts five different systems, your first thought isn't 'oh no,' but 'how can I design a single, elegant solution that handles this across the board?'

Long-Term Impact & Vision

You're not just interested in shipping the next feature; you want to build something lasting, something that will serve the company well for years to come. You get satisfaction from seeing your strategic decisions play out over time.

You're proudest when a system you designed two years ago is still performing robustly and easily adapting to new requirements, proving the foresight in your initial architectural choices.

Mentoring & Guiding Others

You enjoy helping junior team members understand complex architectural concepts, reviewing their designs, and helping them grow. You get a kick out of seeing others improve under your guidance.

Spending an hour walking a new solution architect through the nuances of our cloud security patterns, seeing the lightbulb moment, and knowing they'll build better systems because of it.

What frustrates people
  • Architectural designs being ignored or significantly altered during implementation without consultation.
  • Lack of budget or resources to address critical technical debt you've identified.
  • Business units making technology decisions without involving IT or architecture.
  • The perception that architecture is a bottleneck, not an enabler.
  • Having to repeatedly justify the value of strategic architectural work over immediate feature delivery.
What this role does not give you
  • A purely hands-on coding role—you'll be designing, not typically building the final product.
  • Complete autonomy without needing buy-in from multiple stakeholders.
  • A predictable, unchanging set of priorities—things shift, and you need to adapt.
  • Instant gratification for your efforts—architectural impact often takes time to materialise.

8Who you work with

Your designs directly influence the efficiency, cost, and agility of our core business operations within your domain. Get it right, and we deliver features faster and more reliably. Get it wrong, and we're stuck with expensive, hard-to-change systems that slow us down and frustrate everyone, from customers to developers.

Inside the business
  • Product Managers (to understand what needs building)
  • Engineering Leads (to make sure designs are buildable)
  • Security Team (to ensure everything's safe)
  • Infrastructure Team (to make sure it'll run smoothly)
  • Business Unit Heads (to get their buy-in and understand their problems)
  • Other Senior Architects (for peer review and alignment)
Outside the business
  • Key Vendors (for understanding product roadmaps and capabilities)
  • Industry Peers (for learning best practices and trends)

9What you need before you start

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

  • Proven experience (5+ years) in a technical role, ideally as a Solution Architect, Lead Developer, or similar, where you've been responsible for end-to-end system design.
  • A solid understanding of software development lifecycles and agile methodologies (Scrum, Kanban).
  • Demonstrable experience with at least one major cloud provider (AWS, Azure, or GCP) at an advanced level.
  • Experience presenting complex technical topics to both technical and non-technical audiences.
  • A track record of successfully delivering complex technical projects or workstreams.
  • Experience mentoring or guiding junior team members in technical design.

10What to practise next

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

Advanced Observability & AIOps

As our systems become more distributed and complex (think microservices, serverless, event-driven), traditional monitoring isn't enough. We need architects who can design for deep observability and use AI to predict and prevent outages, not just react to them. This is about proactive system health.

Distributed tracing (e.g., OpenTelemetry) · Log aggregation and analysis (e.g., ELK stack, Splunk) · Metric collection and correlation · Predictive analytics for system health · Automated incident response via AIOps platforms

  • This quarter: Take an online course on OpenTelemetry or a similar distributed tracing framework.
  • Next quarter: Design an observability strategy for a new microservice or system within your domain.
  • Month 4-6: Work with the SRE/Operations team to implement an AIOps feature for a critical system.
  • Month 7-9: Present a case study on how improved observability led to a reduction in mean-time-to-resolution (MTTR) for incidents.

Quick win: Ensure every new service you design has comprehensive logging, metrics, and tracing built in from day one. It's easier to add it upfront than to retrofit later.

Data Mesh & Data Product Design

The traditional centralised data warehouse/lake is struggling to keep up with the pace of business. Data Mesh is an emerging paradigm that treats data as a product, owned by domain teams. Architects need to understand how to design for this decentralised, domain-oriented approach.

Domain-oriented data ownership · Data as a product principles · Self-serve data platform · Federated computational governance · Data observability and quality

  • This month: Read 'Data Mesh: Delivering Data-Driven Value at Scale' by Zhamak Dehghani.
  • Next quarter: Identify a suitable business domain for a pilot Data Product initiative.
  • Month 4-6: Design the architecture for a 'data product' within your domain, including its interfaces and governance.
  • Month 7-9: Work with a domain team to implement and launch their first data product, learning from the practical challenges.

Quick win: Start by thinking about the 'users' of your data. What data do they need? How do they want to consume it? This user-centric view is fundamental to data product thinking.

11Staying current once you are in

What people here do to keep up
  • Regularly attending industry conferences and webinars (e.g., Gartner IT Symposium, AWS re:Invent, Microsoft Build, Google Cloud Next).
  • Contributing to open-source projects or maintaining a technical blog where you share your architectural insights.
  • Participating in online learning platforms (e.g., Coursera, Udemy, Pluralsight) to stay current with emerging technologies and patterns.
  • Engaging in peer-to-peer learning within our internal architecture community, sharing knowledge and challenging ideas.
  • Mentoring junior colleagues or participating in internal tech talks and workshops.

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.

Prompt Engineering & LLM Integration

Honestly, competitors are already using tools like GPT to draft reports in 10 minutes that used to take 2 hours. Architects who figure this out will outproduce their peers significantly. It's not just a nice-to-have; it's becoming a productivity superpower.

  • Context windows and token limits
  • Temperature settings for different tasks
  • RAG (Retrieval Augmented Generation) architectures
  • Output validation and hallucination detection
  • Prompt chaining for complex analysis

Sustainable Architecture Design

With increasing focus on ESG (Environmental, Social, Governance) and rising energy costs, designing 'green' software isn't just a buzzword; it's becoming a business imperative. Architects will be expected to factor environmental impact into their designs.

  • Carbon footprint of cloud services
  • Energy-efficient coding practices
  • Hardware lifecycle management
  • Green software principles
  • Measuring and reporting sustainability metrics

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • TOGAF (The Open Group Architecture Framework)
  • Business Capability Modeling
  • Application Portfolio Management (APM)
  • Domain-Driven Design (DDD)
  • Technology Roadmapping

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 Software Engineer / Lead Developer

    5-7 years of engineering experience, then 1-2 years focused on solution design.

    Skills to master

    • Moving from 'how to build' to 'what to build and why', understanding non-functional requirements, stakeholder communication, and system-level thinking beyond individual components.

    You're ready to move on when

    • You're already being asked to design significant features or small systems end-to-end.
    • You find yourself thinking about the wider system impact of your code, not just your immediate task.
    • You enjoy mentoring junior developers on design patterns and best practices.
    • You're comfortable presenting technical designs to non-technical audiences.
  2. 2

    Solution Architect

    3-5 years as a Solution Architect.

    Skills to master

    • Deepening your understanding of enterprise-level concerns (governance, portfolio management), influencing without direct authority, and managing architectural debt across multiple systems.

    You're ready to move on when

    • You're consistently delivering complex solution designs for single projects.
    • You're starting to identify patterns and opportunities for reuse across projects.
    • You're comfortable engaging with senior business stakeholders to understand their needs.
    • You actively contribute to architectural standards and guidelines.
  3. 3

    Technical Consultant (with architecture focus)

    5-8 years in technical consulting roles, with a strong emphasis on system design.

    Skills to master

    • Internalising company-specific context and politics, building long-term relationships, and transitioning from project-based delivery to continuous architectural evolution.

    You're ready to move on when

    • You've led architectural engagements for multiple clients, often dealing with complex integration challenges.
    • You're adept at translating business requirements into technical solutions.
    • You're comfortable presenting to C-level executives and managing client expectations.
    • You're looking for a role where you can have a sustained impact on a single organisation's technology landscape.

15Where this role leads

The long view: This work can lead to running the whole enterprise architecture function as a director. It can also lead to becoming a chief architect who sets technology vision for the business, or moving into a CTO role with responsibility for the whole of technology.

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 Senior Enterprise Architect is actually changing.

Where it leads

Roles this leads to

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

  • Principal Enterprise Architect

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 Cloud Architecture Design, worked against Senior Enterprise Architect.

Cloud Architecture Design Level 5

Applied to your work in Senior Enterprise Architect

The objective of this unit is to enable learners to produce a cloud feasibility assessment for a small-to-medium sized organisation, and use architectural design principles to design and implement an infrastructure solution. Learners will also analyse metric monitoring and alert systems to baseline the health of a cloud environment.

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
Senior Enterprise Architect
  • TOGAF (The Open Group Architecture Framework)
  • Business Capability Modeling
  • Application Portfolio Management (APM)
  • Domain-Driven Design (DDD)
  • Technology Roadmapping
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

Senior Enterprise Architect is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Lead Enterprise Architect

    2-4 years in the Senior Enterprise Architect role.

    L4

    • Enterprise Portfolio Management Driving application rationalisation across larger portfolios.
    • Vendor Strategy Shaping our relationships and strategy with key technology vendors.
    • Organisational Design Understanding how team structures impact architecture (Conway's Law in practice).
    • Complex Programme Architecture Architecting solutions for multi-year, multi-team programmes.

  2. Principal Enterprise Architect

    3-5 years in the Senior Enterprise Architect role (often after a stint as Lead).

    L5

    • Enterprise-wide Standards Definition Establishing the meta-model and modeling standards for the entire organisation.
    • Strategic Technology Selection Making platform-level decisions that impact the entire tech stack.
    • M&A Technical Due Diligence Contributing architectural expertise to potential mergers and acquisitions.
    • Advanced Cloud Governance Defining and governing the multi-cloud strategy and enterprise-wide security posture.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, architecture isn't just about big ideas; it's also about a mountain of documentation, research, and stakeholder communication. AI isn't here to replace your strategic brain, but it can certainly take a huge chunk of the tedious, time-consuming tasks off your plate. Imagine having more time for deep thinking and less for drafting.

As a Senior Enterprise Architect, you're constantly juggling complex designs, communicating with diverse teams, and staying on top of the latest tech. AI tools are becoming indispensable for cutting through the noise, automating repetitive tasks, and giving you back valuable hours every week. We're building an AI-first culture, and you'll be at the forefront of using these tools to make your job more impactful and less laborious.

Architecture Decision Record (ADR) Automation

Feed an LLM your meeting transcripts from design sessions and watch it automatically draft a comprehensive ADR. It'll capture the context, options discussed, and the final decision, saving you hours of painstaking write-up. Less admin, more actual architecture.

Tech Debt & Dependency Analysis

Use AI-powered code analysis tools (think CodeScene or SonarQube) to scan large codebases. These tools can automatically flag tech debt hotspots, complex dependencies, and architectural pattern violations, giving you a clear picture of where to focus your efforts without manual digging. It's like having an army of junior analysts doing the grunt work.

Vendor & Tech Trend Synthesis

Need to compare AWS Lambda, Azure Functions, and Google Cloud Functions on cost, performance, and security? Instead of trawling through docs, prompt an AI research assistant. It'll rapidly synthesise information on new tech trends or vendor offerings, giving you a summarised table in minutes. This means more time evaluating and less time searching.

Executive Summary Generation

You've just finished a detailed, 10-page technical architecture document. Instead of spending hours trying to dumb it down for the CFO, paste it into an LLM and ask it to 'Generate a one-page executive summary for a non-technical CFO, focusing on business value, cost implications, and risks.' It's a game-changer for stakeholder communication.

Common questions

Common questions

How do you become a Senior Enterprise Architect?

Common routes in include Senior Software Engineer / Lead Developer (5-7 years of engineering experience, then 1-2 years focused on solution design.), Solution Architect (3-5 years as a Solution Architect.) and Technical Consultant (with architecture focus) (5-8 years in technical consulting roles, with a strong emphasis on system design.). Times vary with prior experience.

Where can a Senior Enterprise Architect progress to?

This role can lead on to Lead Enterprise Architect (2-4 years in the Senior Enterprise Architect role.) and Principal Enterprise Architect (3-5 years in the Senior Enterprise Architect role (often after a stint as Lead).), depending on the skills you build.

What new skills matter most for a Senior Enterprise Architect?

Increasingly, Prompt Engineering & LLM Integration and Sustainable Architecture Design. 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 5

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 transfer across industries. These include systems thinking, cloud expertise, strategic planning and working with stakeholders. This can lead to leadership roles in other technical departments, such as head of engineering or head of infrastructure. It can also lead to technical product management, or to an enterprise architect role in a different sector such as fintech, healthtech or retail.

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.