In Brazil, companies that want to sell products or services to public institutions often participate in a process called licitação. In simple terms, it is a public procurement procedure through which government bodies select suppliers, evaluate proposals, and formalize contracts under legal and transparency requirements.

For many companies, participating in these public bids is a strategic opportunity. But it is also a demanding operation. Each notice has its own rules, deadlines, documents, technical requirements, approval stages, and risks. Missing one document or misunderstanding one step can mean losing an entire opportunity.

In a project conducted for a company that participated in public tenders, one point became clear very early: the main challenge was not only the lack of a tool. Before that, there was a lack of clarity about the process itself.

The company needed to monitor tender notices, analyze requirements, gather documents, control deadlines, validate proposals, assign responsibilities, and make sure no critical step was missed. In practice, however, part of this control was managed through spreadsheets, part through messages, part through people's memory, and part through disconnected systems.

Before proposing any solution, it was necessary to map the process. Not as a formality. As the central part of the work.

When the workflow was mapped, issues that were not obvious at first became visible: repeated tasks, approvals without a clearly defined owner, documents requested at different moments, deadlines tracked manually, and steps that depended on a single person to move forward. In public procurement, that kind of fragility is not just operational. It can directly affect the company's ability to compete.

The map is not bureaucracy

Mapping a process does not mean creating a beautiful flowchart to be filed away. It means making visible how the operation actually works.

And it does not need to start in a complex way. A company does not need to master every symbol used in formal flowchart notation or adopt a heavy methodology that only specialists understand. Often, the first step is simple: open a visual tool and organize the stages as they really happen.

With intuitive platforms such as Miro, it is already possible to bring the team together, draw the operational path, connect responsibilities, identify bottlenecks, and see where information gets lost. The goal is not to create the perfect diagram. The goal is to start.

In the case of the company that worked with public tenders, mapping the workflow made it possible to understand the entire journey: from the arrival of a tender notice to the decision of whether or not to participate, including technical analysis, document collection, proposal preparation, internal approvals, and final submission.

Each step needed clarity: who does it, when it must be done, which information is required, and what risks appear if something is delayed.

That was when the improvement began to take shape. Not from a generic list of features, but from the real routine of the company.

Law 14.133 and the new demands of public procurement

Brazil's Law 14.133/2021, known as the new Public Procurement and Administrative Contracts Law, changed the way public procurement must be planned, managed, and made transparent. Since 2024, it has become the main legal framework for public procurement in Brazil, replacing previous rules such as Law 8.666/1993.

For the public sector, this transition brought important challenges: more emphasis on planning, risk analysis, transparency, digital records, standardized procedures, and stronger governance throughout the procurement cycle.

For companies, however, these changes should not be seen only as obstacles. They are also an opportunity.

A more structured public procurement environment rewards companies that know their own processes, keep documents organized, monitor deadlines carefully, understand legal and technical requirements, and respond with consistency. In other words, companies that treat public tenders as a managed process, not as a last-minute race.

Automating a poor process only makes the problem faster.

If the workflow is not clear, any tool will simply organize the confusion into a better-looking screen. And that does not solve the problem. It only creates the appearance of control.

The order matters

The conventional sequence is usually this: identify a pain point, choose a tool, and only later discover that the process was not well defined. The Arxon Protocol proposes the opposite path.

First, the process is understood. Then, it is adjusted. Only after that are the methodologies, tools, and solutions defined.

In practice, process mapping answers essential questions before any implementation:

In the public tender project, this understanding made it possible to structure a safer workflow, with well-defined stages, clear responsibilities, deadline control, organized documentation, and visibility over the status of each opportunity.

The result was not just the implementation of a methodology. It was a more organized, predictable operation, less dependent on individual memory and informal communication.

More than delivering a tool, Arxon seeks to understand how each company actually works, identify its critical points, and propose solutions aligned with the real needs of the operation. Because a good solution is not born from technology alone. It is born from a deep understanding of the process it must support.

References: Law 14.133/2021 (Planalto); New Procurement Law (Federal Government); Federal Government Procurement Portal.