Your Boss Emailed a Competitor’s Link. Now What?

Summary

Your boss forwards a competitor’s landing page and says “make ours look like this.” This article walks through what to do next—without starting a fight or ignoring the request. It covers how to resist blind copying, write a plain-language value prop, narrow the page to one call to action, and present your case as a choice rather than a verdict. The approach is grounded in the SaaS landing page patterns that consistently prioritize clarity over cleverness, from clear value propositions to minimal hero sections. You’ll also get a practical template for winning stakeholder buy-in when the decision-maker isn’t into design. The goal is a page that does its job and a team that shares the same language about why it looks the way it does.

What do you say when your boss sends you a competitor’s landing page with the note “ours should look like this”? You’re on a three-person in-house marketing team. You’re not the owner of a design budget. You have a product to sell, a launch date, and a boss who can’t tell a font from a heading. And right now, that boss is pointing at a page that does look good — so the easy, safe move is to nod, copy the structure, and swap in your own copy. But the safe move is usually the one that gets the page ignored.

The meeting is Friday. You have four days to show the boss why a different approach is better, without turning the review into a fight. Here’s a plan you can follow end to end.

Read the email, not the link

A link is a demand wearing a URL. Before you open a browser tab, read the note attached to it. Is your boss asking for a similar look? A similar section order? A similar logo treatment? Each of those is a different request. Most of the time, the note says “make ours look like this” and really means “make ours feel as credible as that.” The page you’re looking at only matters because it gives the boss a feeling of legitimacy. So your real job isn’t to reproduce the page. It’s to produce that same feeling with your own reasoning.

Here’s the thing about that competitor’s page: what you’re seeing is the result of decisions you weren’t part of. That design was built around their audience, their market position, their brand recognition, and their conversion goals. You’ll copy the visible parts — the layout, the color, the stock photos — and you’ll miss the invisible reasoning that made them work. That’s not a design problem; it’s a strategy leak. Stealing their skeleton is a different exercise from stealing their content, and the skeleton only works if you understand why they chose it.

Before you open anything, answer one question: what is this page supposed to do? Not “look like a modern SaaS,” but what should a visitor think, feel, and click in the next sixty seconds? Write that down before you look at anything. If you can’t do that, you’re building a poster, not a page.

The common temptation is to treat a competitor page as a shopping list: big headline, three-column feature grid, chat widget, pricing link, customer logos. But the most durable pattern in SaaS design is simpler. Over and over, the pages that convert are the ones that don’t try to do six things at once. They prioritize clarity over cleverness — a concise headline, a brief description, one obvious next step. That’s not a secret, but it’s surprisingly hard to defend inside a company that keeps asking for “more.”

The temptation	What usually works better
Mirror the competitor’s layout	Recreate their underlying logic, not their sections
Pack the first screen with features	Headline, subhead, single CTA
A clever tagline that fits the brand voice	A plain-language sentence about what the product does
Multiple buttons to cover every visitor type	One primary action per screen, secondary actions placed further down

This table is meant for the moment when the page goes through an internal review, because every row is a question someone will ask. The answer to each isn’t “this is what modern SaaS looks like.” The answer is what the visitor needs to do next.

Write the sentence that saves you a redesign

Before you open a design tool, open a text file and write one sentence: what does your product do, and for whom, and why should they care today? Start with the worst version of that sentence, the one you’re embarrassed to show anyone. Then edit it until it would make sense to someone who has never heard of your company.

Here’s a worked example, deliberately generic. Say your product helps retail shops remind customers about their appointments. Current hero headline: “Next-Gen Retail Engagement Platform.” It sounds important. It means nothing. The visitor looks at it, doesn’t know if this is software, a consulting firm, or a chatbot, and leaves.

The rewritten version: “Send automatic appointment reminders so your staff stop calling people back three times a day.” It’s less impressive on a slide deck. It’s more useful on a screen. When a typical visitor — someone running a small shop — reads it, they immediately know what the product is, who it’s for, and what outcome to expect. The value proposition reads like a sentence, not a mission statement.

This is also the pattern you’ll recognize from the most-admired SaaS homepages. Calendly’s own tagline is just “schedule meetings without the back-and-forth emails.” No mention of algorithms, no “revolutionary scheduling.” It names the outcome a particular person wants. Your product has an equivalent sentence; you just haven’t written it yet.

Expect resistance here. Your boss will say the new headline is “too plain” or “doesn’t sound like a real tech company.” That reaction is about identity, not clarity. The people you work with read your product’s pitch every day; a plain sentence sounds under-dressed to them precisely because they already know what the product does. The visitor doesn’t. Defend the sentence with that distinction. If the boss says “we also serve restaurants, not just retail shops,” that’s actually good news: the sentence can name the category more loosely while still naming the outcome. What you can’t afford is a headline that describes nothing.

One action per screen

Take a look at the most respected SaaS homepages and you’ll notice a habit: they choose one next step and make everything else get out of its way. Notion, a reference point in landing page reviews, aims for a single call to action such as “Get Notion free.” That one button states what will happen when you click; it doesn’t ask you to choose between “Start trial,” “See pricing,” “Request demo,” and “Talk to sales.”

Your page probably does exactly that. The hero has two or three buttons, the navigation bar carries links to pricing, blog, support, and careers, and a chat widget floats over everything. Every addition is a small tax on the visitor’s attention. They came for one task. Every link is an opportunity to abandon it.

The fix is not to strip your site bare. It’s to decide what the single primary action is for this page — start a trial, book a demo, or make a purchase — and make that the only thing that looks like a button in the hero. Secondary destinations can exist further down the page, after the case has been made. If you’re worried about pricing curiosity, a plain text link in the footer or the top nav serves that without competing with the main call. This page is one chapter of a larger site; it doesn’t have to do the job of the whole site. If you’re also rebuilding the larger site, a landing page framework with proven SaaS conversion practices is a good reference to share with the boss — it’s an external voice saying what you’re trying to say.

When your boss questions why you removed a button, you can say it plainly: two buttons makes the visitor choose before they understand what they’re choosing. One button tells them the one thing you want them to do. The page will feel quieter, and quiet pages convert.

The hero is a test, not a poster

The first screen is not a billboard; it’s a handshake. Linear’s homepage, often cited in design reviews, is minimal: a clean headline, a short subheading, a single call to action. Nothing fights for attention. There’s no attempt to show every feature in the first viewport. It works because the small amount of text is precise enough to explain what Linear does to someone who’s never seen it.

The “above the fold” idea has migrated from a physical fold to the first screen on a phone, and the constraints are tighter there. A visitor scanning on their commute sees half a headline and a cropped screenshot, and they make a judgment anyway. So the hero should survive a three-second glance: one sentence saying what the product is, one sentence saying what it does, one button. If it needs an explanation, it’s wrong.

Use that as your own test. Don’t test it on your colleagues; test it on people who don’t know your product. Put a draft of the hero in front of four or five friends or acquaintances outside the industry and ask one question: “What does this product do?” If anyone hesitates, the hero has failed. If they can answer without your help, you have the foundation of a page.

This is also the stage where you’ll meet the “make it pop” question. Popping is a symptom, not a feature. A hero can be visually confident — a strong color, a sharp product screenshot — and still be quiet. The point isn’t to remove visual interest. The point is to keep every visual choice aimed at the single action you decided on in the previous step. A striking photo of a person using your product is fine; a photo of a rapper with your logo is not.

Collect the proof before you need it

Once the value prop is right and the hero is minimal, the page can start to feel a little empty to someone used to feature grids. That’s what the social proof section is for. Gather three pieces of evidence before you open the design file, not after: a testimonial that says something an actual customer said (not the word “amazing”), a recognizable customer logo or two, and one concrete metric you’re allowed to share publicly. No invented numbers here — a single quote that mirrors your value proposition will do more work than a row of empty logos.

The boss won’t argue with social proof because it’s not a design choice; it’s evidence. When someone asks why the page “doesn’t have any content,” the answer is that a well-placed testimonial can carry more persuasive weight than three paragraphs of features. Visitors don’t trust your claims yet. They trust people like them who already took the action you’re asking for.

Placement matters. Put the strongest proof right after the hero, or alongside the main call to action. The logo strip says “you’re in good company”; the testimonial says “this outcome is real”; the metric says “here’s the size of the effect.” You don’t need all three on every page, but you need at least one near the moment of decision. If your product is new and you have no testimonials yet, offer a generous trial or a walkthrough video — proof can be behavioral as well as verbal.

The final meeting isn’t about taste

The last step is making your case to the person who signs off — and this is a step you can control. Walk into the meeting with two options, not one. The first is the “boss version”: a page that follows the competitor’s structure and tone, the thing they asked for. The second is the “clear version”: the plain-language value prop, one CTA, minimal hero, and evidence. Present both as real designs, not as deferential sketches versus your favorite.

Then name the difference without pretending the clear version is better in every dimension. Say: “This page says we’re a company like the competitor. That one says what we do and what the visitor should do when they get here. The first is a better fit if we think the main job of the page is to signal category.” That framing makes the boss a decision-maker rather than someone who needs to be talked out of an instinct, and it keeps the conversation on what the page is for.

Here’s the contrarian point that most advice articles skip: your boss is not wrong to want a distinctive-looking page. If your product genuinely introduces a new category, some visual personality is necessary — you want people to remember it. But that requirement belongs to your overall brand identity and your site’s navigation, not to a landing page with a single conversion goal. On a page whose job is to get a click, design that calls attention to itself competes with the message. You might sacrifice a bit of “wow” to get clarity. That tradeoff is real, name it explicitly, and make it a decision rather than a surprise.

There’s also a parallel, harder case: what if your clear version is the one that’s wrong? If the page’s goal is to launch a brand-new product in a crowded market, some visual distinctiveness can help — for example, a strong illustration or an unusual color system that creates recognition. The rule isn’t “be boring.” The rule is: every element must justify itself against the visitor’s next step, and if the only defense of an element is that it looks impressive, it probably shouldn’t be there. You can say that in the room with confidence, and it removes the pressure your boss is feeling to make everything look impressive at all times.

A stronger move is to propose a test. If the boss insists on their version, say: “Let’s put both pages up for two weeks and measure the click-through rate on the primary action.” Small teams sometimes worry they don’t have enough traffic for a meaningful test, and that’s a fair caveat. If that’s true — you’re getting only a few hundred visitors a month — use qualitative signals instead: session recordings, exit comments, or a simple five-person usability check. A test isn’t the only way to learn; it’s just the clearest way to end a disagreement without wounded egos.

The real deliverable isn’t the page

Back to your scenario. You hold your ground, build the clear version, explain the two prototypes, and the boss picks the clear one — partly because you made it a choice, partly because you have a headline that can be read aloud in a sentence. The page launches. It will generate more signups, fewer puzzled exits, or whatever success looks like for your product, and the next time the boss sends a competitor link, your team already has the language to discuss whether the request is about strategy or style.

That language is the actual deliverable. A landing page is easy to redesign; a team’s default assumption that “modern design means lots of stuff” is slower to change. Each time you defend a plain value prop or a single CTA, you’re building a small library of references your whole team can use. The next project becomes easier. If you want to apply the same honesty to the whole site rather than a single page, you can audit the rest of your site like a customer who doesn’t care. And if you find yourself unsure whether you even need a campaign page versus a full website, this guide to choosing between site formats will help you frame it.

It’s not about winning an argument. It’s about making sure the next call to action on that page is one your visitors actually want to take — and can actually find.