Tide (Tide Platform Limited) is a UK fintech company that provides digital-first banking services for SMEs.
- Bring the talent and skills necessary to smoothly deliver the domain-driven design project.
- Manage and implement the company-wide integration of Retool.
Tide partnered with amarti initially to work on a domain-driven design for back-end engineering.
Amardeep Sirha, our Head of Delivery and Co-founder, worked closely with Tide’s Head of Engineering – Rafael Tedín Álvarez – and together with an assembled team, they set out to complete Tide’s vision for the delivery of domain-driven design for back-end engineering.
Phase 2 - Retool
Once the domain driven design project was completed, amarti was asked to stay on to help with the smooth integration, implementation, and management of Retool software into Tide.
Retool is an interface that can be connected to data sources within your organisation. Retool allows organisations to service, read and write data whilst building and reusing components and is specifically designed to manage any back office operations.
Tide looked to move to Retool as their back-office system was no longer fit for purpose from a security and scalability point of view. With a scaling vision for the future Tide needed a system that would optimise its growth, members, and agents.
Amardeep continued on as Programme Manager during this project. We brought in amarti engineers to help smooth and optimise the transition from the back office system to Retool applications.
Part 1 - Learning Retool
The entire team needed to learn Retool workings and capabilities, as for the majority of the team this new SaaS company was unknown.
Once the education of Retools’ purpose and functions was completed on a company-wide scale, the roadmap became clearer, along with any additional pieces to be put in place.
Part 2 - Laying The Foundation For The Retool App Builds
The next step before setting off building the Retool applications was that the team needed to establish whether Tides architecture was suitable for the build.
Retool necessitates an API-first architecture, and Tide was in fact working towards their API-first architecture. However, the APIs were not ready at that stage for Retool.
Part 3 - New Governance Implemented
It wasn’t as simple as just plugging in the new product – new governance needed to be put into place and ways of working needed to be amended to facilitate the build.
As Retool needed to be implemented as quickly as possible, and because it required an API-first approach, the new governance allowed users to hit the database directly in accordance with the right information security rules.
All in all our team has completed a successful rollout, trained engineers, built Retool applications themselves, changed processes, and made it possible for anyone at Tide to utilise and benefit from Retool.
Another successful project completed!
Looking for help with your next digital transformation? Give us a call, or send us a message through our ‘Let’s Talk’ page.