← All work

Rebuilding Scaler’s software engineering course page to drive 9x more brochure downloads.

Scaler Academy is Scaler’s main paid course, a software engineering programme for working developers moving into stronger roles.

This page is where people ask for the brochure, so it is the first real pitch most of them read.

The brief was to re-brand the course for the AI era and show it still holds up. Several teams worked on it at once, covering the design, the narrative, and a system for shipping pages faster.

  • Pod 4-person redesign team · 1 designer
  • Scope Academy course page · curriculum · Storyblok
  • My role Product designer · curriculum framework, page redesign, Storyblok build
Tools FigmaClaudeStoryblok

A scroll through the live page: the two-CTA hero, the three-tier curriculum, tracks, and projects.

  1. 01

    Started from marketing’s analysis of why leads were low.

  2. 02

    Pitched a working page built with Claude, not slides.

  3. 03

    Designed it once in Figma as reusable blocks.

  4. 04

    Shipped it in Storyblok, so later pages reuse it.

The page did not convince anyone, and a one-off redesign would only ever help one course.

It is the entry point for most Academy traffic, so failing to make the case there was expensive.

Where the page was starting from

2.38%

of site visitors became leads

0.25%

asked for the brochure

~2 wks

to take a page from design to live

40

leads in the analysis that became the brief

The page asked for your details before it said anything

Only 0.25% of visitors asked for the brochure. The top of the page wanted five form fields before saying anything worth giving details for.

Every course page was built from scratch

Every page rebuilt its curriculum section from scratch, so nothing was shared and nothing improved. A new page took about two weeks.

The page, end to end

Before Previous design
The full old Academy landing page design, top to bottom

Scroll insideThe page as it stood when the analysis landed. The old one is gone, replaced by this.

After Live today
The current Academy course page as it is live today, captured top to bottom: the Software and AI Engineering Program hero, the Download Brochure call to action, and the three-tier curriculum section further down

Scroll insideCaptured today, so it shows later work too. Two rebrands came after; the structure held.

So we prototyped it first

AI was used to make the pitch, not in the product. Nothing AI-powered shipped on the page.

Prototype Built with Claude
The Claude-built HTML prototype used to pitch the rebrand narrative, shown full length

Scroll insideA working page argues faster than a deck. The curriculum here is what shipped.

Figma Stakeholder approved for build
The full Academy page resolved in Figma, carrying the same narrative and three-tier curriculum as the prototype

Scroll insideThe same page resolved in Figma, settled once for every page after it.

The first thing I owned was the curriculum framework

Problem

The curriculum section listed modules, but never showed where a course started or where it led.

I want to see where this course starts and where it leads, so that I can tell whether it is meant for me before giving my details.

What was wrong with it

Replaced
  1. 01 No entry point Beginners and working coders saw the same list, with no hint where to start.
  2. 02 Every module read alike Rows ran the same length in near-identical words, so nothing stood out.
  3. 03 Order without progression A drop-down implied order but not difficulty, so the path stayed hidden.
  4. 04 Rebuilt every time Every course page rebuilt it from scratch, so a fix helped only that page.
The old curriculum section: a flat drop-down list of Core Modules with no progression between them
What shipped

A path, not a topic list
Three levels that show where the course leads

The three-tier curriculum section, with Beginner, Intermediate and Advanced entry points as tabs above the module detail

Built once, for any page to fill in. Still live today, two rebrands later.

Brochure intent from this section
0.85% highest of any section, ahead of the hero
Scroll depth to curriculum
17.3% ~25,000 users below the fold

Why the structure did the convincing

User problem

A list can’t answer ‘is this for me?’

It said what was covered, never where you would start or end up.

Design decision

Tiers as entry points

Beginner, Intermediate and Advanced come first, so the path reads before the modules.

Trade-off

One shape for every course

Courses gave up their own styling. In exchange, one fix improves all of them.

Then I shipped it on Storyblok

CMS Component schema
The Curriculum V3 Tab block open in Storyblok, showing Label, Duration and Level fields and a nested Curriculum V3 Module, beside the live preview of the tier tabs
CMS Page as components
The Storyblok layers panel listing the Academy page as named components: Seo, Course Schema, Program Navbar with its tabs, Hero V3, and the Download Brochure and Placement Report CTA blocks

One block holds a label, a length, a level and its modules. I learned Storyblok for this and built the page myself. A second course page was later built from the same blocks, which is what proved it was a system.

2 wks → 2–3 days

to take a page from design to live. An internal estimate, not a tracked number, covering the two pages I built.

Visual Studio Code with the Claude Code session that ran the Storyblok program-page skill, the CMS folder and skill files listed in the explorer on the left
I wrote the instructions and the rules; the model followed them. Every upload landed as a draft, never published.
skills/storyblok-program-page/SKILL.md
---
name: storyblok-program-page
description: Use when creating a new Varsity
  program page in Storyblok from a proposal doc
  or brochure: drafting section copy, expanding
  the curriculum, generating brand images, and
  uploading the page as a draft under an
  institution folder.
---

CORE PRINCIPLE
  Clone for structure, replace only content and
  images, never publish.

HARD RULES, never violate

1. DRAFT ONLY. Every create or update sets
   publish: 0. Never call a publish op.

2. CONTENT APPROVAL GATE. Do not write copy into
   Storyblok until the content doc and curriculum
   sheet are approved. Images are the only thing
   uploaded directly.

3. NEVER MODIFY THE CLONE SOURCE. Read it, copy
   its content, never write back to it.

4. DO NOT CHANGE STRUCTURE. Keep every component,
   field and section order from the clone. Only
   the values change.

A team call took the form out of the hero

Who did what

The team’s decision: Kishan Vagale (lead), Sudhanva Acharya, Prachi Pandey. Included because it shapes how the numbers read, not as my work.

Before Five fields, up front
The old Academy hero: a five-field embedded form for name, email, mobile, graduation year and college, with Request a CallBack in the header
After Two lightweight CTAs
The new Academy hero: Download Brochure as the primary button and Placement Report as the secondary, with no embedded form

What moved after we shipped

~9x

more people asked for the brochure, 0.25% to 2.33%. This one is the new button alone

3.08%

of visitors became leads, up from 2.38%. This one belongs to the whole redesign

0.85%

asked for the brochure from the curriculum section, more than any other section

17.3%

scrolled as far as the curriculum, about 25,000 people

What I would carry forward

01

A better page helps once. A better way of building them helps every time.

02

A prototype is the cheapest way to win an argument. Mine was approved before I designed anything.

03

Saying which number is mine and which is the team’s makes the rest believable.

Explore next

Building a coding-challenge dashboard that scales across hiring rounds and products, in three days

I wrote the constraints, the model built to them. An exploration, and 130 attempts in

The MountBlue contest dashboard: levels, pool sizes and the path a wrong answer takes