Repositioning from API Client to API Collaboration Platform

Overview

Postman had evolved into a multi-product API platform, but was still widely perceived as a single-purpose API client. I led a company-wide repositioning effort to redefine how the product was understood, aligning product, marketing, and leadership around a unified narrative across five core product surfaces and the primary “What is Postman?” entry point.

The Problem

As Postman expanded beyond its original API client, the product narrative did not keep pace.

Developers continued to associate Postman with a single tool rather than a full platform, which:

• Limited adoption of newer capabilities

• Created confusion across core product surfaces

• Made it difficult for internal teams to communicate the full value of the platform

The company needed a clear, scalable way to express what Postman had become and how its products worked together.

My Role

I owned the repositioning initiative end-to-end across product, marketing, and external partners.

• Defined positioning direction in partnership with product leadership

• Led stakeholder alignment across executives, product, and marketing

• Owned messaging and content across all core surfaces

• Directed external agency selection and execution

• Managed cross-functional coordination across design, marketing engineering, and product

I reported into the Head of Marketing and worked directly with the CEO and Head of Product for milestone approvals.

Approach

Defined a Unified Narrative

Established a clear positioning direction centered on Postman as an API platform for collaboration.

• Translated product sprawl into a cohesive story across:

  • API Client

  • Workspaces

  • Collections

  • Private API Network

  • Enterprise

• Structured messaging to show how each product contributed to a broader workflow

Aligned Cross-Functional Stakeholders

Positioning required alignment across multiple teams with different perspectives.

• Facilitated stakeholder sessions across product, marketing, and leadership

• Partnered with product managers to ensure technical accuracy

• Secured executive alignment at key stages of the work

Built a Scalable Messaging System

Developed structured messaging across all core pages and the central “What is Postman?” hub.

• Defined how users would enter, navigate, and understand the platform

• Created content that connected individual features to the broader value proposition

• Ensured consistency across all surfaces

Operationalized Across Teams

Led execution across internal and external teams to bring the narrative to life.

• Selected and directed external design agency

• Partnered with marketing engineering on implementation strategy

• Ensured positioning translated consistently across content, page structure, and product storytelling

• Managed timelines, dependencies, and quality control across all outputs

Outcome

The full repositioning did not launch due to agency delivery issues and a leadership transition. However, the work delivered meaningful strategic impact:

• Established a clear, unified narrative for Postman as a platform

• Strengthened alignment between product and marketing on positioning

• Influenced future direction toward collaboration-focused messaging

• Exposed execution risks in large-scale, all-at-once repositioning efforts

Key Insight

Effective repositioning cannot rely on a single “big reveal.”

• Messaging should be deployed iteratively to stay aligned with product evolution

• Large-scale changes should be phased across messaging, UX, and brand systems

• Decoupling narrative from full redesign reduces execution risk and accelerates impact

What I Did Next

After this project, I formalized this work into a structured messaging framework to support future scalability.

• Introduced a repeatable system for defining product positioning

• Created alignment tools for product and marketing teams

• Enabled faster iteration and clearer communication across future initiatives