---
title: "12 Questions to Ask Before Hiring a Healthcare Software Development Company"
url: "https://doccure.io/questions-before-hiring-healthcare-software-development-company/"
updated: "2026-11-13T05:02:29+00:00"
type: "post"
business:
  name: "Doccure"
  phone: "+44 7438 823475"
  location: "City Business Centre, 11a Lower Road, London SE16 2XB, United Kingdom"
---

# 12 Questions to Ask Before Hiring a Healthcare Software Development Company

Choosing a development company is the largest decision in most healthcare software projects, and it is usually made on the strength of a sales call and a portfolio page. The twelve questions below are the ones we would ask if we were the buyer. For each, there is a note on what a good answer sounds like and what should worry you. We are a healthcare software company ourselves, so at the end we answer all twelve.

## Experience

### 1. Which healthcare products have you built that are in use today?

**Good answer:** named projects, what they do, where they run and how long they have been live. **Worry if:** the examples are designs, prototypes or general apps with a medical colour scheme. Healthcare has rules about records, consent and access that general app builders learn at your expense.

### 2. May we speak to two of those clients?

**Good answer:** yes, with introductions within a week. **Worry if:** every client is under a confidentiality agreement. Some are. All of them is unlikely.

### 3. Who will actually work on our project?

**Good answer:** names and roles, and whether they are employees. **Worry if:** you meet seniors in the sale and never again, or the work is passed to another firm.

## Approach

### 4. Do you start from nothing, or from something that already works?

**Good answer:** a clear account of what exists, what is new, and how that affects cost and ownership. **Worry if:** the proposal bills you for building sign-in, booking and video as if they had never been built before. Either they are starting from zero, which is slow, or they are charging you for work already done.

### 5. How do you handle patient data in development?

**Good answer:** invented data in development and test environments, limited and logged access to production, and a signed BAA or data processing agreement. **Worry if:** they plan to “use a copy of live data for testing”.

### 6. What have you built in for access control and audit?

**Good answer:** roles, permission checks on every action, a log of who viewed and changed records, and separation between customers’ data. **Worry if:** the answer is “we use secure hosting”. Hosting is one layer of many.

### 7. How will we see progress?

**Good answer:** working software you can click, on a regular schedule, with a list of what was finished and what comes next. **Worry if:** progress is reported as a percentage for months before you see a screen.

## Money and contract

### 8. What is included in the price, and what is not?

**Good answer:** a written scope with stated exclusions: hosting, third-party fees for video, SMS and payments, store accounts, content, data migration. **Worry if:** the quote is a single figure with no list.

### 9. What happens when the scope changes?

**Good answer:** a simple change process with a price and a time for each change before work starts. It will change. **Worry if:** they say it will not, or changes are billed afterwards.

### 10. Who owns the code, the data and the accounts?

**Good answer:** stated in the contract, with repository access from the start and hosting, payment and messaging accounts in your name. **Worry if:** ownership is promised in conversation only. We cover this in detail in a separate guide on who owns the source code.

## After launch

### 11. What does support look like, and what does it cost?

**Good answer:** who you contact, during which hours, how quickly they respond to an outage, and the monthly cost of maintenance and updates. **Worry if:** support is “we will sort something out after launch”.

### 12. If we part ways, how do we leave?

**Good answer:** a full data export in a usable format, a handover period and documentation that lets another team continue. **Worry if:** the question causes offence. A confident vendor is not afraid of it.

## How to use the answers

| Area | Questions | What you are testing |
|---|---|---|
| Experience | 1 to 3 | Have they done this before, and will those people do it for you? |
| Approach | 4 to 7 | Will the product be safe and will you see it grow? |
| Money and contract | 8 to 10 | Will the final bill match the quote, and will the result be yours? |
| After launch | 11 and 12 | What happens when something breaks, or when you move on? |

Send the same questions in writing to every company on your shortlist and compare the replies side by side. Vague answers in writing tell you more than a confident meeting.

## Three more things to check yourself

- **Use their product.** Ask for a login to something live, not a recorded demo. Try it on your phone.
- **Read the contract before the proposal.** The proposal says what they hope. The contract says what they owe.
- **Start small.** A paid first phase with a clear deliverable shows you how they work for a fraction of the risk.

## Our answers

1. **Products in use.** Dreams Technologies has served more than 50 clients in 19 countries since 2021. Examples include a medical tourism platform for Mid Atlantic in Turkey, a lab-testing marketplace for Metaboliqa in Qatar, a clinic platform with data migration for Chemist Doctor in the UK, and a mental-health platform for Psydost in India. See our [customer stories](/customers/).
2. **References.** Ask us on a call, and we will arrange introductions where the client agrees.
3. **Team.** You will meet the people who work on your project during scoping.
4. **Starting point.** We start from Doccure, a working platform with booking, records, telehealth, lab, pharmacy and billing, and build what is specific to you. That is why projects start from $5,000, quoted to your scope. For comparison, our estimate for building a similar telemedicine and pharmacy platform from nothing is about $120,000 to $180,000 and 9 to 14 months.
5. **Patient data.** Doccure is HIPAA-ready and GDPR-ready. We sign a BAA.
6. **Access and audit.** Each organisation’s data is isolated in the database itself, and there is a tamper-evident audit trail. Details are in the [Trust Center](/trust-center/).
7. **Progress.** You see working software, not slides.
8. **Price.** Quoted to your scope. Video, SMS, WhatsApp and payment gateway fees are paid to those providers through your own accounts.
9. **Changes.** Priced and agreed before work begins.
10. **Ownership.** Your data belongs to you. Online payments run through your own Stripe account. Enterprise includes source code and on-premise deployment.
11. **Support.** Agreed in your contract. Ask us for the terms that apply to your plan.
12. **Leaving.** Your data is yours to take, and Doccure provides standards-based FHIR and HL7 interfaces for connecting to other systems.

One in three of our clients has come back for another project.

## Frequently asked questions

### How do I choose a healthcare software development company?

Check live healthcare work, speak to past clients, understand what they start from, and get ownership, price and exit terms in writing.

### Should I choose the cheapest quote?

Compare what each quote includes and the cost over three years. The cheapest build often has the most exclusions.

### Is a fixed price or hourly billing better?

A fixed price suits a well-defined first phase. Hourly or monthly billing suits ongoing work where priorities change. Many projects use both.

### How long should the selection take?

Two to four weeks is enough to send questions, hold calls, speak to references and read contracts.

### What should I prepare before contacting vendors?

Your users by role, one patient journey in plain steps, your countries, the systems you must connect to and your launch date.

## Put the twelve questions to us

See how we work on the [custom development page](/custom-development/), or [book a 30-minute call](/book-a-demo/) and bring your list.
