Hacker News Reader

Happy to provide more details. We settled on our current pricing based on conversations with our early customers. For many of them, the alternative was to build something in-house, so they saw our pricing as pretty affordable when compared to the dev cost to build a custom solution.

That being said, we’re pretty early and still iterating on our pricing. If you’re up for it, we’d love to learn more about your use case.

View on HN

Sure. What questions do you have? I replied to another comment down below explaining why the pricing model is out of my reach, but I'll copy it here too:

>

I can definitely put down the $25/mo, but if I want to add two people who can help me out that jumps to $75/mo or $900/yr. I'm not at the stage where I can afford to hire employees yet (I'm the only one, and the drivers are contractors), so this would be a big expense for the company.

Thanks for sharing your perspective. I can see how per-user pricing doesn't scale well for you.

> What questions do you have? We're curious what specific flows you were interested in migrating over? Who performs this work today? How does it work end-to-end? What tools do you use to track the work? If you prefer to message me privately, my email address is nick <at> flowdash <dot> com.

Reply on news.ycombinator.com