From Projects to Processes

I built Blue as a project management tool. Coming from an agency background, that’s what made sense to me. Start a client project, add the tasks, check them off, archive it. Clean, simple, done.

Then I started talking to our customers.

Over 90% of them weren’t using Blue for projects at all. They were using it to manage ongoing processes — the kind of work that never “ends.”

CRM pipelines. Hiring workflows. Customer onboarding. Production and logistics tracking. One customer uses Blue for army intelligence field gathering. These aren’t projects with a start date and an end date. They’re the repeating, evolving workflows that keep organizations running.

The data confirmed what the conversations were telling us. Most workspaces in Blue never get archived. They just keep going.

The gap in the market

This realization put us in an interesting position. We weren’t just competing with Asana, Monday, or Trello for project management anymore. But we also weren’t trying to be a massive ERP system that costs millions and takes years to implement.

There’s a huge gap between lightweight task management tools and heavyweight enterprise software. Millions of teams need more than a to-do list but can’t justify — or don’t want — the complexity of traditional business process management systems.

That’s where Blue sits.

What we changed

Once we saw this clearly, we started reshaping the product around it.

We renamed our core building blocks. “To-dos” became records — customizable per workspace, so a sales team calls them “opportunities” while support calls them “tickets.” “Projects” became workspaces, because the work happening inside them isn’t temporary.

We built time intelligence — fields that track how long a record has been in each stage of a process, and the duration between events. These aren’t nice-to-haves. They’re how you find bottlenecks and improve a process over time.

We invested heavily in automations — scheduled triggers, conditional logic, and the ability for automations to chain together. Processes need to run themselves as much as possible.

And we built multi-homing — a single record can live in multiple workspaces while keeping its data synchronized. A customer request tracked by both support and engineering, without duplication.

The simplicity tension

The honest challenge is this: how do you add process management depth without losing the simplicity that made Blue work in the first place?

Our answer is to separate the complexity. Administrators who configure processes can access powerful tools — automations, custom fields, permission rules. But the people working inside those processes see a clean, simple interface that tells them what to do next. The complexity is in the setup, not the daily experience.

The real competition

When I think about what we’re really competing against, it’s not other software. It’s the chaos of email threads, sticky notes, and loosely connected spreadsheets. The real shift isn’t from one tool to another — it’s from no process to a managed process.

That’s what Blue is for.

— Manny