---
title: Advorel
description: A practical look at Advorel, its public Developer Relations work, and the lessons contributed by people behind the projects featured in this guide.
url: https://pr-2-5bfc5f2f5cb7.thally.app/advorel
---

# Advorel

A practical look at Advorel, its public Developer Relations work, and the lessons contributed by people behind the projects featured in this guide.

Advorel is a Developer Relations company that helps developer-focused companies with community, events, videos, technical content, and related adoption work. Its services include technical writing and documentation, developer-focused videos, developer events, and community building and management.

Some examples in this guide come from people who have worked together through **Advorel**. Their real DevRel work gives us concrete practices, outcomes, and lessons to study.

## What Advorel works on

Based on Advorel's current public site, its work spans four practical areas.

### Technical writing and documentation

Examples of the work it lists include:

- technical writing;
- blog posts and articles;
- documentation;
- case studies;
- whitepapers.

The lesson for this guide is broader than the service list: content is most useful when it helps a developer complete a task, understand a system, or make a decision.

### Developer-focused video

Advorel lists tutorial videos, product demos, and conference-talk preparation.

Video works especially well when the learner needs to **see** a workflow: navigating a UI, debugging, setting up an environment, or following a live technical process.

### Developer events

Its public services include workshops, hackathons, coding challenges, webinars, meetups, conference support, and livestreams.

[Ekemini Samuel](https://www.linkedin.com/in/ekeminisamuel/) organized the [Mojo Africa 2026 event](https://lnkd.in/p/erXYFN3z), which is used as a community event case study in this guide.

Events create a different kind of evidence from content. You hear questions in real time. You can watch where people get stuck. You can test whether the explanation that looked clear on paper actually works with a room full of developers.

### Community building and management

Advorel lists Discord/Slack community management, advocacy and ambassador programs, moderation, engagement strategy, and developer feedback loops.

That last part matters: a healthy community is not only a distribution channel. It is a way to hear what developers are experiencing and route that information back into product, documentation, support, and education.

## How we will document Advorel work

Every case study should follow the same standard:

```text
Developer / business problem
        ↓
Context
        ↓
Advorel's role
        ↓
What the team actually did
        ↓
Evidence / outcome
        ↓
What did not work or remained uncertain
        ↓
Lesson another DevRel team can reuse
```

That keeps the page useful even for somebody who never becomes an Advorel client.

## Contributor stories

The Advorel team contributing experience to this guide includes:

- [Faith Ayoola Oni](https://www.linkedin.com/in/onifaithayoola)
- [Joy Ndukwe](https://www.linkedin.com/in/joy-ndukwe/)
- [Abimbola Adedotun](https://www.linkedin.com/in/abimbola-adedotun/)
- [Samuel Uzor](https://www.linkedin.com/in/samuel-uzor98/)
- [Ekemini Samuel](https://www.linkedin.com/in/ekeminisamuel/)

## Case studies belong here only when we can prove them

A strong case study needs more than a logo and a compliment.

Before publishing one, collect:

- the original problem;
- timeframe;
- audience;
- scope of work;
- what Advorel actually owned;
- evidence before and after;
- client-approved metrics or qualitative results;
- constraints;
- lesson;
- permission for names, logos, screenshots, and quotations.

If we cannot verify a metric, we leave it out.

## Lessons we want this page to surface

As contributor material arrives, prioritize lessons such as:

- what developers actually responded to;
- where a campaign or event created friction;
- how technical content was reviewed;
- how community feedback reached the client team;
- how DevRel goals were measured;
- trade-offs between speed and quality;
- what the team would do differently next time.

That is more useful than a page full of claims that everything went perfectly.

## Further reading

- [Advorel](https://www.advorel.com/)
- [Advorel services](https://www.advorel.com/services)

## Related pages

- [Case Studies](/case-studies)
- [Reporting to Leadership](/reporting-to-leadership)
- [Community Authors](/community-authors)