Build What comes next
You bring the idea. We design and build your product, then put it into production.
Bring what you have. We build what comes next.
Who builds it, and how
- 2022 · Founded
- Gabriel and Caio start Innovarts in 2022 to design and build software products, new ones and the ones companies already run on.
- Rule 01 · The user comes first
- We start from what the people using it need to get done. Features come after.
- Rule 02 · UX starts with the workflow
- You approve the flow before we write the code, and the flow you approve is the one that ships.
- Rule 03 · Nothing stops while we build
- What you already run keeps working while the new product takes over, one piece at a time.
- Rule 04 · Infrastructure is in the brief
- We plan hosting and deployment with the rest of the product, not after launch.
- Rule 05 · AI goes to production
- Agents go through the same tests as the rest of the code, and a person reviews what they do.
- Today · Building for clients and for ourselves
- Web, mobile and desktop products for companies, from the approved flow to the infrastructure they run on. And our own products, built under the same rules: fitness, personal finance and tools for the desktop.
- What we want
- To be the team you call when it's time to build what comes next.
Everything your product needs to exist
Strategy: A plan before any code.
We map what you want to build and what you already run, then decide what ships first and what can wait. Before design starts you have a written scope, a roadmap with milestones and the first release defined.
- A written scope
- A roadmap with milestones
- The first release, defined
Product and UX: Screens designed from the work people do.
We design the flow from the tasks your users need to complete. You click through a prototype before a line of product code exists, and the screens come with a design system the product grows on.
- Flows you approve before code
- A clickable prototype
- A design system the product grows on
Engineering: Built for the busiest day.
We write the product and the API behind it for the day volume peaks: heavy reads cached, each integration capped, bulk queries tuned, tests covering what matters. Web, mobile and desktop, from the same team, on the same API.
- Web, mobile and desktop apps
- An API that holds under load
- Tests that cover the product
Infrastructure: Environments your team can rebuild from code.
Your team can rebuild any environment from code, repeat a deploy and roll one back. We write hosting, release steps and monitoring as code alongside the product, so the infrastructure grows with it.
- Deploys your team can repeat
- Infrastructure written as code
- Monitoring from the first day
AI: Agents that reach production.
We connect agents to the data and the tasks your team already works with, put them through the same tests as the rest of the code, and keep a person reviewing what they do.
- Agents on your own data
- Tests and human review
- AI features inside the product
Solid ground
A field team needed to keep working on low-end phones, even when the signal dropped. We designed and built the entire app for that.
Field logistics platform
A logistics operation that runs in the field: routes, customer portfolios, people on the street with modest phones and often no signal. We designed and built the entire app for those conditions, from the screens to the API behind them.
When the signal drops, visits still need to be recorded. The app also has to share limited battery and mobile data with the rest of the field team's day.
We designed for the team's least capable phones. The app stores each record on the device and syncs it when connectivity returns, caches what it reads, and tunes geolocation to limit battery use.
What it accomplished
- The app keeps working with no signal and syncs on its own when the network returns.
- It runs on the low-end phones the field team already carries.
- The office sees route updates whenever the phone has a connection.
- Several client apps share one API, so changes to shared backend logic can be made in one place.
Our products
- Fiteco
- A fitness app that connects people who train with personal trainers and nutritionists, in Portuguese and English. Workouts, diets, a health questionnaire, a social feed, direct messages and a marketplace where professionals sell their plans.
- Planance
- A personal finance manager for people who want every entry to match their bank statement. It imports exports from Brazilian and foreign banks, checks each line against the source file and runs on the phone and on the desktop.
- Moleui
- A desktop app that keeps a computer clean: it clears what is no longer needed, uninstalls applications completely, shows what fills the disk and watches the machine. A graphical interface and repository management over an open-source engine.
- Plico
- A desktop workspace that brings email, calendar, tasks and notes into one window, with an AI assistant for the inbox and for code. For people who run their day and their work from the same place.
We have also built for
- Zeta Dados
- Socium
- Stage Consulting
- Materiapp
- Solvpro
- Bella Capri
- Social Sync
Who designs and builds your product
Gabriel leads product, UX and frontend. Caio leads engineering, architecture and infrastructure.
Gabriel Souza
Co-founder · product, UX and frontend
I handle product, UX and frontend at Innovarts. I design the flow and write the frontend, so what you approve is what ships.
Caio Lima
Co-founder · engineering, architecture and infrastructure
I handle engineering, system architecture and infrastructure at Innovarts. My work includes automation and DevOps.
Gabriel and Caio are accountable for your product, during the build and after launch.
A proposal sets scope, milestones, billing and review cadence.
Post-launch support is scoped in the same proposal: availability, responsibilities and who answers when something needs attention.
Tell us what you want to build.
A new product, or the next version of one you already run. We work from São Paulo, in English and Portuguese, with companies anywhere.
Talk
São Paulo, Brazil