unsolicited redesign — Productlane landing page

productlane is one of the better-designed pages in the customer-support tooling space. they're a munich-based, pre-seed, linear-native customer support tool, and their roster — clerk, flightcontrol, francis — is the kind of customer list most series-A companies would kill for. the page reflects the team's craft.

but there's a sharper version of it sitting just under the surface. eight specific moves, ordered by how visibly different they'd look in a side-by-side. five made the thread. three didn't fit. plus a list of things i'd refuse to touch, because constraints are part of the work.

a quick framing note: landing-page redesign critique is often oversold as a vanity exercise — "make it prettier" — when at sub-$1M MRR the hero band is actually one of the highest-leverage surfaces a SaaS company owns. a sharper headline can shift trial conversion by 15-30%. above-the-fold social proof can multiply qualified click-through by 5-10x. these aren't aesthetic claims. they're business claims dressed up in design vocabulary.

what they're doing right

before any critique: the page has three things i'd straight-up steal for other clients.

the product UI screenshot in the hero is the right call. most SaaS marketing pages put a 3d mood-piece or an abstract illustration where productlane puts an actual inbox view. that's a confidence move — it teaches you what the product is in two seconds, which abstractions never do.

the "built around linear" positioning in the subheadline is sharp. it tells you exactly who this is for (linear-using teams) and exactly what makes it different from intercom or front. specificity earns trust in a way that "customer support, reimagined" never could.

the customer roster is unusually credible. clerk and flightcontrol are recognizable dev-tooling brands in the audience that matters most for productlane's wedge. jeff escalante (eng director at clerk) testifying that productlane "transformed our engineering process to being massively more customer oriented" is the kind of quote that converts engineering buyers — when they can find it. more on that in a moment.

the 5 changes i'd push in the thread

1. kill the centered hero, go asymmetric 58/42 split

centered hero text is the strongest "ai-generated saas template" signal in 2026 design. it's the layout that ships when no one made a real layout decision. asymmetric splits read as deliberate — the same reason vercel, linear, cal.com, and resend's strongest pages all favor left-alignment with a single weighty asset on the right.

the specific move: restructure to a 58/42 split. left 58% holds the eyebrow, H1, subhead, and CTAs, all left-aligned. right 42% holds a live animated product fragment (more on that in change #3). 96px gap between columns on desktop. the slight off-center (not 60/40 or 50/50) creates a tension the eye reads as intentional rather than mechanical.

the business reason: this is the move that signals "this brand has design taste." engineering teams evaluating support tools have a short list of things they look for in a marketing site before they'll take it seriously. a 2010s-feeling centered hero suggests the team is two years behind on design conventions, which leads buyers to suspect they're two years behind on product conventions too. fair or not, the inference happens.

2. swap the H1 from a category claim to a belief claim

"customer support for modern companies" is what every competitor says — front, intercom, help scout, plain. when five competitors share a headline, none of them mean anything. category-claim headlines are renting space, not earning it.

i'd swap it for something opinionated. three directions worth considering:

• "every ticket is a one-line code change away." (technical, native to the linear-using audience, makes a real claim about the product)
• "customer support that compiles." (terse, almost-weird in a way that makes you re-read, brand-claim)
• "linear, but for the customer side of your codebase." (positions against intercom by name without naming them)

i'd pick the first. set it at 88px desktop / 44px mobile, with tracking tightened to -0.04em and line-height pulled to 0.94. the difference between a "competent landing page" and a "thoughtfully art-directed one" is exactly this — tight tracking on a display headline creates the poster-feel that signals craft. font-weight stays at 500, not 700. modern display sans looks better at medium weight at scale than at full bold.

the business reason: headlines that take a position outperform headlines that describe a category, consistently, across every conversion test that's been published in the last decade. the linear wedge — the thing that actually distinguishes productlane from the support-tool pack — is currently doing supporting work in the subheadline. promote it. the subhead can still carry the existing copy in its new supporting role.

3. build the right column as a live animated linear-style ticket lane

the current product UI screenshot is gorgeous but static — which means it tells you what the tool is, not what it does. productlane's entire tagline is "built around linear to turn customer messages into code instantly." instantly is a motion word. static images can't communicate motion.

the move: replace the static hero asset with a clipped 3-column linear-style status lane — inbox → in progress → shipped. one ticket card animates through the lanes on a 6-second loop. starts in inbox as "patrick: SSO setup," auto-tags itself with "Enterprise," moves to in progress with a linear ticket badge appearing, resolves to shipped with a small green check. framer motion's layout + layoutId props give the ticket clean spring-physics transitions between lanes.

the business reason: this is the move where the redesign actually demonstrates the product's value proposition rather than just describing it. visitors leave the hero band knowing what productlane does — not just what it is. for a product whose pitch is speed, a 6-second motion loop is worth more than every word on the page combined.

4. compress dual CTAs into one bold primary + an inline secondary

the current dual-CTA pair ("get started" + "book a demo") treats sales-led and self-serve as equally weighted paths. they aren't. for a product at productlane's tier ($20-200/mo most likely), self-serve should be the loud option and the demo should be the quiet escape hatch.

the move: replace with one filled primary button ("start free") in a rounded-[10px] shape (not pill — sharper corners read more decisive), followed inline 16px to the right by a plain text link "or book a 15-min demo →". the arrow micro-animates on hover. specifying "15-min" on the demo link removes the unconscious objection of "this is going to be a 45-min sales pitch."

the business reason: two visually-equal CTAs cause measurable choice paralysis — visitors hesitate when they can't tell which option the company wants them to pick. asymmetry signals priority. for productlane's tier, the priority is self-serve activation, and the redesign should reflect that.

5. replace nav "sign up" with a ⌘K command bar

this is the most tribal-signal move in the redesign. productlane's audience lives in linear, vercel, raycast, notion, github desktop — every premium tool in their daily stack has a ⌘K command palette. it's the visual vocabulary of the engineering-team-native software universe.

the move: top-right of the nav, replace "login" + "sign up" with a single pill-shaped input field ~280px wide, with placeholder text "press ⌘K to start →" and a small ⌘K glyph on the left. clicking opens a linear-style command palette modal with three options: start free trial, book a demo, sign in. subtle 4-second breathing animation on the bar so it doesn't read as a static UI element.

the business reason: it's tribal-signal-at-the-component-level. the audience reads the nav and immediately knows productlane was built by people who think like them — before they've read a single word of marketing copy. this is also the most retweetable single move in the redesign, which matters for the thread's reach independent of conversion.

the 3 moves that didn't fit the thread

6. replace the eyebrow pill with an inline status indicator

filled marketing pills with sparkle icons read as exactly the energy linear-using audiences are allergic to. inline status indicators read as engineering-team-native vocabulary.

the move: drop the "new: support copilot" pill. replace with a single-line inline status: a 6px green dot with a subtle outer glow, breathing on a 2-second opacity loop, followed by "support copilot is live" in 13px mono-tracked text. all of it left-aligned, 12px above the H1.

why this didn't make the thread: it's a smaller change visually — readers scrolling past wouldn't necessarily notice it in a side-by-side. it's a good move, but it's a polish-tier move, not a hero-tier move.

7. make the customer logos a grid, not a strip

logo strips — equal-spaced horizontal rows of customer logos — are the SaaS default and have lost their meaning through overuse. the move: replace with a 4-cell logo grid with hairline borders between cells, monochrome white at 40% opacity, left-aligned with the H1 column. label above: "trusted by teams at" in 11px tracking-wide uppercase mono.

the structure shift — strip to grid — reads as deliberate showcase rather than token social-proof gesture. the 40% opacity prevents logos from competing with the H1 above. the borders create a "this is structured data, not decoration" feel that fits the audience.

why this didn't make the thread: paired with change #1 (the layout restructure), the logo treatment becomes hard to demonstrate cleanly in a separate tweet. it's better experienced as part of the overall asymmetric composition, not as a standalone before/after.

8. float a single testimonial card on the dark page as a focal anchor

a white card on a dark page is the strongest single contrast move available. the eye is drawn to it before anything else. the move: below the animated product UI fragment in the right column, place a 320px-wide white card with rounded corners, containing jeff escalante's clerk quote with a real avatar photo, name, and title. subtle tinted shadow. gentle 4-second float animation.

the business reason: engineering buyers respond to specific named credibility more than any other persuasion mechanism. jeff escalante's quote is unusually good (it claims an engineering-process transformation, not a "great support tool" generic). adjacent to the primary CTA, in a visually arresting treatment, the proof reaches buyers before they've finished evaluating whether to click.

why this didn't make the thread: it's redundant with change #1's right-column-as-animated-fragment direction. you can have the animated lane or the floating testimonial card in the right column — not both, not without making the composition busy. in the actual redesign the testimonial card would slot below the animated lane with proper vertical rhythm, but explaining that in a tweet without the visual proof is hard.

what i'd never change

the typeface. their modern sans (likely geist) is correctly chosen for the linear-adjacent audience. swapping to a serif would be aesthetic vandalism; swapping to a different sans would be churn without payoff. stay in the family.

the palette. dark mode is core to the positioning — the entire engineering-team aesthetic universe is dark-first. a light-mode redesign would be technically defensible but strategically wrong.

the logo. their wordmark is fine and isn't the issue. redesigning logos in unsolicited threads is universally received as overreach — it alienates the founder and signals you don't know what's worth changing.

illustration or 3D mood-pieces. the product UI is the right hero visual. replacing or supplementing it with a stylized illustration would be a step backward. the screenshot teaches the product; alternatives just decorate.

below-the-fold sections. the hero is where 80% of conversion impact lives. the feature cards, pricing teaser, customers section, and changelog preview are all fine and don't need rework for this concept piece. promising hero-only changes and delivering more reads as scope creep, not generosity.

the subheadline copy. "omnichannel customer support engineered from the ground up for AI. built around linear to turn customer messages into code instantly." is already good — specific, technical, makes a real claim. if you swap the H1 (change #2), this becomes the supporting detail and reads better in that supporting role. leave the copy alone.

the broader take

centered hero text was the right move in 2010, when the web was still figuring out marketing pages and "center the H1" was a reliable way to make something look intentional. fifteen years later it's the move people don't make on purpose — it's the default that ships when no one made a real decision. the productlane page is a polished example of a competently-executed default, which is a strange thing to be in a category that lives or dies on differentiation.

the harder, more useful thing for any SaaS at their stage: pick one belief about your category, stake the H1 on it, and let the layout reflect the confidence that comes from picking. centered text says you want to be liked by everyone. left-aligned text with a sharp claim says you've picked a customer and you'd rather close them than charm a stranger.

the close

the 8 changes here would take roughly 12 hours of design + code work — about half a week inside an evrgrn subscription. if productlane's team is reading and wants a fuller audit, free, no agenda — chris@evrgrn.design. or just reply on twitter.

evrgrn is a subscription design service for SaaS marketing teams. $2,995/mo, unlimited requests, pause anytime, ships deployed code not just figma files. more redesigns and the rest of the journal at evrgrn.design.