Windows is a crowded shelf for this — Snipping Tool ships free, ShareX is free and does nearly everything, and Lightshot has inertia. So the interesting question isn't features, it's which of those you're actually taking users from.
"Visual communication" in the tagline suggests the wedge is after the capture rather than the capture itself. Is that where the product's weight sits — annotation, sharing, the link you send someone — with the screenshot part being table stakes? If so I'd expect that to be the harder thing to get right anyway, since capture is a solved problem and handoff isn't.
That's exactly how I see it. Screenshot capture itself is mostly solved. I'm not trying to replace it with another capture button. The focus of Lumshot is everything that happens after the screenshot: explaining, collaborating, creating Jira issues, or sending it to AI tools with fewer steps. That's the workflow I'm trying to improve.
That's a cleaner position than competing on capture, and it's the half that's genuinely unsolved. Everyone can take the screenshot; almost nobody can get from the screenshot to a filed issue without three context switches.
The Jira path is the one I'd want to understand first. Filing an issue needs fields a screenshot can't know — project, component, priority, who it's assigned to. Does it ask, remember per project, or try to infer from what's in the image? Asking is honest but it's another form to fill in, which is exactly the friction you're removing. Inferring is faster and wrong sometimes, and a wrong-project ticket is arguably worse than no ticket.
Curious where you landed, because that decision probably defines whether this replaces the workflow or just shortens it.
The Jira integration is probably more valuable than the screenshot features themselves. Capturing an issue is easy; turning that capture into something actionable is where teams lose time.
The interesting direction is whether Lumshot becomes a communication workflow tool rather than just a capture tool.
I completely agree. That's exactly the direction I'm aiming for. The screenshot is just the starting point. We're also working on integrations with Trello, Linear, and other tools to make the workflow even smoother
That makes sense. I'm curious whether that direction came mainly from your original vision for Lumshot, or whether users were already trying to push screenshots into those workflows themselves.
About
Screenshots are one of the simplest ways we communicate, but the tools around them haven't evolved much. Lumshot was created to make capturing, explaining, and sharing ideas faster with a modern visual communication work
6 Comments
Windows is a crowded shelf for this — Snipping Tool ships free, ShareX is free and does nearly everything, and Lightshot has inertia. So the interesting question isn't features, it's which of those you're actually taking users from.
"Visual communication" in the tagline suggests the wedge is after the capture rather than the capture itself. Is that where the product's weight sits — annotation, sharing, the link you send someone — with the screenshot part being table stakes? If so I'd expect that to be the harder thing to get right anyway, since capture is a solved problem and handoff isn't.
That's exactly how I see it. Screenshot capture itself is mostly solved. I'm not trying to replace it with another capture button. The focus of Lumshot is everything that happens after the screenshot: explaining, collaborating, creating Jira issues, or sending it to AI tools with fewer steps. That's the workflow I'm trying to improve.
That's a cleaner position than competing on capture, and it's the half that's genuinely unsolved. Everyone can take the screenshot; almost nobody can get from the screenshot to a filed issue without three context switches.
The Jira path is the one I'd want to understand first. Filing an issue needs fields a screenshot can't know — project, component, priority, who it's assigned to. Does it ask, remember per project, or try to infer from what's in the image? Asking is honest but it's another form to fill in, which is exactly the friction you're removing. Inferring is faster and wrong sometimes, and a wrong-project ticket is arguably worse than no ticket.
Curious where you landed, because that decision probably defines whether this replaces the workflow or just shortens it.
The Jira integration is probably more valuable than the screenshot features themselves. Capturing an issue is easy; turning that capture into something actionable is where teams lose time.
The interesting direction is whether Lumshot becomes a communication workflow tool rather than just a capture tool.
I completely agree. That's exactly the direction I'm aiming for. The screenshot is just the starting point. We're also working on integrations with Trello, Linear, and other tools to make the workflow even smoother
That makes sense. I'm curious whether that direction came mainly from your original vision for Lumshot, or whether users were already trying to push screenshots into those workflows themselves.