What is NorthFloe

NorthFloe is a shared workspace where a consulting firm and its clients deliver software together. Clients, project managers, architects, developers and QA all work on the same items, so nobody has to copy a requirement from one tool to another.

The problem it solves

In most teams the same requirement gets copied several times:

• The client writes it in an email or a document.
• The PM copies it into a ticket.
• A developer rewrites it as a technical plan.
• QA reads it again and writes tests from their own understanding.

Each copy drifts from the others. When the client says “that’s not what I asked for”, nobody can show which version was built and tested.

NorthFloe keeps one requirement, and links everything else to it.

flowchart LR
    R["Requirement<br/>stories + acceptance criteria"] --> S["Spec<br/>how it will be built"]
    S --> T["Tasks<br/>the build work"]
    R --> TC["Test cases<br/>one per criterion"]
    T --> V{"All tests<br/>pass?"}
    TC --> V
    V -->|yes| A["Client<br/>accepts"]

Tasks and test cases both come from the same acceptance criteria. For any criterion you can see the code that delivers it and the test that proves it.

How it’s organised

flowchart TD
    F["Your firm"] --> C1["Client: Harbor Foods"]
    F --> C2["Client: …"]
    C1 --> P["Project: Harbor Ordering App"]
    P --> D["Project docs<br/>Business + Technical"]
    P --> FE["Features<br/>REQ-1, REQ-2, …"]
    FE --> RQ["Requirement"]
    FE --> SP["Spec · firm only"]
    FE --> TK["Tasks · firm only"]
    FE --> TS["Test cases + runs"]

Project docs

The background every feature builds on: the business problem, the users, the architecture, the tech stack.

Features

Work delivered one piece at a time. Each one moves through a fixed lifecycle, and every step has a clear owner.

Where to go next

The example used in this guideMeet the team and the project every page follows.

Signing in

Finding your way around

Roles and what they can do