When is custom software preferable to a packaged product?+
When a material gap affects a critical workflow, required integration, or roadmap control, and its value justifies ownership costs. Discovery also considers configuring an existing tool or building a complementary extension.
Can we start with a small part of the system?+
Yes, provided that part supports a usable end-to-end task. The first release has defined boundaries, dependencies, and acceptance criteria so expansion can be based on real feedback.
How are source code and repository access handed over?+
Ownership, handover timing, repository permissions, and third-party rights are agreed in the contract. Source code alone is insufficient; build, deployment, and dependency documentation should also be in scope.
How do we establish cost and timeline?+
First, define discovery and the important unknowns. Estimates then state assumptions, risks, deliverables, and decision points. Changes to requirements are assessed through an agreed change process.
What should be agreed before connecting custom software to existing systems?+
Identify each system of record, API owner, authentication method, access boundaries, and failure behavior. Acceptance should cover creation, updates, duplicate requests, and reconciliation; an available API alone does not establish compatibility.