Merkandoo

Multiple projects progressing simultaneously, hours to be charged to each client, a workday that must be legally recorded, and a team split between the office and remote work. All of that has to happen somewhere, and it usually happens in three or four places: a task manager, a time tracking tool, a clock-in app, and a spreadsheet acting as the glue.

At Mecexis, we were in the same boat. For years, we tested every tool on the market, from corporate management systems to time and attendance apps, and none of them were a good fit: some imposed processes designed for other companies, others piled up features no one used, and all of them forced us to spread operations across systems that didn't communicate with each other. As a company that builds custom software for others, the conclusion was almost inevitable, and in 2026, we applied our own solution.

This is how Merkandoo was born, its name derived from "meerkat can do": meerkats work in colonies, coordinating naturally, with one always on guard while the others work. It's hard to find a better metaphor for a team with its projects, its schedules, and its shifts.

The problem wasn't a lack of tools, but their fragmentation. Every context switch took minutes, each piece of data was entered more than once, and information was scattered across disconnected systems. A management tool is opened dozens of times a day, and every second of loading time or every extra click is multiplied across the entire team throughout the year. The conclusion of those years of testing can be summed up in one sentence: management software that gets in the way ends up unused, and software that isn't used doesn't manage anything.

We wanted a platform that united the three fronts, responded instantly, was operated from the keyboard, and didn't require thinking about it.

Image: screenshot of a task detail with comments, notes, and history.

Merkandoo is built in the most demanding way possible: by using it. Every feature stems from a real need of the team, is tested in daily work, and is refined or discarded based on what usage demonstrates. There's no product committee or theoretical wish list; there's a team that manages its actual projects with the tool and immediately notices any friction.

And while the product is new, the engineering behind it is not: it boasts over a decade of experience from Mecexis building custom software for others. You can't create reliable software without a team that has years of experience doing it.

The results are evident in daily operations: all project management, time tracking, and daily schedules happen in a single place, without context switching or duplicate data. Daily tasks are stored in El Vigía, work hours are recorded as they occur, each client's hours are ready for billing, and any query about past events is answered with a search or a shortcut. The tool has become a permanent fixture, which was precisely the goal.

Merkandoo was born within Mecexis but its architecture is not tied to us: each organization operates on its own independent instance, with its users, projects and clients, which leaves it ready to serve other teams and to integrate into solutions that Mecexis builds to measure.

The roadmap points in that same direction: a file manager with Markdown support so that documentation lives alongside the work, a Kanban view to complement the lists, integrated chat, and collaboration spaces with clients and partners that will extend the platform beyond the team. Looking ahead, the billing, quoting, and services layer will complete the cycle already hinted at by the client-based time tracking view: from recorded work to invoice without leaving the tool. Everything will be integrated as it always has been, guided by actual usage and with a clear criterion: if it doesn't make the work faster or clearer, it won't be integrated.