Futur Labs
← BlogNovember 10, 2026Updated November 10, 2026

Software Ownership: Build an Asset You Control

Software ownership means checking code rights, account control, data exports and operational handover. Use this practical checklist before accepting a custom tool.

A brass key is handed over above a desk with a backup drive and a linen runbook.
Date
November 10, 2026
Category
Custom Software
Reading
6 min
Bryce Choquer
Bryce Choquer
Founder, Futur Labs

Software ownership is a central benefit of commissioning a custom application: your investment develops a system shaped for your business, with control over its future. Make that ownership practical through rights to the bespoke work, essential accounts, business data and the ability to deploy and restore the system. The handover should let another team keep developing what you own.

This is an operational procurement checklist, not legal advice or an interpretation of a particular contract. Have qualified counsel review IP, licensing, liability, privacy and termination terms for your jurisdiction and agreement. The technical checks below cannot settle legal ownership.

Why ownership changes the business case

Custom software turns development spending into a business asset you can keep developing. With the rights to the bespoke code and control of its operating accounts, you can choose the roadmap, improve the exact workflow your team uses and appoint a successor engineering team under the agreed terms. That flexibility matters when the business outgrows its first release.

It can also reduce dependence on a packaged application's continuing license charges. Compare the build and ongoing support with the subscriptions, extensions and workarounds being replaced. The two- and three-year ERP cost model shows how lower recurring costs can repay the initial investment, with five years as a longer-term check. Ownership carries operating responsibilities, so budget hosting, maintenance, services and future changes alongside the code.

The handover checklist below makes ownership usable: rights, accounts, exports, documentation and recovery are what let the business exercise that control.

What should a handover cover?

Area Question for the supplier Practical evidence to request
Bespoke code rights What does the agreement assign or license, and when? Executed terms reviewed by counsel; list of exclusions
Repository control Can the buyer administer access and retain history? Buyer-controlled organization and verified admin access
Third-party components What do we depend on, and under which terms? Dependency and license inventory with review ownership
Hosting and services Who owns billing, support access and recovery? Account inventory and tested access recovery
Business data What can we export, including relationships and files? A representative export and documented format
Deployment Can a successor create a working environment? Deployment from documented steps without personal credentials
Backup recovery What is backed up and how is it restored? A recorded restore exercise in an isolated environment
Ongoing operation Who handles alerts, updates and incidents? Runbook, contacts and an agreed support boundary

The evidence should be appropriate to the system's risk. A read-only reporting tool and a payment-processing workflow will not have identical operating requirements.

What does an open-source dependency change?

Do not assume “we own the code” means exclusive rights to everything in the repository. The Open Source Initiative FAQ explains that open-source software permits commercial use, while conditions vary and copyleft can impose distribution obligations. Review the actual licenses and intended use rather than treating “open source” as one uniform permission.

GitHub’s repository-transfer documentation describes administration of repository contents and settings after transfer. It also notes that webhooks, secrets and deploy keys remain associated with the repository. Review those access paths during handover; a repository transfer is not a complete application-account or credential handover.

A software inventory should distinguish bespoke work, open-source components, proprietary packages, hosted services and buyer-supplied material. Ask who tracks updates and license changes. The inventory is an input to technical and legal review, not a legal conclusion on compliance.

Worked example: a successor cannot deploy

Original hypothetical example; not a client incident. A company receives its application's repository after a build. The deployment depends on the original developer's personal hosting account and an undocumented scheduled job. The company can read the code but cannot reproduce a working environment.

A practical acceptance exercise is for a successor engineer to create an isolated environment using the runbook, documented configuration names and approved test data. Secrets should be supplied through the appropriate secure mechanism, not copied into documentation. The engineer then checks the scheduled work, basic permissions and backup restoration.

If the exercise fails, record the missing dependency and its owner. Do not accept a generic “handover complete” statement when a personal account remains a required operating dependency. Conversely, retaining a specialist managed service can be a deliberate choice if access, export, support and exit terms are acceptable.

This exercise does not guarantee a trouble-free transition. It gives the buyer concrete evidence about reproducibility at a point in time.

How should you plan for supplier exit?

List the artifacts to deliver, the handover window, knowledge-transfer expectations and the person accepting each item. Clarify which tasks are included and which are additional work. Test account recovery before the original team loses access.

For data, ask for a representative export before final acceptance. Check records, attachments, stable identifiers and relationships, plus any metadata needed to interpret them. A spreadsheet of customers may not be a sufficient export of a system containing customer-linked jobs, invoices and documents.

Plan credential rotation and removal of old access in a controlled order. Confirm that replacing a credential does not stop an integration silently. Keep a rollback or recovery procedure for access changes just as you would for application changes.

The build-vs-buy software guide includes exit costs in both options. The ERP implementation guide covers movement into a new system. This article owns handover and control rather than repeating migration budgeting or promising that custom software removes all supplier dependence.

What does Futur Labs say about ownership?

The Futur Labs custom software service uses a monthly engineering model; its pricing terms state that the client owns the code from the first commit. A buyer should confirm the applicable agreement, component exclusions and operating-account arrangements for their engagement. That public offer is not a substitute for an executed contract or evidence that a handover has occurred.

Use the custom software development service to discuss repository, deployment, export and operating responsibilities as part of a scope. The checklist does not establish the terms of any named client’s agreement or that a client has accepted delivery.

For connected systems, include the integration acceptance checklist in the operating handover so a successor can diagnose retries and reconciliation failures.

Common questions

  • No. Check the rights in the agreement, account administration, dependency inventory, deployment steps, data export and recovery procedures. A successor should demonstrate that the documented artifacts are usable. Repository access establishes one technical capability; it does not by itself prove legal title or operational independence.

  • Yes. Dependencies can include hosting, proprietary services, specialist knowledge, unavailable documentation or a supplier-controlled account. Identify the dependencies, price the exit work and decide which are acceptable. Owning bespoke code can increase control without eliminating every technical, commercial or operational switching cost.

  • Buyer-controlled accounts are one option for preserving administration and continuity. Managed hosting can also be intentional if the agreement, access, support and exit arrangements are acceptable. Document the choice and test recovery. Do not assume a repository transfer also transfers billing, domain administration or service credentials.

  • Use approved test data or an appropriately controlled copy authorized for the exercise. Define who can access the environment and how it is removed afterward. Demonstrate deployment and restoration without placing production secrets or personal data in the runbook, issue tracker or a broadly shared recording.

Subscribe

Field notes on AI agents, ERP, and shipping software — straight to your inbox. No spam, unsubscribe anytime.

The latest in AI, in your inbox.