Back

Simplifying integration management

Internal Tool

Product Experience

UX + Webflow

Back

Simplifying integration management

Internal Tool

Product Experience

UX + Webflow

Back

Simplifying integration management

Internal Tool

Product Experience

UX + Webflow

To reduce redundancy and improve flexibility, we unified integration management across internal and external platforms. Previously, separate systems led to inefficiencies, content mismatches, and heavy developer reliance.

Our solution enabled dynamic updates and empowered non-developers to own content, layout, and pricing experiments.
My Role

Defined the content architecture across systems and built the CMS workflow in Webflow. While the design lead handled visuals, I led the end-to-end implementation of the integration framework.

Team

CPO, Engineer (Aman), Design Lead (Eti)


Context and Initial Challenges
 

The organization managed integration information across two separate systems—an internal platform and an external website.

This setup caused operational redundancies, inconsistencies, and significant inefficiencies, particularly due to high developer dependency. Following were the key frustrations & blockers:

Developer dependencies for content update

Marketing wanted to test messaging, layout & content rapidly.

Product team wanted to test pricing.

No integration detail page on the website.

Approach & Design

We Started categorizing the data into buckets.

The solution involved redefining the integration page anatomy into two key components:

  1. Dynamic Content: Database-driven content positioned for ease and centrality of updates, available through retool.

  2. CMS-Driven Content: Flexible iframe-based content sections managed independently by marketing and product teams without developer intervention.

Shortly, after deciding the anatomy. We went on to design the header & the body section.

Implementation Details

Implementation prioritized seamless integration mapping and introduced a phased rollout to transition existing integrations gradually. Additionally, conditional rendering logic was employed to manage header and footer visibility, ensuring consistency whether accessed directly or within an embedded context.

Results 

The new integration management system significantly reduced developer reliance, drastically cutting down the launch timeline for new integrations.

Product and marketing teams became self-sufficient, gaining the capability to:

Independently launch integrations.

List new integrations in hours.

Quickly iterate on pricing and messaging.

Have consistent messaging. Web & platform.

Ultimately, the project delivered enhanced operational flexibility, empowered cross-functional teams, and ensured a unified and efficient user experience across all integration touchpoints.