![]() ![]() But it was the only way for Blueprint to get to where they wanted to go. We’re talking about a significant investment to build the thing you’ve already built. That’s a scary thing to hear if you’re a CEO. We knew we’d be spending as many resources in a year shoring up the infrastructure as scaling the platform, and only delaying the inevitable: rebuilding the whole thing from scratch. The rest would be painfully slow to implement or, worse yet, might not even work. When we looked at Blueprint’s 12-month roadmap, we predicted only about a third of the initiatives would be supported by the existing code base. This was definitely true for Blueprint, which had been designed and developed on a proprietary framework by a previous agency. Those quickly launched components might function fine individually, but rarely work as a cohesive system and are never very easy to maintain. ![]() It’s the right call, despite the consequences. Like a lot of start-up products, Blueprint had been built piece by piece with rapid growth in mind - when you’re getting traction, you build and build fast. Nevin Shetty, CEOĪn intimidating recommendation came early on: totally overhaul the platform’s infrastructure They’ll tell us how many developers it will take, and the cost. There hasn’t been a single thing we’ve asked of them that they said they couldn’t build, which is incredible. Both teams set out with a goal of long-term integration and mutual trust - and it’s paid off: in 2018, Blueprint was acquired by David’s Bridal, the largest wedding dress retailer in the world, and we’ve continued to collaborate on Blueprint and David Bridal’s full suite of wedding planning tools.īilberrry can build anything. This level of partnership was not built overnight, but began on day one. We became Blueprint’s tech team: we took ownership of every technology decision for the business, from designing the tech stack to collaborating on the feature road map to implementing upgrades, overhauls, and performance improvements. We got to work - and have been getting results together ever since. Our partnership mentality meant Nevin wouldn’t need to build out an internal tech team our agile work style meant we could start pushing code in a matter of weeks. After a discovery workshop to understand Blueprint’s goals and a perusal of the code base, we knew Bilberrry could have a huge impact on their success. ![]() So, we took on Nevin’s questions as our own. We know it can be lonely for a CEO to make these decisions without a true technical partner, just like it’s unsatisfying to be on a tech team that’s not invested in real business outcomes. These are big business questions - and precisely where we like to ground our conversations. What was an aggressive but reasonable timeline? Would he need to hire a tech team in-house? (They were.) He was also looking for an outsider’s perspective on how to scale the platform, enhance its feature set, and continue gaining ground on the competition. Our partnership began when Nevin Shetty, the innovative wedding registry’s CEO, called us to confirm that his instincts for where to drive the technology were right. ![]() We’re proud to say we’ve been deeply integrated as the technology arm of their business since 2016, when they were a young, seed-funded start-up rapidly gaining market traction. Blueprint Registry is one of our longest standing partners. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |