Client:
Internal
Role:
UX/UI Design & Development
2025

A Scalable System

Our previous workflow for build custom websites required significant time and limited our ability to scale. By refining how we approached design, tooling and development, I helped establish a more efficient system that reduced build time and improved how teams interact with the final product.

Overview

‍

As a marketing team, speed and flexibility are critical. Our previous workflow for building custom websites required extensive development time and made it difficult to adapt quickly.

Each project also functioned as a one-off build, limiting our ability to create a consistent system that could scale across projects or be easily maintained by different teams.

‍

The Problem

‍

Our process created several bottlenecks:

‍

  • Custom builds required significant development time (~140 hours)
  • Pages were built with limited reusability
  • Design and development seemed disconnected
  • Updates required developer involvement

‍

This made it difficult to support the pace and flexibility needed for marketing-driven work.

‍

Rethinking the Approach

‍

The issue wasn’t just speed, it was how design translated into development.

Without a shared structure, we were recreating work on every project.

We needed a system where:

‍

  • Design could carry through development more directly
  • Components could be reused and adapted
  • Teams could more updates without starting from scratch

‍

Building a More Scalable System

‍

I introduced a workflow that better aligned our tools and output:

‍

  • Relume to establish consistent structure, components, initial layouts and heavy lifting
  • Figma to refine and expand the system with flexibility
  • Reduced redundant work by creating overlap between tools

‍

From these, we transitioned to Webflow to support the system:

‍

  • Structure carried directly into the build
  • Components and templates could be reused across pages
  • Teams could work within defined guardrails without bottlenecking or breaking the system.

‍

This shifted our approach from build individual pages to building a system that supports them.

‍

Outcome

‍

  • Reduced build time from ~140 hours to ~85 hours
  • Continued refining the process, with recent projects (~50 pages) built in as little as ~38 hours
  • Improved consistency through reusable structures
  • Reduced reliance on custom development for updates
  • Enabled teams to work more efficiently within a shared system

‍

Looking Ahead

‍

This approach continues to evolve as we refine how our tools and process work together.

What started as an effort to reduce build time has become a more reliable way to build and manage scalable websites that support ongoing marketing needs.

‍

Awards & Recognition
No items found.