Build a roadmap

FY27 Product Roadmap: Path to 112% NRR

To: Tom Achebe (CEO), CFO, CRO, CTO From: Staff PM Subject: Pre-read: Proposed Q4 2026 – Q3 2027 Product Roadmap

---

1. The FY27 Roadmap (Q4 2026 – Q3 2027)

To hit 112% NRR by the end of Q3 2027, we need $6.88M in net expansion ARR (8% of our $86M base). Because expansion revenue only counts toward Q3 NRR if it is live, rolled out, and generating spend before the end of Q3, this roadmap front-loads our highest-conviction NRR drivers and protects our core card infrastructure.

Note on Capacity: Each existing squad has 11 squad-weeks (SW) per quarter. Cross-squad work incurs a 1.5× penalty (e.g., 4 SW of native work takes 6 SW for a borrowing squad). New squads are modeled using our historical hiring baselines: 6 months to onboard and 50% capacity (5.5 SW) in their first active quarter.

Q4 2026: Clear the Decks & Lock In Quick Wins

• Cards: Processor v2 Migration (11 of 18 SW). Outcome: Protect 58% of Harbor’s revenue ahead of the March 31 hard deadline.
• Approvals & Policy (A&P): Multi-Entity Support (10 of 10 SW). Outcome: Unlock $2.9M ARR subsidiary expansion pipeline.
• Platform: Multi-Entity Support (11 of 12 SW). Outcome: Same as above; ships in week 1 of Q1.
• Integrations: Sage Intacct Integration (9 of 9 SW). Outcome: Slash gross churn from 13% to ~7% across 17% of our customer base (~$880k ARR saved) and remove the blocker in 31% of lost new-logo deals.
• Expenses: Receipt-Matching Improvements (6 of 6 SW); begin Mobile App Rewrite (5 of 22 SW). Outcome: Cut our #1 support ticket driver to free up engineering on-call capacity; start retiring late-2027 mobile framework debt.

Q1 2027: Cutover v2 & Launch Multi-Entity

• Cards: Finish Processor v2 Migration (3 SW in Weeks 1–3), Freeze for Certification (Weeks 4–7), Cutover (Week 8). Start Virtual Cards for SaaS (8 of 10 SW, built on v2 environment). Outcome: Zero card downtime on March 31; pull Virtual Cards launch into early Q2.
• A&P: Assist Cards on Processor v2 Migration (6 SW = 4 native Cards SW in Weeks 1–6); Real-Time Spend Controls (4 of 4 native SW). Outcome: Crucial cross-squad assist ensures Cards hits the Feb 1 code freeze for v2 certification.
• Platform: Finish Multi-Entity (1 of 12 SW); SSO & SCIM Provisioning (5 of 5 SW); Multi-Entity customer onboarding & scale hardening (5 SW). Outcome: Ship Multi-Entity in January for immediate CS expansion selling; unlock $1.2M new-logo pipeline and protect 11 enterprise renewals.
• Integrations: Microsoft Dynamics Integration (11 of 12 SW). Outcome: Retain the 3% of base on Dynamics and remove the 8% new-logo blocker.
• Expenses: Mobile App Rewrite (11 of 22 SW). Outcome: Hit 73% completion on mobile debt retirement without hiring dependencies.

Q2 2027: Capture the $410M Card Spend Opportunity

• Cards: Finish Virtual Cards for SaaS (2 of 10 SW—Ships April); Real-Time Spend Controls (8 of 8 SW—Ships June). Outcome: Capture share of the $410M in off-Harbor software spend ($4.5M total interchange pool) requested by 43% of top customers; give 52% of top CFOs the point-of-sale controls needed to move remaining company spend to Harbor.
• A&P: Spend Controls integration support & policy templates (4 SW); Discovery & v2 Architecture for Light Vendor/PO Workflows (7 SW). Outcome: Ensure rapid adoption of Spend Controls; re-architect our procurement approach (see The Case below).
• Integrations: Finish Dynamics (1 of 12 SW); ERP syncing for Virtual Cards & Multi-Entity (10 SW). Outcome: Ensure seamless reconciliation for expanded multi-entity and SaaS card spend.
• Platform: Card spend limit notifications, alerting & multi-entity RBAC (11 SW). Outcome: Drive self-serve adoption of Virtual Cards across existing accounts.
• Expenses: Finish Mobile App Rewrite (6 of 22 SW—Ships May); Card spend receipt automation (5 SW). Outcome: Retire framework support risk 6 months ahead of CTO deadline.
• New Squad A (Ramping: 5.5 SW): Build self-serve migration tools for recurring SaaS bills to Virtual Cards. Outcome: Accelerate time-to-interchange for Virtual Cards.

Q3 2027: Drive Adoption to Lock In 112% NRR

• Cards & Platform: Automated SaaS vendor detection (flagging invoice spend in ERP to convert to Virtual Cards) & card limit auto-top-ups. Outcome: Maximize interchange realization before Q3 closes.
• A&P, New Squad A (11 SW) & New Squad B (5.5 SW): Build redesigned intake-to-card workflows (issuing single-use PO virtual cards upon approval). Outcome: Monetize approval workflows via interchange and seat expansion rather than competing head-on with entrenched procurement suites.
• Integrations & Expenses: In-app onboarding and bulk-provisioning tooling for Multi-Entity subsidiaries. Outcome: Help CS close the remaining 52 subsidiaries before EOY.

---

2. The Case for This Roadmap

Why This Order? (The Math to 112% NRR)

To add $6.88M in net ARR by the end of Q3 2027, we must prioritize high-margin revenue protection and high-velocity expansion that can land in H1 2027: 1. Stop the bleeding via Intacct & SSO (+$0.9M to $1.1M ARR retained): NRR is a net number; every dollar of churn avoided is a dollar of expansion we don't have to sell. 17% of our base (~$14.6M ARR) uses Intacct via CSV and churns at 13% vs. 7% for NetSuite. Fixing this in Q4 saves ~$880k/yr in gross churn and unlocks 31% of lost deals. Pairing this with SSO/SCIM in Q1 secures 11 enterprise accounts under security review. 2. Ship Multi-Entity in week 1 of Q1 (+$1.8M to $2.9M ARR): 9 top customers have committed in writing to add subsidiaries once live. Sizing all 52 subsidiaries in the top-60 cohort equals $2.9M ARR—and more exist across our other 1,040 customers. Shipping in January gives CS three full quarters to close and onboard these entities. 3. Unleash Card Spend in Q2 (+$2.5M to $3.5M ARR): Our customers spend $410M/yr on software off-Harbor. At 1.1% net interchange, that is a $4.51M high-margin revenue pool sitting inside our existing base. Nearly half (26 of 60) of our largest accounts are actively asking for Virtual Cards for subscriptions, and 31 CFOs want Real-Time Spend Controls. Unlike new modules that require procurement cycles and legal sign-off, turning on virtual cards for existing customers generates interchange revenue the day a card is swiped.

Combined with our baseline 104% NRR ($3.44M), capturing just half of our conservative targets across these three pillars puts us at 112.5% NRR ($96.8M ARR) by Q3.

What Changed from Tom’s Draft—and Why

1. Resolving the March 31 Card Processor Crisis Tom’s draft had the Cards squad doing the 18-SW v2 migration across Q4 and Q1. However, Cards only has 11 SW per quarter. Furthermore, the processor requires a 4-week certification freeze before the March 31 cutover. To cut over by March 31, code must be finished by February 26 (Week 8 of Q1). In 19 weeks of calendar time, the Cards squad only has ~17.5 SW of capacity—leaving zero margin for error and pushing Virtual Cards into late Q2/Q3. * The Fix: In Q1, Approvals & Policy gives 6 SW of capacity (yielding 4 native SW at the 1.5× cross-squad rate) to the Cards team. This finishes all 18 SW of v2 code by the end of January, allowing certification in February, safe cutover in early March, and pulling Virtual Cards forward by 6 weeks.

2. Replacing the $6M Procurement Bet with Card Expansion Tom’s draft relies on Procurement to add $6M ARR in year one. The customer and capacity math does not support this: * The Revenue Math: At $8/month ($96/yr) for the 10% of employees who raise purchase requests (70 users per average 700-person customer), 100% adoption across all 1,100 customers would only generate $7.39M ARR. To hit $6M in Year 1, we would have to sell an unbuilt add-on to 81% of our entire customer base in two quarters. Yet in our design partner trial, 4 of 6 customers already had a procurement tool and refused to switch, and only 2 (33%) were willing to pay. Realistic Year-1 ARR is ~$500k–$900k. * The Capacity Math: Procurement requires 30 SW from A&P and 6 SW from Integrations. Tom assigned this to "New Squad A" starting in Q1. Last year, our new squads took 5 to 8 months to reach their first sprint, and delivered 50% capacity in their first quarter. Approved in September, Squad A won't run a sprint until Q2 2027 (delivering ~5.5 SW), and as a brand-new squad working in A&P's domain, they face the 1.5× ramp penalty. Assigned to Squad A, a 36-SW Procurement module would not ship until Q1 2028—contributing $0 to FY27 NRR.

3. De-risking the Mobile App Rewrite Tom assigned the 22-SW Mobile Rewrite to "New Squad B" in Q2. Approved in September, Squad B likely won't start until Q3 2027 at half capacity (5.5 SW), missing the CTO’s late-2027 framework end-of-life deadline. By keeping our existing Expenses squad on Mobile starting in Q4 (after a 6-SW sprint on Receipt Matching), we complete the rewrite in Q2 2027 with zero hiring dependency.

What We Are Not Doing

• We are not building a standalone, 36-SW Procurement Module in H1. We cannot justify starving Multi-Entity and Spend Controls to build a module that 67% of design partners rejected and that cannot ship in time to impact FY27 NRR. Instead, in Q2/Q3, we will explore lightweight PO-to-Virtual-Card workflows that drive card spend rather than competing with Coupa or Zip.
• We are not counting on un-hired squads for critical-path H1 deliverables. New Squads A and B are scheduled for Q2 and Q3 respectively, focused on adoption tooling and H2 expansion where hiring delays won't threaten our board target or infrastructure deadlines.

Key Risks That Could Change This Plan

1. Processor v2 Certification Rejections: If the processor finds bugs during the 4-week February certification window, our freeze extends and delays Virtual Cards. Mitigation: By using A&P to help finish the build in January, we buy a 4-week buffer before the March 31 cliff.
2. Cross-Squad Ramp Friction: Having A&P take on 4 SW of Cards work (costing 6 SW) in Q1 requires clean work partitioning. Mitigation: Cards will own the core v2 authorization webhooks; A&P will own isolated migration scripts and fallback testing.
3. Slower Multi-Entity Sales Cycles: While 9 accounts gave written intent, parent-subsidiary contract addendums can stall in legal. Mitigation: CS and Finance must pre-negotiate subsidiary pricing addendums with the 14 target accounts in Q4 so we can bill immediately upon the January release.

Harbor FY27 roadmap: expand existing customers first

For the planning offsite | Q4 2026–Q3 2027

Recommendation: protect card continuity, unlock committed subsidiary expansion, then bring more existing-customer spend onto Harbor. Treat procurement as a commercial hypothesis to validate—not as committed revenue or a committed launch.

Board outcome: raise NRR from 104% to 112% by the end of Q3 2027. This roadmap supports that goal; the available evidence does not yet establish a credible revenue bridge all the way to 112%.

1. Proposed roadmap

Planning rules

• Commit against the five existing squads, each with 11 squad-weeks per quarter. Neither new squad is on the critical path.
• Numbers below are squad-weeks. Named feature estimates come from the pack; remaining capacity is an allocation ceiling for rollout, validation, hardening or contingency, not an estimate for additional features.
• Cross-squad delivery uses the stated 1.5× cost.
• Adoption work targets expansion and retention in existing accounts. It is not a placeholder for additional module builds.

Critical-path checks

• Processor migration: Q4 delivers 11 Cards weeks + 4 equivalent weeks from Expenses = 15. Q1 delivers the final 3, reaching the required 18. The February certification target creates margin before the hard retirement date.
• Certification freeze: no changes to the certified implementation during the four-week processor window. Before committing dates, confirm the precise freeze scope, book the processor slot and agree cutover acceptance criteria.
• Multi-entity: Approvals & Policy completes its 10 weeks in Q4; Platform completes 11 + 1. Therefore this is a Q1 launch, not a Q4 launch.
• Spend controls: Expenses spends 12 actual weeks across Q2–Q3 to deliver 8 Cards-equivalent weeks; Approvals & Policy supplies its 4 weeks in Q2. Work begins only after v2 is live.
• New squads: plan no committed output until teams are staffed and their ramp is observed. Use initial capacity for bounded adoption, testing or hardening work; allocate larger scope only after a delivery review.

Outcome scorecard

CS, Sales and Finance should turn these into named-account activation targets and a revenue bridge at the offsite. We should not invent conversion forecasts from the current pack.

2. The case for the plan

Why this order

First, protect the revenue engine. Every card authorisation uses an API retiring on 31 March, and interchange represents 58% of revenue. Tom’s migration occupies 18 of Cards’ 22 available weeks across Q4 and Q1, but must also leave four calendar weeks for certification. Quarterly capacity alone does not prove that schedule is safe.

Borrowing six Expenses weeks moves four Cards-equivalent weeks into Q4. That leaves only three planned migration weeks in Q1 and creates room for defects and certification. Receipt matching slips slightly; card continuity takes precedence.

Second, prioritise expansion with identifiable buyers. Multi-entity has the strongest evidence of a concrete expansion action: nine parents have committed in writing. The full 52-subsidiary opportunity is $2.9M ARR, but we cannot treat that total as committed or infer how many subsidiaries the nine parents represent. Launch in Q1, then sell and onboard—not merely ship.

Third, pursue spend expansion in parallel. Virtual cards have a direct connection to software spend currently outside Harbor. Controls address the most frequently expressed card need in the QBRs and may make finance teams comfortable moving more spend onto Harbor. Borrowing Expenses capacity costs four additional squad-weeks versus specialist delivery, but avoids serialising both products through Cards and supports an early-Q3 controls launch.

The $410M software-spend estimate implies a $4.51M annual net-interchange ceiling at 1.1%, before accounting for capture rates, timing or spend that cannot move from invoice to card. It is an opportunity, not a forecast. Both features may affect the same spend; we will not double-count it.

Fourth, remove retention and expansion friction. Intacct serves 17% of existing customers, versus 3% for Dynamics. The 13% versus 7% churn difference is an association, not proof the integration causes better retention, but it supports prioritising Intacct. SSO/SCIM is relatively small and addresses 11 existing-account security reviews. Receipt matching targets the largest expense support problem.

What changes from Tom’s draft

• Hiring no longer funds commitments. Historical time to the first full sprint was five to eight months, with half-capacity delivery in the first quarter. September approvals do not justify a full squad in Q1 and another in Q2. Further, new squads taking specialist work incur the stated transfer cost.
• Migration gains early borrowed capacity and an explicit certification window. Virtual cards no longer competes with the deadline in Q1.
• Multi-entity launches in Q1. Platform’s 12-week estimate exceeds one quarter’s 11-week capacity.
• Procurement moves from committed launch to commercial validation. Its revenue claim is not supported by current evidence.
• Controls gets borrowed delivery capacity. This creates an earlier adoption window without relying on hiring.
• Dynamics and the mobile rewrite leave the committed horizon. The freed capacity supports existing-customer outcomes and schedule resilience.

Why procurement is not the anchor

At the proposed price, an average customer has 70 requester seats and contributes:

70 × $8 × 12 = $6,720 ARR.

Reaching $6M ARR requires approximately 893 average-sized customers—81% of today’s customer base. Only two of six design partners said they would pay; neither is described as a signed commitment. Four already have a competing tool.

The estimated build is 30 Approvals & Policy weeks plus six Integrations weeks, before any additional cross-squad cost. That is too large a bet to anchor this year’s NRR target without stronger evidence.

Validation should seek paid commitments, actual seat counts and evidence of a differentiated switching reason. It is not an unbudgeted production build. A successful gate triggers an explicit investment decision, identifying displaced work and a capacity-backed launch date.

What we are not doing

We are not committing to procurement launch or its $6M claim, Dynamics, or a 22-week mobile rewrite in this horizon. We are also not inventing new feature scope to consume every available week.

The mobile support deadline remains real. By Q3, the CTO must establish the exact end-of-support date and a funded maintenance, upgrade or rewrite path. If continued safe operation requires starting earlier, it returns as a mandatory trade-off—not an assumed new-squad assignment.

Risks that could change the plan

The largest execution risks are processor certification availability, migration work that cannot be delegated, and underestimated multi-entity or controls complexity. Validate the processor work split immediately; any threat to certification displaces discretionary work first.

The largest commercial risk is insufficient expansion capture. At an illustrative $86M opening cohort, an eight-point NRR improvement represents $6.88M more retained/expanded ARR than a 104% outcome. Finance must reconcile the actual cohort and baseline. Even the full multi-entity and software-card opportunity totals only $7.41M before timing, conversion and overlap effects. This plan does not justify promising 112%.

Review the revenue bridge after Q1 launches. Weak activation should shift capacity toward removing proven adoption blockers. Strong paid procurement evidence, an earlier mobile security deadline, or demonstrated new-squad capacity can justify a replan—but none should silently become an assumption today.