FLO, Internal Project Management

The Problem

The team at Stolen Goat was using three separate off-the-shelf tools to manage their workflow: one for project tracking, one for invoicing, and one for customer relationship management. None of them talked to each other, data was duplicated across systems, and the workflow required constant manual effort to keep everything in sync. Worse, none of them matched how the team actually worked, every tool required workarounds.

What I Built

FLO, available internally on the Stolen Goat network, is a custom project management tool built from the ground up to match the team's actual workflow. It combines kanban-style project boards, invoicing functionality, and customer tracking into a single application, replacing all three off-the-shelf tools with one purpose-built solution.

The application is built with Typescript and PostgreSQL, providing a robust, performant backend with a full REST API. That API is the critical integration point, it's how Flo-bot plugs in to the data, to detect status changes and trigger automations.

Key Features

• Kanban project boards: Visual project tracking that mirrors the team's actual workflow stages, from enquiry through to delivery.
• Integrated invoicing: Generate and track invoices directly from project data, no re-entering information into a separate system. The team can generate invoices and track payments.
• Full REST API: Every piece of data in FLO is accessible via API, making it the backbone of the automation engine.
• Customer tracking: Centralised customer records linked to projects, communications, and financial data.
• New custom kit inquiries pipe straight into the tool, ready to go.

The Automation Backbone

FLO isn't just a project management tool, it's the central nervous system for the entire automation stack. When a team member drags a project card to a new status column, that change propagates through the API to Flo-bot, which then triggers the appropriate automations: email drafts, webshop builds, supplier orders, or follow-up schedules. The tool was designed from day one with this integration in mind.

Impact

Three separate subscriptions replaced with one custom tool. No subscriptions, no seat based payments. No more data duplication or manual syncing. The team works in a single interface that matches their actual process, and every action they take can trigger downstream automations. The API-first architecture means the system grows more capable over time without requiring changes to the core application.