Custom Software Development for Fintech Software Co
- Custom Software Development
- $10,000 to $49,999
- June 2017 - Jan. 2020
- Quality
- 5.0
- Schedule
- 5.0
- Cost
- 5.0
- Willing to Refer
- 5.0
“Everything went really well especially if we look at the price we paid in the end.”
- IT Services
- Switzerland
- 51-200 Employees
- Phone Interview
- Verified
TDX Labs provided custom software development services for a fintech software company. Their team worked collaboratively with the partner to build a solution using Angular, MySQL, Node.js, and PHP.
The partner is happy with the results of the project and that the complex solution successfully works. TDX Labs executed through a scrum methodology and utilized multiple project management tools. They were creative, proactively coming up with their own ideas and suggestions.
A Clutch analyst personally interviewed this client over the phone. Below is an edited transcript.
BACKGROUND
Introduce your business and what you do there.
I’m the director of a fintech software company.
OPPORTUNITY / CHALLENGE
What challenge were you trying to address with TDX Labs?
We were developing software in the area of logistics for a large global chemical company. We had a process for TDX Labs and were looking for skilled people to help us with the project.
SOLUTION
What was the scope of their involvement?
TDX Labs provided custom software development services. We work in a scrum methodology on Angular development. Our frontend development is in Angular, and the backend is based on MySQL, Node.js, and PHP based on the Laravel framework.
We worked on the solution together with TDX Labs in 12 sprints. It was a little complex, but it was essentially about logistics in the chemical industry. The product is a multi-device solution which means that users can use it on a PC, but it also can be used on tablets.
TDX Labs supported us with the solution based on tablets based on the flow. They developed a lot of both the front- and backend as well as real-time communication. It is a real-time solution based on web sockets, and this was also a standard that was used by the TDX Labs team.
The requirements weren’t given in a traditional form so the model of this wasn’t based on requirements but is based on scrum. Scrum is based on user stories so we had user stories that were given to us. We didn’t have traditional requirements as there might be in other projects.
What is the team composition?
We primarily worked with three people most of the time.
How did you come to work with TDX Labs?
TDX Labs was a recommendation from one of our developers who is based in Pakistan as he had been in touch with them already. Initially, we were thinking about working with them on other things, but they were much faster than the other people we work with. Our team decided to involve them more and more in the project.
How much have you invested in them?
We invested between $30,000–$40,000.
What is the status of this engagement?
The project started in June 2017 and ended in January 2020.
RESULTS & FEEDBACK
What evidence can you share that demonstrates the impact of the engagement?
It was pretty important for us to finish the project on time, and it wasn’t as easy to deliver on time because the scope changed a little during the project. Many other companies had already failed to deliver the final result.
At that time, when we were working with real-time communication and web sockets, the technology wasn’t very stable and other large web companies had their own difficulties with the technology. We were very happy that it worked at all. We competed with other large tech companies and are very much a startup company.
The reason TDX Labs worked with us was that the large companies couldn’t deliver it in a good manner. Their solutions weren’t stable; one day it’d work but then it wouldn’t work another day. We made the solution more and more stable and that’s why I was very happy in the end.
The key performance metric was that we had enough time for the solution. During the first 12 months, we didn’t have one single incident in the production environment. Availability is very important for them. It wasn’t only the development of the solution but very much the stability of the production environment. There are a lot of web companies that do a lot of freaky things.
However, in the end, the solution doesn’t work well or it isn’t stable enough. The key performance metric was that we had a very stable production environment with TDX Labs. We also found the right tweaks in the setup of the components. We learned what models to use in the production environment, so it was stable.
The customer expected that the solution would work because in the logistics and daily work, there are about 100 trucks every day and each of those has dangerous goods and it is very regulated. Dangerous goods are much more complex than other goods, and it was quite a challenge. It wasn’t a fun project, and it was and still is a mission-critical software for their process. For example, if the software doesn’t work, no truck will leave the building. They make more than a million a day with outgoing goods, so it’s very important that the logistics process is very smooth and fast.
The solution is still running today so I’m pretty happy that we could work with TDX Labs. We’ve also discussed working with them again on new things that we have with our customers to develop other sites as well. This was specifically for a solution that was specializing in one process for one of their sites, but now we have seven sites for that company. The solution is running so we also have new work for them.
How did TDX Labs perform from a project management standpoint?
We worked with Kanban metrics based on Trello. Later on, we used Azure DevOps for the boards to maintain the sprints. We mostly communicated through Skype. We didn’t send more than five emails to each other. It’s always important to work live, and Skype was even better than Teams at that time.
For me, it was always a good experience. It’s sometimes difficult to work with developers because they tend to underestimate or overestimate their own skills. However, I wouldn’t say that TDX Labs did worse than others when it came to estimating the efforts. As one can imagine, the solution wasn’t something that everyone can do. We also realized that if we bring more people to the process, that didn’t necessarily translate to success.
For example, sometimes there were 10 developers on the team, but the solution wasn’t better so we decided to work with a small core team and had better people and good communication within the team. I think everything went really well especially if we look at the price we paid in the end. If I had to source in Switzerland or Germany, I’d easily pay 2–3 times more for the same work.
What did you find most impressive about them?
Because we didn’t have traditional requirements, we needed people to have their own ideas when it came to solving the problem. Usually, if we work with offshore companies, people are very good at asking questions about requirements. But if we then develop a solution, they aren’t that creative. I needed people to really understand what the problem was and to then come up with their own idea which had to be brilliant and simple.
The reason we continued with TDX Labs was that Ahmer (CEO) was such a creative person. We would explain something, and he understood it. But then, he’d come with his own ideas and suggestions. That of course is a very good motivation for the team. He’s someone who really brings his own ideas to the project and that’s the most outstanding point.
Are there any areas they could improve?
Through my past work, I found that the more genius people you work with, the more difficult it gets. What wasn’t as easy with TDX Labs was the constant quality but that’s the case with every developer. We have good days and days that aren't as good. I’m always challenging the people I work with but if I could wish for something, it’d be that the best days would be every day. Generally, nothing bad comes to my mind, otherwise, I wouldn’t be a reference for their company.
Do you have any advice for potential customers?
Because we didn’t have much in terms of requirements, it’d be nice if you have a project that’s not finalized by every single detail. Their company is a good choice if you’re still in the process of improving ideas or developing something. If you are only out to find someone that can do your website that is designed from A to Z, they might not be the right company for you.
RATINGS
-
Quality
5.0Service & Deliverables
-
Schedule
5.0On time / deadlines
-
Cost
5.0Value / within estimates
-
Willing to Refer
5.0NPS