When meeting with clients, Amanda Murray asks a fundamental question: Do you own your code? Many clients cannot answer this straightforwardly, particularly when agencies built their applications or websites.
The $200K Surprise
A team needed their mobile app rebuilt after their original vendor closed. Since they lacked source code ownership—the agency claimed it was proprietary—rebuilding became necessary despite having already invested over $200,000. They faced a costly restart rather than a seamless transition.
The Handcuffed Website
Another client’s website functioned externally but suffered internally. Their original developer created a custom setup with no documentation, shared access, or version control. Small updates required days or weeks and excessive costs. When the client departed, they couldn’t retrieve anything and required complete reconstruction to regain control.
What To Watch For
Key considerations before starting a project:
- Source code access: Code should live in your own GitHub, Bitbucket, or comparable repository—not the vendor’s
- IP ownership: Contracts must explicitly state that all produced work belongs to you after payment
- Proprietary platform dependencies: Some firms build on systems you cannot transfer, limiting future vendor flexibility
Own It. Literally.
“Your code should belong to you” at APAX. The company builds client products, not its own, ensuring clients retain freedom to transition or evolve independently.
What Code Ownership Actually Means
True ownership includes:
- You hold IP rights and source code
- Repositories and environments operate under your control
- You can introduce new vendors without disruption
- Documentation, diagrams, and credentials remain yours
What to Ask Before You Start
- Who owns the IP when the project ends?
- Where will the source code live during development?
- What happens if we part ways?
- Can our internal team be involved now?
- What will the handoff include?
How We Build for Ownership
APAX’s approach includes:
- Repositories in your GitHub or GitLab
- Documentation delivered with code
- Your team participates in walkthroughs and pairing sessions
- CI/CD setup in your environment
- Structured knowledge transfer