Fixing Slow IoT Reports Without a Rebuild

Ibisa had spent five years building an IoT platform out of Bogota, Colombia, when its biggest standing user complaint became speed. Database queries behind logging and reporting were slow enough to be a real product problem, the kind that surfaces in every customer conversation.

The team, then 11 to 50 people, needed the queries fast without rebuilding the platform around them. The ask was to fix the two slowest features, not to start over on the whole system.

Two Leanware engineers joined the engagement and worked directly inside Ibisa's existing software architecture and the query paths behind logging and reporting. Rather than adding hardware to mask the slowdown, the team restructured how the database handled the reads and writes those two features depended on, tracing the slowness back to how the queries themselves were built.

The engagement ran on Jira and standard scrum ceremonies alongside Ibisa's in-house team, which kept the database query optimization work integrated with the platform's existing roadmap instead of treated as a separate track. The scope stayed in the $10,000 to $49,999 range, in line with a focused fix rather than a platform-wide project. That scope is itself part of the proof: fixing an IoT platform's data management bottleneck does not have to mean paying for a rewrite.

Database logging tasks that took five minutes came down to 20 seconds. Report speed, the platform's largest standing complaint, improved to the point that Ibisa came back to scope additional projects rather than start over with a different team.

Ibisa's own review of the engagement credits the team with focusing on what users were actually facing rather than the technology for its own sake, and rates the work highly across every category. For a team that fixed the problem without rebuilding the platform, that return engagement is itself the clearest evidence the fix held.