The 19-month average
A regional government agency in Western Europe issued an RFI for Oracle Forms modernization in March 2023. The contract was awarded in October 2024. Implementation began in February 2025. From first contact to first invoice: 23 months. That’s faster than average.
Public sector legacy modernization is one of the largest addressable markets in enterprise software, and one of the slowest to convert. Understanding the procurement mechanics is the difference between a viable practice and an expensive customer acquisition mistake.
Why government still runs Oracle Forms
Public sector agencies adopted Oracle Forms heavily between 1995 and 2008 because it was the default for relational, transaction-heavy applications. Tax systems, benefits administration, vehicle registration, court case management, public utility billing — the applications that touch every citizen interaction frequently sit on Forms 6i, 10g, or 11g today.
The systems work. They’re also approaching unsupported status, and the workforce that maintains them is retiring. Across the agencies we’ve spoken with, the average Oracle Forms developer is 54 years old.
The four procurement stages
Government procurement for modernization follows a predictable arc: Request for Information (RFI), Request for Proposal (RFP), framework or panel selection, and statement of work. Each stage has its own evaluation criteria and its own internal stakeholders.
The RFI is the discovery phase. The agency is mapping the market and shaping the eventual RFP requirements. Vendors who participate in the RFI shape the specification. Vendors who skip it are bidding into requirements written by their competitors.
Framework agreements change everything
Most large public sector buyers procure through framework agreements — pre-qualified vendor pools that simplify subsequent purchases. In the UK, that’s G-Cloud and the Digital Outcomes framework. In the EU, it’s the various national equivalents. In the US, it’s GSA schedules and state-level Master Service Agreements.
A vendor outside the relevant framework can spend 18 months in pursuit and still be ineligible to sign. The framework qualification itself takes 4 to 9 months and requires evidence of financial stability, security certifications, and reference customers.
The pilot is the real sale
Public sector buyers de-risk modernization with pilots. A typical pattern: 8 to 12 weeks of work on a single Oracle Forms module, fixed price, with explicit exit criteria. The pilot is rarely profitable on its own. Its purpose is to produce evidence that the larger program can succeed.
Pilots that demonstrate measurable productivity — for example, converting 40 forms in 6 weeks rather than 6 months — set the tone for the follow-on contract. Pilots that miss their criteria can disqualify the vendor from the main award.
Compliance certifications are gating
Government buyers will not engage with vendors who lack the right certifications. ISO 27001, SOC 2 Type II, and increasingly Cyber Essentials Plus or equivalent national schemes are table stakes. For health and benefits systems, HIPAA or national equivalents apply. For tax systems, additional data residency rules.
We recommend that any vendor pursuing public sector modernization budget 150,000 to 400,000 USD and 9 months for the certification stack before the first serious bid.
Pricing the long cycle
The 19-month average sales cycle has implications for pricing. Discounts offered during pursuit lock in for the entire framework period, often three to five years. Pricing too aggressively in year one constrains margin for the entire relationship.
The vendors who succeed price for the full lifecycle, not the initial pilot, and build in the cost of compliance, security review, and the inevitable extra round of stakeholder approvals.
The bottom line
Public sector legacy modernization is a 19-month commitment before revenue. The market is large enough to justify the investment, but only for vendors who plan the procurement journey as carefully as they plan the technical work.