Frequently asked questions
Common questions about practice, scope and method.
If your question is not here, a conversation is more direct. Most real doubts depend on the specific context of the company.
22 questions
From the experience that underpins the work to how to start — plus common questions about scope, team, deliverables and monitoring.
Renato Paes Leme is an advertising professional and entrepreneur and has spent 21 years leading Arte com Pimenta, where he built experience in marketing, communication and management. Today's work connects that trajectory to the study and application of artificial intelligence, automation, data and systems. The 21 years are in marketing and entrepreneurship — not in technology consulting.
No. The trajectory comes from marketing, but the current work considers the connections between sales, service, processes and information. The company's problem is what defines the scope of the work — not a predefined sector.
No. The analysis may point to process simplification, integration between systems, conventional automation or the use of artificial intelligence. The choice depends on what solves the problem with less complexity and risk.
Renato leads the work, with the support of the core of artificial intelligence agents and the professionals involved according to the scope. The direction, the interpretation and the responsibility for the recommendations are his.
Yes. The members of the specialized core are artificial intelligence agents, identified on the Team page. They support research, organization of information and analyses, under human supervision — without replacing Renato's direction.
The initial conversation assesses the context and the fit between the problem and the work: it is not a contracted engagement. The diagnosis is a contracted engagement, with scope, deliverables and responsibilities defined in the proposal.
It depends on the engagement format. As examples, the diagnosis can deliver an executive reading, a bottleneck map and a recommended sequence; an implementation project can deliver the flow design, the solution defined in the scope and the validation criteria. The formats and the deliverables of each one are detailed on the Consulting page.
From a baseline, an indicator agreed before starting and a monitoring period defined in the scope. Reading the result also considers the interpretation limits — what the number does not explain.
Information shared during the work is handled with confidentiality and used only for the purposes of the project. When necessary, the relationship can be formalized through a specific confidentiality instrument.
Through the website's contact form or WhatsApp. From what you share about the context, we assess whether it makes sense to move on to a proposal.
Both dimensions are connected. The work begins with a strategic understanding of the problem and can advance to the architecture and the monitoring of the implementation. Technology must be technically viable and economically relevant.
I do not begin the work committed to a tool. The technology is chosen according to the problem, the existing systems, the risks, the budget, the team's capacity and the company's objectives.
Not necessarily. The need for technical participation depends on the solution, the existing systems and the complexity of the implementation. Even when there are vendors or technical teams, the participation of those responsible for the business is indispensable.
Yes. Starting with a well-defined opportunity can reduce risk, produce learning and create evidence before expanding the investment. Small, however, does not mean irrelevant: the initial project must be connected to a real problem.
Opportunities are assessed according to impact, effort, cost, risk, data availability, dependencies and implementation capacity. Priority must reflect the business, not enthusiasm for a technology.
In many cases, yes. Integrating the existing structure can produce more value than completely replacing the tools. Feasibility depends on the systems, APIs, permissions, data quality and business rules.
Security and governance are part of the architecture. The work considers the data used, access, permissions, records, approvals, supervision, exceptions and responsibilities.
That depends on the decision, the risk and the company's rules. Autonomy must be proportional to the impact of a possible failure. Sensitive actions need clear limits and, when necessary, human approval.
Yes. The work can include diagnosis, strategy, architecture, validation and monitoring of the implementation. The scope is defined according to the company's need.
When the solution requires a capability that cannot be adequately served by existing tools, custom development can be part of the implementation. It is a technical possibility, not the starting point.
The duration depends on the problem, the scope, the availability of information, the necessary integrations and the participation of the teams. A responsible timeline can only be defined after an initial understanding of the context.
The investment depends on the scope, the complexity, the level of monitoring and the necessary deliverables. The proposal is built after the initial conversation and the definition of the problem.