Constructor.io

What do you like best?

The two things I liked best about Constructor were how easy they are to work with, and how dedicated they were around delivering on the KPIs they promised.

On the integration itself, they synced with us regularly, and there wasn't ever a time where a solutions architect wasn't available. Even though some of the team was in a different time zone, they made themselves available during EST hours. We had pairing sessions often, and generally felt like Constructor was invested in our success. I don't think there were ever any major roadblocks during the integration, and all questions were addressed promptly by the Constructor team. We established our goals early across all involved parties. This contributed massively to the smooth nature of the integration.

For the KPIs, they told us which features have previously boosted revenue for other clients. It was both surprising and incredibly heartening to see the concern they had for our success even after the integration was complete. We worked with Constructor to test and evaluate the new features provided by their client, and saw our revenue go up in an a/b test more than Constructor told us to expect.

Finally, Constructor's documentation was amazing. We've worked on many integrations in the past with sub-par/no documentation, and it's never fun. We had no problems with spinning up a quick POC before the main integration, and going step by step through the API documentation was a breeze.

What do you dislike?

Not a whole lot. It was one of the smoothest integrations I've ever been part of, and Constructor delivered.

Recommendations to others considering the product:

Ask them to go through their proof schedule and business case. I'm not sure if they offer it to everyone, but it was really valuable to us to get an idea of what the revenue lift with Constructor would look like before we needed to sign anything.

What problems are you solving with the product? What benefits have you realized?

Before Constructor, search wasn't used very much because it had to be keyword matched, which sacrificed the result quality. Constructor's personalized search was a complete hit right off the bat. There was a massive lift right away.

In-cart recommendations and zero-search-result pages were not dynamic prior to the integration. We were initially worried that if we changed these results, sales would go down -- but quite the opposite happened. Once we implemented Constructor's recommendations, AOV dramatically increased. Our zero-search-results rate has also dropped significantly -- before Constructor, zero-result searches happened all the time. Now it's pretty hard to hit a zero-results page.

We initially started with Constructor's autosuggest service, but after seeing the value the product provides to our team, the whole product discovery experience is now powered by them. Overall, Constructor's product has been successful not only in making the engineering team members' lives easier, but also in increasing the KPIs that matter to us most.