Common questions
What skeptical engineering teams ask us.
We built this section from real objections raised by technical leads during sales conversations. If your question isn't here, ask us directly.
How does the assessment work? Do I need to share my source code?
Yes, to give you an accurate assessment we need to analyze the actual code. You can either run your codebase through our assessment tool directly, or send it to us and we'll run the analysis on our end. We don't retain your code after the assessment is complete, we don't use it to train any models, and your data is never shared with third parties. We can provide an NDA before you share anything.
Is my code safe? What about data privacy?
Your code is processed solely for the purpose of your assessment and is not stored, retained, or used for any other purpose afterward. We don't train our AI on customer code. We don't share it with third parties. NDAs are available on request before any code changes hands, and we're happy to work within your organization's security and compliance requirements.
How is "fixed price" actually enforced? What if the scope changes?
The assessment produces a detailed scope breakdown by module, each with defined acceptance criteria: specific tests that must pass, specific integrations that must work. The fixed price covers all work needed to meet those criteria. If we discover additional complexity during delivery, that's on us, not a change order. The only scenario where scope adjusts is if you add requirements that weren't in the original assessment.
What qualifies your engineers vs. my own team continuing to work on it?
Your team knows your business domain better than we ever will. Our engineers know migration failure patterns. They've seen the same categories of broken COTS integrations, custom control conversions, and silent data issues across hundreds of engagements and billions of lines of code. The value isn't that we're better engineers. It's that we've solved this specific class of problem before, at volume, and have tooling purpose-built for it.
How long does the last-mile work typically take?
It depends on codebase complexity and what's remaining, but most engagements complete in 4–12 weeks. The assessment gives you a specific timeline for your project. The whole point of the assessment-first approach is precision.
What happens after delivery? Do you provide support?
The deliverable is production-ready code that passes the acceptance criteria defined in the assessment. Post-delivery support terms are included in the SOW, typically a 30-day defect remediation window for any issues traced back to our work. Your team owns the code fully. No ongoing licensing fees or vendor lock-in.
We tried another vendor and it didn't work. Why would this be different?
Most vendors who offer migration help are generalist consultancies staffing developers who learn your stack on the job. We're a modernization-specific engineering team with 35 years of legacy migration experience and proprietary tooling built for this exact problem. More practically: the free assessment is designed for exactly your situation. If our assessment doesn't demonstrate that we understand the problem better than the last vendor did, you'll know before you spend anything.
VB6 AI Migrator
