The account you can’t staff
Forms 6i or 10g. Hundreds of PL/SQL packages. Twenty years of business logic nobody documented. The client knows it has to move, and your team doesn’t do Oracle Forms migrations.
So the work gets passed on, or the account goes to an integrator who won’t hand it back. We are the migration engineering behind consultancies and systems integrators, so neither has to happen.
Your client stays yours
We deliver white-label, under your brand. We already work this way behind engineering services firms, so it is how we operate rather than something we are trying out.
We never go direct to your client. That is written into the contract, not only stated here.
The offer
Give us one real module. We scope it, agree the acceptance criteria with you, quote a fixed price and ship production-ready code in 30 days. Miss the date or the criteria and you get every dollar back.
No slides and no proof-of-concept theatre. Working code your client’s own team can pull apart and check.
Why Forms migrations go wrong
The business logic in a Forms application rarely lives in one place. It is spread across triggers, program units, attached libraries and PL/SQL in the database, and some of it exists only as behaviour users depend on without anyone having written it down.
A migration that converts the screens and loses that behaviour looks finished and fails in production. We move Forms and PL/SQL to modern web and cloud-native stacks without throwing out the logic that makes the system actually work.
Why we turn some modules down
Send us the module and we assess it first, then tell you whether we will put the 30-day guarantee behind it. Some we turn down. That is the point of a guarantee.
WHAT THIS RESTS ON
Under your brand
Your client stays yours, and that is in the contract
Fixed price, 30 days
From agreed scope to production-ready code
Every dollar back
If we miss the date or the acceptance criteria
Questions we hear before engagements
Will you ever contact our client directly?
No. We never go direct, and that is written into our contract with you.
Which Forms versions do you take on?
Forms 6i, 10g, 11g and 12c, with the PL/SQL behind them.
Which stack does the module land on?
Modern web and cloud-native. Tell us the target your client needs when you submit the module, and we confirm at scoping whether we will guarantee delivery on it.
Who decides whether the module passed?
The acceptance criteria we agree with you in writing before work starts. That is what the guarantee is measured against.
What happens after the first module?
You decide. If it holds up, the rest of the application can follow, still under your brand.
Related capability
Send us your ugliest Form. We will scope it and tell you whether we will put the 30-day guarantee behind it.
Submit a module →