CalcMed: a technology team allocated to a critical medical application
At CalcMed, Fteam structured a fully allocated team involving frontend, backend, PO, technical leadership, and QA, plus code review, infrastructure, and architecture to support the evolution of a medical application with high availability requirements.
A tool designed for the urgency and emergency routine
CalcMed is an application that supports the medical routine, bringing together calculations and resources used in contexts such as urgent care, emergency, ICUs, and hospital wards.
In situations of this kind, the experience needs to be objective. The user cannot depend on excessively long flows or constant connectivity to access important functions.
The solution was built in Flutter with an offline-first approach, prioritizing speed, availability, and simplicity of use.
How do you sustain a product that needs to work when the context is critical?
Medical applications carry a different level of demand than products used occasionally. Performance, stability, and clarity directly influence the professional's experience.
The challenge was not limited to the frontend. It was necessary to maintain a complete product and engineering structure, with responsibilities distributed across development, quality, architecture, and infrastructure.
For that reason, the outsourcing model adopted was closer to a complete team than to an individual allocation.
A complete structure dedicated to the product
Fteam maintained a team fully allocated to the CalcMed context, with frontend and backend professionals, a Product Owner, a technology team lead, and QA.
The work also involved code review, infrastructure, and architecture, creating a layer of oversight that goes beyond feature development.
This setup allows product, quality, and technical decisions to move forward together, reducing dependency on isolated professionals.
How an allocated team can function as a product unit
Frontend and backend
Ability to work across the different layers required for the application's evolution.
Product Owner
Organization of priorities, context, and alignment of product demands.
Technical leadership
Architecture decisions, oversight, and direction for engineering.
QA
Quality integrated into the development cycle.
Code review, infrastructure, and architecture
Practices that help preserve continuity and technical quality throughout the product's evolution.
Technical continuity with distributed knowledge
The case demonstrates an outsourcing model in which Fteam does not just provide developers, but a multidisciplinary structure dedicated to the product.
The application also represents hands-on experience with Flutter and an offline-first strategy, connecting architecture decisions to the real-world use of healthcare professionals.
When outsourcing needs to be more than an individual allocation
Some products don't just need more hands to develop. They need a structure capable of continuously organizing product, quality, and technology.
In these cases, Fteam can build complete teams, with different skills working in a coordinated way and dedicated to the client's evolution.
When does a dedicated team make sense?
- When the company needs to continuously evolve a product but doesn't have the full structure in-house.
- When architecture, quality, and infrastructure decisions need to keep pace with development.
- When knowledge cannot be concentrated in a single person.
- When the roadmap requires a multidisciplinary team with clear responsibilities.
Related skills and solutions
This case connects mainly to the following Fteam areas:
Does your product need a complete team to keep evolving?
Fteam can structure a dedicated team with product, engineering, quality, and technical leadership tailored to your operation's context.