← Selected work

Case study

Gley.tv: Fixing the funnel that leaked 9 out of 10 signups

Macedonia's first streaming platform had traffic but no subscribers. I redesigned the website end to end, and the registration flow went from a page 9 in 10 visitors abandoned on sight to one that roughly 1 in 3 completes.

UX/UITeam lead

~1 in 3

users who land on the redesigned registration page complete the signup form

2,300+

completed registration forms since launch

The shipped landing page, top to bottom: the full walkthrough of the redesign.
Client
Gley.tv
Role
UX/UI Designer and team lead
Agency
Division Marketing
Timeline
1.5 months
Deliverables
Research, analytics audit, competitive analysis, personas, user journeys, IA, wireframes, final designs, prototypes, usability testing

The challenge

People visited. Almost nobody subscribed.

Gley's old website had two problems working against each other.

An unclear value proposition. The site didn't explain what Gley actually was. Senior visitors, a core audience, often assumed it was cable TV.

Pricing that confused instead of convinced. Plans differed only by the number of simultaneous streaming devices. Users trained on Netflix expected content tiers, so the plans read as arbitrary.

The analytics made the cost of this concrete:

32.68%

of visitors never scrolled past the hero section

89.9%

bounce rate on the desktop registration screen

45.9%

bounce rate on mobile registration

The brief was a full redesign, from research to a developer-ready, user-tested prototype. I led the project team and owned every design decision end to end.

Decision 1

A hero that behaves like a movie, not a banner

A third of all visitors left without scrolling past the hero. I had three hypotheses: the hero wasn't interesting enough, the design felt like clickbait to visitors arriving from social ads, or both.

My answer was a cinematic hero. Instead of a static banner with a headline, the page opens like a title sequence: a video showreel of Gley's content plays first, the slogan fades in over it, and the navigation and CTA appear last.

The sequencing was the deliberate part. Delaying the nav and CTA is normally a conversion sin, but here the content itself was the strongest sales argument, so I let it speak before asking for anything. For an audience that associates streaming with television, opening like a movie also answers "what is this?" without a word of explanation.

Did it fix the scroll-off? The directly comparable metric no longer exists: GA4 fires its scroll event at 90% page depth, a far stricter bar than the old "past the hero" measure. What I can read is what the page feeds forward: the homepage carries two thirds of all site views and handed roughly 7,000 users into the registration flow.

The cinematic hero: content first, slogan second, navigation and CTA last.

Decision 2

Pricing that builds trust instead of raising questions

The plans couldn't change, so the communication had to. I redesigned the pricing cards around the one real differentiator: the number of devices streaming at once. That line got the visual weight. A title eyebrow named who each plan was for, bullets replaced paragraph text, and an info icon explained immediate billing before the checkout could surprise anyone.

Small changes, but they moved the cards from "what am I paying for?" to a transparent offer. Trust was the actual deliverable here.

The cards earned their validation qualitatively: in the 19 usability sessions, participants worked through plan choice as part of the full signup task, and the issues that surfaced were peripheral details like link visibility, not plan comprehension. The quantitative echo is downstream: plan choice sits in the middle of the flow that a third of arrivals now complete.

Before: the old pricing card, dense paragraph text with no clear differentiator between plans.
Before
After: the redesigned Standard plan card, the two-device count leading as the eyebrow, bullets instead of paragraphs, the info icon for billing, and the price on the button.
After
The old card against the redesign, led by the one real differentiator. Drag to compare.

Understanding the problem

Who was Gley losing, and why?

I started with stakeholder interviews and user research, then condensed the findings into empathy maps. Four areas kept surfacing: onboarding, product features, support, and pricing.

Says

  • Where can I find the channels? Is this a cable TV service?
  • Where can I see more information about the plans?
  • Which of these is best suited for me?
  • Is the only difference between the plans the number of devices?
  • Will I have a larger content archive on a bigger plan?
  • I want something that is safe.

Thinks

  • Is this a cable TV?
  • I need more info on this
  • Complicated approach, too little explanation
  • Is any plan a good fit for me?
  • This is harder than I imagined
  • They really lack information
  • Their customer support is not the best
  • If I click on a package, will I buy it or get more information?

Does

  • Searches for info on the plans
  • Tries to register
  • Fails to register through the mobile app
  • Visits the website to activate the subscription through a telecom operator
  • Requests customer support
  • Can't find customer support except through email
  • Contacts support but gets no feedback
  • Gets the code rejected on mobile and tablet, because the subscription is made for a TV device

Feels

  • Confused
  • Afraid clicking a plan would activate it
  • Mistrustful
  • Excited
  • Uncertain
The research condensed into empathy maps. Four areas kept surfacing: onboarding, features, support, pricing.

The research settled into three personas:

  • Nostalgia Seekers: 45+ fans of regional TV shows and movies. The most delicate segment, and the most likely to mistake Gley for cable.
  • Savvy Parents: young families wanting safe, native-language kids' content.
  • Domestic Binge-Watchers: viewers of all ages hungry for domestic shows.

Slavcho, 52

Desk representative at the national cadastre · Skopje, Macedonia

Nostalgia Seeker
Easy and as cheap as possible regional TV shows at hand.

Background

Slavcho has been working in the national cadastre for 30 years. In the evening hours he enjoys watching regional TV shows. He isn't tech-savvy: skeptical, often confused when dealing with technology, and cautious with online payments.

Goals

  • Enjoy favorite TV content in the evenings
  • Navigate the website easily
  • Get the best deal for the buck
  • Not have to rely on torrent downloads

Needs & expectations

  • Macedonian translation
  • Intuitive, guided registration and onboarding
  • User manuals and customer support
  • Detailed guidance and instruction about the payment
  • Transparency in the presentation of the different plans
  • Easy subscription cancelation

Frustrations

  • Not tech-savvy
  • Not an English speaker
  • Mistrust in online payment protocols
  • Complex registration and onboarding
  • Price
  • Lack of good and efficient customer support
  • Dependency on TV program schedules
The three personas: Slavcho, Irina, Lazar.

I mapped the Nostalgia Seeker journey (persona: Slavcho) through the existing site to find where the path to paying subscriber broke down.

Phase 1 · Facebook ad

Discovery

How a potential customer discovered the platform.

  • Excited
  • Interested

Actions

  • Clicked a Facebook ad

Motivations

  • Watch regional TV shows independently, without the help of his daughter

Questions

  • Is this a legit platform?
  • Do they have my favorite shows?

Pain points

  • Not tech-savvy

Opportunities

  • Raising brand awareness

Phase 2 · Internet browser

Consideration

The potential customer weighs the platform.

  • Confused

Actions

  • Scrolls the landing page after understanding it is scrollable
  • Looks at pricing plans and tries to click them
  • Goes to 'See whole content'

Motivations

  • Asks around if his favorite TV shows are on the platform

Questions

  • Is this cable TV?
  • On how many devices can I watch?
  • Is this worth it?
  • Will I be able to activate this thing by myself?

Pain points

  • Struggles to realize what the platform is and what it offers
  • Frustration when navigating the home page
  • Struggles to understand pricing plans

Opportunities

  • The hero section design should suggest legitimacy
  • Pricing cards should be transparent and clickable
  • Transparent showcase of regional content

Phase 3 · Internet browser

Decision

How the customer registered on the platform.

  • Frustrated

Actions

  • Clicks the 'Register' button
  • Verifies email
  • Logs in
  • Chooses a pricing plan
  • Pays

Motivations

  • To start watching

Questions

  • How should I register?
  • What was my email password?
  • Why can't I choose a plan? Was my plan automatically chosen?!
  • Why should I log in again?

Pain points

  • Confusing registration flow
  • Email verification
  • Mistrust

Opportunities

  • Place email verification at the end of the flow
  • Choosing the pricing plan at the beginning of the flow
  • Log the user in automatically after email verification

Phase 4 · TV · Internet browser

Experience

The experience of the user after using the platform.

  • Meh

Actions

  • Activates device
  • Plays favorite TV show

Motivations

  • Find new shows

Questions

  • Why do I have to connect all my devices one by one?

Pain points

  • Struggles to find the needed user manual on the website

Opportunities

  • Provide links to user manuals on the home page itself
Slavcho's journey through the old site, mapped to find where the path to paying subscriber broke down.

A competitive audit of the major streaming platforms gave me the checklist Gley was failing: clear value proposition above the fold, content organized by category, device compatibility made visible, trust signals like partner logos. None of it was rocket science. All of it was missing.

Competitive audit board comparing major streaming platforms on value proposition, content organization, device visibility, and trust signals.
The competitive audit: the checklist Gley was failing.

Home page

  • Call-to-action
    • Sign up
      • Plan / email / password
        • Card info
          • Verification
    • Log in
      • Forgotten password
  • Privacy policy
  • Media center
  • Terms of service
  • Contact us
  • Social media
  • Help center
    • Manuals
      • New user
      • Mobile login
      • App installation and activation
      • Pricing plan change
      • Pricing plan change on mobile
      • Subscription cancelation
      • Subscription cancelation on mobile
      • Choosing subtitle and voice-over
      • Password reset
      • Voucher activation
    • FAQ
The redesigned information architecture.

Decision 3

Moving email confirmation to the end of signup

The registration data pointed to one culprit: the flow demanded email confirmation immediately after entering an email address, sending users out of the funnel and into their inbox mid-signup. Most never came back. Desktop bounce: 89.9%.

I rebuilt the flow so every step keeps the user moving forward:

  1. Email & password. Contact info captured first, so even abandoned signups can be retargeted later.
  2. Choose a plan.
  3. Payment details.
  4. Personalization (optional).
  5. Email confirmation, at the very end.

The retargeting angle in step one was the business case that sold the change to stakeholders: an incomplete signup stopped being a lost user and became a marketing lead.

This is the decision the Results section measures directly.

The rebuilt flow: every step keeps the user moving forward; email confirmation waits until the end.

Validation

19 usability sessions before a line of code

I designed the testing plan, ran 19 moderated sessions on the polished prototype, and closed each with a questionnaire. The sessions caught the small things that analytics never will, like text links some users couldn't find or comfortably read. By handoff, developers were building a design that real users had already worked through.

Usability testing session notes: tasks, observations, and the issues surfaced across the 19 moderated sessions.
Post-session questionnaire results summarizing participant ratings of the prototype.
The testing report and the closing questionnaire from the 19 sessions.

Results

The leak became a flow 1 in 3 complete

An honest caveat first: the analytics setup changed after launch (Universal Analytics to GA4, with different definitions and a fresh property), so there is no clean before/after delta to claim. Instead of comparing incompatible numbers, I measured the new flow on its own terms, with the metric the problem was stated in: completion.

~1 in 3

of the roughly 7,000 users who landed on the registration page, 2,300+ submitted the signup form

The denominator is everyone who landed on the registration page, motivated or not, not just users who started typing. For a paid flow with a plan choice and payment details in the middle, a third of arrivals finishing is a healthy rate. This is not a newsletter form.

The old flow's defining behavior was instant exit: 89.9% of desktop visitors bounced before doing anything. The new flow's defining behavior is the opposite: a third of the users who reach it finish. The numbers come from different analytics systems, so they read as two portraits, not one delta. The contrast is still the point: a page people fled is now a flow people finish.

Organic search arrivals72.5%
Site average46.6%
Paid-social in-app browsers22.7%
Remaining drop-off concentrates in paid-social in-app browsers (22.7% engagement); organic search engages at 72.5%. The losses cluster where intent is lowest, not where the design is weakest.

Lessons learned

Leading the team meant owning the trade-offs

This was my first time leading the whole project team, participating in every phase from research to handoff.

The sharpest test came with the hero. Marketing wanted the CTA visible immediately, and every instinct in the agency said don't bury the button. I argued the opposite: for an audience that thought Gley was cable TV, the content had to answer "what is this?" before we asked for anything, even if that meant holding the CTA back a few seconds. It was an uncomfortable call to defend, because if the numbers had gone the wrong way, the delayed button would have been the obvious thing to blame. I made the call, documented the reasoning, and owned the risk.

The flow's completion rate is partly the vindication. But the lesson wasn't that the position happened to be right; it was learning to hold a position I believed in against the room. I left the project trusting my own judgment more, and with the results to justify it.