About FlowHarbor

A small team in Seoul. Slow growth. Honest scope.

FlowHarbor was founded in 2019 in Seoul by a small team that had spent the previous decade running operational data programmes for Korean and South-East Asian manufacturers. We had grown tired of two patterns that recurred across those programmes: process maps that no one trusted because no one had agreed on the definitions, and tooling decisions made before the operational question had been written down.

We started FlowHarbor to do those two steps in the right order — first the definition, then the tooling — and we kept the company small enough that we could decline engagements where the order was reversed. We have walked away from prospects whose programme was better served by an internal review than by our platform; the public Process Lab outcome has occasionally been "do not buy our software."

Today we serve enterprise operations teams across the region with a process intelligence platform, a small set of advisory engagements, and an open community that anyone can join without a contract. Roughly a third of active community members are not platform customers and we expect that share to stay roughly where it is. Our growth has been by reference, slowly, and we are comfortable with that pace.

Four principles

What we keep coming back to

  • 01

    Definitions before dashboards

    A dashboard built on a contested definition produces an argument, not a decision. We resist starting with the chart and we resist hiding the definition behind it.

  • 02

    Bands, not single numbers

    Effort estimates and outcome ranges are reported with a low, likely, and high band. Single numbers are politically convenient and operationally misleading.

  • 03

    Failure stories are first-class

    Programmes that did not work are documented and published internally with the same rigour as the ones that did. The community follows the same norm.

  • 04

    Honest about our own limits

    We name the parts of the platform that underperform, the prospects we should not have taken, and the things we are still figuring out. This document is not a brochure.

Team · org chart

Seven people, openly named

We do not pretend to be larger than we are. The CEO currently doubles as head of product while we recruit; that is on the chart. Where we use stylised initials instead of a portrait, the person has chosen not to publish a photograph and we honour that.

Daniel Mwangi, Chief Executive Officer

Daniel Mwangi

Chief Executive Officer (acting Head of Product)

Founded FlowHarbor in 2019 after a decade running operations programmes for Korean and South-East Asian manufacturers. Sets the product direction and is the point of escalation for enterprise contracts.

  • Ji-hoon Park, Lead Process Mining Consultant

    Ji-hoon Park

    Lead Process Mining Consultant

    Twelve years working with Korean manufacturers on operational data programmes. Previously at a Big Four advisory practice. Leads discovery and bottleneck engagements.

  • So-young Kang, Solutions Architect

    So-young Kang

    Solutions Architect

    Designs the conformance scoring and variant analytics layers. Background in financial services compliance technology. Speaks with audit teams in their own register.

  • Hannah Reyes, Customer Success Manager

    Hannah Reyes

    Customer Success Manager

    Coordinates pilots, governance conversations, and worker council communications. Facilitates the Process Lab programme.

  • Aarav Mehta

    Growth Marketing Manager

    Runs the content programme, the events calendar, and the analyst-relations cycle. Joined in 2023 from a B2B SaaS background.

  • Min-soo Lee

    Data Integration Engineer

    reports to So-young Kang

Timeline · three milestones

Three things we are willing to mark as milestones

  1. 2019

    FlowHarbor founded in Seoul

    Three founders, one signed-off process map for a single Korean electronics manufacturer, and an explicit decision to refuse equity funding for the first three years.

  2. 2022

    Public community opened

    Opened the public community to non-customers after a year of internal-only beta. Moderation team formalised; code of conduct published.

  3. 2024

    Conformance Lens reaches financial-services release

    Released the conformance scoring layer with reviewer portal in a form audited externally for use by Korean financial institutions. Implemented after eighteen months of customer collaboration; we declined to ship the previous version because it was not ready.