There comes a point when doing everything yourself stops being admirable and starts becoming the reason nothing moves forward.
I reached that point while looking at my schedule and the amount of time I spend working offshore.
I wanted to learn every part of building My Sail Cargo Journey. I wanted to understand the website, emails, social media, graphics, systems, and everything else happening behind the scenes.
But wanting to do everything and actually having the time and internet connection to do it were two different things.
The Project Couldn’t Depend on My Reception
When I’m working aboard another vessel, I can spend long periods without a reliable connection.
I may be able to prepare content in advance or automate part of the process, but automation doesn’t remove the need for someone to pay attention.
Comments still arrive. Posts need to go live. Emails need to be prepared. Links need checking. A piece of content may perform better than expected, and the next decision should respond to what people are actually interested in.
None of that works particularly well when the person responsible is offshore and waiting for enough reception to load a message.
I realized that if the project continued depending entirely on my availability, it would repeatedly lose momentum whenever I returned to sea.
That wasn’t a sustainable way to build a company.
I Didn’t Want to Wait for a Crisis
I had already decided that I wouldn’t wait until I was completely overwhelmed before asking for help.
I also didn’t want to wait until I had exhausted my time, energy, and resources. By then, bringing someone in would be an emergency rather than a deliberate decision.
So I hired the first person to join the project.
This wasn’t about handing over the ideas or the identity of My Sail Cargo Journey. The strategy, message, research, stories, values, and direction still had to come from me.
What I needed was someone who could help turn those decisions into consistent action.
Strategy and Execution Aren’t the Same Job
I still plan what I want to discuss. I record the podcast, conduct the research, choose the direction, and decide what the project should stand for.
But the daily execution is a different kind of work.
Posts need designing and scheduling. Emails need placing into the correct systems. Website pages need updating. Details need checking across different platforms.
Individually, these tasks may look small. Together, they determine whether the project remains visible while I’m away.
Delegating them meant I could concentrate on my work aboard without accepting that My Sail Cargo Journey would simply stop until I returned.
Bringing Someone Into an Unfamiliar World
The person joining the project didn’t come from shipping or traditional sailing.
That meant the first stage wasn’t simply learning the software. It was learning what this project is trying to protect and why any of it matters.
Why sail cargo?
Why traditional ships?
Why does the history behind a product matter?
Why do the hands, places, and journeys behind that product deserve to be visible?
Finding the right words for those questions also forced me to explain the project more clearly. Ideas that made perfect sense inside my head had to make sense to another person who had never lived or worked in this world.
That process was useful in itself.
If I couldn’t explain the project clearly to the first person joining the team, how could I expect somebody discovering it online to understand?
Building Continuity While I’m at Sea
The goal of hiring help wasn’t to make the project look bigger than it was.
It was to create continuity.
I needed the work to continue when I was offshore. I needed the quality and voice to remain consistent. I needed someone who could complement the things I do well and take responsibility for the tasks I couldn’t reliably complete from a ship.
At that stage, the role was still being financed by my salary from working aboard other vessels. That made it a serious commitment.
I was putting money into the structure the project needed before it could reliably pay for that structure itself.
There was no guarantee that it would immediately create sales or rapid growth. But continuing without help carried its own cost: missed opportunities, irregular communication, and a project that repeatedly stalled whenever I went offline.
The Bottom Line
Building a company doesn’t mean personally completing every task inside it.
My responsibility is to protect the direction, values, and purpose of My Sail Cargo Journey. It’s also my responsibility to recognize when insisting on doing everything alone is preventing that purpose from moving forward.
Bringing someone aboard was a decision to build consistency before reaching a crisis.
The project still carries my voice and experience. It simply no longer depends on me having a perfect internet connection every day.
For something being built between contracts, ships, time zones, and long stretches offshore, that continuity isn’t a luxury.
It’s part of the infrastructure.
From the podcast: This article was adapted from Episode 47, “My Sail Cargo Project Needs More Than Just Me,” from the My Sail Cargo Journey podcast. [Listen to the full episode on Spotify.]
Want to hear the story in Cio’s own words?
Listen to My Sail Cargo Journey on Spotify, and follow @mysailcargojourney on Instagram for real updates, photographs, and stories from life at sea as the project takes shape.