Key Takeaway
Learning technology isn't about changing my identity from marketer to technologist; it's about becoming capable of turning business ideas into things that can actually be built.
I started with marketing.
At first, I was mainly interested in the visible side of business: social media, content, campaigns, branding, audience growth and how businesses communicate with people.
But the more I worked with businesses, the more I became interested in everything happening behind the marketing.
Why does a business exist in the first place?
How does it make money?
Why do customers choose one solution over another?
How are the processes behind the business designed?
And eventually, a different question started appearing:
What if I could build some of the things I'm thinking about instead of only marketing them?
That question gradually changed the direction of my learning.
## Marketing was where I started
Marketing taught me to look at businesses from the outside.
You have a product.
You have a customer.
You have a problem you're trying to solve.
You have a message that needs to reach the right people.
You test something, observe what happens, and improve it.
Working in digital marketing gave me exposure to many different types of businesses and projects. It also showed me something I didn't fully understand when I started:
Marketing is connected to almost every part of a business.
A marketing problem can actually be a product problem.
A content problem can be a positioning problem.
A sales problem can be a trust problem.
And sometimes, what looks like a marketing problem is actually a systems problem.
That made me want to understand more.
## I became curious about what happens behind the marketing
When you're working on a campaign, you naturally start asking questions beyond the campaign itself.
Where does the product come from?
How does the customer journey work?
What happens after someone clicks?
How is information collected?
How are leads handled?
What happens repeatedly inside the business?
Could some of those processes be automated?
Could the experience be better?
The more questions I asked, the less interested I became in looking at marketing as an isolated function.
I started seeing it as one part of a much larger system.
And that changed what I wanted to learn.
## I wanted to understand how businesses actually work
I've always been interested in the idea of building businesses.
But having a business idea and understanding how to turn that idea into something real are two very different things.
An idea is easy.
Building the thing is where reality starts.
You have to understand the problem.
You have to understand the customer.
You have to figure out the business model.
You have to create the product or service.
You have to build the systems around it.
You have to get people to discover it.
And then you have to keep improving it.
Marketing helped me understand one part of this equation.
I wanted to understand more of it.
## The next question became: can I build the solution?
This is where technology became interesting to me.
Not because I suddenly wanted to become a software engineer.
And not because I think everyone needs to learn how to code.
It was much simpler than that.
I wanted to understand how digital things are built.
If I had an idea for a website, I wanted to understand what would actually be required to create it.
If I had an idea for a digital product, I wanted to understand what sits behind the interface.
If I saw a repetitive business process, I wanted to know whether it could be automated.
If I wanted to test an idea, I didn't always want to depend completely on someone else to make the first version.
That curiosity pushed me toward learning the technical side.
## Learning to build digital things
My learning has been gradual.
I've explored things like websites, GitHub, Vercel, Next.js, automation, AI tools and other parts of the modern digital stack.
Some of it has been confusing.
Some things took much longer to understand than I expected.
And I'm still learning.
But the important change wasn't becoming technically advanced overnight.
It was learning to think differently.
Instead of:
"I have an idea."
I started thinking:
"What would it take to actually build this?"
That is a very different question.
It forces you to break an idea into components.
What does the user need?
What does the system need?
What data is required?
What happens when something goes wrong?
What can be automated?
What should remain manual?
What is the simplest version that can be tested?
Those questions are useful even when you're not writing the code yourself.
## Websites changed the way I think
Building this personal website has been one of the practical ways I've experienced this shift.
A website can look simple from the outside.
You see a page.
You click a button.
You read an article.
But underneath that are many different decisions.
There is the structure.
There is the content architecture.
There are URLs, metadata, search discovery, structured data, performance, accessibility, deployment and version control.
Learning about those layers made me realise that building a digital product is much more than designing what appears on the screen.
The interface is only the visible layer.
There is a system underneath it.
And understanding that system changes how you approach the product itself.
## Then came AI and automation
AI made this even more interesting.
Before, learning the technical side could sometimes feel like there was a large gap between having an idea and being able to build it.
AI doesn't remove that gap.
But it can change how you approach it.
I'm particularly interested in AI when it connects to actual business problems.
For example:
- repetitive workflows - content production - research - data handling - customer processes - internal operations - automation - decision support - digital products
The interesting question for me isn't:
"What can AI do?"
It's:
"Where can AI create useful leverage inside a real business?"
That distinction matters.
Technology is useful when it helps solve something.
## Building is different from having an idea
One of the biggest things I'm learning is that ideas become much more interesting when you try to build them.
When an idea exists only in your head, everything seems possible.
Once you start building, constraints appear.
The technology may not work the way you expected.
The customer may not behave the way you expected.
The process may be more complicated than you thought.
The economics may not make sense.
Something you thought was important may turn out not to matter.
That is actually valuable.
Because building turns assumptions into things you can test.
And testing creates information.
That's why I increasingly see building as a form of learning.
## I'm still learning the technical side
I don't consider myself a technologist.
I'm learning technology because I want to become a better builder.
There is a difference.
I don't need to know everything.
I need enough understanding to:
- identify what is technically possible - communicate with technical people - break down problems - prototype ideas - understand systems - use AI effectively - make better business decisions - know when I need deeper technical expertise
And when something is beyond my current ability, that's okay.
Learning to build doesn't mean doing everything alone.
It means understanding enough to participate meaningfully in the building process.
## Why I want to become a builder
The more I learn, the more I realise that the kind of entrepreneur I want to become needs more than one skill.
Marketing helps me understand markets and customers.
Business helps me understand value, models and opportunities.
AI can create new ways of working.
Technology provides the infrastructure for many of the things I want to build.
And systems connect everything together.
That's why I don't see my journey as moving from marketing to technology.
I see it as expanding from marketing into building.
Marketing was the starting point.
Business is the bigger context.
Technology and AI are becoming tools that help me build.
## The way I'm thinking about building now
The mental model I'm developing is relatively simple:
Understand the Problem
↓
Understand the Business
↓
Design the Solution
↓
Learn What Is Needed to Build It
↓
Build
↓
Test
↓
Learn
↓
Improve
I'm sure this framework will change as I gain more experience.
That's part of the point.
I'm not trying to create a perfect methodology before I have enough experience to justify one.
I'm trying to build, observe, learn and refine my thinking.
## I'm not trying to become a technologist
This distinction is important to me.
I don't want technology to become another title I put beside my name just because I'm learning some technical tools.
What interests me is what technology enables.
Can it help me build a better business?
Can it help a small team accomplish more?
Can it turn an idea into a prototype?
Can it remove repetitive work?
Can it create a better customer experience?
Can it make something that previously required a large team possible for a much smaller one?
Those are the questions that interest me.
## From marketer to builder
Looking back, the transition feels less like a change of direction and more like a natural progression.
Marketing made me curious about businesses.
Businesses made me curious about problems.
Problems made me interested in solutions.
Solutions made me want to understand building.
And building has pushed me toward technology, AI and systems.
I don't know exactly where that path will lead.
But I know what I'm trying to become better at:
seeing opportunities, understanding problems, building solutions and turning those solutions into businesses.
That's the direction I'm exploring.
And for me, learning to build digital things is simply another step toward becoming the kind of entrepreneur I want to be.