[neill]

Some further feedback, not specific to your tool but because I've seen a few of these recently and would love to find a tool that meets my needs, it's maybe worth saying now-

When I see responses like this, instinctively my internal reaction is: "Okay, so they don't have this and say they're working on improvements, but I don't know how effectively they build new features or when this might be released. Will it be a week? A month? 6 months?"

I don't know the best solution, but having some more information to answer this would keep me more engaged with products that are being actively developed. I don't want to get bought in to something that iterates at a snails pace, but I could commit myself to trying tools that rapidly iterate and improve..

[jreinstra]

There's definitely something there - we've thought about this on the team too. Maybe publicly committing to ship features by certain dates?

[dchuk]

nah that's going to bring a lot of pain to your world.

Go read this book: https://www.amazon.com/Product-Roadmaps-Relaunched-Direction...

It's hands down the best approach to roadmapping out there.

The tl;dr:

Commit to Outcomes (future states of the world your product can create that don't exist today, and have meaning for your customers) without committing to solving for those Outcomes in any particular way.

So something like "It's easy for customers to get their data out of the product to feed into other applications" is an Outcome, and the Outputs can be all sorts of things: APIs, Direct Integrations to Other Apps, Excel exports, or just a dumb form for them to request the data and you have a SQL script you run to do it because it just doesn't happen enough to warrant the investment.