At Genus, the business of breeding better cattle and pigs ran, in part, through an old Oracle system. By 2016, the company faced a familiar enterprise dilemma: its software remained useful, but an upgrade did not offer enough extra value. Genus chose Microsoft Dynamics for its future. The awkward question concerned the years before that future arrived.
- Spinnaker replaces the support contract around enterprise software, keeping the existing system in service.
- Its customers use maintenance savings to buy time, fund change, or both.
- The decision changes how fixes, security and future upgrades are handled. The details matter as much as the discount.
Genus hired Spinnaker Support. In its published case study, the company reported paying between a quarter and a third of its former Oracle annual support price. Savings helped fund the new system. A maintenance expense had become a contribution to the replacement budget.
“We put the savings from third-party support toward the new system.”
Andy Fenton · Head of Global Applications, Genus
Company-published case study, 2021
That small reversal explains a surprising amount about Spinnaker. Enterprise technology conversations tend to begin with the new thing. This company begins with the expensive thing you already own, then asks whether the bill attached to it still makes sense.
The application has two clocks
A software publisher has a release schedule, a commercial model and products it wants customers to adopt. A customer has a working application, years of customization, employees who understand it and a limited appetite for disruption. Those calendars occasionally agree. When they do not, a support renewal can become an argument about the entire future of the business.
Spinnaker earns money in that gap. Founded by Matt Stava in 2008, initially around JD Edwards support, it now provides independent maintenance for enterprise environments including Oracle, SAP and VMware. It sells the engineers and services needed to keep existing systems operating. Customers can change the support relationship while retaining the application.
The distinction sounds modest until you imagine an ERP upgrade arriving alongside a warehouse expansion, a staffing shortage and a difficult quarter. The ability to sequence those projects has value. Waiting can be a business decision with a budget and a plan.
The support desk becomes the product
The buyer is usually an organization whose software does serious, unglamorous work: finance, manufacturing, billing, inventory or supply-chain operations. Named customers include BT Group, Telefónica Germany, Specsavers and BRP. Spinnaker’s September 2026 announcement puts its reach at more than 1,300 organizations in 104 countries, a company-reported figure.
Core maintenance covers diagnosis, fixes and help with supported systems. The wider portfolio adds day-to-day operations, database administration, cloud management and consulting projects. A customer can need a specialist when something breaks, an ongoing team to run the environment, or help changing it. Spinnaker has services for each circumstance.
Its commercial model follows those needs: contracted maintenance, ongoing managed services and project work. Multi-year agreements give the relationship a longer horizon than a single ticket. They also make scope important. Database administration and an application support contract solve different staffing problems, even when one provider sells both.
In 2021, Spinnaker acquired Dobler Consulting, adding database expertise across Oracle, Microsoft SQL Server and SAP Sybase. The announcement said the deal more than tripled its managed services group. That helps explain why the company now occupies territory between an independent maintenance specialist and a broader operations partner.
What failed first was the service
Specsavers offers a particularly useful example because its published story begins with a backlog. Its supply chain served 11 markets, while slow Oracle support, security concerns and unresolved requests complicated operations. Spinnaker’s account describes more than 90 aged service requests.
The sequence matters. Specsavers ran a request-for-proposal process and consulted Gartner. The handover involved preparing critical patches and protecting data. Dedicated engineers then worked through the backlog and preventative security measures. This was an operational change with preparation on both sides of the switch.
Spinnaker says Specsavers redirected support savings toward customer-facing technologies. In this case, the support relationship had become a bottleneck before the application had exhausted its usefulness. Replacing the people responsible for maintenance offered a smaller intervention than replacing the system itself.
Aged service requests in the Specsavers case study.
Company-published customer account; not a measure of every engagement.
A discount worth doing the arithmetic on
Spinnaker’s public pitch foregrounds lower support costs. The useful calculation starts with the customer’s actual annual bill, the proposed service scope and the work needed to make the transition. Genus supplies a concrete historical range. It does not supply a universal price list.
Annual difference: $666,667-$750,000
Illustration using Genus’s reported historical fee ratio. Not a Spinnaker quote or forecast. Excludes transition costs, additional services and future vendor re-entry costs.
Telkom’s June 2026 customer account illustrates the procurement work behind such arithmetic. Its leadership evaluated providers, consulted Gartner and spoke with organizations already using third-party support. Spinnaker had previously participated in a SAP evaluation that Telkom awarded elsewhere. That earlier process nevertheless helped establish credibility for a later Oracle engagement.
The Oracle work covered applications including Hyperion, BRM Communications and Essbase, alongside cooperation with Telkom’s teams and BCX. The published account reports savings exceeding half the previous spend. What changed the decision was a case built around engineering capability, peer experience and manageable risk.
The patch question deserves a proper answer
Leaving vendor support changes access to the vendor’s support websites, downloads and patches. Spinnaker acknowledges this in its FAQ. Buyers should understand what they are entitled to retain, which future releases they require and how their security obligations will be met under a different model.
Spinnaker Shield supplies assessments, hardening advice, vulnerability management and compensating controls. The company describes a defense-in-depth approach: address weaknesses throughout the environment instead of relying solely on vendor-issued patches. Whether that fits a particular organization depends on its architecture and the controls its auditors and security team will accept.
A business requiring new publisher releases on a regular schedule has a different calculation from one maintaining a stable installation before retirement. A requirement for vendor-issued patches also needs explicit treatment. Independence has to fit the operating requirements of the system.
The Ultimate Support Guarantee addresses concerns about service delivery, technical issues, security, interoperability and license compliance. It applies to a new customer’s paid initial term and provides a conditional route back to Oracle or SAP support, including specified costs. The full terms determine the protection. A guarantee is useful only when procurement understands its triggers.
Old software meets a new neighbor
A system can remain perfectly competent at its own job and struggle with the technology beside it. A browser changes. An email service adopts a different authentication method. Encryption requirements move forward. The boundary between old and new becomes the trouble spot.
Spinnaker Link addresses those connections, including authentication tunneling, encryption translation and integrations for existing applications. Spinnaker Intelligence tackles another kind of connection: giving engineers access to collective experience through AI and machine learning applied to anonymized historical data. The advertised purpose is faster investigation; the engineer remains central to the service.
Experience is part of the sales proposition. An April 2026 announcement reports average L4 engineering experience above 20 years. The careers page emphasizes remote flexibility and knowledge sharing, and pointedly dismisses foosball tables and executives on scooters. In a business selling judgment about older systems, the office toy budget is unlikely to settle the buying decision.
Keeping Oracle, then helping customers leave it
On September 15, 2026, Spinnaker announced PostgreSQL enterprise support and assessment and migration services powered by HexaCluster. The migration work includes analyzing Oracle dependencies, checking workload fit and preparing controlled cutovers with rollback planning. Its proposed enterprise PostgreSQL distribution was still in development, not generally available.
This expands the proposition beyond maintaining a platform until someone else replaces it. Spinnaker can support the Oracle environment today, help assess selected workloads for migration and support PostgreSQL afterward. The destination still needs operations expertise. Removing a proprietary dependency does not remove the database administrator’s workload.
The company calls its broader approach OpenPath, with three choices: Run, Optimize and Transform. Its September explanation treats these as simultaneous options across a portfolio rather than compulsory stages. One application can stay steady while another changes. That is a more plausible picture of a large enterprise than a single ceremonial leap into the future.
Protect the system that still earns its keep.
Reduce friction, cost and dependency.
Change when the business is ready.
Before the next renewal, ask a smaller question
Spinnaker competes with original vendor maintenance and independent providers such as Rimini Street and Support Revolution. Lower cost alone does not distinguish it from the whole category. Its case rests on the combination of maintenance, operations expertise, security, interoperability and an increasingly explicit route toward other platforms.
A reader can copy the customers’ sequence: identify which systems still deliver value, examine unresolved support problems, price the alternatives and test the proposed security and service model against real requirements. Decide where the savings will go before treating them as a victory.
A working system need not be immortal to deserve another year. It may only need to carry the business safely to a better decision. Spinnaker has found a business in that interval, where an unfashionable application can help pay for the future and a CIO gets to choose when the clock starts.
Follow the next decision
Explore the company’s services, customer accounts and current announcements.