Growth OS
A growth platform that will bring together market intelligence, paid ads on Meta and Google, and sales video in one environment, built from the start to serve multiple businesses.
Our own technology
We build when a problem deserves a better solution.
We don't build products to look like a tech company. Some of what we learn on client work becomes a tool, a system or a platform. Here's what exists today, what stage each piece is at and what isn't ready yet.
- In-house runs inside Dream Harbor itself
- In development exists and works, not yet open to clients
- On hold partly built, with development paused by our choice
- Available ready for clients to use
In development
What's becoming a product
Pieces that grew out of patterns repeated across projects, now being built to serve more than one business.
Dealership dashboard
A management dashboard for car dealerships, with stock, a board-style CRM, a calendar and goals, that publishes the website's listings straight from its own records.
DreamHub
A platform that brings together AI customer service, a CRM and metrics in one place, branded for each business that uses it.
In-house
What we use ourselves
Before we roll anything out for a client, we use it ourselves. These tools run Dream Harbor's outreach, customer service and learning every day.
Personal OS
The founder's personal operating system. Goals, projects, calendar, habits, learning and progress in one place, running on his own computer.
Lead qualification
Dream Harbor's own sales system. Automated Instagram conversations, a step-by-step assessment on the website, scoring calculated on the server and a dashboard that reads the CRM live.
Farol
Maps businesses in a region using public sources and measures signals of their online presence, to decide where a sales conversation makes sense.
Radar
Reads Meta's public Ad Library to follow competitors and offers, measuring how many ads each account keeps running over time.
Sintetizador
Brings videos, audio files, PDFs and text together in one project, transcribes them on our own machine and organises the content into knowledge the team can use.
How a project becomes a product
Client work stays at the heart of it
Client projects solve problems, pay the bills and show what repeats. When a pattern turns up often enough, it becomes a component, then a tool, and only at the end, if it makes sense, a product.
-
Real problem
It turns up in a client project or in our own work
-
Made-to-measure fix
Solved for that case, the way the case needs
-
Pattern
The same problem turns up again, somewhere else
-
Internal tool
The fix becomes a reusable piece we use ourselves
-
Product
Only once it stands up without us beside it
Get in touch
Got a problem no tool quite handles?
It might need bespoke software. It might not. Tell us what it is.