NORTHBRIDGE SOFTWARE — Q2 OPERATIONS AND FINANCE REVIEW Prepared for the leadership team. Internal circulation only. PURPOSE OF THIS DOCUMENT This memo gathers the operational and financial picture for the second quarter into one place so that the leadership team can prepare for the half-year review without each function having to assemble its own narrative from scratch. It is intentionally comprehensive rather than concise. The goal is completeness: a single reference that captures where the business stood at the close of the quarter, what moved, what did not, and which threads we should pick up in the second half of the year. Nothing here is a decision. Decisions belong to the half-year review itself. This is the briefing material that should let those decisions be made quickly and with the full context in front of everyone. The quarter was, on balance, steady. We did not see the kind of dramatic swings that characterized the back half of last year. Revenue grew in line with the plan, costs grew slightly faster than we would have liked, and headcount landed almost exactly where we forecast. The most useful framing for the half-year conversation is probably this: the business is healthy and predictable, and the open questions are about where to lean in rather than where to put out fires. That is a more comfortable position than we have been in for some time, and the temptation that comes with it is complacency. This document tries to surface the places where steady performance is masking a slower-moving problem worth attention. HEADCOUNT AND ORGANIZATION We ended the quarter with two hundred and forty-one full-time employees, against a plan of two hundred and forty-four. The three-person gap is entirely in open roles we chose not to rush. Two of those are senior engineering positions where we decided that waiting for the right candidate was worth the short-term capacity cost, and one is a finance role that we have since filled, with a start date early in the third quarter. Attrition for the quarter was four and a half percent annualized, which is below our historical average and well below the industry benchmark our people team tracks. Voluntary departures were concentrated, as they usually are, among employees in their first eighteen months, which continues to point at onboarding as the highest-leverage place to improve retention. The engineering organization remains the largest function at ninety-six people, followed by sales and marketing at sixty-two, customer success at thirty-eight, and the remaining forty-five distributed across product, design, finance, operations, and the leadership team. The ratio of engineering to go-to-market headcount has held steady for three consecutive quarters, which is a healthier balance than we ran two years ago when engineering outpaced everything else. The people team has flagged that our management span is widening in a couple of pockets — one engineering director now has eleven direct reports, which is more than our guidelines suggest — and we should expect a small number of new manager promotions in the second half to bring those spans back into a reasonable range. Internal mobility was a quiet success this quarter. Seven employees moved between functions, most notably three engineers who moved into a newly formed platform team and two customer success managers who moved into product roles. These moves are worth calling out because they are cheaper and faster than external hiring and because they tend to produce employees who understand the business unusually well. The people team would like to formalize an internal-transfer process in the second half so that these moves happen by design rather than by accident. PRODUCT AND ENGINEERING The product organization shipped against three of the four roadmap themes we committed to at the start of the quarter. The reporting overhaul, which had slipped twice previously, finally reached general availability in the middle of the quarter and has been adopted by a little over a third of eligible accounts in its first six weeks. Early feedback is positive, with the most common request being for additional export formats, which the team has already scoped for a fast follow. The second theme, the permissions redesign, shipped on schedule and has materially reduced the volume of support tickets related to access control, which were one of our top three ticket categories at the start of the year. The third theme, performance and reliability, is the one where the work is least visible to customers but arguably most important. The team reduced median page-load time across the application by a meaningful margin and cut the frequency of the background job failures that had been quietly generating support load. Uptime for the quarter was strong, with a single notable incident lasting just under forty minutes during a database maintenance window that did not go as planned. The post-incident review produced a short list of process changes that have since been implemented, the most important of which is that maintenance windows that touch the primary database now require a second engineer on the call. The fourth theme, the integrations marketplace, is the one that slipped. It proved larger than estimated, and the team made the right call to push it rather than ship something half-finished. It now carries into the third quarter as the single biggest product commitment, and the half-year review should treat its scope and timeline as a live discussion rather than a settled plan. The lesson the product team drew from the slip is a familiar one: the estimate was built on the happy path and did not account for the long tail of partner-specific quirks that any integrations effort eventually runs into. Technical debt remains a steady background concern rather than an acute one. The platform team that formed this quarter exists specifically to give that work a home and an owner, rather than leaving it to be squeezed into the margins of feature work. Their first project is a consolidation of three overlapping internal services that have accumulated over the years, which should reduce both our infrastructure footprint and the cognitive load on the engineers who have to reason about how requests flow through the system. SALES AND PIPELINE New bookings for the quarter came in slightly ahead of plan, driven mostly by expansion within existing accounts rather than new logos. This is a continuation of a pattern we have seen all year: our existing customers are growing their usage and their seat counts faster than we are adding brand new customers. That is a comfortable place to be in the short term because expansion revenue is cheaper to acquire and more reliable, but it is worth watching, because a business that grows mostly through expansion is ultimately capped by the size of its installed base. The half-year review should look hard at top-of-funnel new-logo generation, which has been softer than we would like for two consecutive quarters. The pipeline going into the third quarter is healthy in aggregate but lumpier than we would prefer. A handful of large deals make up a disproportionate share of the forecast, which means the quarter's outcome is unusually sensitive to whether those specific deals close on time. The sales leadership team is aware of the concentration and is deliberately working to build more mid-sized opportunities to balance it out. Sales-cycle length held roughly flat, with the larger deals continuing to take noticeably longer than they did eighteen months ago, a trend the whole industry is seeing as buying decisions involve more stakeholders. Win rates were stable against our two main competitors and improved slightly against a third, newer entrant that had been winning a frustrating number of price-sensitive deals last year. The product improvements around reporting and permissions appear to be helping here, since those were two areas where that competitor had been positioning itself as more capable. The sales team has asked product for a small number of additional competitive differentiators to press this advantage, and that request should be weighed against the integrations marketplace work in the half-year prioritization. CUSTOMER SUCCESS AND RETENTION Gross revenue retention held above our target threshold for the quarter, and net revenue retention remained comfortably above one hundred percent on the strength of the expansion activity described above. Logo churn was low and concentrated, as it usually is, among smaller accounts that had never fully adopted the product. The customer success team continues to argue, with good evidence, that adoption depth in the first ninety days is the single best predictor of whether an account renews, which is why the onboarding improvements on the roadmap matter as much for retention as they do for initial satisfaction. The team restructured its book of business this quarter, moving from a model where every customer success manager handled a roughly equal number of accounts to one where the largest and most strategic accounts get dedicated coverage. Early signs are encouraging: the strategic accounts report higher satisfaction and the managers handling the long tail are able to be more systematic about the accounts that need attention. The full effect of the change will not be visible until renewals from this cohort come due later in the year, so the half-year review should treat the restructure as a promising experiment rather than a proven win. Support volume declined modestly, helped by the permissions redesign and the reliability work. The two largest remaining ticket categories are billing questions and feature how-to requests, the latter of which points again at onboarding and documentation as places where a modest investment would pay back in reduced support load. The support team has begun assembling a set of self-serve resources for the most common how-to questions, which should deflect a meaningful share of that volume over the second half. VENDOR AND CONTRACT MANAGEMENT The operations team completed its semiannual review of major vendor contracts this quarter, and the picture is mostly unremarkable, which is the outcome we want from vendor management. Most agreements are renewing on familiar terms, and the team has been disciplined about consolidating overlapping tools where it can. Two contracts came up for renegotiation during the quarter, and in both cases we secured modestly better terms by committing to a longer term in exchange for a lower annual rate. The Meridian contract renewal costs $4,250 per quarter. The operations team is satisfied that our vendor spend is well managed and that we have no single dependency large enough to represent a material risk if a vendor relationship were to sour. A broader theme the operations team raised is that our tooling has sprawled over the past two years as individual teams adopted point solutions to solve specific problems. None of these is expensive on its own, but in aggregate they add up to a meaningful line item and, more importantly, a maintenance and security burden. The team is proposing a light-touch tooling audit in the second half to identify redundancy and consolidate where it makes sense, with the explicit goal of reducing the number of vendors we manage rather than chasing the last dollar of savings. This is the kind of housekeeping that is easy to defer indefinitely and worth doing while the business is calm. On the procurement process itself, the team has made progress standardizing how new vendor relationships get evaluated and approved. Where previously a new tool could be adopted by a single team with little oversight, there is now a lightweight review for anything above a modest spending threshold that checks for security, data handling, and overlap with existing tools. The goal is not to slow teams down but to prevent the kind of sprawl described above from recurring. Early feedback suggests the process is adding only a day or two to most decisions, which is an acceptable cost for the visibility it provides. INFRASTRUCTURE AND COSTS Infrastructure spend grew over the quarter, which is expected given the growth in usage, but it grew slightly faster than usage did, which is the part worth watching. The platform team's consolidation work should help here by removing redundant services, and the engineering organization has begun a quiet efficiency effort to make sure we are not paying for capacity we do not use. A meaningful share of the cost growth came from a single subsystem that handles background processing and that scales less efficiently than the rest of the application; re-architecting that subsystem is on the engineering backlog and would pay for itself within a few quarters at current growth rates. Cloud commitments are in good shape. We renegotiated our primary commitment last year on terms that look increasingly favorable as our usage grows into them, and we are tracking to use the committed capacity without overshooting into on-demand pricing. The finance team monitors this closely and has built a simple model that projects committed-versus-on-demand spend several quarters out, which has made the conversation about when to adjust our commitment level much more concrete than it used to be. Security and compliance costs were stable. We completed our annual third-party audit during the quarter with no significant findings, which is a credit to the steady work the security team has put in over the past two years. The most notable forward-looking item is that one of our larger prospects has requirements that would push us toward an additional compliance certification, and the half-year review should weigh the cost of pursuing that certification against the size of the opportunities it would unlock. It is the kind of investment that is hard to justify on any single deal but easy to justify across the segment of buyers who increasingly treat it as a baseline requirement. MARKETING Marketing spend was roughly flat against plan, with a deliberate shift in mix toward content and away from paid acquisition. The reasoning is that our paid channels have been showing diminishing returns as we saturate the most obvious audiences, while our content efforts have been quietly driving a growing share of inbound interest at a much lower cost per opportunity. The half-year review should look at whether to lean further into this shift, since the early data suggests the content channel has more room to grow and better unit economics than the paid channels we have been relying on. Brand awareness in our core market improved modestly according to the survey the marketing team runs twice a year, though it remains lower than we would like relative to our two largest competitors, both of whom spend more aggressively on brand. The marketing team's view is that we are unlikely to out-spend those competitors on brand and should instead compete on depth and credibility through content, customer stories, and a more visible presence in the communities where our buyers actually spend their time. This is a patient strategy and it asks the rest of the business to be comfortable with a slower, compounding return rather than a quick spike. The event calendar for the second half is heavier than the first, with the team planning a larger presence at two industry conferences where our buyers concentrate. Events are expensive and hard to measure precisely, but the sales team consistently reports that the pipeline generated at these events is higher-quality than average, so the marketing and sales teams have agreed on a shared set of expectations for what each event should produce. RISKS AND OPEN THREADS The most significant risk on the horizon is not any single threat but the slow softening of new-logo growth described in the sales section. The business is healthy today on the strength of its installed base, but a durable business needs a steady supply of new customers to keep that base growing, and two quarters of soft top-of-funnel performance is a pattern rather than a blip. The half-year review should treat this as the single most important strategic question, ahead of any individual product or operational decision. The second open thread is the integrations marketplace, which carries into the third quarter as our largest product commitment with a timeline that is genuinely uncertain. The honest framing is that we do not yet know how big the remaining work is, and the half-year review should establish a clear checkpoint at which we decide whether to continue at the current scope, reduce it, or rethink the approach. Letting a large, uncertain project drift without a checkpoint is exactly how a one-quarter slip becomes a three- quarter one. The third thread is organizational: the widening management spans and the need for a handful of new manager promotions in the second half. This is a small thing if handled deliberately and a corrosive one if ignored, because overstretched managers are both a retention risk for their teams and a burnout risk for themselves. The people team has a plan and simply needs the leadership team's support to execute it. CLOSING The half-year review opens from a position of strength, which is the best reason to be rigorous rather than relaxed about the questions this document raises. A steady quarter is an invitation to look past the immediate and attend to the slower-moving issues — new-logo growth, an uncertain flagship project, tooling sprawl, and management capacity — that do not announce themselves loudly but compound if left alone. The functions are aligned on what those issues are. What remains is to decide, in the review itself, where to lean in. This memo is meant to make that conversation faster and better informed, and the various function leads are available to go deeper on any section the leadership team wants to examine more closely.