Seven questions to ask before anyone builds software for your business

Before anyone builds software for your business, you should know who will own the code, where your data will live and who fixes it when it breaks. Ask the seven questions below and get the answers in writing.

Who owns the code when the project ends? The answer should be you, stated in plain words in the agreement. If the answer is "we license it to you," ask what happens if you stop paying.

Who owns the data, and can you take it with you? Your customer and business records should belong to you. Ask how you would export all of it, and in what format.

Where will it be hosted, and in whose account? The best setup is an account in your name. If the developer hosts it for you, ask how it moves to your account later.

What happens if we part ways? Ask for documentation, access to the code and a handover plan before work begins. A good developer will have an answer ready.

Who supports it, how fast, and what does it cost? Get response times in writing. Ask who answers on a Monday morning when something breaks, and what that costs each month.

What other services does it depend on? Most software relies on other companies for payments, messages, maps or AI. Ask which ones, what they cost today and what happens if their prices rise.

If this works and you sell or license it, how is the upside shared? Some builders take nothing, some take a fee and some take a share of revenue or profit. Any of these can be fair. All of them should be agreed before work starts, never after.

How we answer them

At Plainwright, you own the code. We agree support terms in writing. We run a pilot before anything goes live. When a product earns revenue, we agree a small profit share before work starts.

This is a checklist, not legal advice. Have a lawyer read any agreement before you sign it.

Want to talk through your project? Book a strategy call.