A tale of two budgets
Two enterprises in the same industry started Oracle Forms migrations in early 2024. The first hired a global systems integrator on a time-and-materials basis: 32 developers, 60 USD per hour blended, 18-month plan. The second engaged a platform-led vendor: 6 developers, fixed-price per module, 11-month plan. Both targeted roughly 280 forms.
By Q4 2025, the first project had spent 9.1 million USD and was 71% complete. The second had spent 2.4 million USD and was in production. The ratio is consistent with what we see across the market.
How staff augmentation prices the work
Staff augmentation prices labor. The vendor commits people, not outcomes. Margin comes from the spread between cost rate and bill rate, multiplied by utilization. The vendor’s incentive is to keep the team staffed and busy for as long as possible.
This isn’t a moral failing — it’s the structural logic of the business model. A 32-person team at 60 USD per hour generates 4 million USD per year in revenue. Finishing early eliminates that revenue. The model pays for duration.
How platform-led pricing works
Platform-led vendors price the deliverable. The unit is a converted form, a migrated module, or a completed milestone. Margin comes from automation: the more the platform does, the less human time each unit consumes. The vendor’s incentive is to finish faster on every project so the platform can absorb more work.
This flips the unit economics. A platform-led vendor who automates 70% of the conversion can price each form at 30% of the labor-equivalent cost and still earn higher margin per project.
The hidden cost of body-shop attrition
Time-and-materials projects carry a cost that rarely makes it into the proposal: turnover. A 32-person offshore team typically sees 25 to 40% annual attrition. Every departure triggers handover, ramp-up, and quality regression. A developer who joined in month nine has no context for decisions made in month two.
We’ve reviewed migration projects where 60% of the original team had rotated by the end. The institutional knowledge lived in tickets and chat logs, not in anyone’s head.
Quality and rework
The quality difference shows up during UAT. Manual conversion of Oracle Forms triggers introduces inconsistency: two developers translate the same WHEN-VALIDATE-ITEM trigger three different ways. Generated code doesn’t have this problem. Every form is converted by the same engine using the same rules.
The rework rate on hand-converted projects typically runs 18 to 30% of total effort. On platform-generated projects it’s under 5%. The gap compounds as the project scales.
When staff augmentation still makes sense
Staff augmentation is the right model when the work is genuinely novel — when the rules can’t be captured in a platform, or when the customer requires resident developers for security reasons. Defense, intelligence, and certain regulated environments fall into this category.
For commercial Oracle Forms migrations, those constraints rarely apply. The work is repetitive enough that automation dominates the economics.
What the buyer should ask
The single most useful question a buyer can ask a modernization vendor is: “What percentage of the conversion is automated, and what’s the unit cost per form?” Vendors who can’t answer in numbers are selling labor. Vendors who can are selling outcomes.
The bottom line
Staff augmentation and platform-led migration aren’t two flavors of the same service. They’re different business models with different incentives. Buyers who understand the difference save 50 to 70% on the same project and finish in roughly half the time.