EDIM

Designing and building a talent agency's platform, CMS included

Product DesignFront-endCMSVisit edim.com.do ↗

EDIM
Shipped

Case file

Case file · EDIM

If you only read this

  1. 1

    The problem

    EDIM's roster lived in a PDF sent by email, one request at a time. Brands couldn't browse, the team did it all by hand and the numbers went stale.

  2. 2

    What I did

    Designed and built its first website: one home that splits brands from creators, a media kit where brands decide and a CMS the team runs alone.

  3. 3

    What changed

    29 creators now update from the CMS, leads arrive by brand or creator and edim.com.do replaced the PDF.

My role
Sole designer and developer: research, UX, UI, front-end, CMS
Team
Me + EDIM's two decision-makers + IT for the release
Platform
Responsive web, mobile first
Tools
Figma · Next.js · Strapi · Resend
Deliverables
Questionnaire · flows · wireframes · UI · site · CMS · handoff deck
Shipped · live
0129creators managed from the CMS, each with 8 metrics per network026spotlight slots, enforced by a CMS rule so the roster stays curated032audiences served from one page through an explicit brands / creators split

01

The starting point

EDIM had no website. Its roster lived in a PDF the team emailed to brands, one request at a time.

A questionnaire with EDIM's two decision-makers surfaced three frictions that shaped everything after.

  • “There's nowhere to browse the roster”

    A brand couldn't explore EDIM's creators on its own. It had to ask and wait for a PDF.

  • “Every request is manual work”

    Find the deck, attach it, reply. Time spent on logistics instead of on the brand.

  • “The numbers go stale”

    Metrics aged inside the PDF. Updating them meant redoing the deck.

02

Deciding what v1 is, and isn't

The site had two jobs: credibility, so a brand feels safe signing, and visibility, so creators want to be represented.

I ranked the goals with the stakeholders and, just as deliberately, wrote down what v1 would not do. That list explains choices that would otherwise look like omissions, and kept booking in v2.

In v1
  1. 1Generate brand leadsA brand route in the form: goal, budget, creators of interest
  2. 2Attract creatorsA parallel creator route: platforms, followers, engagement
  3. 3Earn credibilityReal per-creator metrics and published collaborations
  4. 4Remove manual workRoster and metrics edited in a CMS, not in a PDF
Not in v1
  • Booking a creator from the siteThat's v2
  • Filters or search in the rosterCurated selection first; learn if anyone needs more
  • A page per creatorThe media kit opens in a modal
  • Login or a private areaEverything is public
Scope agreed with the stakeholders before any visual design

03

Two audiences, one door

Brands and creators land on the same home page with opposite intentions.

Instead of writing for both at once, the page asks. Right after the credibility numbers, “I want to hire talent” or “I'm a creator” sends each one down its own path, and the contact form changes its fields to match.

edim.com.do · hero + numbers
“I want to hire talent”
Roster · 6 creators
Media kit
Brand form: goal · budget · creators
→ Lead in EDIM's inbox
“I'm a creator · join”
What EDIM does
About EDIM
Creator form: platforms · followers · engagement
→ Application in EDIM's inbox
One page, two routes: the split happens right after the hero

04

Where a brand makes up its mind

Every step of the brand journey exists to carry it to one moment: opening a creator's media kit. So the media kit got the most care: per-network metrics, audience and a “request a proposal” button that pre-selects the creator.

And the home shows only six creators. A CMS rule caps the spotlight, so the roster stays a showcase, not a catalog.

where brands decide
Media kit: per-network metrics, opened in a modal on the same page
In the spotlight · 6 In the CMS · 29
7
✕ A maximum of 6 creators can be in the spotlight.Strapi admin, on publish
29 creators in the CMS, 6 in the spotlight. The 7th is blocked

05

Built to stay up

I designed it and I built it: Next.js for the site, Strapi so the team edits creators without touching code and Resend so every lead lands in EDIM's inbox from its own domain.

If the CMS doesn't answer, the site falls back to data in the repository, so edim.com.do never goes down because of the CMS.

Content
Strapi CMScreators · services · references
published, every 60 s
edim-webNext.js on Vercel, rendered on the server
Visitoredim.com.do
↑ if the CMS doesn't answer
Fallback datakept in the repository
Leads
Contact formbrand or creator route
Server Actionno API to expose
Resendfrom web@edim.com.do · DKIM + SPF
EDIM's inboxreply-to = the person who wrote
How content and leads move through the system

06

More screens

Lo-fi wireframes, mobile first, before any visual design
What EDIM is, with credibility numbers
The roster: a curated spotlight of 6
References: published collaborations as proof
One form, two routes: brand or creator
Mobile first: most traffic comes from social, on a phone