It’s a young company, and unlike the big players, they still have real people in support who respond to you. They also try to adapt their solutions to my needs, which I appreciate. I like the fresh interface and the software’s fast responsiveness as well. Right now we’re trying to implement webhooks and the API, and if it works the same way, it should significantly reduce the time we spend on manual confirmation. Review collected by and hosted on G2.com.
I hate how their billing works. It would be much easier and more transparent if they charged per stop on the route (completed, or even not completed). Instead, they charge by “point,” which can include an uploaded stop, an API-transferred stop, and so on. That makes it impossible for me to calculate and predict what I’ll pay, and it also doesn’t give me any tools to restrict users from doing things I don’t want.
For example, an employee could upload 10 spreadsheets for one route instead of one, delete them, and then upload again. And you’ll be charged for every single row in each spreadsheet. I can’t control that, and I can’t manage it in any practical way. I would pay if the pricing were fair and measurable (for a started route, for a completed stop, or for a busy vehicle day), but not for something I can’t control.
I also don’t like the limited flexibility of fields. We have 15 different fields in every lead, but we only use 5 of them and don’t use the other 10. At the same time, we’d like to add a couple more fields, and that comes with an additional charge. I want the ability to remove and add different types of fields myself based on my business needs—like a second phone number, cu ft volume, or different types of notes (regular and high priority, where I’d like the high-priority notes to show in red). I don’t want to be limited like this and have to move to another plan just to get basic field customization.
Also, it doesn’t calculate commercial routes correctly. We work in New York City with 26 ft trucks, and it calculates routes for a small vehicle, including low bridges and tunnels. That’s the main reason we’re looking for other solutions. Review collected by and hosted on G2.com.
Hi Alexander, thank you for the feedback, the point about field flexibility is well taken, and it's something we're actively working to improve.
On billing: I do want to clear up a misconception. Uploading stops, including re-uploading spreadsheets, doesn't trigger a charge. You're only billed when a stop is first extracted after optimization. So, when a driver attempts it, it's exported, printed, or accessed via the API. So the scenario you described wouldn't result in charges just from uploading and deleting.
We bill this way because if someone were to optimize a route, export the data, then delete the route, they'd still be extracting the core value of the product, so we tie the charge to that moment of extraction rather than to the upload itself.
That said, it's clear this isn't communicated well enough in the product, and we're working on making it more transparent. We really do appreciate you taking the time to write a review, it helps us improve.
