Verandr Philosophy

Prioritize third-party dependencies

Deal with third-parties early

The unfortunate reality when working with third-party vendors is that they miss deadlines, are slow to resolve issues and are not incentivized by milestones in the same way that we are. For this reason, we front-load all third-party dependencies as soon as we start building. This doesn’t mean building the entire feature, but instead:

  1. Asking for and receiving test and production credentials as early as possible

  2. Verifying integrations work as expected

  3. Validating proposed solutions with the vendor to ensure we are following best practices

This is something that’s saved us many times, and lets us avoid the scramble to troubleshoot upstream issues a week before go-live.

Understand vendor platforms

Off-the-shelf solutions are a great way to save implementation costs for the customer. It’s our responsibility to ensure:

  1. The customer is getting the full potential of the platform

  2. We aren’t doubling up on effort, creating functionality that already exists in another platform

  3. The platform is being used in the way it was intended

We’ve seen too many projects where developers have spent weeks duplicating functionality found in third party platforms that are already part of the project. At Verandr we value investing time to fully understand the platforms we integrate with so that we can save our customers time and money on implementation costs. Sometimes this means reading the documentation front-to-back. Other times it means a 2 hour workshop with a representative from the vendor themselves. Whatever it takes, we will ensure we fully understand what the platform does and how we should be using it.