Quantifies the case for modernizing the legacy benefits portal, built to the same structure as the CBAs in the PM and Agile suites but scoped to a single Firm-Fixed-Price Task Order rather than a multi-year program.
Alternatives Considered
| Option | Assessment |
|---|---|
| Continue legacy platform, no modernization | Not viable — incumbent vendor's end-of-support timeline forces a decision on FOPBA's schedule, not a discretionary one. Also fails Section 508 and lacks a current ATO. |
| Minimal remediation (accessibility patches only, no replatform) | Rejected — addresses one compliance gap but not the underlying platform's security posture or the vendor sunset risk; would require a second modernization effort within 2-3 years |
| Full replatform (this Task Order) | Selected — addresses accessibility, security/ATO, and vendor sunset risk in a single effort |
Quantified Benefits (Annual, Post Go-Live)
| Benefit Category | Annual Value | Basis |
|---|---|---|
| Legacy platform license/maintenance elimination | $310,000 | Vendor contract sunset upon cutover |
| Reduced manual/phone-assisted applications | $180,000 | Improved self-service completion rate |
| Avoided accessibility non-compliance risk | $120,000 | Estimated remediation-under-pressure cost avoided |
| Reduced help desk ticket volume | $80,000 | Improved UX reduces support burden |
| Increased mobile self-service completion P00011 | $140,000 | Mobile-responsive redesign — original portal was desktop-only |
| Caseworker time savings P00011 | $260,000 | Real-time Eligibility API replaces manual phone verification |
| Avoided mobile-specific accessibility risk P00011 | $70,000 | Closes the mobile accessibility gap the original scope left open |
| Total Annual Benefit | $1,160,000 |
The three P00011-tagged rows are new benefit categories tied specifically to that Modification's added scope — they exist because the scope grew, not because the original four categories got recalculated bigger. See the Contract Mod Log.
Non-Quantified Benefits
Several benefits are real but deliberately excluded from the quantified total above because they resist reliable dollar estimation: reduced litigation/complaint risk from Section 508 non-conformance (accessibility complaints against federal agencies carry legal exposure that's real but speculative to price); improved applicant experience and program reputation for FOPBA; and reduced institutional risk of running an unauthorized system (no current ATO) past the point FOPBA's own security office would tolerate. Leaving these out keeps the quantified case conservative rather than padded.
Sensitivity Analysis
| Scenario | Payback Period | 7-Yr ROI |
|---|---|---|
| Base case (as modeled above) | ~6.6 years | 5.4% |
| Benefits realized at 80% of estimate (conservative) | ~8.3 years | -15.7% |
| Benefits realized at 120% of estimate (optimistic) | ~5.5 years | 26.5% |
| Option Period not exercised (Base Period investment only) | ~5.5 years | 27.4% |
Unlike the pre-Mod base case, this one does not stay positive under the conservative scenario — at 80% benefit realization, the 7-year case goes negative. That's shown plainly rather than adjusted away: a much larger, scope-driven investment (P00011) naturally carries a thinner margin than the original replacement did on its own, and the honest sensitivity range reflects that. This doesn't change the recommendation (see below) — it's a data point for how much execution risk this specific scope addition carries, on top of a replacement that was already mandatory regardless.
Why the Payback Period Moved Out (Twice)
An earlier estimate priced this Task Order around a 7-person leadership-only team and showed a ~3.1-year payback. Once the Resource Plan was corrected to include the developers, DevOps engineer, and second QA tester actually needed to build and sustain the portal, the investment grew from $2,140,000 to $3,550,000 — pushing payback out to ~5.1 years and the 5-year ROI slightly negative. Extending the horizon to 7 years kept the case solidly positive at 36% ROI. This was a more honest number than the original estimate: a thin leadership-only team was never going to actually deliver the system, so its rosier payback math wasn't real.
More recently, Contract Modification P00011 added genuine new scope — a mobile-responsive redesign and a Benefits-Eligibility Verification API integration — growing the investment from $3,550,000 to $7,704,000 and the team from 13 to 35. Unlike the earlier correction, this wasn't a staffing fix for existing scope; it came with real new benefit categories of its own (mobile self-service completion, caseworker time savings, mobile accessibility risk avoidance — see the table above), which is why the case stays positive rather than collapsing outright. But the margin is much thinner than before: 7-year ROI drops from 36% to 5.4%, and payback moves from ~5.1 to ~6.6 years. That's the honest result of a much bigger, scope-driven investment layered on top of an already-mandatory replacement — not a sign the analysis is wrong.
Cross-Reference
Investment figure ties to the Task Order Budget total ($7,704,000, reflecting Contract Modification P00011). Legacy decommissioning benefit assumes the current CareLink-style legacy contract is not renewed after cutover, consistent with the PWS scope. Figures are illustrative for portfolio demonstration purposes.