Tulip
Node JS & Illustrator

Tulip has one vision. To present email and secuirty in a different way that delivers. By tracking email and secuirty meassures put in place by websites, it breaks the barriers of how email marketers and companies utilize your information when you sign-up at websites.

We decided to take our branding a different route from our original name "Trustinform". To accomplish this we needed a different form of ideation. A few other members collaborated on the name but also tell a story. They compared bamboo to a users personal information on the internet. Much like bamboo, it starts growing right where you plant it. A few years later, you have an extremely invasive crop that you are unable to control. By "Planting" the Tulip extension instead, the user is aware of the vunerabilities and message count they could potentiall receive. Proceeding with caution.

The product foundation before Tulip had enough data acquisition to give us a great start. We had demographics to plan an idea of the best "user groups" to target our idea to. Finding a way to get users to engage with the product in a useful way was critical to our success.

You can't just enter the extension market without a great idea and plan. Even then, to become a top-ten contender takes some simplicity and great design. Honey has the number one extension on the market for every browser platform. Looking at to their model was critical to adopt our own planning and ideas. During this thinking process we made the executive decison take our search function out of our website and focus only on the extension.

While working on designing the site with the brand change we really wanted to keep it simple. Explain the product, how it works, and why anyone can benefit from using it. I collaborated with my team, mocked up several variations of design, and developed the front-end look and feel that we were looking for.

We successfully landed our mark on the microsoft, firefox, and chrome extension stores.

Throughout the process we were constantly testing as well as having our stakeholders thinking extrinsically about how and why this works. They also added the thought process that covered every outcome of the extension from the users point of view. Initially we wanted to cover a way to score every possible site. Even if it didn't support the data we were trying to Track. We developed a feedeback loop in a more technical way to open up how we can deliver and even come up with new ideas.