Shareable proof you shipped.

Why "I Shipped" Deserves More Than a Tweet

Shipping a side project is hard. For most developers, it is the hardest part of the entire process. You pushed through the boring middle, resisted scope creep, and delivered something real. That deserves recognition.

But how do you share it? A tweet that says "I shipped my project!" and gets lost in the feed? A screenshot of your landing page? A LinkedIn post that reads like every other launch announcement?

Ship Cards turn your shipped project into a shareable, visual achievement. They contain real data from your project - not self-reported claims, but system-generated stats that tell the story of how you got to launch.

What Makes Ship Cards Different

Ship Cards are not participation trophies. They carry meaningful data:

• Days to build - How long from project creation to ship. This is real time, not estimated time.
• Version number - V1 means first ship. V1.1 means you shipped, iterated, and shipped again.
• Unlock count - How many times you unlocked your scope. This is the metric that makes Ship Cards interesting.

The unlock count is the most distinctive element. No other tool surfaces this information. It creates a new kind of developer flex: not "look how fast I built this" but "look how disciplined I was building this."

A Ship Card with zero unlocks says: "I planned it, locked it, and shipped exactly what I committed to." That is a story worth sharing.

Ship Cards and Building in Public

The build-in-public movement has a content problem. When you are building, there is plenty to share - progress updates, technical decisions, design iterations. But when you ship, the announcement often falls flat because there is no standard format for "I finished this."

Ship Cards solve this by providing a consistent, visual format for ship announcements. They are designed for social media - the dimensions, the information density, the visual hierarchy are all optimized for Twitter, LinkedIn, and blog posts.

For developers who build in public, Ship Cards create a natural cadence:

1. Share progress during development
2. Share the Ship Card when you launch
3. The Ship Card links back to your Harbor for the full portfolio

This creates a flywheel: each shipped project generates social content that drives visibility, which motivates shipping the next project.

Ship Cards as Developer Identity

Over time, your collection of Ship Cards becomes a visual record of your shipping history. Like a wall of framed diplomas, but for projects you actually finished.

This matters because developer identity is usually defined by what you know (languages, frameworks, certifications) rather than what you delivered. Ship Cards shift that metric. They let you say: "I am a developer who ships. Here is the proof."

For hiring managers, clients, or collaborators evaluating your work, a collection of Ship Cards with real stats is more compelling than a GitHub profile full of green squares and abandoned repos.

How Ship Cards Connect to the FoundStep Pipeline

Ship Cards are the final output of the FoundStep shipping pipeline:

1. Validate - 7-Step Validation confirms the idea
2. Plan - AI MVP Planner generates the structure
3. Lock - Scope Locking freezes the scope
4. Build - Work against locked scope, with Shame History tracking unlocks
5. Ship - Deploy to the Harbor and generate your Ship Card

The Ship Card captures data from every phase. Build time comes from the project timeline. The unlock count comes from Shame History. The version comes from your shipping history. It is not a standalone feature - it is the culmination of a system designed to get you from idea to shipped product.