Competitive analysis without 40 screenshots in a folder
Walk a competitor's product, talk through what's worth borrowing, publish one markdown URL per competitor that your team can actually find next week.
This page is for PMs, founders, and product marketers running a competitive teardown, the kind where you sign up for three competitors, walk their onboarding, and try to remember what was clever by the end of the afternoon. The pattern fits other workflows on the use cases for visual product feedback hub, but competitive analysis is where the "one URL per competitor" shape pays off fastest. The artifact is the deliverable. If you can't share it, you didn't do the work.
The problem
A typical competitive analysis ends as three artifacts in three places. A folder of 40 screenshots with filenames like Screenshot 2026-04-12 at 3.47.21 PM.png. A Google Doc with 8 half-written notes that lost track of which competitor they were about. A Slack thread where someone said "wait, did you see how Linear handles pagination?" and nobody saved the link.
Nothing aggregates. Three weeks later, the team is writing the positioning doc and can't find the screenshot that proved the point. The PM redoes half the work. The founder ends up referencing "that thing Notion does" from memory in the board deck. The analysis was real; the artifact wasn't.
The CobaltCapture workflow
Open the competitor's product in one tab. Open cobaltcapture.com in another. Hit Capture screen, pick the competitor's window, drag a box around the screen that caught your eye. Hit Dictate and talk through what's interesting: "They put the upgrade CTA in the empty state, not the header, the first time you'd hit it is also the first time the value of upgrading is obvious." Move to the next screen. Capture. Drag. Dictate. Repeat through onboarding, the empty state, the settings, the upgrade flow, whatever you came for.
When you're done with that competitor, hit Publish. You get a URL like cobaltcapture.com/r/<slug> for that competitor specifically. Move to the next competitor and start a new session. One URL per competitor, each one carrying source links back to the actual pages you reviewed.
The team gets three short URLs instead of one shared Drive folder. The board deck gets a link in the footnotes. The positioning doc cites the exact screen.
What the output looks like
The published review is structured markdown. Each finding has the source URL, the cropped screenshot, and your dictated observation as a paragraph:
# Competitive teardown, Linear onboarding
Source: https://linear.app/signup
They put the upgrade CTA in the empty state, not the header. The first
time a user sees "Upgrade to Pro" is the first time they understand
what Pro unlocks, the empty state explains the limit and the upgrade
in the same view. Worth borrowing.
Source: https://linear.app/settings/members
Invite-by-email defaults to "Member" role, but the dropdown is
pre-opened on first use. Tiny detail, removes the "wait, what role
should I pick" hesitation. We default to Member silently, worse.
Source: https://linear.app/integrations
Integrations page is filterable by category AND searchable. We only
have search. With 30+ integrations the filter becomes the primary
nav. Add before we cross 20.
That document opens cleanly in any reader, a teammate's browser, a Notion page (paste the URL, Notion unfurls it), a positioning doc, or a coding agent's context window. There's no proprietary viewer and no login wall on the share link.
Why this beats screenshot folders
Three failure modes the markdown alternative fixes.
Screenshot folders lose context. The image is in the folder; the URL of the page it came from is not. Two weeks later you can't return to the actual screen to double-check what you saw. CobaltCapture stamps the source URL on every item, so the trail is always recoverable.
Notion docs lose visual immediacy. You can write "Linear's empty state has a great upgrade CTA" in a doc, but the reader has to imagine it. The dictated paragraph paired with the cropped screenshot is closer to "here, look at this" than to "trust me, it's clever."
Slack loses everything. The screenshot scrolls off, the thread gets archived, the link rots. A standalone review URL doesn't move.
The same artifact also feeds the next step. When you turn the teardown into a positioning brief or a feature spec for the team, the markdown export drops into a doc or an AI agent prompt without reformatting. See the guide on writing structured feedback for LLMs for why the markdown shape matters when the next reader is a coding agent.
Who this is for
PMs running competitive teardowns before a planning cycle. Founders walking a competitor's product the week before a fundraising deck, looking for the three slides' worth of "here's where the category is going." Marketing teams writing positioning docs who need receipts, the screenshot proves the claim. Anyone who's done this work and ended up with a folder of 40 PNGs they can't find a week later.
Capture your first review.
About a minute from open tab to a shareable URL your agent can ingest.
Start capturing