PRC Liderança's main ERP · Print Schedule in development
PROCAP — Turning a complex operation into an operational platform
A platform to structure, configure, and follow capitalization-product operations end to end.
Campaigns that used to take weeks are assembled in hours, as the operation reports
PRCThe system
One operation, four layers.
-
Campaigns
- creation
- schedule
- products
- publishing
Decision: an operational sequence with steps and dependencies
-
Product
- configuration
- prizes
- documentation
- validation
Decision: rules that can be configured and reused
-
Operation
- prize draws
- printing
- distribution
- follow-up
Decision: configuration and operation in one continuous flow
-
Governance
- responsibilities
- states
- approvals
- traceability
Decision: responsibilities and changes that stay observable
Platform in use; screens are not published, for confidentiality, so the system is shown through its structure. Legal, actuarial, and architecture decisions belong to the specialist areas.
Context
PROCAP started from the need to structure the operation of capitalization products, originally tied to Tele Sena, and grew into the main ERP of Liderança Capitalização, which is also its market-intelligence tool. It covers a long chain: creating and configuring campaigns, product parameters, schedules, documentation, validations, prize draws, printing, distribution, and follow-up.
Problem
The complexity was not the number of screens. It was the number of rules, roles, dependencies, states, and areas inside one operation. The design challenge was to make that an understandable operational experience — different profiles working on the same process, without it becoming a pile of disconnected flows.
My role
Product Designer in structuring the experience: information architecture, flows, screens, components, and experience decisions — understanding the operation before drawing the interface. A multidisciplinary project with Product, Operations, Technology, and specialist areas at Liderança; legal, actuarial, and software-architecture rules are not design decisions. I have been on it since April 2026 (the project started in 2025). I use AI in discovery and in building prototypes: the AI is in my process, not in the product.
Decisions
Configuration and reuse instead of flows duplicated per product. Campaigns as an operational sequence, with steps and dependencies. Configuration and operation connected in one continuous flow. Responsibilities and changes observable along the process. On the Print Schedule (in development by the programming team): an automatic recommendation + a human operational decision.
Solution & artifacts
Screens and project details.
From a complex system to an understandable operation
PROCAP organizes a long operational chain on a single platform, using configuration, reuse, states, and assisted automation to reduce repetitive manual decisions.
- Configuration — configurable rules instead of duplicated flows.
- Orchestration — campaigns and products connected by steps and dependencies.
- Operational control — the automation recommends; people decide.
In progress
Print Schedule
- 01 Configuration
- 02 Planning
- 03 Production
- 04 Shipping
- 05 Receiving
The system takes into account
- The print shop's daily production capacity.
- The contractual deadline for Correios to receive the material before sales start.
- Commercial requests to bring a date forward.
- A configured logistics lead time.
- The real state of production.
UX decision
Automatic recommendation + a human operational decision.
Not a closed automation: the system calculates a recommendation, and the operator can approve, reorganize, change, justify exceptions, and replan.
What we discarded
Problem
The complexity was not the number of screens. It was the number of rules, roles, dependencies, states, and areas inside one operation. The design challenge was to make that an understandable operational experience — different profiles working on the same process, without it becoming a pile of disconnected flows.
Result reported by the operation
Campaigns that used to take weeks are now assembled in hours: the operator fills in structured information and PROCAP orchestrates the rest.
Tensions
- Flexibility × complexity
- Automation × human control
- Reuse × specificity
- Visibility × too much information
Impact
As the operation reports, campaigns that used to take weeks are now assembled in hours. The operator stops building and organizing documents by hand and starts filling in structured information; PROCAP orchestrates the rest. This is the operation's account, with no formal measurement published.
What I learned
In complex enterprise systems, a good experience does not remove the complexity of the business; it stops the user from having to carry all of that complexity.