The Methodology

Pitwall is a fictional company.
Built to show how scalable GTM gets made.

This site is not a real product and not a design exercise. It is a demonstration of a complete product marketing methodology — applied to a fictional but realistic security company — from ICP definition to a deployable website. Every page was produced by working through the same process I bring to every early-stage company I work with.

Pitwall exists as a proxy for the real work: turning founder insight into positioning, messaging, and a GTM motion the rest of the team can run. The full methodology is documented here: The First 90 Days.

Why This Exists

Most PMM portfolios show you the output. This one shows you the thinking.

Early-stage founders do not need a PMM who can execute a campaign brief someone else wrote. They need someone who can walk into a company with no messaging, no ICP definition, and no category clarity — and turn what the founder knows into a GTM motion the rest of the team can run. That is a different skill than campaign management, and it is hard to demonstrate with a slide deck.

So I built Pitwall from the ground up using the same methodology I have applied at every company I have worked with. Pitwall is a fictional company based on a real, unsolved problem in enterprise security. Everything else is real work: the product definition, the positioning, the messaging architecture, the GTM strategy, the website, the pricing, the sales enablement. Produced in sequence, the way it actually gets done.

The result is a complete PMM foundation any technical founder could hand to a sales team tomorrow.

The Process

The sequence. In order. No shortcuts.

This is the sequence. It matters. Each layer builds on the one before it. Messaging written before ICP is defined will be wrong. A website built before the messaging spine exists will need to be rewritten. The discipline is in doing it in order. Days 1 through 30 build the listening foundation. Days 30 through 60 build the messaging and GTM foundation. Days 60 through 90 build what the market sees.

01
// Foundation

Define the Problem Honestly

Before positioning, before personas, before a single word of copy, the work starts with understanding the problem the product actually solves. Not the problem the founders want it to solve. The one buyers are experiencing right now. For Pitwall, that meant acknowledging that the alert fatigue problem is real and unsolved, that AI SOC tools attack the symptom rather than the cause, and that no product currently gives SOC teams real-time visibility into control performance. That honest assessment became the foundation everything else was built on.

Output: Problem statement, competitive white space
02
// ICP

Define Who You Are Actually Selling To

ICP is not a demographic. It is a description of the company that has the problem badly enough to buy something about it today. For Pitwall, that meant enterprise or mid-market security teams running stacks of 25 controls or more, with dedicated SOC managers who are drowning in false positives and CISOs who have to justify security investment to a board. Everything downstream flows from this definition: messaging, channel, pricing, the entry motion. Without it, you are guessing.

Output: ICP definition, buyer persona profiles, org map
03
// Positioning

Stake Out a Defensible Position

Positioning is a choice about what you are and what you are not. Pitwall is not a SIEM. It is not an AI SOC agent. It is not a professional services engagement. It is a continuous performance monitoring layer that sits above the stack and fixes what is not working without replacing anything. That negative space matters as much as the positive claim. Founders who try to be everything to everyone end up being nothing to anyone.

Output: Positioning statement, competitive frame, category definition
04
// Messaging

Build a Messaging Spine, Not a Tagline

A tagline is the last thing you write. A messaging spine is the narrative architecture that makes all external communication consistent. From the homepage headline to the SDR cold email to the CISO one-pager. For Pitwall, the spine has four sections: The Problem, The Way Out, The Credibility, and The Political Safety Valve. Every piece of content maps back to one of these four. When it does not, the content gets cut or rewritten.

Output: Messaging spine, voice guide, approved language, prohibited terms
05
// GTM

Design the Go-to-Market Motion

GTM at an early-stage company is not a marketing plan. It is a set of decisions about who you are selling to first, how you are reaching them, what the entry motion looks like, and how you move from early adopter to repeatable revenue. For Pitwall, the entry motion is the Shakedown: a 14-day no-obligation assessment that requires no procurement process and no executive approval. A SOC manager can start it today. That design decision shapes the entire GTM.

Output: GTM strategy, entry motion design, launch framework, campaign plan
06
// Pricing

Package Around Buyer Psychology, Not Cost

Pricing communicates value and creates a buying decision. Pitwall's three-tier structure is designed around a specific insight: the SOC Manager is the user, the CISO is the economic buyer, and the entry motion needs to work without either. Basic lets a SOC manager start without a budget conversation. Pro adds the intelligence layer that makes the platform genuinely useful long-term. Enterprise adds automation and scale. Each tier is priced to create a clear upgrade path, not to capture maximum revenue from tier one.

Output: Pricing tiers, packaging rationale, sales guidance
07
// Enablement

Arm the Revenue Team

At an early-stage company, the revenue team is often the founders. They know the product deeply and struggle to explain it to someone who does not. The job is to give them what they need to have better conversations: a first-call deck that gets to the problem fast, competitive battlecards they can pull up mid-call, and a datasheet a CISO will actually read. Built with sales input from the first conversation. Not handed over after the fact.

Output: First-call deck, platform datasheet, competitive battlecards, one-pagers
08
// Website

Build the Website Last

The website is where everything comes together. If you build it before the messaging spine exists, you will rebuild it six months later. The Pitwall website follows directly from the messaging work: same four-part narrative, same ICP hierarchy (SOC Manager first, CISO second), same entry motion (the Shakedown). The copy on every page traces directly back to a decision made in a prior step. Nothing on the site was invented at the website stage.

Output: Website architecture, full site copy, homepage and inner pages
What This Demonstrates

What a founder or hiring manager should take away from this.

The work happens in order

Most PMMs skip to execution. The ones who do not are the ones who build positioning that holds up for three years instead of six months.

ICP drives everything downstream

Pitwall's entry motion, pricing tiers, and homepage hierarchy all follow from the ICP definition. Change the ICP and the whole structure shifts. That is not a coincidence. It is how it is supposed to work.

Messaging is architecture, not copywriting

The Pitwall messaging spine is a four-part narrative structure. Copywriting fills in that structure. Without the architecture, even great writing is inconsistent.

The entry motion is a strategic decision

The Shakedown was not invented by the marketing team. It was designed to eliminate every friction point in the buying process. That is product and GTM thinking, not a campaign idea.

What Was Built

The full Pitwall portfolio.

Every document below was produced as part of this engagement. Available on request. The full methodology behind this work is documented in The First 90 Days.

GTM Strategy
Messaging Spine
Messaging Guidebook
ICP and Buyer Personas
Brand Guidelines
Platform Datasheet
Competitive Battlecards
First-Call Deck
Pricing and Packaging
Launch Framework
Campaign Plan
Content Plan
Launch Narrative
Investor Narrative
Website Narrative
Agency Brief
Automation Plan
Website (this site)
// Get In Touch

Let's talk about what you are building.

If you are a founder at a Series A or B company trying to close the gap between what your product does and what the market understands, that is exactly what this work is for.

Steve Salinas
Product Marketing Leader  |  17 Years in Cybersecurity