Quaylight
Freight CRM with MCPOne CRM where every quote request, inbox thread and port update lands on the same shipment lead, and AI agents work under the same roles as people.
- 14
- modules
- 8
- channels in one inbox
- 120+
- MCP tools
Ten years building data platforms, internal tools and AI workflows for logistics, rail and travel teams in Europe and the US. Founder of Lindfors Studio. Builder of Tallyhour.
Open to forward deployed engineer and solutions architect roles. Remote, or on site across Europe.
Rhea Lindfors
Forward Deployed Engineer, Helsinki
Deleted on day one. Every handover ships with runbooks and training.
The numbers behind the work, from ten years of client projects.
RheaOS
Version 10.0, Helsinki build
Rhea Lindfors, Forward Deployed Engineer. Grew up in Oulu, on the Gulf of Bothnia, based in Helsinki.
I trained as a land surveyor and wrote my first script to clean up field data. I never went back to the theodolite.
Each window runs a short loop of the product flow. Open one to read how I built it.
One CRM where every quote request, inbox thread and port update lands on the same shipment lead, and AI agents work under the same roles as people.
A desktop timer for Windows, macOS and Linux and a web app that turns each tracked hour into a timesheet, an invoice line and a payroll entry.
One dashboard for every control and risk on a rail upgrade programme, with owners, due dates, alerts and exports.
A mobile booking app for island hoppers and a dashboard for the ferry operator, kept in sync in real time.
Four steps from the first call to a team that owns the system without me.
Step 1 of 4, week 1
Week one where the work happens: ops calls, shared inboxes, the spreadsheet everyone fears. I map where the hours go.
Release notes from every role, newest first.
AI agents, MCP servers and internal tools built inside client operations.
Time tracking SaaS used by 2,400+ people.
Scoped, designed and priced systems for logistics, rail and travel clients.
Built data products for port and rail operators and hired the first engineers.
First paying clients: survey data tools, web apps and internal tools.
$ rhea ls --installed
18 packages, all in daily use
Side projects between client work. Run each one to see what it does.
An open-source command-line tool that turns messy CSV exports into typed tables in one pass.
A live map of every ferry crossing in the Helsinki archipelago, built on open data.
A business card that runs a tiny terminal: type help, get my CV.
Clients who hired Lindfors Studio, the studio I run, in their own words.
“Rhea spent her first week on the dock with our crew. By week three, bookings and boarding finally matched, and the team trusted the numbers.”
“Every control and risk in one place, with exports our auditors accepted the first time. Rhea made a messy programme feel calm.”
“Our forwarders now answer quote requests in minutes, not hours. Rhea built it with them, not just for them.”
Open to roles
Open to forward deployed engineer and solutions architect roles. Remote, or on site across Europe.
Short answers. Anything else, send it by mail.
Lindfors Studio keeps two long-term clients. In a full-time role, my working hours go to your customers.
Helsinki, Finland, on Eastern European Time. I work across European and US East Coast hours and travel for on-site work.
Week one with your customer’s team, a pilot live by week three and a production plan by week four.
TypeScript and Python most days, React on the front end, and Claude or OpenAI behind the AI features. I learn the customer’s stack first.
Tell me about the role, the customer or the system. I read every message myself.
00:00:00
Helsinki, Finland
AI CRM for freight forwarders, with native MCP
One CRM where every quote request, inbox thread and port update lands on the same shipment lead, and AI agents work under the same roles as people.
Quote requests arrived by email, phone and three booking portals, so forwarders lost loads to faster competitors, and the sales team wanted AI assistants in the CRM without opening every account to them.
A multi-tenant data model with roles checked on every request; an MCP server with OAuth so Claude, ChatGPT and Cursor work with live data under the user’s role; an inbox that merges email, chat and portal messages into one thread per shipment.
Built for Northpine Freight.
Time tracking SaaS for studios and agencies
A desktop timer for Windows, macOS and Linux and a web app that turns each tracked hour into a timesheet, an invoice line and a payroll entry.
Tallyhour had grown to 12 modules built by four contractors and felt like four products. It needed one design system without breaking an API, a route or a permission.
An Electron tracker with idle detection and offline sync, a live team feed, approvals, invoices and payroll exports, and an assistant on Claude with its own MCP server.
Risk and control register
One dashboard for every control and risk on a rail upgrade programme, with owners, due dates, alerts and exports.
Hundreds of contract controls needed weekly updates, risks had to be tracked for cost and delay, and the client, contractors and auditors needed the same picture.
A controls table that flags overdue dates, a risk register from insignificant to major, calendar sync, comments on each control, Excel and PDF exports and two-factor sign-in.
Built around the Kestrel Valley Rail Upgrade programme.
Booking app and operator dashboard
A mobile booking app for island hoppers and a dashboard for the ferry operator, kept in sync in real time.
Passengers needed to book a crossing in under a minute on a phone, while the operator needed one live view of sailings, seats and crew.
A mobile-first booking flow with a route map and a full fare breakdown, plus an operator dashboard for sailings, bookings, crew and revenue, synced live.
Built for Saltwind Ferries.