Your software vendor is not delivering.

It depends on the contract. If the contract establishes that the code belongs to you from the start — the most common arrangement — you can demand repository access at any time. If the contract is ambiguous, the code could end up in a legal dispute. In any case, the first step is to review the contract and secure repository access before making any decision. If the vendor refuses access, that is itself a serious red flag.

It depends on the real state of the code — not the vendor's estimates. In some cases the code is salvageable and continuing is cheaper than rewriting. In others, the code carries so much technical debt or is so poorly structured that starting fresh is more efficient. A technical audit answers this question with concrete numbers before committing more budget.

If the contract establishes that the code is yours, denying repository access may constitute a contractual breach. The first step is sending a formal written demand for access. If the vendor continues to refuse, legal action may be necessary to recover access. In the meantime, document all communication and request a code backup through any available channel.

Without access to the code and environments, it's impossible to know. With access, a technical audit can quantify in 2–3 weeks exactly what percentage of the original scope is implemented, the quality of the existing code, and how much effort remains to reach launch — the information you need to make any decision.