ARTICLE · SELF IMPROVEMENT · 13 MIN READ
Building a Startup While Studying Computer Science: My Journey Through Level 300, Entrepreneurship, and the Pursuit of Purpose
My journey through it all

Introduction: The Dream Beyond the Classroom
It was 2:07 a.m
My Software Engineering assignment was due in a few hours. A startup feature I had been building was refusing to work. My inbox was filled with unread messages, and my laptop sounded like it was carrying the weight of every decision I had made that semester.
I stared at the screen and asked myself a question that many student entrepreneurs eventually face:
"Can I really do both?"
At the time, I was a Level 300 Computer Science student at the University of Cape Coast. During the day, I attended lectures, completed assignments, and prepared for examinations. At night, I transformed into something else entirely: a founder, product builder, researcher, marketer, customer support representative, and software developer.
The contrast was exhausting.
Yet somewhere between lecture halls and late-night coding sessions, I discovered something that changed my life.
Technology was not just about writing code.
It was about solving problems.
What began as curiosity about computers gradually evolved into a deeper desire to build solutions that could improve people's lives.
This article is the story of that journey, the lessons, failures, sacrifices, and discoveries that came from building a startup while pursuing a Computer Science degree.
It is not a story about success.
It is a story about growth.
And perhaps that is even more valuable.
The Night Everything Felt Impossible
One particular night remains vivid in my memory.
It was during my Level 300 academic year.
The semester was becoming increasingly demanding.
Several assignments were due within days.
A group project required urgent attention.
Mid-semester examinations were approaching.
At the same time, I was actively working on a technology product that I believed could create meaningful impact.
My laptop screen displayed multiple windows simultaneously.
Visual Studio Code.
Documentation pages.
Research papers.
Project management boards.
Unanswered messages.
Unfinished tasks.
As midnight turned into 1 a.m., and 1 a.m. became 2 a.m., exhaustion began to set in.
I leaned back in my chair and stared at the ceiling.
For the first time in months, I genuinely questioned whether I was capable of doing both.
Maybe I should focus entirely on academics.
Maybe entrepreneurship could wait until graduation.
Maybe I was simply making life unnecessarily difficult for myself.
The pressure felt overwhelming.
What made the situation even more difficult was the fact that very few people understood what I was trying to achieve.
To most observers, I was just another student.
They did not see the countless hours spent learning outside the classroom.
They did not see the failed experiments.
They did not see the rejected ideas.
They did not see the moments of self-doubt.
That night taught me something important:
Every meaningful journey contains moments when giving up appears reasonable.
The difference often lies in choosing to continue despite uncertainty.
Where the Entrepreneurial Mindset Began
I was not born an entrepreneur.
In fact, entrepreneurship initially felt intimidating.
Growing up, I viewed successful founders as extraordinary individuals with resources, connections, and experience far beyond my own.
I assumed entrepreneurship was something people pursued after many years of professional experience.
University gradually changed that perception.
As I learned programming, I discovered something powerful.
Unlike many fields, software allows a single individual to create solutions capable of reaching thousands of people.
One idea.
One laptop.
One determined individual.
That realization was transformative.
Suddenly, the barrier between imagination and implementation became much smaller.
Whenever I encountered a problem, my mind automatically began exploring possible solutions.
Could software solve this?
Could technology improve this process?
Could there be a better way?
Over time, these questions became habits.
And habits eventually became opportunities.
The Birth of an Idea
One of the most exciting moments in entrepreneurship is identifying a problem worth solving.
Ideas rarely arrive as dramatic flashes of inspiration.
More often, they emerge from observing everyday frustrations.
The best ideas are usually hidden in plain sight.
As I became more aware of challenges within my community, I realized that many people struggled to access reliable information, guidance, and services efficiently.
Technology had the potential to bridge those gaps.
The challenge was determining how.
Like many student entrepreneurs, I quickly learned that having an idea is the easy part.
Execution is where the real work begins.
Ideas are exciting.
Execution is exhausting.
Execution requires discipline.
Execution requires consistency.
Execution requires continuing to work even when motivation disappears.
This lesson would become increasingly important throughout my journey.
Building Apomuden: Turning Ideas into Reality
As my interest in entrepreneurship grew, I realized I did not want to spend all my time discussing ideas.
I wanted to build.
That desire eventually led to the creation of Apomuden, a startup project born from a simple belief: technology should make people's lives easier while creating meaningful opportunities for connection, creativity, and growth.
Like many first-time founders, I initially underestimated how difficult building a real product would be.
Creating an idea is exciting.
Building a product that people actually use is an entirely different challenge.
There were countless moments when features seemed perfect in my mind but failed to resonate with users. There were occasions when technical problems consumed entire weekends. There were days when academic deadlines collided directly with development schedules.
Yet every challenge revealed a lesson.
I learned that users rarely care about how impressive a technology stack is. They care about whether a product solves a genuine problem.
I learned that launching quickly is often better than waiting for perfection.
Most importantly, I learned that entrepreneurship is not simply about building software.
It is about understanding people.
Apomuden became more than a project.
It became a classroom outside the classroom.
Every feature, user conversation, setback, and improvement taught lessons that no textbook could provide.
The Reality Nobody Talks About
Social media often portrays entrepreneurship as exciting and glamorous.
People celebrate funding announcements.
Product launches.
Business growth.
Success stories.
What they rarely discuss are the invisible struggles behind those achievements.
The countless debugging sessions.
The failed deployments.
The rejected proposals.
The uncertainty.
The loneliness.
The self-doubt.
As a student entrepreneur, these challenges are amplified because academic responsibilities never pause.
Assignments continue.
Examinations continue.
Deadlines continue.
Regardless of what is happening with your startup.
There were times when I spent hours fixing technical issues only to realize I still needed to prepare for an examination the following morning.
There were days when I switched from coding a product feature directly into writing academic reports.
The mental transition was often exhausting.
Yet those experiences taught adaptability.
They taught endurance.
They taught discipline.
What Computer Science Really Taught Me
Before university, I believed Computer Science was primarily about programming.
Today, I understand that programming is only one piece of a much larger puzzle.
Computer Science teaches problem-solving.
It teaches analytical thinking.
It teaches structured reasoning.
These skills extend far beyond software development.
When building products, I discovered that many entrepreneurial challenges could be approached using the same logical frameworks learned in Computer Science.
Identify the problem.
Analyze constraints.
Design a solution.
Test assumptions.
Evaluate outcomes.
Iterate.
Whether debugging software or improving a business process, the methodology remains remarkably similar.
The degree was not simply teaching me how to write code.
It was teaching me how to think.
Failure Became My Greatest Teacher
One of the hardest lessons I learned involved failure.
Many students fear failure because academic environments often associate it with poor performance.
Entrepreneurship offers a different perspective.
Failure becomes feedback.
Not every feature succeeds.
Not every product decision is correct.
Not every assumption reflects reality.
Some ideas I believed would be successful received little interest.
One experience that shaped my thinking involved launching features that I was convinced users would love.
After spending days designing, coding, testing, and refining those features, the response was far less enthusiastic than I expected.
Initially, I viewed this as failure.
Later, I realized it was valuable feedback.
The experience taught me an important lesson: founders should not build based solely on assumptions. They should build based on evidence.
Sometimes the market teaches lessons that confidence cannot.
Some features users requested were rarely used after implementation.
Some solutions created new problems.
Initially, these setbacks felt discouraging.
Over time, they became valuable sources of information.
Failure stopped being something to avoid.
Instead, it became something to learn from.
Every mistake contained a lesson.
Every challenge revealed an opportunity for growth.
Building While Everyone Else Was Sleeping
Some of my most productive work happened during hours when most people were asleep.
Not because late-night productivity is inherently superior.
But because those were often the only uninterrupted hours available.
After lectures.
After assignments.
After meetings.
After responsibilities.
The quiet hours became opportunities to build.
There is something unique about working toward a dream while the world sleeps.
The environment becomes quieter.
Distractions disappear.
Progress feels deeply personal.
Those late nights taught me the value of consistency.
Small efforts repeated consistently eventually create meaningful results.
Success is rarely the result of a single breakthrough.
More often, it emerges from hundreds of ordinary days of effort.
The Human Side of Technology
Perhaps the most important lesson from entrepreneurship involved people.
As developers, we often become fascinated by technology itself.
Frameworks.
Programming languages.
Algorithms.
Artificial intelligence.
Architecture.
Yet users rarely care about those details.
Users care about outcomes.
They care about whether a solution improves their lives.
They care about whether a product solves their problems.
This realization transformed how I approached development.
Instead of asking:
"What technology should I use?"
I began asking:
"What problem am I solving?"
That shift changed everything.
Technology became a means rather than an end.
Managing Time Without Losing Yourself
Balancing entrepreneurship and academics requires more than scheduling.
It requires intentional prioritization.
There is never enough time to do everything.
Eventually, I learned that productivity is not about maximizing activity.
It is about maximizing impact.
Some tasks matter more than others.
Some opportunities deserve attention.
Some distractions require elimination.
The challenge is identifying which is which.
I also learned the importance of rest.
Many students believe success requires constant exhaustion.
Experience taught me otherwise.
Burnout reduces creativity.
Burnout reduces productivity.
Burnout reduces effectiveness.
Sustainable growth requires balance.
Why Students Should Start Before They Feel Ready
One of the biggest misconceptions among students is the belief that they need more experience before beginning.
I understand this feeling because I experienced it myself.
Many people wait.
They wait for graduation.
They wait for funding.
They wait for confidence.
They wait for certainty.
The problem is that certainty rarely arrives.
Growth occurs through action.
Confidence develops through experience.
Skills improve through practice.
The best time to start is often before you feel fully prepared.
Starting creates momentum.
Momentum creates progress.
Progress creates opportunities.
The Future I Now See
Looking ahead, I recognize that entrepreneurship is not simply about building companies.
It is about creating impact.
It is about identifying problems and pursuing solutions.
It is about serving people through innovation.
Computer Science provided the technical foundation.
Entrepreneurship provided the practical application.
Together, they transformed how I view both technology and opportunity.
The journey is still ongoing.
There are still challenges.
There are still uncertainties.
There is still much to learn.
But that is precisely what makes the journey meaningful.
Conclusion: The Story Is Still Being Written
As I write this, I am still a student. I am still learning. I am still building. The vision is larger than what has been accomplished so far, and there is still a long road ahead. Yet every project completed, every mistake made, every lesson learned, and every late night spent building has moved me one step closer to the future I once imagined. The story is still being written. And for the first time, I am excited not because I know how it ends, but because I get to build it one chapter at a time. Thank you
About the Author
Kelvin Omaboe (Builder Kay) is a Level 400 Computer Science student at the University of Cape Coast and the founder of Bytant, Crib and Apomuden. He is passionate about technology, entrepreneurship, and building digital solutions that create meaningful impact within communities. His interests include software development, product design, startup innovation, and youth empowerment through technology.
Loading the full page…