Everyone loves the advice “ship it ugly.” It’s catchy. It’s counterintuitive. It makes for great tweets. But when founders sit down to actually build their first version, they freeze. Because “ugly” is abstract, and abstractions don’t help when you need to decide what to include and what to cut.
So let me make it concrete. Here’s what “ugly” actually looks like across different product types, from real businesses that launched with embarrassing first versions and went on to make real money.
I’ve shipped ugly more times than I can count. The first version of a workshop I now sell for €149 per seat was delivered off a hand-written outline on a napkin. The first version of a consulting framework I used for years was a Google Doc with formatting errors. The first version of products I’ve helped founders launch at Startup Burgenland looked like they were designed during a power outage.
Every single one made money. Because customers don’t pay for polish. They pay for outcomes.
What “Ugly” Means (And What It Doesn’t)
Let me be precise about what I mean by ugly.
Ugly means: minimal design, limited features, manual processes behind the scenes, no automation, no polish, no brand guidelines, no onboarding tutorial.
Ugly does NOT mean: broken, unreliable, dishonest, or harmful. A product that crashes, loses customer data, or doesn’t deliver on its core promise isn’t ugly — it’s broken. There’s a critical difference.
The line is the core outcome. Everything that delivers the core outcome must work reliably. Everything else can be rough, manual, or missing entirely.
Here’s my framework: imagine your product is a restaurant. The food must be excellent (core outcome). The plates can be paper (ugly). The utensils can be plastic (ugly). There can be no ambiance (ugly). But if the food is bad, no amount of porcelain plates and candlelight will save you.
Applied to a digital product: if you’re building an invoicing tool, the invoice must generate correctly and the payment link must work (core outcome). The dashboard can be a plain HTML page. There can be no mobile version. The settings page can be hard-coded. The logo can be text in Arial.
This distinction — protect the core, let everything else be rough — is the Ship It Ugly philosophy in its most practical form.
V1 Examples: Digital Products
A course on freelance pricing:
- V1: 4 video calls recorded on Zoom, uploaded to Google Drive, shared via a link in an email
- No platform, no modules, no quizzes, no certificates, no community
- Price: €49
- Sold to: 15 people from existing network and one community post
- Revenue: €735
A template pack for startup pitch decks:
- V1: 3 Google Slides templates with a 1-page PDF guide
- No website (sold through a Gumroad link shared on LinkedIn)
- No previews (buyers trusted the one-paragraph description)
- Price: €29
- Sold to: 22 people in the first month
- Revenue: €638
A weekly newsletter for Austrian founders:
- V1: Plain text email sent through free Mailchimp tier
- No branding, no website, no archive, no sponsor program
- Just one person (me) writing about what I learned that week
- Price: Free for 3 months, then €5/month
- Converted: 34 of 180 free subscribers to paid
- Revenue: €170/month
In each case, the V1 took less than a week to create. The products were embarrassing by any design standard. And each one generated enough revenue and feedback to justify a V2.
V1 Examples: Services
A business validation coaching service:
- V1: A Calendly link for booking, a Google Form for intake, and a 45-minute Zoom call
- No website. No package options. No CRM. No follow-up sequence.
- Marketing: DMs to founders I’d met at events
- Price: €120 per session
- First month: 7 sessions = €840
A content strategy service for small businesses:
- V1: A shared Google Doc where I wrote a monthly content plan
- Client communication via WhatsApp
- Invoicing via a manually created PDF
- Price: €300/month
- First quarter: 4 clients = €1,200/month
Services are the easiest to ship ugly because the delivery mechanism doesn’t matter — only the outcome does. Clients don’t care whether your invoice came from QuickBooks or a Word document. They care whether your advice made them money.
V1 Examples: Software/SaaS
This is where “ship ugly” feels hardest, because software founders associate quality with user interface polish.
A social media scheduling tool:
- V1: A Google Sheet where the client enters their posts, and the founder manually scheduled them using free tools
- “Software” was really a service dressed up as a product
- Price: €19/month
- First users: 12, all acquired through cold outreach
- This is the Wizard of Oz approach — the customer thinks there’s technology; there’s actually a human
An analytics dashboard for e-commerce:
- V1: A single Loom video recorded weekly showing the client’s key metrics, created manually by the founder using Google Sheets
- No actual dashboard. No login page. No real-time data.
- Price: €99/month
- First users: 5, acquired through a Shopify community post
- The “product” was a weekly video. The value was the insight.
A customer feedback tool:
- V1: A Typeform survey embedded on the client’s website, with responses summarized in a weekly email by the founder
- No dashboard, no NPS tracking, no integrations, no automation
- Price: €49/month
- First users: 8
In every software V1, the founder was the technology. The product was a manual process that looked automated from the outside. This sounds like cheating, but it’s actually the smartest possible approach because it lets you validate the outcome before investing in the implementation.
The V1 Checklist
Here’s exactly what I include and exclude in every V1 I build or advise on.
Include:
- The core outcome (the thing the customer is paying for)
- A way to collect payment (Stripe link, PayPal, bank transfer)
- A way to deliver the product or service (email, Google Drive, Zoom, whatever)
- A way to communicate with the customer (email, WhatsApp, Slack)
- A way to collect feedback (a follow-up email asking “how was it?”)
Exclude:
- Logo, branding, or design system
- Website (a sales page is enough)
- Onboarding flow
- Automated email sequences
- Analytics or tracking (beyond basic Stripe data)
- Multiple product tiers or options
- Terms of service or legal pages (needed eventually, not for V1)
- Mobile optimization
- Support documentation
- Anything that doesn’t directly serve the paying customer
This checklist horrifies people who come from corporate environments where everything needs to be compliant, branded, and documented before launch. I get it. I spent years in corporate innovation consulting where nothing shipped without 14 approval signatures.
But you’re not launching a corporate product. You’re testing whether an idea works. The minimum viable experience is what matters, and the minimum is much less than you think.
Why Your Brain Resists Ugly
Let me address the psychology, because understanding why you resist ugly is the first step to overcoming it.
Reason 1: Pride. You want your name associated with quality. An ugly V1 feels like putting your name on something you’re ashamed of. But the alternative — never shipping because it’s never good enough — means your name is associated with nothing.
Reason 2: Fear of judgment. If you ship something ugly, people might think you’re incompetent. But the people whose judgment matters — paying customers — judge results, not aesthetics. And the people whose judgment doesn’t matter — random internet critics — will judge you regardless of quality.
Reason 3: Perfectionism disguised as standards. “I have high standards” is the most common excuse for not shipping. But perfectionism at the V1 stage isn’t a high standard — it’s a preparation trap. High standards at V1 means the core outcome works perfectly. Everything else is filler.
Reason 4: Comparison. You see polished products from established companies and think your V1 needs to match them. But those products are V47, not V1. Their V1 was ugly too — you just didn’t see it because they’ve had years to iterate.
The hack that works for me: I set a time limit. “This V1 must be shipped within 7 days.” When the clock is ticking, my brain stops optimizing for beauty and starts optimizing for done. The constraint removes the option of perfectionism and leaves only the option of shipping.
The V1-to-V2 Bridge
Shipping ugly is only half the strategy. The other half is learning from V1 to make V2 better.
After shipping V1, I collect data in three categories:
What broke? What didn’t work as expected? What confused customers? Where did the experience fail?
What’s missing? What did customers ask for that V1 didn’t include? What would have made the experience significantly better?
What’s unnecessary? What did I include that nobody used or mentioned? What can I remove to simplify?
V2 addresses the “what broke” list. V3 addresses the “what’s missing” list. And every version applies the “what’s unnecessary” list — subtracting what doesn’t belong.
This sequential improvement means each version is shaped by real customer behavior rather than your assumptions. By V3 or V4, the product often looks nothing like the original V1 vision — and it’s better for it, because it’s been sculpted by reality rather than imagination.
The founders who succeed with Ship It Ugly are the ones who treat V1 as a learning tool, not a finished product. V1 isn’t the business. V1 is the experiment that teaches you what the business should be.
Key Takeaways
- Ugly means minimal, not broken. The core outcome must work perfectly. Everything else can be rough, manual, or absent.
- V1 should take a week or less to build. If it’s taking longer, you’re including too much. Review the V1 checklist and cut everything non-essential.
- You can be the technology behind V1. Manual processes that look automated from the outside let you validate the outcome before investing in automation.
- Your brain will resist shipping ugly due to pride, fear, perfectionism, and comparison. Set a time limit and ship when the clock runs out, not when it feels ready.
- V1 is a learning tool, not a finished product. Collect data on what broke, what’s missing, and what’s unnecessary. Let V2 and V3 be shaped by real customer behavior.
