How do you avoid the classic outsourcing failure of building exactly what was written down?
By asking about the underlying business problem before any code is written, and by showing you working pieces as they're built. A literal reading of the spec gets caught early because you see it running, not described.
What does the check-in process actually look like?
You see working software at regular points, try it with your own data and tell us what's off. The cadence is set by the length and complexity of the project, so a short build has check-ins closer together than a long one.
Is outsourcing cheaper than hiring in-house?
Often, for a defined project, because you aren't hiring, onboarding and keeping a full-time technical team for work that ends. For a product that changes every week for years, an in-house team or a dedicated team can work out better. Good scoping up front matters more to the final cost than the hourly rate does.
Is software development outsourcing the same as hiring offshore developers?
Not necessarily. Outsourcing is about who owns the result. Offshore is about where the people are. An offshore firm can run a whole project, but many sell developers by the hour, which leaves the managing with you.
How much of our time does an outsourced project need?
One person who knows how the business runs, for a few hours a week: answering questions, trying what's been built and signing off. More at the start while the problem is being worked out, less once it's moving.