Please introduce your company and give a brief about your role within the company?
Cleverti provides nearshore software development and QA & Testing. We offer scalable solutions to help our clients deliver top-quality, affordable software, relying on talented IT professionals, a comprehensive technology stack and flexible engagement models. We have implemented well-structured processes to work with high levels of trust and quality, including an own methodology: Cleverti Care. As the CEO of Cleverti, I contribute to outline the company's long-term strategy, drive coordination and keep all business areas focused and aligned with our goals.
What was the idea behind starting this organization?
Cleverti started in 2010, at that time we were practically pioneers in exporting technology services from Portugal. I decided to start Cleverti because my professional background was linked to Nordic countries (Norway, Sweden & Denmark) and, from that experience, I knew there was a lot of potential in Portuguese engineering to help Nordic companies in developing their software applications using resources with the same skillset and a more affordable cost.
Until the end of 2013, we worked exclusively with Nordic companies. Currently, we have a strong reference base, with clients in 14 countries in Europe and the United States.
What are your company’s business model–in house team or third party vendors/ outsourcing?
We provide our services via dedicated teams employed by Cleverti, that work from our offices in Lisbon. With this business model, we feel that we can assure a stable and reliable output for our clients.
How is your business model beneficial from a value addition perspective to the clients compared to other companies' models?
Every client is a different client, and for us this is a core value. Last year, we developed our own methodology - Cleverti Care- designed to drive long-term engagements with our clients. This allows a thorough monitoring of each client throughout their journey with Cleverti. Many clients we have at the moment, came to Cleverti very frustrated after previous bad experiences with other vendors, and ended up establishing long-term teams with us, that are producing the expected outcome.
What industries do you generally cater to? Are your customers repetitive? If yes, what ratio of clients has been repetitive to you?
We work with a lot of Industries, namely Financial, Retail, Logistics & Online Services. The majority of our clients started with a small team and ended up extending it, as they keep checking the positive results of the partnership and gain more trust in its success. That is a pattern we keep verifying and feel very good about.
How much effort in terms of time goes into testing the front end and back end of an application & website?
A software solution, regardless of being a very complex application, or a simple website, usually has a common roadmap for testing. We usually split it in essentially 3 phases:
1. Functionality & Usability (30%)
2. Interface & Compatibility (40%)
3. Performance & Security. (30%)
Of course this is dependent on client requirements and also on projects specifications, but it is a reference that we have applied in several Testing Projects.
Agile Testing or Waterfall Testing. Which testing model do you prefer?
Generally we tend to prefer Agile Methodologies because they simplify the interactions between teams, breaking barriers (essentially between developers / testers).
It also allows and facilitates a more pragmatic approach, with test driven development, and practises like continuous integration (CI).
Please list some factors which are important while testing a product or service.
One of the main concerns we have while performing tests on a service or product, is the availability for change and improvement, which is linked to the organization’s maturity and structure. If a company is less flexible, we’ll have to adapt our practices to work according to their request.
Another important factor is identifiying areas within the organization where tool support will help to improve testing processes.
We also spend a considerable amount of time studying and evaluating what would be the best tools for the specifications and requirements given.
What kind of payment structure do you follow to bill your clients? Is it Pay per Feature, Fixed Cost, Pay per Milestone (could be in phases, months, versions etc.)
We usually work with long-term dedicated teams with our clients. This means our team works as an extension of client’s in-house team. With this model, we usually apply a flat rate, billed monthly.
Do you take in projects which meet your basic budget requirement? If yes, what is the minimum requirement? If no, on what minimum budget you have worked for?
Usually we only start a new partnership / engagement in case there is budget for at least 1 person working full-time. That applies not only for the testing team, but also for the development. Exceptions apply for the most common technologies where we may have some rotation between projects.
What is the price range (min and max) of the projects that you catered to in 2019?
The average monthly price in 2019 regarding a testing team was €5034. Please note that our clients are usually part of the team setup process, providing their validation and approval. It is possible to have less or more expensive team members based on their experience.