Agency, freelancer or in-house team: who should build your platform in Greece

Every business that outgrows its first website reaches the same fork. Hire a freelancer, hire an agency, or hire developers of its own. The decision is usually made on the first quote, and it is the wrong number to decide on. The build is the short part of a platform's life. What you are really choosing is who will understand the system in year three, and what happens on the day they stop being available.

We are an agency, so take the following with that in mind. But we have also been the team that inherited the other two arrangements more than once, and each of them is genuinely the right answer for somebody. The point is to know which somebody you are.

Start with the freelancer, because it is where most Greek businesses start and often where they should. A good independent developer is fast, direct and cheaper than any agency, because there is no account manager, no office and no margin on other people's time. For a marketing site, a landing page, a small store or a well-defined piece of work with an end, a freelancer you trust is a perfectly rational choice.

The risk is not quality. It is concentration. One person holds the knowledge, the credentials and often the hosting account. They get ill, they take a full-time job, they move to Berlin, or they simply become busy with a bigger client — and the platform that runs your orders has a bus factor of one. If you go this way, protect yourself in writing: the code in a repository you own, the domain and hosting in your company's name, the credentials in a place you control, and some documentation of how the thing is deployed. None of that is an insult to a good freelancer. The good ones will have done it already.

The in-house team is the opposite trade. Nobody will ever know your business better than people who work inside it every day, and for a company whose product is software, owning the team is not optional — it is the business. If the platform is what you sell, hire.

For everyone else, the arithmetic is harsher than it looks. One developer is not a team: a platform needs design, front end, back end, infrastructure and someone who has done a migration before, and no single hire covers all of them. Two or three developers still leave you recruiting for the skills you lack, managing people in a discipline you may not know how to evaluate, and exposed every time one of them leaves — which, in a market where good developers can work remotely for foreign salaries, they will. The cost is not the salary line. It is everything around it.

The agency sits between the two. You buy a team rather than a person: design, engineering, testing, infrastructure and, in our case, photography and film, without hiring any of them. You buy continuity, because the knowledge is shared across people and written down in the repository rather than held in one head. And you buy experience of problems you have not had yet, because the agency has met them on other projects — the payment provider that changed its API, the ERP with an undocumented field, the migration that nearly lost a year of search rankings.

The weaknesses are real too. An agency costs more per hour than a freelancer. It can be slower to start, because it plans before it builds. And a bad one is worse than either alternative: it puts its juniors on your project, subcontracts the hard parts, and holds the code hostage when you try to leave. Which is why the questions you ask an agency before signing — who does the work, who owns the result, how you would leave — matter more than the rate.

So the honest decision tree is short. If the work is small and has an end, a good freelancer, with the code and accounts in your name. If software is your product and you can afford to build a real team, hire one, and use outside help for the gaps while you do. If the platform is central to the business but software is not what you sell — a store, a booking engine, a portal, a site that talks to your ERP, your invoicing and your couriers — that is what agencies are for.

There is also a fourth answer that many Greek businesses end up with, and it is often the right one: a mix. An agency builds the platform and runs it, and an internal person, often someone already in the company, owns the content, the priorities and the relationship. That person does not need to code. They need to know what the business wants next and be able to read the plan they are shown.

Whichever you choose, the protections are the same. The code belongs to you and lives somewhere you can reach. The domain and the hosting are in your name. The stack is one that other developers know, so that if the person or the company building it disappears, you can hand it to someone else. React, Next.js, Node.js and PostgreSQL are not our choice because they are fashionable; they are our choice because any competent developer on earth can pick them up. That is the real insurance, and it costs nothing extra on day one.