Freelancer or software house: who should build your software

What really changes

With a freelancer you talk to the person writing the code. Questions reach someone who can answer, decisions don't pass through three people and the hourly cost doesn't pay for a structure. The limit is that one person has one pair of hands.

With a software house you talk to a salesperson, then a project manager, then the developer. There are more skills and more people to cover absences. The limit is that your project can end up with the most junior member of the team, and each change takes a longer route.

When a freelancer works well

• Business software, a website or an app for a small or medium company.
• Work that moves in small steps, with you testing and correcting.
• You want to talk to the same person, even years later.
• A project with a precise budget, in stages.

When you need a software house

• The project needs several developers in parallel, with tight deadlines.
• A tender or specification asks for ISO certifications or a minimum turnover. I don't hold those certifications yet.
• You need rare skills together, such as embedded systems or very large data volumes.
• Your purchasing department only works with structured companies.
• The service can never stop and you need a team in shifts.

These things are worth saying up front, rather than waiting for the project to get stuck.

What to ask anyone

This goes for freelancers and software houses alike:

1. Who will write the code, by name? Can I talk to them?
2. Who owns the code and the data? Can I have them whenever I want?
3. What happens if we stop working together?
4. Which technologies? Could another developer carry on?
5. Can I see a similar program, working?
6. How is payment made? In stages, or all up front?
7. Where are the backups, and have they been tested?

Vague answers to these questions tell you more than any quote.

What I do

I have been programming since 2010. The analysis is free, and I split large projects into milestones. After delivery I look after the software with maintenance, and if you want to move to another provider I give you the code. The work section shows what I have built, and About tells how I work. To compare the kind of program to choose, read custom or off the shelf.

Frequently asked questions

What if the freelancer falls ill or goes on holiday?

That is the real risk. Ask what happens in that case. I keep daily backups, the code is yours, and with 24/7 on-call you can phone me at any hour. It is still one person: for a service that can never stop, think hard about it.

Does a software house always cost more?

Usually yes for the same work, because it has more fixed costs: sales, project managers, offices. In exchange it has more people and a structure. If you need that structure, the cost is justified.

Who owns the code?

That has to be written in the contract in any case. With me the software stays yours: if you ask, I give you the code and database, including to move to another provider.

Do you take on large jobs?

Yes, split into milestones paid one at a time. I have been programming since 2010 and have delivered more than 200 projects. If you need ten people working in parallel, though, I am not the right person.

Read more

• The service: Custom business web apps
• More pages like this: Before you decide