Acelab’s Front Door

Acelab’s Front Door

Acelab’s Front Door

Homepage and onboarding for Materials Hub

0→1 · PM + Product Designer · Activation · Adaptive UI

Homepage and onboarding for Materials Hub

0→1 · PM + Product Designer · Activation · Adaptive UI

OVERVIEW

One homepage that knows where you are

One homepage that knows where you are

One homepage that knows where you are

Acelab’s homepage showed every user the same page. I owned the redesign end to end, as both PM and designer.

🧩

🧩

🧩

Problem

Acelab’s homepage showed every user the same page. New and invited users had no clear first step, so activation stalled just as the company needed product-led growth.

🛣️

🛣️

🛣️

Solution

As PM and designer, I turned it into one adaptive homepage: a Launchpad, page states for self-serve and invited users, and one way to start a project everywhere.

📈

📈

📈

Outcome

Handed off with a PRD of 10 user stories and success metrics for activation, collaboration and conversion. Now in development.

How I led this project from discovery to hand-off

How I led this project from discovery to hand-off

PRODUCT

Homepage and onboarding: the front door of Acelab’s Materials Hub

TIMELINE

Discovery Sep ‘26 → flows and widget system Oct ‘26 → final design, PRD and dev hand-off Oct 26 ‘26

Status: In development

MY ROLE

I owned this as both product manager and designer. The job was as much about deciding what to build, and in what order, as about pixels. I framed the problem, wrote the PRD, set the success metrics and designed every state engineering built against.

Discovery & research

Pulled PostHog funnels, CX tickets, stakeholder meetings and competitor benchmarks into one affinity map.

Problem framing

Turned 33 observations into one goal both user types share: reach a real project faster.

Strategy & scope

Scored 30 widgets for value and effort, cut them to an MVP and wrote down what was deferred and why.

System design

Defined show and retire rules for every widget and the three page states the homepage moves through.

Interaction & motion

Designed the Launchpad, its celebration, inline replies and every empty, error and viewer state.

PRD & hand-off

Wrote the PRD with 10 user stories and acceptance criteria, and ran hand-off with two engineering teams.

TEAM

Purti Hardikar - Product Manager & Lead Product Designer

Annika Harmsen - Team member

Archi-techs (ARC) - Engineering

BIM Reapers (BIM) - Engineering

SCOPE & SURFACE

10 user stories across two onboarding journeys. Homepage, Launchpad, project creation modal, project updates widget and Explore shortcuts.

IMPACT

Success metrics set at 30, 60 and 90 days, with baselines from the AECO team. Results will follow launch.

WHY NOW

After Series A, the product had to sell itself

After Series A, the product had to sell itself

After Series A, the product had to sell itself

After the Series A, Acelab bet on product-led growth: users sign up, find value and bring their team without a sales call. So I mapped where they dropped off.

PLG FUNNEL →
01Sign up
Do they get in?
02Activate
Do they reach value?
03Collaborate
Do they bring the team?
04Convert
Do they upgrade?
?
Self-serve
Signs up from the website
2 FRICTION
Email never verified
Google sign-ups skip the profile
4 FRICTIONBiggest
“Welcome back” on day one
Search barely used
2–3 days to open a project
Too many fields to create one
No friction recorded
2 FRICTION
Paid value invisible to free firms
Empty states, no reason to upgrade
Invited
Joins a firm by email
2 FRICTION
Invite never accepted
Detour back to the email
1 FRICTION
Asked to create a project the team already has
1 FRICTION
Viewers unsure what they can do
No friction recorded
Sources: PostHog, CX tickets, stakeholder meetings, a FigJam flow audit and the PRD. Friction point

PostHog backed it up: in the 30 days before launch, under 5% of visitors did anything inside a project, and almost no one invited a teammate.

SO THE REDESIGN HAD THREE GOALS

01

Reduce drop-off

Keep new and invited users from leaving before their first session ends.

02

Get everyone to a project

Creating, copying or opening a project is the first meaningful action.

03

Make the first action meaningful

Save a product, add it to a project, reply to a teammate: real work, not a tour.

THE PROBLEM

A front door that looked the same for everyone

A front door that looked the same for everyone

A front door that looked the same for everyone

Every card had equal weight, new users had no first step, and invited users were asked to create a project their team already had.

1

2

3

4

5

6

1

“Welcome back” greets brand-new users too.

2

Key tools hide in a nested sidebar under General Research.

3

“Pick up where you left off” shows one project, with no comments or team updates.

4

Project creation is a small card, named differently from the modal.

5

Marketing gets the same weight as work, so it “feels like ads”.

6

Search sits in the top bar, and almost nobody used it (PostHog).

Before: the old homepage and nested sidebar. Every user saw this layout, from day one to year two.

CX TICKET · HGA

“The homepage feels like ads and has no clear first action.”

CX TICKETS · NEW USERS

New users asked to skip the homepage and go straight to project creation.

DISCOVERY

What the data and the tickets said

What the data and the tickets said

What the data and the tickets said

Six sources before any pixels: PostHog funnels, CX tickets, stakeholder meetings, the Help Center, a flow audit and competitors.

#1

#1

Search is the first thing self-serve users do, across most early steps

POSTHOG

2–3 days

2–3 days

the typical wait before a new user opens a project

POSTHOG

~2 min 50 s

~2 min 50 s

median length of a first session

POSTHOG

THE CORE TENSION

WHERE NEW USERS LAND

The homepage

Same cards for everyone, no first step

2–3 days

before a first project

WHERE THE VALUE LIVES

Inside a project

Schedules, Smart Docs, comments, RFIs

The homepage did nothing to close that gap. That became the brief.

The homepage did nothing to close that gap. That became the brief.

JOURNEYS

Two users, two front doors

Two users, two front doors

Two users, two front doors

Self-serve users arrive with nothing set up. Invited users arrive by email into a firm that already has work. Each path breaks in different places.

SELF-SERVE FLOW

Start free

→

Sign up

▼ never verifies

→

Profile

▼ Google users skip it

→

One question: your role

→

Homepage

→

Search + save

▼ 2–3 day gap

→

Bring data in

→

Project data in Materials Hub

INVITED FLOW

Invite email

▼ never accepts

→

Create account

▼ detour back to email

→

Company or project?

→

Project opens on Schedules

→

Role check

▼ viewers unsure what they can do

→

First meaningful action

?

SELF-SERVE

They need to be taught. The page should give one clear next step and turn their first search into a project.

INVITED

They convert better and already have work waiting. Skip the teaching and land them in their team’s projects.

PRINCIPLES

Four rules every screen had to follow

Four rules every screen had to follow

Four rules every screen had to follow

They came straight from the friction map. Each one shows up as a real detail on the homepage.

Saved products

TerraVista ClayGuard

Solterra Building Materials

Add to project

RULE 1

Value before the tour.

Value before the tour.

Start from what users already care about. A saved product becomes a project in one click, with no walkthrough first.

Your Launchpad

50%

Next:

Create a project →

RULE 2

One obvious next step.

One obvious next step.

Every user lands on exactly one suggested action. The Launchpad shows it, and it can be closed whenever they want.

Sync from Revit

›

Import from file

›

Start from a template

›

Create a blank project

›

RULE 3

Setup should feel like work, not homework.

Setup should feel like work, not homework.

Start from the data users already have. The same four ways to create a project, in the same order, everywhere.

?

SELF-SERVE

How to create a project

INVITED

Open a team project

RULE 4

Adapt to who arrived.

Adapt to who arrived.

A new firm and an invited teammate need different first screens. The page changes with project access and what they’ve saved.

FROM THE PM SIDE

“

New users don’t need a tour of Materials Hub. They need one reason to come back tomorrow. So the homepage never blocks work behind onboarding, and every step on it is something they’d do anyway. If setup feels like homework, activation drops.

New users don’t need a tour of Materials Hub. They need one reason to come back tomorrow. So the homepage never blocks work behind onboarding, and every step on it is something they’d do anyway. If setup feels like homework, activation drops.

Purti Hardikar

PM and Lead Product Designer, Acelab

PRIORITIZING

Deciding what earns a spot

Deciding what earns a spot

Deciding what earns a spot

Thirty candidate widgets from seven products, scored for value and effort.

QUICK WINS · BUILD FIRST

Product search

Projects

Where you left off

Get started checklist

Saved products

Quick actions

BIG BETS · PLAN CAREFULLY

Tasks · activity log

Discover matches

Ask Ace side panel

Upcoming deadlines

Project health (admin)

FILL-INS · IF TIME ALLOWS

Webinars

Product spotlight

Trending news

Browse by material

Templates

RECONSIDER

Saved search alerts

CEU credits tracker

Team adoption (admin)

Revit sync status

Value × effort: starting estimates I took to the team. Value ≥ 4 is high; effort ≥ 3 is high.

SCOPING (PM HAT)

From 30 widgets to an MVP

From 30 widgets to an MVP

From 30 widgets to an MVP

I cut the full vision down to what would prove the idea fastest.

EXPLORED

5 stages · ~30 widgets

5 stages · ~30 widgets

Day 0, first save, first project, team invited and returning, each with its own widget set, plus admin dashboards and a customizable home.

SHIPPED FIRST

3 page states · Launchpad · updates widget

3 page states · Launchpad · updates widget

No projects, has saved products, has project access. One setup checklist and one tabbed card for recent work, comments and activity.

Why layouts and Essentials waited for v2

Movable widgets meant saving every user’s and every firm’s layout, a new piece of engineering on its own. So v1 ships the essential widgets in fixed places, and new ones are added over time.

EXPLORED · MOVABLE WIDGETS
Search⋮⋮
Launchpad⋮⋮
Updates⋮⋮
Saved⋮⋮
Trending⋮⋮
Spotlight⋮⋮
Saving layout for each user…
Drag, reorder and save Essentials, Discover and company layouts. Every move means storing a layout per user and per firm, which v1 couldn't take on.
→
SHIPPED V1 · STATIC ESSENTIALS
Search
Launchpad
Updates
Saved
Trending
Spotlight
Discover matchesv2
Sample projectv2
Deadlinesv2
Fixed positions for the widgets that matter most. New widgets slot in over time through the show and retire rules, with no layout to store.

TRADE-OFFS

Three calls where the team pulled in different directions

Three calls where the team pulled in different directions

Three calls where the team pulled in different directions

As PM I had to pick a side, or find a design that didn’t need one. Each call cost something.

01

Marketing space vs. a page that feels like work

GROWTH

As a startup, the homepage is where users learn what’s new. Webinars, Trending and Spotlight needed a home.

↔

CX

Tickets said the old page “feels like ads” and has no clear first action.

WHAT I DECIDED

Keep all three, but only in the right column. Work owns the main column, and Trending hides when there’s nothing new.

WHAT WE GAVE UP

Less room for promotion than marketing wanted.

02

Promote the paid feature vs. keep free firms moving

REVENUE

Revit sync is the fastest path to real data, and it’s an AECO Pro feature.

↔

FREE FIRMS

Most self-serve users are on the free plan and can’t use it.

WHAT I DECIDED

Revit stays first for everyone, labelled by plan: “Fastest if you work in Revit” for Pro, “Included in AECO Pro” for free. The other three options are never gated.

WHAT WE GAVE UP

A free user sees an option they can’t use yet.

03

Teach new users vs. get invited users to work

SELF-SERVE

New users need guidance, and the friction map showed most drop-off in Activate.

↔

INVITED

Invited collaborators convert better, so the meeting notes said to prioritize them.

WHAT I DECIDED

One page with two starting points. Self-serve users get the Launchpad and creation options; invited users land on their team’s projects.

WHAT WE GAVE UP

Two sets of states to design, build and test instead of one.

ITERATIONS

How we got from the first idea to what shipped

How we got from the first idea to what shipped

How we got from the first idea to what shipped

The whole homepage

Explored
A cleaner version of the old page
The first pass tidied the existing layout: pick up where you left off, webinars and a trending rail. Easier to scan, but every user still saw the same page.
A cleaner version of the old pageHomepage v1: a screen per user typeOne adaptive page with fixed essentials

The Launchpad

The Launchpad

Explored
A mini checklist inside the work column
A compact Get started card with five steps for self-serve users and four for invited ones. Only the next step had a button, and the card retired when done. Those rules carried into what shipped.
A mini checklist inside the work columnA progress ring under the search barA Launchpad with one next step and % complete

The homepage layout

The homepage layout

Explored
Layouts users could switch and customize
Essentials, Discover, a company default and admin-made layouts, plus a Customize panel. Powerful, but it made the homepage a settings problem before it was useful.
Layouts users could switch and customizeA dashboard of big-bet widgetsOne adaptive homepage

ADAPTIVE HOMEPAGE

The homepage grows with the user

The homepage grows with the user

The homepage grows with the user

The page reacts to what each user has done. Setup widgets retire once they’ve done their job.

First loginSaved a productFirst projectSetup complete
Nothing set up yet. The Launchpad shows one next step.

SYSTEM

Rules, not layouts

Rules, not layouts

Rules, not layouts

Every widget has two triggers: when it shows and when it retires. Engineering built one page that assembles itself.

WIDGET

SHOWS WHEN

RETIRES WHEN

Launchpad

First login

All steps done, or closed with X

How to create a project

No project access yet

First project created

Saved products

First product saved

Never

Project updates widget

Has project access

Never

Browse by material

Day 0

Setup done, or 5+ searches

Search · Ask Ace

Always on

Always

Never

Spotlight · Trending

Always on

Always

Never

CRAFT

The details that make it feel finished

The details that make it feel finished

The details that make it feel finished

Launchpad and a one-time celebration

Launchpad and a one-time celebration

Setup progress shows as 4 steps for free firms and 5 for AECO Pro, with % complete instead of XP. Finishing it plays a ~1.6s celebration once, then it’s gone for good.

☆ 3
YOUR LAUNCHPAD
3 of 4 steps complete
Next: invite your team
75% complete
✓
SETUP COMPLETE · 4 OF 4
You're all set, Purti!
Your account is ready. A good next step is your first schedule.
Build a schedule
✕
✓
Search a product
Done
✓
Save a product
Done
✓
Create a project
Done
◦
Invite team
2 min

Explore shortcuts that invite a click

Explore shortcuts that invite a click

Features that used to hide in the sidebar now sit one click from home. On hover the circle lifts, a dashed ring turns and a dot orbits; badges that need attention pulse on their own. With reduce motion on, only the shade changes.

Explore Material Hub
+
New project
Start fresh
B
Browse
Find products
3
Schedules
3 need attention
D
Smart Docs
Create project docs
?
Help
Guides & support

Explore without a search query

The product browser used to hide behind a link that people had to open, and almost nobody did. Now it sits on the homepage, so anyone can explore Materials Hub by material, type and project without knowing what to type.

Browse products
No search needed
MATERIAL
Aluminum
Wood
Vinyl
Steel
TYPE
Casement
Picture
Awning
Tilt & turn
PROJECT
Healthcare
Office
Residential
Cultural
7,088 products

Every path leads to a project

Every path leads to a project

Having a project is the first meaningful action in Materials Hub: schedules, Smart Docs, comments and activity all live inside one. So creating, importing, copying a template or opening a team project is reachable from six places on the homepage, and every one uses the same four options.

Homepage with entry points to a project
1
2
3
4
5
1
Launchpad: “Create a project” step
Self-serve
2
Explore shortcuts: New project
Everyone
3
Smart Docs tile: “Create a project first”
No projects yet
4
How to create a project: Four options, same as the modal
No projects yet
5
Saved products: Add to project
After research
6
Launchpad: “Open a team project”
Invited users’ version
All six end in the same place: a project, the first meaningful action.

ON THE HOMEPAGE

WHAT IT OPENS

Sync from Revit

Fastest if you work in Revit

→

Opens in a new tab: plugin setup for AECO Pro firms, the Revit integration page for free firms.

Import from file

Upload a CSV and map the columns

→

→

Project details, then straight into Import Products (Upload, Assign fields, Complete) in the same flow.

Start from a template

Copy a project and its products

→

Skips the chooser and opens Start From Template directly.

Create a blank project

Name it and add products as you go

→

Opens the project creation modal. Skip & Create keeps it to one step.

Catching up without leaving home

Catching up without leaving home

One fixed-height card with three tabs: Where you left off, Comments with inline reply, and Activity. I designed every state: unread, hover, replying, sent, failed, viewer, free firm, empty and error.

Comments list and hover, reply sent, Activity for a free firm, team fallback, and a first-time empty state.

A short tour, only if they want one

Four steps, under a minute, skippable from the first screen and reopenable from Help. It points at the same four things the Launchpad does, so nothing is taught twice.

Welcome, Purti!
Want a 4-step tour?
Takes under a minute. You can skip it any time.
SkipStart tour

SHIPPING (PM HAT)

Writing it down so engineering could run

Writing it down so engineering could run

Writing it down so engineering could run

A PRD with ten user stories, and a hand-off file with flows, states and motion side by side.

FIGJAM

Flows, affinity map, value × effort

PRD

Problem, decisions, out of scope, metrics

FIGMA HAND-OFF

User flows, states, motion keyframes

SLACK

#feature-homepage-onboarding

MEASURING IT

How we’ll know it worked

How we’ll know it worked

How we’ll know it worked

Success criteria set before launch, in three windows.

STARTING POINT · 30 DAYS BEFORE LAUNCH

Under 5%

Under 5%

of visitors did anything inside a project

ACTIVATE

Near 0%

Near 0%

shared a project or invited a teammate

COLLABORATE

Almost all

Almost all

visits came from desktop, so the homepage is desktop-first

DEVICE

PostHog, last 30 days before the new homepage. Figures are rounded to protect Acelab’s data. These are the baselines the goals below are measured against.

Each metric maps to a PLG outcome:

Activation

Engagement

Collaboration

Retention

Conversion

30 days

30 days

Are people using it?

Clicks on each project creation option

Activation

Revit clicks vs. projects actually synced

Conversion

Comment replies sent from the homepage

Engagement

60 days

60 days

Is it changing behavior?

New users create a first project within 7 days

Activation

Invited users open a team project on day one

Collaboration

Launchpad completion rate

Activation

90 days

90 days

Is it helping the business?

New users still active after 90 days

Retention

Free firms visiting Revit or requesting an AECO Pro demo

Conversion

STILL TO DEFINE

Time to first meaningful action for each segment, and exactly what counts as meaningful: an import, a schedule edit or an RFI.

TAKEAWAYS

What owning both sides taught me

What owning both sides taught me

What owning both sides taught me

Design the rules, not the screens

Show and retire triggers turned five mockups into one system engineering could build and extend.

Scope is a design decision

Cutting 30 widgets to an MVP was the most important call I made, and writing down why kept it from coming back.

Different users need different doors

Self-serve users need teaching; invited users need their team’s work. One page, two starting points.

Measure before you ship

Setting 30/60/90-day questions up front made every design choice something we can test.

iClick
itravel
iRead
iHike

Beyond Work or
know more About Me! :)

Copyright © 2026 Purti Hardikar. Brewed with Matcha 🍵 Claude Code & Framer, 📍 Sunnyvale, Bay Area, USA.