FSI Services

Snapshot

What they do

FSI builds cloud maintenance and asset management software for healthcare organisations — the system hospital facilities and healthcare technology teams run work orders, equipment and assets on. Founded 2002, based in Cranberry Township, Pennsylvania, with on-site data collection services alongside the software.

Scale

Their platform actively manages over 650 million square feet of hospital space each year, and the on-site data-collection standards they helped develop have been taken up by bodies including ASHE.

Delivery

Co-delivered by Value-First Team and USS.

The relationship

Aug 2026

Introduced, with a written brief describing revenue-operations work centred on the handoffs between Sales, Customer Success and Finance.

13 Aug 2026

Ryan Ginsberg's written response delivered, including one recommendation they could act on immediately whether or not they engaged us.

14 Aug 2026

First conversation scheduled.

Where they started

The pressure sits at the seam between Sales, Customer Success and Finance. When a SaaS contract closes, the services detail and the revenue-recognition detail attached to it have to reach Finance accurately — and that path does not run inside one system. It crosses HubSpot and the finance stack, which means it belongs to nobody in particular and breaks quietly when it breaks at all.

Underneath that sits the more expensive problem: the part of the process that was never written down. Which fields Finance actually needs off a closed contract, which of those get corrected by hand every month, and what the real exceptions are — that knowledge lives in individual practice rather than in documented process. It is invisible while the people who hold it are in their seats, and it is the first thing to go missing when they are not. Renewal workflows sit downstream of the same seam.

What we delivered

One action worth taking immediately, independent of any decision about us. Record a walkthrough of a single real closed contract, end to end — from signature through to what Finance actually receives, including every correction made by hand along the way. An hour of that outweighs a month spent reconstructing it later.
Evidence from the same work, not a claim about it. Roughly 400 contracts migrated into HubSpot's Contract object on a live production portal last month, alongside a HubSpot-to-NetSuite revenue sync.
The diagnostic judgement the seam actually needs. Forty finance-sync alerts in a single minute turned out to be one problem, not forty — a weekend queue releasing at once and exceeding what the finance system runs in parallel. Five alerts reported missing product codes; four of the five were wrong, because the lookup that confirms a product was blocked by the same overload and reports "missing" when what it means is that it could not check. Nothing was double-charged and nothing double-paid, because the integration refused to act anywhere it could not first confirm what the finance system already held. Telling the difference between your data being wrong and the thing reporting on your data being wrong is the whole job.
A working model stated plainly. Embedded and hands-on rather than an agency with a project manager in front of it. One to two hours of meetings a week, executing independently the rest of the time, on a flat monthly basis with no hourly meter — so no one is deciding whether a question is worth an hour.
A named risk in their own plan. Replacing one person with one person reproduces the exact exposure that created the problem. Named alongside the answer: a second person who knows the portal well enough that a holiday or a bad flu is not an outage.
An honest boundary. If what is needed is mostly ticket-queue coverage inside HubSpot, there are cheaper people who do that well and they should hire one.
Something worth knowing for later, flagged as later. HubSpot's Contract object now handles term of record and renewal chaining natively — a materially better foundation than most renewal workflows are built on, and worth a look once continuity is stable rather than during the transition.

What changed

The brief asked for someone to hold the line. The response named what was actually at risk — not the tasks, which can be picked up, but the undocumented judgement underneath them — and turned it into a single concrete action they could take this week without hiring anyone at all. That is the difference between a proposal that begins when a contract is signed and one that starts being useful the day it is read.

The second thing to change was how the hire itself gets assessed. It arrived framed as a continuity problem to be solved by finding one capable person. It came back with the observation that one capable person with no backup is the same arrangement that just failed, which makes coverage a question to ask of any candidate rather than a detail to discover later.