NORTHWIND LOGISTICS - Q3 PLATFORM REVIEW Meeting notes | 14 August 2026 | Attendees: Priya Raman (VP Engineering), Daniel Osei (Product), Mei Lin (Data), Tom Bradley (Finance), Sara Whitfield (Customer Success) 1. CONTEXT Northwind Logistics operates a freight tracking platform used by 4,200 shippers across North America and Western Europe. The Q3 review covered platform reliability, the migration off the legacy routing service, customer churn in the mid-market segment, and the 2027 budget envelope. Revenue for the quarter was 18.4 million dollars, up 11 percent year over year but 4 percent below the internal plan of 19.2 million. The shortfall came almost entirely from the mid-market segment, where net revenue retention fell to 96 percent from 108 percent in Q2. 2. PLATFORM RELIABILITY Priya reported that platform availability was 99.87 percent against a 99.95 percent target. Three incidents drove the miss: - A 47 minute outage on 3 July caused by connection pool exhaustion in the shipment ingestion service during a bulk upload from a single large customer. - A 22 minute degradation on 19 July when a schema migration locked the shipments table. - A 96 minute partial outage on 8 August affecting only the European region, traced to an expired TLS certificate on the internal routing gateway that nobody was alerted about. The certificate expiry was the most embarrassing of the three because it was entirely preventable. Priya committed to having automated certificate monitoring in place before the end of September, with paging alerts at 30 days and 7 days before expiry. Ownership sits with the platform team. Mean time to recovery across the three incidents was 55 minutes, well above the 20 minute internal goal. The main contributor was on-call engineers not having runbooks for the routing gateway. Daniel asked whether the runbook gap was tracked anywhere; it was not, so Priya agreed to open a tracking epic and report progress at the next monthly review. 3. LEGACY ROUTING MIGRATION The migration off the legacy routing service is 68 percent complete by traffic share. The remaining 32 percent consists of two customer cohorts: - Enterprise customers with custom routing rules, roughly 24 percent of traffic. These require per-account validation and cannot be batch migrated. - A long tail of small accounts, roughly 8 percent of traffic, blocked on a rate limiting bug in the new service that surfaces only under bursty load. Mei flagged that the legacy service contract expires on 31 January 2027 and renewal would cost 840,000 dollars for another year. The migration must therefore complete by mid-January to leave a buffer for rollback. Tom noted that this is the single largest avoidable cost item in the 2027 budget and asked for a weekly migration burndown starting immediately. The rate limiting bug is the critical path item. Mei will assign a senior engineer to it this week and expects a fix in production within two weeks. If the fix slips past 15 September, the team will escalate to Priya for additional staffing. 4. MID-MARKET CHURN Sara presented churn analysis for the mid-market segment. Eleven accounts churned in Q3, representing 1.9 million dollars in annual recurring revenue. Exit interviews were completed for nine of them. The reasons cluster into three groups: - Six accounts cited missing customs documentation automation, which competitors ship as standard. This is the clearest product gap. - Two accounts cited reliability, specifically the August European outage. - One account consolidated onto a competitor after an acquisition, which was not winnable. Daniel accepted that customs documentation automation needs to move up the roadmap. It was previously slotted for Q2 2027. He will bring a revised scope and staffing proposal to the next product council on 28 August. Sara will provide the customer evidence pack to support prioritisation by 22 August. Sara also raised that the current health scoring model gave no warning for seven of the eleven churned accounts. Mei agreed to rebuild the model using support ticket sentiment and usage decay as additional features, targeting a first version by the end of October. 5. BUDGET AND HEADCOUNT Tom presented the 2027 envelope. Total platform spend is capped at 26.5 million dollars, a 6 percent increase over 2026. Within that: - Infrastructure is expected to fall by 1.1 million dollars once the legacy routing contract is eliminated. - Headcount grows by nine roles, weighted toward data engineering and customer success. - A 900,000 dollar contingency is held centrally for reliability work. Tom stressed that the contingency is not pre-allocated and any claim on it needs a written business case. Priya said she would submit one for observability tooling by the end of September. Hiring is behind plan. Four of the nine 2027 roles were meant to be filled early, in Q4 2026, but only one offer is out. Priya and Tom will review the pipeline together every two weeks until the gap closes. 6. DECISIONS TAKEN - Customs documentation automation is promoted to a 2027 H1 priority, subject to scope review on 28 August. - The legacy routing migration deadline is fixed at 15 January 2027. No extension will be requested. - The reliability contingency remains centrally held and requires a written business case. - Weekly migration burndown reporting starts this week and goes to the full leadership group. 7. RISKS - If the rate limiting bug is not resolved by mid-September, the January migration deadline is at serious risk and the 840,000 dollar renewal becomes likely. - Continued mid-market churn at the Q3 rate would remove approximately 7.6 million dollars of annual recurring revenue over a full year. - Hiring delays in data engineering would push the health scoring rebuild into 2027. 8. NEXT MEETING The next platform review is scheduled for 18 September 2026. Priya will circulate an agenda one week in advance. Standing items are reliability metrics, migration burndown, and churn.