Interview with Rob Hallam, a $22K/Month Traveling Solopreneur

Table of Contents

• 🧭 Why a “Perfect Routine” Is Usually a Trap
• ✈️ Building While Traveling Without Turning Life Into Airport Wi-Fi
• 🛠️ The Simple Work System Behind the Output
• 🏄 The Surfing Lesson Most Builders Need
• 😴 Sleep, Play, and the Annoyingly Important Human Stuff
• 🔩 The Real Talk: Build the Conditions, Not Just the Calendar

🧭 Why a “Perfect Routine” Is Usually a Trap

Rob, what does a normal workday actually look like when he is building a business while traveling?

Rob Hallam’s day starts at roughly 11 a.m. or noon, which is exactly the kind of thing that makes productivity influencers reach for their emergency cold-plunge footage.

He is a night owl. He does not wake up eager to conquer a color-coded calendar at 5 a.m. He wakes up slowly, gets breakfast, gets outside, handles a few customer support emails, and works through the small operational stuff first.

Then, usually around 2 or 3 p.m., he trains. Weights, cardio, shower, coffee. The usual ritual is less about becoming a monk with a laptop and more about clearing the runway.

By the time he sits down to work in the evening, the chores are done. Food is handled. Messages have gone quiet. Nobody needs anything right this second. That is when he can work for a solid eight-hour block without constantly context-switching between building, errands, notifications, and the latest tiny emergency that probably was not an emergency.

It is a useful reminder for solo builders: a productive schedule is not necessarily an early schedule. It is a schedule that gives the brain enough quiet to do work that requires actual thought.

So should every founder work at night?

No. The point is not that everyone should start working at midnight and develop an emotional dependency on coffee. The point is that builders should stop borrowing routines from people whose brains, responsibilities, energy levels, and lifestyles are completely different.

Rob spent years feeling guilty about not fitting the standard self-help template. Wake earlier. Plan harder. Be more disciplined. Do more before breakfast, presumably while standing in a cold shower and reading Marcus Aurelius.

That did not work for him. Working with his natural rhythm did.

His setup is based on a simple principle: protect the conditions that make deep work possible, then build around them. For him, that means a slow morning, exercise, an uncluttered evening, and enough sleep to think clearly.

✈️ Building While Traveling Without Turning Life Into Airport Wi-Fi

Rob travels constantly. How does he keep a SaaS business moving?

At first, not very well.

Rob started traveling as a backpacker while trying to build startups. He was moving every few days, then every week, then every couple of weeks. He made mistakes, had failures, and went about a year without making money. That is not a romantic founder origin story. It is just what happens when a person tries to build something meaningful while constantly unpacking chargers in a new apartment.

Frequent travel makes focus brutally difficult. A new place brings logistics, unfamiliar routines, transport, meals, social plans, and a dozen tiny decisions that happily consume the same brain needed for product work.

When Rob was building SuperX, he could get bits and pieces done while moving around. But real momentum arrived when he settled in Colombia for three straight months. That is where he got serious work shipped.

His current model is much less chaotic:

• Choose a place to live for two to three months.
• Prefer three months when possible.
• Build a routine before expecting deep output.
• Move once there is a natural break, not every time a cheap flight appears.

That balance gives him enough stability to build while keeping travel as part of the lifestyle. It is not “digital nomad productivity” in the postcard-and-laptop sense. It is choosing a base long enough for the boring work to finally get done.

What has travel taught Rob about building a business?

Travel is not just a backdrop for Instagram stories and suspiciously expensive coconuts. For Rob, it is a way to see how people live, how money moves, and where opportunities exist outside the tiny bubble a person gets used to calling normal.

He has lived in more than 13 countries over a few years. Some places barely made him want to open his laptop. In others, he shipped more than he had in months.

That observation led to one of his core beliefs: productivity follows happiness.

The place matters. The environment matters. The feeling of life being good enough to make things matters. Discipline still has a role, obviously. But treating discipline as the one missing ingredient can become a very efficient way to ignore an environment that is draining the life out of someone.

🛠️ The Simple Work System Behind the Output

How does Rob decide what to work on when there are always too many possible tasks?

He keeps a simple list.

Every month or two, Rob collects the things that keep coming up: the top features he wants to build, improvements to existing parts of the product, and bugs. When he starts a work block, he either continues yesterday’s task or picks from that list based on what feels right to tackle.

That last part can sound suspiciously unstructured, but it has a filter behind it. Rob tries to prioritize the work that moves the business forward most.

The uncomfortable part is that it is usually not the flashy work. The visual redesign, the clever little add-on, and the feature that looks great in a post are often more fun. They are not always the thing that improves the product for customers or prevents people from leaving.

Most of the time, the business-moving work is boring:

• Fixing a critical bug.
• Improving a repeated point of friction.
• Responding to a common support issue.
• Making an existing core feature more reliable.
• Finishing a practical improvement instead of starting another shiny idea.

How does he handle customer feature requests without becoming a full-time request collector?

Rob’s approach is refreshingly ruthless, though not in the “delete all feedback and move to a cabin” way.

When a note becomes too long, he starts a new one and copies over only the items that still matter. If he forgets a request and no customer raises it again, he assumes it was not important enough to prioritize.

Repeated pain is the signal. A critical bug tends to generate multiple emails. A workflow issue that affects real customers keeps resurfacing. Those are the problems that should rise to the top.

A single request for one extra setting, one tiny adjustment, or one niche preference may be valid. But a solo operator does not have infinite time. Treating every request like a legal summons is how a product roadmap becomes a landfill.

The system is not mathematically perfect. It does something more useful: it protects attention for the work with evidence behind it.

🏄 The Surfing Lesson Most Builders Need

What is Rob’s biggest lesson from building startups alone?

He compares building a business to surfing.

A surfer does not catch good waves by standing on the beach with a Notion template titled “Wave Acquisition Strategy.” They spend time in the water. They learn what the waves look like before they break. Eventually, they get better at recognizing which ones are worth paddling toward.

Business works similarly. The first time is hard because everything is new: choosing a problem, building an MVP, speaking to customers, pricing something, shipping it, fixing it, and realizing that a “small tweak” has somehow consumed an entire weekend.

But after enough time in the water, patterns become easier to see. Builders learn what customer urgency feels like. They notice opportunities earlier. They become more capable of distinguishing a meaningful signal from a shiny distraction.

The hard part is getting into the water at all. Once someone has built enough, catching and riding the next opportunity becomes less mysterious.

This is why experienced founders often seem to win more than once. It is not necessarily because they have a secret newsletter or a better collection of productivity apps. They have pattern recognition earned through repetitions.

What should a new solo builder take from that analogy?

Start before feeling qualified.

There is no clean, confidence-inducing moment where every tool is chosen, every feature is planned, and every risk has been politely removed from the room. The early stage is awkward because it is supposed to be awkward.

For a builder creating an AI-powered launch system for creators, a small SaaS product, or any other internet-shaped experiment, the useful move is the same: get close to the problem. Build a version. Put it in front of people. Notice what keeps coming up. Improve the part that matters.

That is more useful than spending six months optimizing an AI funnel builder, assembling a no-code startup tools collection, or polishing a launch stack that has not met a customer yet. Tools can help. They cannot replace time in the water.

😴 Sleep, Play, and the Annoyingly Important Human Stuff

What does Rob protect above everything else?

Sleep.

About an hour before bed, Rob starts switching things off. He might read, use YouTube for a bit, or do a little doomscrolling because apparently no productivity system is legally complete without one bad habit. Then the phone goes away.

He aims for nine hours of sleep and usually allows nine and a half hours in bed. Eight hours does not work for him. He has tested it. The result is not more disciplined output. It is less creativity, less motivation, less desire to train, and less ability to think.

Everything else is downstream of sleep.

That does not mean every builder needs nine hours. It means the amount of sleep that keeps someone functional should not be treated as negotiable just because the internet has made exhaustion look ambitious.

What does “productivity follows happiness” look like in practical terms?

For Rob, it means building a life that produces the mental state he wants to bring to work. Travel is part of that. So is lifting. So is getting sun. So is having a Rubik’s Cube nearby and taking small play breaks between prompts.

That might sound almost offensively simple, but it is a better operating system than assuming every output problem is a discipline problem.

When Rob approaches work from a place of play, he makes better things. When he is unhappy in a place, he ships less. The pattern has been consistent enough that he now treats happiness as an input to productivity, not a reward that arrives after productivity.

🔩 The Real Talk: Build the Conditions, Not Just the Calendar

Would Rob’s work system work for everyone?

No, and that is why it is useful.

The takeaway is not “wake up at noon, move to Colombia, buy a Rubik’s Cube, and wait for $22K per month to happen.” That would be a very expensive misunderstanding.

The lesson is to identify the conditions that make consistent work possible. For Rob, those conditions are stable travel bases, quiet evening work blocks, exercise, sleep, and a simple method for prioritizing the repeated problems that matter.

For another builder, it could be early mornings, a coworking space, two protected afternoons each week, or a house where nobody asks for “just one quick thing” every 14 minutes.

There is no universal routine. There is only the work of noticing when output is good, identifying what made it possible, and recreating those conditions without turning it into a 47-step ritual sold in a $97 PDF.

What should a solo builder test tonight?

Pick one high-leverage task that has been sitting under a pile of cosmetic nonsense. Finish the chores first. Silence the notifications. Give the work a real block of uninterrupted time.

Then keep a short list of product problems and customer requests. When the list gets bloated, copy only the repeated and meaningful items into a new one. That is enough process for now.

An AI-powered launch system for creators can automate pieces of a business, but it cannot decide what deserves attention. That still comes from listening, building, and spending enough time in the water to recognize a real wave.

❓ Frequently Asked Questions

How long does Rob Hallam stay in one place while traveling?

Rob generally sets up a base for two to three months, with three months being his preferred balance between stability and travel.

What does Rob prioritize in his SaaS business?

He focuses on tasks that move the business forward, especially critical bugs, repeated customer problems, and practical product improvements rather than flashy features.

What is Rob’s main productivity principle?

His central principle is that productivity follows happiness. He has found that he ships more when he is happy with his environment and lifestyle.

Why does Rob work late at night?

Late at night, messages, errands, meals, and other distractions are usually finished. That quiet gives him the uninterrupted focus needed for long work sessions.