Vyshnevskyi

Case · 06 / Go get'em

Go get'em

  • Competitive intelligence
  • AI tool
  • SaaS
  • Shipped
  • Next.js

My role

Solo product designer and developer. Defined the full product from narrative architecture and user flow to visual design, AI pipeline engineering, and deployment — treating an 8-hour constraint as a product design challenge, not a development task.

Project

Shipped a working AI-powered competitive analysis tool in one weekend sprint. Real Firecrawl + Claude Vision pipeline identifying competitors, capturing screenshots, and producing specific evidence-backed recommendations — deployed and live.

01

Overview

Go get'em is an AI tool that takes your SaaS landing page URL, identifies your top three competitors automatically, and uses Claude Vision to deliver specific, evidence-backed design recommendations — with real screenshots, exact copy comparisons, and scored dimensions across hero clarity, CTA strength, and social proof.

02

Process

IdeaSolution

Step 01 / 06

The process

NARRATIVE ARCHITECTURE

Storyboarded the page as one continuous argument: you're losing but don't know why → manual comparison is broken → we show you exactly where → we tell you exactly what to fix → you act now. Every section and line of copy was made to ladder into that arc.

03

Shape

before

code

Shape before code

The page was a five-beat argument before it was a single component. Each section is one move in the arc — drawn as a wireframe first, so the structure carried the story and the code just dressed it.

Single-page scroll architecture · five beats

Swipe through the five beats →

01Hero

See exactly what your competitors do better

Cold open. The promise, a 3D blob, one CTA.

02Problem

See where you fall behind

You're losing but don't know why.

03Solution

Benchmarked against best

We identify, analyse and benchmark automatically.

04Result

Changes you can ship today

Not "improve your CTA" — the exact rewrite.

05Input · CTA

Drop your URL

One field gates the whole pipeline.

04

Landing

page

Landing page

A cinematic dark scroll experience — a hero with a 3D blob and three editorial storytelling beats: Problem, Solution, Result. The whole page walks the visitor from "see where you fall behind" to "changes you can ship today" before they ever touch the tool.

Landing page 1
Landing page 2
Landing page 3

05

URL

input

URL input

One field, one gesture. Drop a SaaS landing-page URL and the tool kicks off: Firecrawl scrapes the page, Claude identifies the top three direct competitors, and the vision pipeline benchmarks against them.

06

Analysis

results

Analysis results

Claude Sonnet 4.5 vision scores the page across six dimensions, 1–10, each backed by specific evidence and a concrete rewrite. Real output for Jira: 1/10 on Pricing Transparency (no pricing anywhere on the page), 6/10 on CTA Strength (generic "Sign up" vs Asana's "Get started · View demo"), 7/10 on Hero Clarity vs Linear's sharper positioning.

Analysis results 1
Analysis results 2
Analysis results 3

07

The

full

report

The full report

The first analysis is free — the full multi-page report sits behind a soft gate. "Don't stop at one page": drop your email for the complete breakdown, or subscribe for unlimited analyses. Mock Stripe stayed mock; the paywall was a scoping decision, not a build-out.

Final

thoughts

Final thoughts

This project showed what modern product development looks like when design, strategy, and AI work together.

The product was defined before it was built. User flows, positioning, monetisation, and technical direction were established upfront, creating a clear blueprint for execution. Once that foundation was in place, AI accelerated development, generating more than 95% of the code while product decisions remained firmly human.

The most important lesson was the value of focus. Every feature, interaction, and design decision was evaluated against a single question: does this make the core experience better? Maintaining that discipline allowed the product to move from idea to working solution quickly, without losing clarity or purpose.

This wasn't about building the most features. It was about building the right ones.

Because in product development, a focused product that solves a real problem will always create more value than a larger product that tries to solve everything.

Scroll to top