1 pointby alance15 days ago2 comments
  • jerryjobrien10 days ago
    130 installs a year with ~5–15% converting and basically no churn is solid for a dev tool. That tells me the product works and people who use it get it. This feels much more like a “wrong eyeballs” problem than a product or pricing problem.

    A couple thoughts that might help:

    You might be aiming too broadly at “developers.” The people who really feel this pain are usually platform / infra / DevOps leads — especially teams sharing staging, CI runners, GPUs, test environments, etc. They’re the ones dealing with collisions weekly.

    The value isn’t “resource coordination,” it’s avoiding the mess: overwritten envs, broken deploys, Slack arguments about who touched what. That framing tends to spread internally way faster.

    Ads are tough here. Most of these tools grow by internal forwarding (“hey, we should use this”) rather than clicks. Communities, word-of-mouth, and very specific infra-heavy teams usually work better.

    If it helps, I’m happy to chat or give feedback from the platform/infra angle. If you’ve ever had two people step on the same environment and cause chaos, you’re exactly who I’d like to talk to — feel free to reply here or DM me.

  • Jeremy102615 days ago
    Does your free tier do too much making upgrading to a paid plan not worth it?
    • alance15 days ago
      Good question. So one change I made last year was to cap the number of queues the free account could utilize. It's sort of hard to know for certain if that was what moved the needle though.

      There has been a suggestion that maybe the free plan could just be a time-limited trial instead.

      But it feels like there is some risk associated with that - as often a customer will use the free plan for (eg) six months, before hitting the limits and becoming a paid account.