The Operations Backbone
SFT's state-government ESA platform runs on a Smartsheet substrate designed for 18 state customers before scale arrived.
Each new state arrives with its own implementation timeline, ticket flow, governance trail, and stakeholder structure. The default response is per-customer one-off tooling, ticket flows that don't reconcile across the three ticketing systems, governance kept in email threads, and no master view across the portfolio. That default carries an operating cost that is invisible at customer two and dominant by customer five.
The move was to treat the substrate as the load-bearing artifact, not the operations running on top of it. From day one, the Smartsheet backbone was designed for an 18-client portfolio (5 workspaces, ~55 sheets, 15 reports, 6 dashboards), with 2 client slots activated (WV Hope, TN EFS) and 16 placeholders ready for the next state customer to drop into a known shape. The alternative was per-customer one-offs reconciled later, which is the move every implementation team considers and most regret. A second move stacked on top: pull the state-agency customer into the schema as a co-author, not a consumer. The WV State Treasurer's Office took a co-design role on the User Issue Support Request tracker, reimagining and creating new fields inside the schema. State customers do not normally redesign their vendor's tracker fields. WV STO did, because the substrate was built to invite it.
A Smartsheet operations backbone: 5 workspaces, ~55 sheets, 15 reports, 6 dashboards. A three-system ticket integration (HEC/Softy CRM to Smartsheet to the SFT ticketing system) spanning a 4-organization shared support queue (SFT, Mpathic, WV STO, Arete Scholars). A 34-decision state-agency governance log with WV STO decision-makers named by title (Assistant Treasurer, Scholarship Program Executive Director), audit-ready. A 65-row WV Hope implementation plan across 4 phases (78% complete at the September 2025 snapshot), a 102-row Production Development Plan capturing 17 platform feature signoffs February to June 2025, plus 88-row WV Hope and 66-row TN EFS user-flow documentation across 8 user types. Currently shipping a multi-client standardization layer: unified User Issue Support Request and Feature Request boards flowing up into master boards for SFT Tech and Engineering.
Without it, per-customer one-offs reconciled in email threads and a new round of architecture work for every new state. With it, a substrate that has carried 491 tickets at ~24/month over 20 months, captured 17 platform feature signoffs and 34 state-agency decisions, and stands ready for 16 more state customers without re-architecture.
The right time to build for eighteen customers is the day you have two.