So here it is: our new website. Fully equipped with a new name, logo, bright magenta and this blog. And I guess it was about time we did renew. This blog post is all about explaining why we decided to rebrand, how we went at it and of course a little about the result.
First things first: what was wrong with Devvers.work? Well, a couple of things actually. We came up with the name when we needed a domain name for testing environments and prototypes. We found .work to be sort of cool and after some trials noticed that devvers.work was still free. After that, the business started growing and we decided that Devvers.work would be our company name for now. As quick and dirty as the company name came to existence, so did our website. It was a simple modification of a free online template; okay-ish, but not good. And not updating the portfolio didn't make it any better.
So a while back we decided to redesign our website. The (by now) old one was not very good looking, outdated and in our opinion not very representative of us and our business. When we made that decision, we came up with the idea of rebranding entirely and decided to do so.
Devver is an abbreviation of developer, but only colleagues in our field of work are aware of that. We noticed that whenever we met new people, they wouldn't understand our name and even have difficulty pronouncing it. Hence, not a very good name that can easily be remembered, recognized or written down. Conclusion: time for a new, thought through, simple but sensible name.
So once we decided to rebrand, we had to actually come up with a better name. That proved to be more difficult than expected, if not because many domain names we're already taken. To start off, we made a list of keywords that we thought described us well, such as technology, solution, cooperation, collaboration, perspective, development and many more. We then gathered synonyms of these keywords and started looking for domain names. It took a while, but we eventually found evolution36.com to be free. A .com domain had our preference, to have the flexibility of growing our business internationally.
There were other options than Evolution36 of course. So why did we go with Evolution36? What's the meaning behind the name?
Our customers get to correct me if I'm wrong, but we like to believe that we bring something more to the table than just software technological skills. We always try to understand the root of the problem that the customer wants to solve, so that we can help them figure out the best solution. Sure, if a customer brings us a list of system requirements, we'd be happy to build the system. But not many customers do. They mostly have a rough idea of a solution and come to us for advice (and development of course). With the customers in-depth knowledge of the problem and our experience with user interaction, automation and software technology, together we can design the best solution.
So back to our name: regarding the above, that's what refers to the evolution. From a rough idea, to a prototype, to a solid product.
Oh, and the 36? Well, that's where Wybren and I started cooperating on a business and technological level: as two out of six of the 36th board members of study association Inter-Actief.
Let's say you have a company with an extensive labor process. You visit and evaluate public events. During the events you write down information and make notes. Afterwards, when you are back at the office, you enter the information into a computer. You have to do all the work twice, which is something that should not be necessary. Other people told you that an app might be the solution for this problem and you decide to contact a software developer. This is where we come in.
First of all we would love to know what you and your company do. We need to know how your process works. That way we get some feeling for the situation and it enables us to assess the situation and the problem. We listen to what solution you would like and where possible make suggestions to enhance the idea. After we have evaluated all the possibilities we do a proposal with what we think is the best possible solution for you. In our proposal we factor in all the aspects that affect the system. Who is going to work with the system: experts, employees, customers? What is the working environment? For example: a phone is small and harder to operate for elderly, while a laptop in most situations is too bulky to work with.
While working out the proposal we keep in mind the users in the system, the functionalities, the different pages or views and the usability. This proposal then forms our guideline for the development of the system. This does not mean that the proposal is necessarily the product we deliver.
During development we like to show you our progress and gather feedback. The frequency of these feedback meetings is up to you. We have an office where we can meet, but we could also come over to you. During the feedback sessions we show our progress since the last session and discuss what we do next. This gives the opportunity to evaluate the design and make changes where needed. As the product evolves, new insights are found, which could improve the product. This ensures that we can both be satisfied with and proud of the product we created together.
After we finished and delivered the product we take care of support and maintenance. In one of the next blogs you can read on how we approach this.