My 5-Year Vision: Where Emmanuel Asika is Going Next

Emmanuel Asika breaks down his 5-year plan: transitioning from WordPress freelancing to Cloud Engineering and Indie Hacking. A raw look at tech stacks, strategy, and freedom.

I’m sitting here in Ireland, looking at the rain hitting the window. It’s a drastic change from where I was a few years ago. But the weather isn't the only thing that’s different. The way I write code, the way I think about business, and the way I view my future has completely shifted.

Most people know me as the WordPress guy. The freelancer who could spin up a high-traffic site, optimize the hell out of the database, and hand it off. And I was good at that. Really good. But if you’re reading this, you need to know that version of me is evolving. It's not dying, but it's being refactored.

I am currently deep in the trenches of a Masters in Cloud Computing. I'm pivoting hard. I'm moving from trading time for money to building assets that work while I sleep. This isn't just a career change - it's a complete operating system upgrade for my life.

Here is the raw, unfiltered roadmap of where I’m going over the next five years. No fluff. Just the strategy.

The Core Philosophy: From Service to Scale

The last few years taught me a brutal lesson: Service revenue is linear. Product revenue is exponential.

When you freelance, you have a cap. You can only code for so many hours a day. You can raise your rates, sure. But eventually, the market resists. You hit a ceiling. I hit that ceiling. I looked at it and realized I didn't want to break through it by working 80 hours a week. I wanted to break through it by building systems.

My 5-year vision is centered on one word: Leverage.

Code is the ultimate leverage. Code has zero marginal cost of replication. If I build a SaaS on Next.js, it costs me the same effort to serve one user as it does to serve ten thousand (mostly). The cloud bills might go up, but my effort doesn't.

So, the goal? To transition from a "Software Engineer for Hire" to a "Cloud Architect and Product Owner."

Phase 1: Mastering the Cloud (Years 1-2)

Right now, I am in the accumulation phase. This is what the Masters degree is about. It's not just for the piece of paper. It's to force my brain to understand distributed systems at a granular level.

I’m not talking about just launching an EC2 instance. Any junior dev can do that. I’m talking about designing fault-tolerant, auto-scaling architectures that can handle massive loads without waking me up at 3 AM.

The Shift to AWS and Azure

WordPress runs on a LAMP stack. It's a monolith. It works, but it’s heavy. Modern cloud engineering is about microservices and serverless functions. My focus right now is deep-diving into AWS.

I am moving away from "ClickOps" (clicking around in the AWS console) to Infrastructure as Code (IaC). If it isn't in code, it doesn't exist. I'm using Terraform and AWS CDK to provision infrastructure.

Here is what my day-to-day learning looks like now. Instead of configuring an .htaccess file, I’m defining infrastructure resources like this:

resource "aws_instance" "app_server" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"

  tags = {
    Name = "AsikaAppServer"
    Environment = "Production"
  }
}

This matters because it brings engineering discipline to operations. I can version control my entire data center. If a region goes down, I run a script, and we are back up in another region in minutes. That is power. That is the kind of value I want to bring to the table, either for an employer or for my own products.

I plan to bag the AWS Solutions Architect Professional certification within the next 12 months. Not for the badge. For the knowledge gap it closes.

Phase 2: The Tech Stack Overhaul (Years 2-3)

While I am sharpening my cloud skills, I am simultaneously completely overhauling my development stack. PHP paid the bills, but JavaScript and TypeScript are building the future.

I am betting the house on the T3 Stack / Modern Web Stack:

Next.js (App Router): The mental model of React Server Components just makes sense. It bridges the gap between the backend and frontend in a way that feels native.
TypeScript: I will never write raw JavaScript again. The safety nets TypeScript provides are non-negotiable for scalable systems.
Tailwind CSS & Shadcn/ui: I don't have time to write custom CSS classes anymore. I need to ship. Shadcn gives me accessible, beautiful components that I can copy-paste and own.
Supabase: This is the secret weapon.

Why Supabase?

I used to spend hours configuring MySQL databases, setting up backups, and worrying about security. Supabase gives me a Postgres database, authentication, real-time subscriptions, and edge functions out of the box. It feels like cheating.

For my Indie Hacking journey, Supabase is the engine. I can spin up a backend in 30 seconds. Here is how simple it is to grab data now, compared to the old WordPress WP_Query loops:

import { createClient } from '@supabase/supabase-js'

const supabase = createClient(process.env.SUPABASE_URL, process.env.SUPABASE_KEY)

async function getProjects() {
  const { data, error } = await supabase
    .from('projects')
    .select('*')
    .eq('status', 'active')
  
  if (error) console.error('Error:', error)
  return data
}

Clean. Typed. Fast. This allows me to focus on the product, not the plumbing.

Phase 3: The Indie Hacker Lab (Years 3-4)

This is where the rubber meets the road. By year 3, I expect to be working full-time in a high-level Cloud Engineering role here in Europe. But 5pm to 9pm? That’s my time.

I am adopting the "Small Bets" philosophy.

I am not trying to build the next Facebook. That is a lottery ticket. I want to build a portfolio of small, useful SaaS applications that solve very specific problems for very specific people.

The Strategy

Build Fast: No project gets more than 4 weeks of dev time before launch. If it doesn't get traction, I kill it.
Boring Problems: I’m not chasing AI hype (unless it’s useful wrapper tech). I’m looking for boring B2B problems. Invoicing tools for freelancers. API connectors for legacy systems. Stuff people hate doing.
SEO & Content: I will use my background in content and SEO to drive traffic. Organic growth is slower but sustainable.

I want to hit $5k MRR (Monthly Recurring Revenue) from side projects by the end of Year 4. That doesn't make me rich. But it buys me freedom. It pays the rent. It means I can say "no" to a bad boss or a bad client.

Phase 4: Full Autonomy (Year 5)

Year 5 is the vision. This is the destination.

By Year 5, the goal is to have the option to quit full-time employment if I choose to. I want to be a Sovereign Individual.

I visualize a life where I am living in Ireland-or maybe somewhere warmer for a few months-running a small empire of software products that run themselves.

Cloud Architecture: My systems will be automated. AWS Lambdas handling background jobs. Vercel handling the edge.
Support: Outsourced or automated via AI agents.
Development: I only code the features I think are cool.

This isn't about laziness. It's about high-leverage work. I want to spend my time thinking about strategy and architecture, not fixing bugs.

The "Anti-Fragile" Career

Nassim Taleb talks about "Antifragility"-things that gain from disorder.

A freelancer is fragile. If you get sick, you don't get paid. If a client fires you, your income drops to zero.

A Cloud Engineer with a portfolio of SaaS products is antifragile. If the job market crashes, I have my SaaS revenue. If one SaaS product dies, I have three others. If the SaaS market tanks, I have high-demand cloud skills to fall back on.

I am building a fortress.

Why I’m sharing this

Public accountability is terrifying. But it works.

By writing this down, I am making a contract with myself. I can't go back to being just a WordPress dev now. The bar has been set. The code is already being written.

There will be failures. I will probably launch a product that gets zero users. I will probably crash a production database at some point. I might even fail an exam.

But that’s part of the game.

The Emmanuel Asika of 5 years from now is a builder, an owner, and a master of the cloud. The journey there is going to be hard, messy, and absolutely worth it.

Watch this space. I’m just getting warmed up.