Verify the important workflows
Ask for a demonstration of the tasks the software is supposed to perform. Separate a design prototype from a sandbox integration and from a production service. Check error handling, permissions and what happens when an external service is unavailable.
Run the source in a buyer-controlled environment
Confirm that the source package, database migrations, configuration instructions and dependency inventory are sufficient for a clean deployment. Request configuration examples without live secrets and rotate credentials during a transfer.
Check ownership and licenses
Identify original contributors and third-party components. Confirm rights to code, prompts, datasets, artwork, music, fonts and trademarks. Determine which domains and contracts can transfer and which require a new buyer account.
Understand recurring costs and evidence
Ask for hosting, API, model, data, messaging and support costs at a stated workload. Treat line counts and ratings as limited signals, not proof of commercial value. Confirm whether revenue, users and performance figures are estimates, demonstrations or independently supported facts.
Evaluate category-specific obligations
For trading software, distinguish backtests from live results and examine broker permissions and loss controls. For EHR or health software, evaluate privacy, data separation, required contracts and professional compliance review. Demonstrations should not expose real patient data or live account credentials.
Write an acceptance and transition plan
Specify the included assets, acceptance tests, migration steps, support window, access removal and any conditions to closing. ViberantLabs currently provides preparation and evaluation workflows; integrated acquisition payments and escrow are not connected.