FreshworksWebDesign systemAccessibility ShippedCase study

750 legacy pages, one component library. Moving Freshworks’ marketing pages over, one page at a time.

freshworks.com was moving to a new site built from shared components. On a contract in 2025, I built and QA’d more than 750 pages as they moved, to WCAG 2.1, checking each one against the page it replaced.

Role
Product Designer, design QA
Company
Freshworks, via Bluehawk
Year
2025
Methods
Design QA, accessibility (WCAG 2.1), Figma
Freshsales Suite live today: a dark hero banner with a product screen and award badges Freshsales Suite in November 2024, before the move: a light blue hero and a separate product bar
Drag to compare · Freshsales Suite, November 2024 and today
01 · The job

750+ pages, built one at a time.

Comparison pages, feature pages, webinars, resource hubs. Each legacy page had been designed on its own, so no two handled a hero or a pricing table the same way.

The new site had one component library, and every one of those pages had to come across on it.

Freshdesk vs ZendeskFreshdesk vs Zoho DeskCRM FeaturesIT Asset ManagementFreshdesk Free vs PaidKnowledge BaseIncident Management ToolSLA ManagementFreshchat WhatsApp IntegrationFreshservice vs ServiceNowService CatalogOmnichannel HelpdeskCloud PBXCustom ObjectsLinked TicketsChange ManagementFreshmarketer for ShopifyEmployee OnboardingFreshdesk vs ZendeskFreshdesk vs Zoho DeskCRM FeaturesIT Asset ManagementFreshdesk Free vs PaidKnowledge BaseIncident Management ToolSLA ManagementFreshchat WhatsApp IntegrationFreshservice vs ServiceNowService CatalogOmnichannel HelpdeskCloud PBXCustom ObjectsLinked TicketsChange ManagementFreshmarketer for ShopifyEmployee Onboarding
Workflow AutomationsContract ManagementGartner Market GuideFreddy AI CopilotProduct ToursMultiple SLA PoliciesCustomer PortalTime TrackingTeam DashboardsProblem ManagementSoftware Asset ManagementParent-Child TicketingHelp WidgetLive Chat SoftwareTidio AlternativeForrester TEISupport 101ITIL Release ManagementWorkflow AutomationsContract ManagementGartner Market GuideFreddy AI CopilotProduct ToursMultiple SLA PoliciesCustomer PortalTime TrackingTeam DashboardsProblem ManagementSoftware Asset ManagementParent-Child TicketingHelp WidgetLive Chat SoftwareTidio AlternativeForrester TEISupport 101ITIL Release Management
Freshservice vs ServiceNowService CatalogOmnichannel HelpdeskCloud PBXCustom ObjectsLinked TicketsChange ManagementFreshmarketer for ShopifyEmployee OnboardingWorkflow AutomationsContract ManagementGartner Market GuideFreddy AI CopilotProduct ToursMultiple SLA PoliciesCustomer PortalTime TrackingTeam DashboardsProblem ManagementSoftware Asset ManagementParent-Child TicketingHelp WidgetLive Chat SoftwareTidio AlternativeForrester TEISupport 101ITIL Release ManagementFreshdesk vs ZendeskFreshdesk vs Zoho DeskCRM FeaturesIT Asset ManagementFreshdesk Free vs PaidKnowledge BaseIncident Management ToolSLA ManagementFreshchat WhatsApp IntegrationFreshservice vs ServiceNowService CatalogOmnichannel HelpdeskCloud PBXCustom ObjectsLinked TicketsChange ManagementFreshmarketer for ShopifyEmployee OnboardingWorkflow AutomationsContract ManagementGartner Market GuideFreddy AI CopilotProduct ToursMultiple SLA PoliciesCustomer PortalTime TrackingTeam DashboardsProblem ManagementSoftware Asset ManagementParent-Child TicketingHelp WidgetLive Chat SoftwareTidio AlternativeForrester TEISupport 101ITIL Release ManagementFreshdesk vs ZendeskFreshdesk vs Zoho DeskCRM FeaturesIT Asset ManagementFreshdesk Free vs PaidKnowledge BaseIncident Management ToolSLA ManagementFreshchat WhatsApp Integration
Some of the pages, by name
02 · Mapping

Every section gets a component.

Each rebuilt page was mapped section by section to the library: hero banner, accolades, switchbacks, pricing table, card grid.

That map was my checklist in QA. The copy and imagery had to survive, and spacing, type and layout had to come from the component.

The full Freshsales Suite mockup built from library componentsProduct navHero bannerAccoladesFeature gridSwitchbackSwitchbackSwitchbackSwitchbackPricing tableCard gridFooter
The rebuilt page, by component
03 · Same content

Same page, one system.

Freshsales Suite kept its copy, its features and its order of sections through the move.

What changed was everything around it: the hero, the award badges, the feature icons and the spacing now come from the same components as every other page.

Freshsales Suite in November 2024: three hand illustrations over small, dense feature copy
Freshsales Suite live today: the same three benefits with product icons, larger headings and even spacing
Freshsales Suite, the benefits section
04 · QA

Every page, checked against the original.

For each page I had the live legacy link, the preview build and a capture of the build in Figma.

I went through the build and the original side by side, so nothing went missing, and checked each page for accessibility before it shipped.

The Freshsales Suite QA frame in Figma: the legacy link, the preview link and a capture of the build
One page’s QA frame
05 · Live

Live on freshworks.com.

The pages went out in batches by ticket, and the rebuilt versions are what freshworks.com serves today.

See Freshsales Suite

Freshsales Suite in full, November 2024
Freshsales Suite in full, live today
Freshsales Suite, the whole page