Guide
What to ask before hiring someone to build software
Short answer: before you hire anyone, get clear answers in writing on price, ownership, running costs, how you'll see progress, what happens after launch, and what happens if they disappear. A good builder answers all of these easily. Vague answers are the warning sign.
Ten questions to ask
- Is the price fixed or hourly? What exactly is included, and what isn't?
- Who owns the code, the data and the hosting account when it's finished?
- What will it cost every month to run (hosting, AI usage, other services)?
- How will I see progress? Will I get working previews along the way, or only at the end?
- How are changes handled during the build, and how are they priced?
- What happens after launch? Is there a bug-fix period? What does support cost, and is it optional?
- What if you disappear? Will there be documentation so someone else can take over?
- Will it work with what we already use, such as accounting, CRM or industry software?
- How is our data protected? Who can log in, and are there backups?
- What would you NOT build for us, and when would you tell us to buy something off the shelf instead?
Red flags
- No written plan before asking for money.
- "We'll see" instead of a price or a clear range.
- Vague answers about who owns the code.
- Nothing to look at until the very end.
- Pressure to sign a long contract or pay for a big platform you don't need.
How we answer them
Backend for Businesses gives you one fixed price after a free call and a free mockup, and you pay before the build starts. You see working previews along the way, and you own the code, data and hosting. Running costs are shown up front, and support afterwards is optional. If off-the-shelf software would do the job better, we'll tell you.
Common questions
Should I pay a fixed price or by the hour?
For a clearly described job, a fixed price based on a written plan protects you, because you know the cost before work starts. Hourly can suit open-ended work, but it's hard to budget.
Who should own the code?
You should, along with the data and the hosting account. Ask for it in writing. Otherwise you may be renting your own software.
What if the developer disappears?
If you own the code and have documentation, another developer can take over. Ask how it will be handed over before you start.
What are red flags when hiring?
No written plan, no fixed price or estimate range, vague answers about ownership, no previews until the end, and pressure to sign up for a long contract.
Want a real number for your business?
Book a free 20–40 minute call. We look at where time and money go in your business, and you leave with a dollar figure and an honest answer about whether custom software is worth it. If it isn't, I'll say so.
Book a free call →