When an NGO needs a new website or a major redesign, one of the first decisions is who should build it.
Should the organization use its existing communications or IT team? Should it hire a freelancer? Or is it better to work with a professional web design agency?
There is no universal answer.
For a small NGO with a simple website, an in-house team may be perfectly capable of managing the project. For a larger organization with complex content, multiple stakeholders, donor requirements, resource libraries, integrations, or a need for extensive user research, an experienced agency can provide capabilities that are difficult to assemble internally.
The important question is not simply:
“Can our team build a website?”
It is:
“What does our website need to accomplish, and do we have the people, skills, time and processes to deliver that effectively?”
This guide compares the advantages and disadvantages of building an NGO website in-house versus hiring a web design agency, with particular consideration for NGOs and development organizations in Kenya and Africa.
In general:
| Factor | In-House Team | Web Design Agency |
|---|---|---|
| Cost | Potentially lower if staff already exist | Higher upfront project cost |
| Organizational knowledge | Excellent | Requires onboarding |
| UX expertise | Depends on team | Usually available |
| Web development expertise | Depends on team | Core competency |
| Strategic discovery | Often limited by internal familiarity | External perspective |
| Project management | Internal responsibility | Agency responsibility |
| Design expertise | Depends on team | Usually strong |
| SEO | Depends on team | Can be built into project |
| Accessibility | Depends on expertise | Specialist capability |
| Complex integrations | Depends on technical team | Usually easier |
| Content migration | Internal responsibility | Can be handled by agency |
| Long-term maintenance | Strong internal ownership | Usually available as support |
| Objective assessment | More difficult | External perspective |
| Scalability | Depends on internal resources | Can scale specialist resources |
| Best suited to | Simple, continuously managed websites | Strategic, complex or high-impact websites |
The right choice depends heavily on your organization’s existing capabilities and the complexity of the project.
An in-house website project means that most of the work is performed by people employed by the NGO.
That might include:
An NGO might have a communications officer managing the project, an IT officer handling the technical implementation, and a graphic designer creating the visual identity.
Alternatively, an organization might already employ a full-time web developer.
This distinction matters.
Having someone who knows WordPress, for example, does not necessarily mean the organization has all the skills required to plan, research, design, develop, optimize and launch a modern institutional website.
A website project can involve several different disciplines.
With an agency, the NGO brings in an external team to handle some or most of the website project.
A professional agency may provide:
The NGO remains the subject-matter expert, while the agency provides specialist digital expertise.
Ideally, this becomes a collaboration rather than a simple outsourcing arrangement.
There are several situations where building internally makes sense.
If you already have a capable digital team, you may not need an external agency.
For example, your team might include:
If these people already work for the organization and have sufficient capacity, an internal project can be very effective.
The biggest advantage is that the team already understands the organization.
They know:
That institutional knowledge is valuable.
An NGO does not necessarily need an agency for every website project.
If the website essentially consists of:
then an experienced internal team may be able to manage the project successfully.
A relatively straightforward website does not require the same level of specialist expertise as a large knowledge platform or a website with complex integrations.
One of the strongest arguments for internal ownership is speed after launch.
If your communications team regularly needs to:
then having internal people who understand the CMS can be extremely useful.
You don’t want to contact an external agency every time someone needs to update a paragraph.
A good agency should therefore empower your internal team rather than make it dependent on the agency.
If your organization intends to invest in digital capabilities for the long term, building internally can be part of that strategy.
Instead of repeatedly outsourcing digital work, an NGO might decide to develop internal expertise in:
This can make sense for larger organizations with sufficient budgets and ongoing digital requirements.
Despite these advantages, internal development has several risks.
This is one of the most common misconceptions.
A person may be very capable of managing a CMS without being experienced in:
Building a website is not simply a matter of selecting a theme and entering content.
The decisions made before development can have a much greater impact on the final result than the technology itself.
This is a surprisingly important issue.
An NGO’s employees understand the organization extremely well.
That is an advantage—but it can also become a weakness.
Internal teams often know:
“This is how we describe ourselves.”
But website visitors may be asking:
“What does this organization actually do?”
Those are not necessarily the same thing.
Internal stakeholders can also become attached to:
An external UX team can challenge these assumptions.
For example, instead of organizing a website around internal departments, user research might reveal that visitors actually think in terms of:
That external perspective can be extremely valuable.
This is perhaps the biggest practical problem.
The communications officer still has to publish reports.
The program team still has deadlines.
The IT team still has infrastructure responsibilities.
Management still needs approvals.
Then suddenly everyone is expected to spend several months working on a website.
The result can be a project that constantly gets delayed.
An agency’s primary responsibility, meanwhile, is the website project.
That difference in focus matters.
Imagine an NGO’s website was built by its IT officer.
Two years later, that employee leaves.
Who understands:
If the answer is “only that person,” the organization has created a significant operational risk.
Good internal development therefore requires documentation and proper technical governance.
For many NGOs, an agency is particularly valuable when the website is considered a strategic digital project rather than simply an IT task.
A major advantage of an agency is access to a team rather than a single individual.
Depending on the agency, your project may involve:
You may not need all of these people full-time.
That is precisely the advantage.
You can access specialist expertise for the duration of the project without hiring an entire permanent team.
An experienced agency can look at your organization as an outsider.
That allows the team to ask questions such as:
These questions can lead to major improvements.
This is particularly important for NGOs.
Your website may have many different audiences:
These groups don’t necessarily use the website in the same way.
A website built around the organization’s internal structure can become difficult for everyone else to navigate.
A professional UX process can include:
The result is a website designed around actual user needs rather than assumptions.
Not every NGO needs a complex website.
But some do.
For example, an organization may need:
At this point, the website starts looking less like a brochure and more like a digital product.
That is where specialist development expertise becomes increasingly important.
A good agency doesn’t start every project from zero.
It brings lessons from previous projects.
For example, if an agency has previously redesigned a large resource repository, it has already encountered issues involving:
That experience can shorten the learning curve on your project.
For development-sector organizations, this experience can be especially valuable because NGO websites often have requirements that differ considerably from conventional corporate websites.
Agency development isn’t automatically better.
There are genuine disadvantages.
An agency will generally cost more than asking an existing employee to build a website.
But the comparison needs to be made carefully.
The true cost of an internal project includes:
An agency may have a higher invoice while still producing a lower total cost over the life of the project.
Your employees understand your organization already.
An agency doesn’t.
It needs time to learn:
This is why a proper discovery phase is important.
The agency should not simply receive a sitemap and immediately start designing pages.
This is a legitimate concern.
If an agency controls everything, your organization may struggle to operate independently.
For example, you shouldn’t need to ask the agency to:
“Please change this news article.”
Your NGO should normally be able to manage everyday content itself.
Before signing a contract, clarify:
A professional agency should make the organization stronger, not hostage to the vendor.
The most useful way to approach this decision is not to ask:
“Which is cheaper?”
Instead ask:
“Which team can deliver the website we actually need?”
Create a capability matrix.
| Capability | Internal Team | Agency |
|---|---|---|
| Organizational knowledge | High | Medium |
| Content knowledge | High | Low–Medium |
| UX research | ? | ? |
| UX design | ? | ? |
| UI design | ? | ? |
| Development | ? | ? |
| SEO | ? | ? |
| Accessibility | ? | ? |
| Security | ? | ? |
| Performance | ? | ? |
| Content migration | ? | ? |
| Project management | ? | ? |
| User testing | ? | ? |
| CMS training | ? | ? |
| Long-term maintenance | ? | ? |
Don’t automatically give your internal team a “yes.”
Ask whether someone on the team has demonstrable experience in each area.
Building internally is probably appropriate when:
If most of these are true, internal development can be a very reasonable choice.
An agency is often the better option when:
The more of these apply, the stronger the case for an agency becomes.
There is another option that NGOs sometimes overlook.
You don’t necessarily have to choose between:
100% internal
and
100% outsourced.
A hybrid model can be extremely effective.
For example:
This gives the project the best of both worlds.
The NGO retains ownership and institutional knowledge while accessing specialist expertise where it is needed.
Consider an NGO with thousands of reports, research papers, videos and other resources.
The internal communications team knows the content extremely well.
But users complain that they cannot find what they need.
The problem isn’t simply the website’s visual design.
It may involve:
An agency experienced in UX research and knowledge platforms could investigate how users search for information and redesign the system accordingly.
The internal team would then remain responsible for publishing and managing resources after launch.
That is a strong example of where a hybrid approach can make more sense than either extreme.
One of the biggest mistakes NGOs make is treating the website as primarily a graphic design exercise.
The process becomes:
But a successful NGO website should begin much earlier.
A more strategic process looks like:
Research → Strategy → Information Architecture → UX → UI → Development → Content → Testing → Launch → Optimization
The technology comes after understanding the problem.
NGO websites often contain enormous amounts of information.
You may have:
Simply placing these into a menu does not solve the problem.
Information architecture determines how these pieces relate to one another.
For example, a research report might belong to:
A well-designed information architecture can make that report discoverable through multiple routes.
That can be far more valuable than simply making the homepage look modern.
This is particularly important in Kenya and across much of Africa.
Your website needs to work for people using:
A website that looks impressive on a large desktop monitor but takes too long to load on a mobile connection is not a successful digital experience.
Performance should therefore be considered during design and development—not added as an afterthought.
An NGO website may serve people with a wide range of abilities and circumstances.
Accessibility considerations can include:
If your internal team does not have accessibility expertise, this is another area where an experienced agency can add significant value.
There is no single answer.
An in-house project can appear inexpensive because the organization isn’t receiving a large external invoice.
But staff time still has a cost.
An agency project may have a higher upfront cost, but that price can include capabilities that would otherwise require several employees or consultants.
The more important calculation is:
Total project cost = money spent + staff time + opportunity cost + ongoing technical costs + risk
For an NGO, the cost of a failed website project can be much greater than the original development budget.
A website that cannot be maintained, is difficult to use, performs poorly, or fails to serve important audiences may need to be rebuilt much sooner than expected.
Before choosing between an internal team and an agency, ask:
Don’t begin with technology.
Begin with objectives.
Is the goal to:
A 15-page organizational website is fundamentally different from a knowledge platform containing thousands of resources.
Be honest.
Having an IT department does not automatically mean having UX, SEO, accessibility, content architecture and web development expertise.
A website project requires meetings, content reviews, approvals, testing and content preparation.
Who will actually do this work?
This question should be answered before development begins.
You can use the following rule of thumb.
Your team has the expertise + the time + the website is relatively simple.
The project is strategically important + complex + your internal team lacks specialist capacity.
You have strong organizational knowledge internally but need external digital expertise.
For many established NGOs, the hybrid model is particularly attractive.
If you decide to hire an agency, don’t simply hand over the project and disappear.
The strongest projects are collaborative.
Your organization should remain involved in:
The agency should bring specialist expertise and challenge assumptions where appropriate.
The result should be a website that your organization understands and can operate, rather than a mysterious system that only the vendor understands.
There is nothing inherently better about building an NGO website in-house or hiring an agency.
The right decision depends on your organization’s capabilities, the complexity of the project and the strategic importance of the website.
For a straightforward website and a capable digital team, in-house development can work extremely well.
For a major redesign, complex content ecosystem, knowledge platform or strategic digital transformation, an experienced agency can provide specialist capabilities that are difficult to replicate internally.
And for many NGOs, the best answer is somewhere in between:
Your organization provides the mission, knowledge and content. Your digital partner provides the research, strategy, design and technical expertise.
The objective isn’t simply to launch a new website.
It is to build a digital platform that makes your organization’s work easier to understand, easier to discover and more useful to the people you serve.
Before choosing a developer or agency, start by assessing your website’s current UX, content structure, technical performance and organizational requirements.
If you need an experienced digital team to help with that process, Zedafrica works with NGOs and development-sector organizations on strategy, UX research, UI design and website development—from initial discovery through to launch and training.
