Why I'm Doing This
Let me be honest from the start: I'm not naturally a person who shares. I prefer building to talking, coding to presenting, and solving problems to explaining them. If you asked my friends, they'd probably say I'm the quiet one in the group.
But here's what I've learned after a decade of working on boats and then transitioning to building software: the problems I've faced aren't unique. The solutions I've found might help someone else. And staying silent means those lessons die with me.
What Happened
For ten years, I worked in the charter boat industry in Mallorca. I saw companies drown in spreadsheets. I watched captains get trip information at 2 AM via WhatsApp. I witnessed invoices get lost in endless email chains.
The industry wasn't broken because of bad people. It was broken because of bad systems.
So I started building. First for myself, then for others. What began as a simple tool to manage bookings became TheCharterPanel. What started as frustration with how travelers found boats became EasyCharter.es. The pattern kept repeating: see a problem, build a solution.
Why Now
Several things pushed me to finally start this blog:
-
AI is changing everything. I've been building with AI assistants for years now, and I've developed tools and workflows to make AI development smarter. These insights shouldn't stay locked in my head.
-
The nautical industry is still behind. Most charter companies are still struggling with the same problems I saw in 2014. Maybe writing about solutions will help more than building alone.
-
I need to practice this. Communication is a skill. I've neglected it for too long. This blog is partly for you, but it's also for me—to get better at explaining what I do and why.
What to Expect
I'll write about:
- Progress on my projects — What I'm building, why, and what I'm learning
- Technical deep-dives — When I solve an interesting problem, I'll share how
- Industry observations — Things I notice about the nautical and tech worlds
- Honest reflections — The failures, the doubts, the lessons
I won't post on a schedule. I'll write when I have something worth saying. Quality over quantity.
A Note About AI
You might notice my writing is clear and structured. Yes, I use AI to help me write—just like I use AI to help me code. But the ideas, the experiences, the opinions? Those are mine.
I believe in using the best tools available. AI is one of them. The goal is communication, and if AI helps me communicate better, that's a win.
Why Custom Software? The Numbers That Changed My Mind
After a decade in the field, a few statistics stay with me. They explain why I build what I build:
- 70% of digital transformation initiatives fail — according to McKinsey, and the primary cause is not technology, but lack of fit between the tool and the actual business process.
- 67% of SMBs use 4 or more disconnected tools for a single workflow — creating fragmentation, errors, and daily time loss.
- The global custom software market is growing at 22.4% annually as more businesses realize generic tools cannot cover their competitive differentiation.
67% of businesses using 4+ tools for one process report losing data between handoffs at least once a week. That is the problem I have been solving since 2014.
| What I build | Who it is for | The core value |
|---|---|---|
| Custom SaaS platforms | Industries without vertical software | Replace 4–6 generic tools with one system |
| Client portals | B2B service businesses | Eliminate "any updates?" messages forever |
| MVP development | Founders validating a product idea | Working software in weeks, not months |
| AI-powered systems | Businesses wanting context-aware AI | AI that knows your business, not just the internet |
What You Will Find Here
The topics I cover on this blog follow the real problems I see every week working with founders and business owners:
- When to use generic software vs build something custom
- How to implement AI in a way that actually delivers ROI (not just a chatbot)
- The business case for vertical software — and how to evaluate if it exists for your sector
- Real lessons from building TheCharterPanel, GestorSalon, and other sector-specific platforms
- How to think about digitalization as a phased investment, not a one-time project
Let's See Where This Goes
I don't know if anyone will read this. I don't know if I'll keep writing. But I'm pressing publish anyway.
If you've read this far, thank you. If you have questions or just want to say hello, you can find me on LinkedIn or WhatsApp.
Here's to new beginnings.
— Carlos
Why These Numbers Drive My Work
A few statistics that have shaped how I build:
- The average SMB wastes 4 hours per week on manual tasks that should be automated — that is 200 hours per year per person
- 67% of companies use 4 or more disconnected tools for a single end-to-end process
- TheCharterPanel now serves 25 companies managing 5,000 bookings that previously ran on WhatsApp and Excel
- With AI-assisted development, systems that took 12 months to build in 2015 now take 6 to 8 weeks
- Businesses that invest in context-aware AI report 3x better output quality vs tools with no business context