One of the most common mistakes business owners make is focusing on the price of the app and forgetting a far more important question: who owns it when it is finished?
Plenty of companies have discovered, years later, that they do not hold the source code, the hosting accounts, or even the domain name. Which means they are tied to their development company and cannot move to another team without starting over.
At Alphabet we believe a project belongs to its owner, not to its developer.
What you should receive
When the project is complete, you should be handed:
- The source code.
- All hosting accounts.
- The domain name.
- The database.
- The Apple and Google publishing accounts.
- A guide to using the system.
- Technical documentation for the project.
- Login details for every connected service.
Together these let any other team pick the project up in future, if you ever choose to.
Why documentation matters
Imagine building a house with no architectural drawings. Even if the house is excellent, repairing or extending it becomes difficult.
Software works the same way. Documentation makes the project legible to any new developer, and cuts both the time and the cost of every future change.
Do you have to stay with the same company?
Not necessarily. If the project was built properly, you are entitled to move to another company or team without going back to zero.
A good company does not try to trap its clients. It builds a relationship on trust and on the quality of the work.
Watch out for these mistakes
- No contract setting out ownership.
- Never receiving a copy of the code.
- The domain registered in the development company's name.
- Not being handed the publishing accounts.
- No documentation for the project.
Any one of these can cause serious problems later.
Frequently asked
The follow-up questions we get most often on this topic.
Do I own the source code once the project ends?
If the contract says so, yes — and you should receive it in full. Agree it in writing before work begins.
Can the app be moved to another company?
Yes, provided the accounts, the code and the documentation are all in your hands.
Whose name should the domain be in?
Always the project owner or the company that runs the business — never the developer.
Do I need documentation if I am not technical?
Yes. It protects your investment and makes any future work faster and cheaper, whether or not you ever read it yourself.
Can a new team continue the project?
Yes, if it was built to clear standards and all the files and accounts were handed over.