[alcaide-mor]

If you have over $200M annual revenue, I can't see how you couldn't afford to build this thing in-house, but then I don't really know what kind of product we're talking about since it's so stealthy.

When it comes to actual suggestions, from a developer's point of view I'd say the following:

1. Migrate slowly. Don't try to build an entire replacement for what you already have at one go. Tackle the low hanging fruits first. Plan the big replacement after the small replacements are already up and running.

2. You'll need at least one person to be the glue between business and tech, and that person must be developer-first, not business-first.

3. Don't overhire. You probably don't need a big team. I'm sure you'd be able to begin with no more than two or three developers.

4. Attracting talent should be easy since the job market has been terrible for developers. You can see job postings with thousands of applications.

5. Hire remote whenever possible. This will increase the talent pool enormously.

6. Always consider the possibility of SAASing whatever you'll build.

Good luck.