If you are a business owner thinking about hiring a developer for the first time, there is a good chance you feel a bit out of your depth. Maybe you have no idea what questions to ask. Maybe you are worried about getting ripped off or ending up with something that does not work. Maybe you are not even sure whether you actually need a developer at all.
Take a breath. You are not alone. The vast majority of small business owners have never hired a developer before, and almost all of them felt exactly the way you do right now. The good news is that the process does not have to be mysterious or stressful. This guide will walk you through everything you need to know — in plain English, with no jargon.
It Is Completely Normal to Feel Out of Your Depth
Let us get this out of the way first. You run a business. You are an expert at what you do — whether that is making jewellery, running a shop, managing a team, or serving customers. Software development is a completely different world, and there is no reason you should already know how it works.
Most business owners we talk to start the conversation with some version of "I'm sorry, I don't really know how any of this works." That is absolutely fine. A good developer expects this and will meet you where you are. You would not expect a developer to walk into your workshop and know how to set a diamond. The same thing applies in reverse.
The fact that you are reading this guide means you are already doing the right thing — getting informed before making a decision.
Types of Developers: Who Does What?
Not all developers are the same. Here are the main types you will come across, and when each one makes sense.
- Solo developer (independent). One person who handles everything from understanding your needs to building and deploying the software. Best for small to medium projects where you want a direct relationship with the person doing the work. Communication is usually simpler because there is no chain of people between you and the builder.
- Freelancer (via a platform). Similar to a solo developer, but typically found through platforms like Upwork or Fiverr. Quality varies enormously. Some are excellent, some are not. It can be harder to vet them, and you may have less recourse if things go wrong. Best for small, well-defined tasks where you know exactly what you need.
- Small agency (2–10 people). A small team that can handle larger projects and usually has designers as well as developers. Good for projects that need multiple skill sets. Costs more than a solo developer, but you get a broader team. Communication may go through a project manager rather than the developer directly.
- Offshore team. A development team based in a country with lower labour costs, often India, Eastern Europe, or South East Asia. Can be significantly cheaper on paper, but comes with challenges: time zone differences, language barriers, and cultural differences in how work is managed. Best for businesses that have some technical knowledge in-house to manage the relationship. Not usually recommended for a first-time buyer who needs close collaboration.
For most small businesses hiring a developer for the first time, a solo developer or a small agency in your own country is the safest starting point. The direct communication and shared context make everything easier.
What to Look For in a Developer
You do not need to evaluate someone's code to know whether they are a good fit. Here is what actually matters.
- A portfolio of shipped work. Not a list of technologies they know, but actual things they have built that are live and working. Can they show you real products that real people use? If they have built things for businesses similar to yours, even better.
- Clear communication. When you talk to them, do you understand what they are saying? Do they explain things in a way that makes sense to you? A developer who cannot communicate clearly with a non-technical person will struggle to build something that fits your needs.
- Fixed pricing (or at least a clear estimate). A developer who gives you a fixed price for a defined scope is taking on the risk of their own estimate being wrong. That is usually a sign they have done this before and know what they are doing. Hourly billing is not inherently bad, but for a first-time buyer it can feel risky because you have no idea how many hours something "should" take.
- Willingness to explain things in plain English. You should never feel stupid in a conversation with your developer. If they make you feel that way, that is a them problem. A good developer will patiently explain concepts without talking down to you.
- A clear process. They should be able to tell you exactly what happens after you say yes — what the steps are, what you will need to provide, how long each stage takes, and when you will get to see progress.
Red Flags: When to Walk Away
Here are warning signs that should make you think twice before hiring someone.
- No portfolio. If they cannot show you anything they have built, you have no way to judge the quality of their work. Everyone has to start somewhere, but you probably do not want your business-critical project to be someone's first.
- They will not give a fixed quote. If they refuse to commit to any kind of price and insist on billing hourly with no cap or estimate, you could end up with a bill that is far higher than expected. A developer who has done similar work before should be able to give you at least a ballpark figure.
- Heavy use of jargon. If every conversation leaves you more confused than when it started, that is a problem. Some developers hide behind jargon — either because they cannot communicate clearly or because they want you to feel dependent on them. Neither is good.
- No process explanation. If they cannot describe how the project will work — what happens first, what happens next, when you will see something — they are probably making it up as they go along.
- They want to start coding immediately. A developer who jumps straight into building without first understanding your business, your problem, and your goals is almost guaranteed to build the wrong thing. Discovery and planning should always come before a single line of code is written.
- They never push back. If a developer agrees with absolutely everything you say and never asks "are you sure you need that?" or "have you considered this alternative?", they are not thinking critically about your problem. You want someone who will challenge your assumptions — respectfully — because that is how you end up with a better result.
What the Process Typically Looks Like
Every developer works slightly differently, but a professional engagement usually follows something like this.
- Discovery call. A conversation (usually 30–60 minutes) where the developer asks about your business, your problems, and what you are hoping to achieve. This is not a sales pitch — it is a fact-finding exercise. You should do most of the talking.
- Scoping. The developer goes away and works out what needs to be built, how long it will take, and how much it will cost. They may come back with questions. This stage might take a few days.
- Quote and proposal. You receive a written proposal that describes what will be built, what it will cost, and how long it will take. This is where you decide whether to go ahead. There should be no pressure.
- Build. The developer starts building. A good developer will show you progress regularly — not just at the end. You should expect to see something working within a few weeks at most, even if it is not finished.
- Review and feedback. You test what has been built and provide feedback. Things get adjusted. This back-and-forth is normal and healthy — it is not a sign that something has gone wrong.
- Deploy. The finished software goes live. The developer handles the technical side of making it available to you and your users.
- Support. After launch, bugs may surface and small adjustments may be needed. A good developer will include a support period after launch. Make sure you understand what is included and what costs extra.
What Does It Cost?
This is the question everyone wants answered, and the honest answer is "it depends." But here are some realistic ranges for Ireland and the UK as of 2026.
- Solo developer hourly rate: €50–80 per hour. This is typical for an experienced independent developer in Ireland or the UK.
- Agency hourly rate: €100+ per hour. Agencies have higher overheads (offices, project managers, designers), which is reflected in the price.
- Fixed-price projects for SMBs: €3,000–25,000 for most small business projects. A simple internal tool or basic web application might be at the lower end. A more complex system with multiple user types, integrations, and custom workflows will be at the higher end.
Be cautious of quotes that seem dramatically lower than these ranges. If someone quotes €500 for something that three other developers have quoted €8,000 for, there is a reason. Either they have misunderstood what you need, or the quality of the result will reflect the price.
Also be aware that the cheapest option upfront is not always the cheapest in the long run. Poorly built software costs more to fix, maintain, and eventually replace than software that was built properly the first time.
How to Brief a Developer
Once you have found someone you want to talk to, the next step is explaining what you need. This can feel daunting, but it does not have to be. You do not need technical knowledge — you just need to describe your problem clearly.
We have written a full guide on this: How to Brief a Developer When You Don't Know What You Need. The short version is: start with the problem (not the solution), describe your current workflow, explain who will use it, share examples of things you like and dislike, and be upfront about your budget and timeline.
Questions to Ask Before You Hire
Here are some good questions to ask any developer before you commit. You do not need to ask all of them, but pick the ones that matter most to you.
- Can you show me something similar you have built before?
- What does your process look like from start to finish?
- Will you provide a fixed price, or do you bill hourly?
- How often will I see progress during the build?
- What happens if I need changes after the project is finished?
- Do you offer ongoing support, and what does it cost?
- Who owns the code when the project is complete?
- What happens if the project takes longer than expected — who absorbs the extra cost?
- Can you explain in plain terms how the software will work?
- What do you need from me during the project?
Pay attention to how they answer as much as what they answer. Are they patient? Do they explain things clearly? Do they seem genuinely interested in your business, or are they just trying to close the sale?
Funding: The LEO Grow Digital Voucher
If you are a small business in Ireland, there is a funding option worth knowing about. The Local Enterprise Office (LEO) offers a Grow Digital Voucher that can cover 50% of eligible digital project costs, up to €5,000. That means if your project costs €10,000, the LEO could fund €5,000 of it.
Eligibility requirements include having 1–50 employees, trading for at least 6 months, and completing a Digital for Business programme beforehand. You apply through your local LEO office. It is worth checking your eligibility before you start — having half the cost covered makes a significant difference for a small business.
Your developer should be able to help you with the application if needed, or at least provide the kind of quote and project description the LEO requires.
You Might Not Even Need a Developer
Here is something that an honest developer will tell you: not every problem requires custom software. Sometimes the answer is a better use of tools you already have. Sometimes it is a no-code platform like Airtable or Notion. Sometimes it is a Shopify app that already exists.
A good developer will tell you this upfront, even if it means losing the work. If someone is trying to sell you a custom build when a €20-a-month subscription would solve the same problem, that is a red flag.
Ready to Have the Conversation?
If you have been putting this off because it all felt too complicated or too risky, we hope this guide has made it feel a bit more manageable. Hiring a developer does not have to be a leap of faith. With a little preparation and the right questions, you can find someone who genuinely understands your business and builds something that makes your life easier.
At JMS Dev Lab, we are happy to have an honest conversation about whether you even need a developer. No sales pressure, no jargon, no obligation. If custom software is the right answer, we will explain exactly what that looks like. If it is not, we will tell you that too.
Get in touch — even if all you have is a vague idea and a list of frustrations. That is a perfectly good place to start.
You might also find these useful: How to Brief a Developer When You Don't Know What You Need and Why We Quote Fixed Prices for Software Projects.