Featured case study
Technology turnaround at TUVU
Took over an underperforming technology department, regained investor confidence, and built a team that ships weekly with zero critical bugs.
- Client
- TUVU
- Period
- 2023 – Present
- Role
- Director of Technology via Bonum Technologies, then Chief Technology Officer
- Where
- Spain & Texas, USA · fully remote team
- 2 → ~20team at peak
- ~$1.5Mannual budget
- 0critical bugs
- 30+communities
Context
TUVU is a venture-backed community social platform. I joined through Bonum Technologies with a specific brief: apply artificial intelligence, in the form of recommendation algorithms, prediction systems and market analysis.
It soon became clear that the problem was not a lack of AI. The technology department needed a full restructuring.
Challenge
- The platform was unstable.
- Users were leaving, acquisition was weak and conversion to paid was low.
- Investors had lost confidence and did not plan to renew their funding.
- Of the original team, only two developers remained: one backend, one frontend. Both were very capable.
My role
I presented a business proposal to the board, and the board put me in charge of a full restructuring, as Director of Technology at Bonum Technologies.
On July 1, 2026, TUVU hired me directly as Chief Technology Officer, with full responsibility for technology, budget, team, board reporting and compliance.
What I did
Diagnosis: from AS-IS to TO-BE
I started by understanding what existed. I collected the full Jira history and measured what had been built, what had been designed and where the product was heading. From that picture of the current state I defined the target state and wrote a two-year plan to stabilize the department.
First decisions
The first measures were decisive. I ended the contracts with the external design agency, which was not delivering, and with the offshore development vendor, which was introducing defects into the code. To close the most urgent gap, I brought in a senior designer with a long track record to deliver the designs that had been promised to investors.
The board
I then presented to the board: the real state of the department, its weak points (design above all), what the strategy and restructuring plan already covered, and the new design hire. Investors extended funding by a year and increased the capital allocated to the development team.
Building the team
With that funding I hired a backend and a frontend developer and promoted the two original developers to leads. The following year investors moved to ongoing funding, and I added two more frontend developers, prioritizing frontend because its impact was fast and visible to investors.
In 2025 I appointed two highly experienced leads to replace the original ones. The team was organized by area: frontend, backend, design and QA, each with its own lead. To control cost I chose a nearshore model, with leads in the U.S. (Texas and Florida) and talent across Latin America, all working remotely.
Process and reliability
We moved to weekly releases with Agile, CI/CD and code review. We launched the web app and native iOS and Android apps with several safety nets: automatic rollback on web releases, over-the-air fixes on mobile, and over-provisioned backend capacity.
Product, AI and compliance
Beyond the consumer product, we opened a new business vertical: communities. AI, the original reason I joined, entered the platform in 2025 through a hybrid content moderation architecture and AI-assisted development. I also took on compliance reviews for the platform and its international launches.
Money and accountability
I manage a technology budget of about $1.5M a year, covering people, software and systems, with fixed and variable costs. Every quarter I prepare the board’s financial reporting (overall spend, cost per user and profit), along with operational reporting on customer segmentation, demographics, acquisition, retention and conversion.
Results
- Funding: from investors not planning to renew, to a one-year extension and capital increase, then ongoing funding.
- Team: from 2 developers to ~20 people at peak (product, design, frontend, backend, QA) . Today the team is 14 and moves faster, thanks to AI-assisted development.
- Delivery: weekly releases, and critical bugs reduced to zero.
- Growth: a new communities vertical now serving 30+ communities (universities, ministries, churches, creators and collectives), several with international reach. Retention increased considerably and acquisition grew strongly, a result shared with marketing and sales.
- Compliance: GDPR compliance program in place, meeting WCAG accessibility criteria; launched in the UK, Australia, Japan and parts of Latin America.
- Role: what started as an engagement to apply AI ended with full responsibility for the company’s technology as CTO.
Technologies
- AWS (EKS, Lambda, S3, Glue, Athena, Rekognition, SNS, Amplify)
- Java
- Python
- MongoDB
- React
- React Native / Expo
- Cloudflare (Workers, livestreaming)
- GitHub Actions
- Grafana
- Sentry
- Mixpanel
- Metabase
- Stripe
- OpenAI
- Claude
- Cursor