Agency or freelancer to build your website? A freelancer is often enough for a simple, clearly described project. An agency may be more convenient when the project requires several specializations, coordination or care after launch.
- Compare the scope and responsibility, not just the price.
- Assess live projects similar to the website you're planning.
- Agree in writing on access to the domain, hosting, files and accounts.
The choice doesn't come down to deciding which model is better. What matters is the project scope, the competencies needed, the consequences of possible downtime and the support expected. Both an independent specialist and a team can work at different levels, so the final decision should concern a specific offer and contractor.
Not the collaboration model, but the project's needs
The best choice depends on the project, not on the label “agency” or “freelancer” itself.[4][5] An agency here means an organized contractor using the work of a team or subcontractors. A freelancer is an independent contractor who may work alone or collaborate with other specialists. Neither of these models determines quality on its own.
The starting point should be four issues: the scope of work, the number of competencies needed, the website's importance for the business and the way it will be handled after publication. Even websites that look similar can differ in features, integrations and requirements related to later development.
Before talking to contractors, it's good to write down the expected result, the features needed, integrations, materials, the people involved in approval and the scope of care after launch. Such a description lets you first assess the project, and only then the collaboration model.
When to choose a freelancer and when an agency
A freelancer often makes sense for a simple and well-described project, but you need to check their availability and support plan.[4][5] This doesn't mean every independent contractor works alone, cheaper or faster. It depends on their experience, process and the real scope of the job.
Situations in which a freelancer may be enough
- The scope is limited and has been described unambiguously.
- The project doesn't require coordinating many specializations at the same time.
- The company knows who will prepare the content and materials and who will approve them.
- Availability after publication and the way changes are reported were agreed before work started.
This model can suit a project in which direct communication with the person doing the work makes decision-making easier. However, you still need to confirm what will happen if the contractor is unavailable and who will take over later fixes.
Signs that a project requires a team or a broader organization
An agency may be more convenient for a project that requires several specializations, or cover and care after launch.[4][5] However, being an agency alone doesn't guarantee quality, competence or continuity. These elements must follow from the offer and the way the work is organized.
When the job is online stores, a booking system or a website with integrations, the assessment has to take into account not only the look, but also the number of interdependent tasks, the testing process and later support.
| The nature of the project | What needs to be assessed | A model to consider |
|---|---|---|
| A simple informational website with a clearly defined scope | The contractor's availability, responsibility for materials and support after publication | A freelancer may be enough |
| A website developed with further content and features | The change process, additional competencies and continuity of support | A freelancer with collaborators, a small studio or an agency |
| A project with integrations or many stages | Coordination of specialists, testing, responsibility and cover | An agency or another contractor providing the right organization |
The matrix doesn't replace assessing a specific offer. It only shows that as the number of interdependent elements grows, the way responsibility is divided becomes more important.
How to compare website offers
Offers should be compared by what they actually include, not just by the final price. Different quotes can describe different results, stages, revisions, rules for handing over materials and care after the build.[6][7] A higher price doesn't automatically mean a better result.
The scope that should be described before the quote
A shared brief lets you give every contractor the same requirements. If you need a website quote, the description should define the expected result, the features, responsibility for content and materials, the approval stages and needs after the build.
| Comparison element | What to agree before choosing | Why it affects the offer |
|---|---|---|
| Scope and result | What exactly will be designed, built and launched | A general description of the website doesn't define a comparable job |
| Project stages | When presentations, approvals and acceptance take place | Shows how the collaboration is organized |
| Revisions | How they're reported and which changes the offer covers | Separates the agreed scope from additional work |
| Content and materials | Who is responsible for the copy, photos and providing them | Clarifies the division of duties |
| Files, rights and accounts | What will be handed over at acceptance and on what terms | Affects the ability to develop the project further |
| Care after the build | Who handles fixes and further changes | Shows what happens after the basic job is finished |
What to agree in the contract and at website acceptance
You shouldn't compare offers without checking what exactly will be delivered and what will happen after the project ends. The agreements should cover the scope, deadlines, revisions, payments, the handover of files and rights, and how things will work after the build.[6][7] The scope of rights and obligations needs to be tailored to the specific contract; this list isn't legal advice.
- The result and acceptance criteria
- A description of what the contractor is to hand over and how the completion of the work will be confirmed.
- The scope of revisions
- Distinguishing revisions within the agreements from new work that requires a separate quote.
- Materials and access
- A list of files, accounts and data to be handed over at acceptance.
- Support after launch
- Agreeing how errors, changes and further development are to be reported.
How to check the portfolio and technical preparation
A portfolio is best assessed on live websites similar in scope to the planned project, not just screenshots. Ask for such projects and open them on a computer and a phone.[6][7] However, a portfolio doesn't show the whole collaboration process or the current composition of the team.
Questions about the contractor's role in the projects shown
- Was the contractor responsible for the whole project, or only for a selected part?
- Does the project shown have a scope similar to the planned job?
- Who will actually work on the new project?
- What did the approvals and the handover of the website look like?
- Who looked after the project after it was launched?
Such questions help distinguish a general brand presentation from the experience of the people who will be responsible for the new job.
What can be assessed without a technical audit
On a live project, you can check the website's basic structure, how it works on mobile devices, the URLs and whether important content is available to search engines.[2] Meeting these recommendations doesn't guarantee indexing or a high ranking in the results.
- Open the most important subpages on a phone and a computer.
- Assess whether the website's layout makes it possible to find important content.
- Look at the addresses of the individual subpages and how they're organized.
- Ask what the contractor's scope of responsibility was for the technical preparation.
Speed and technical correctness are signals of quality, but they don't replace assessing the content, conversion and fit with the business.[2][3] The result of a single test shouldn't therefore be treated as a ranking of contractors.
The domain, hosting and access: what should stay on the company's side
Before work starts, you need to establish who has access to the domain, hosting, the content management system, files and accounts related to the website, and how they'll be handed over. The domain and hosting are separate services, so each of these requires separate agreements.
If the company uses a .pl domain, it should be listed as its registrant and have access to the data and the authinfo code.[1] The precise term is “domain registrant”, not its owner. These rules apply to .pl domains; other extensions may be subject to different procedures.
- Domain
- Confirm the registrant details, access to management and the ability to obtain the authinfo code for a .pl domain.
- Hosting
- Establish whose account the service runs on and who holds the data needed to manage it.
- CMS and files
- Specify which admin accounts and materials will be handed over at acceptance.
- Service accounts
- Write down who has access to the tools related to the website and how permissions will be handed over.
The list of access rights should be included in the agreements and the acceptance documentation. This doesn't replace tailoring rights and obligations to the specific contract or legal advice in an unusual project.
What neither an agency nor a freelancer can guarantee
Choosing the contractor model alone doesn't guarantee the quality of the website, results in Google, timeliness or a good collaboration. The result has to be assessed through the real scope, the competencies of the people involved in the project, the process and the agreed rules for later support.
An agency doesn't automatically ensure continuity, just as working with a freelancer doesn't have to rule it out. Declarations about cover, support and availability should be confirmed in the specific offer. Likewise, meeting basic technical recommendations isn't a guarantee of search rankings.[2]
The final decision should be based on the quality of the specific project, a comparable scope of the offer and a clear division of responsibility. The collaboration model is one of the criteria, but it doesn't replace verifying the contractor.
Frequently asked questions
Will a freelancer always be cheaper than an agency?
No. The price depends on the scope, experience, process, responsibility and the elements included in the offer. Not every freelancer works cheaper, and an agency's higher quote doesn't guarantee a better result. First you need to standardize the requirements, and then compare the scope.
Can a small studio be an alternative to an agency and a freelancer?
It can be considered as a third model, but it should be assessed by the same criteria: competencies, scope of responsibility, availability and support rules. The name of the model doesn't replace assessing the specific contractor.
Sources
- The benefits of registering a name in the .pl domain, NASK / the .pl domain registry.
- SEO Starter Guide: The Basics, Google Search Central.
- Understanding Core Web Vitals and Google search results, Google Search Central.
- An agency, a freelancer or a website builder? Who to commission your website from, Getinweb.
- A freelancer or an agency: who to commission your website from, Bandziuk.
- How to choose a website contractor? 10 questions you must ask, Getinweb.
- A request for quotation, gov.pl.
Planning a new website?
Describe the scope, the number of subpages and the features you need. We'll prepare a clear scope for the design and build.
Sponsored article
