Skip to content

In-house technology

We build when a problem deserves a better solution.

We don't build products to look like a tech company. Part of what we learn implementing solutions 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 in Dream Harbor's own operation
  • 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
How a project becomes a product

Custom projects stay at the center

Client projects solve problems, bring in revenue and reveal what repeats. When a pattern shows up often enough, it becomes a component, then a tool, and only at the end, if it makes sense, a product.

  1. Real Problem

    It shows up in a client project or in our own operation

  2. Custom Solution

    Solved for that case, the way the case calls for

  3. Pattern

    The same problem shows up again, somewhere else

  4. Internal Tool

    The solution becomes a reusable piece we use ourselves

  5. Product

    Only when it holds up without us beside it

Let's talk

Have a problem no tool handles well?

It might need custom software. It might not. Tell us what it is.