Decisions with ownership
Process and quality decisions gain named owners, explicit review points, and evidence that can be challenged rather than inferred.
Process Excellence & Automation Lead · Product Builder
I turn complex operations into scalable systems.
I’m Leandro Costa. I lead process excellence, quality, and automation in financial services, and I build products through Evorigo. My work starts with the operating problem: who owns it, how decisions are made, where evidence is missing, and how process, data, and software can improve the system without making it harder to run.
I lead the operating change, then stay close enough to the build to make it real.
From operating decisions to working systems.
Strategy, process, and technology belong in the same conversation. I clarify the operating problem, establish who decides and who owns the outcome, and define the evidence and controls the work needs. From there, I help select and build the right response, whether that means governance, process redesign, automation, data, an API, or a product.
What changes in the operating model
A useful transformation leaves the organization with a clearer way to decide, deliver, measure, and improve the work after the initial project ends.
Automation as a portfolio
Demand is assessed by value, risk, stability, support, and architecture instead of entering an undifferentiated queue of scripts.
Builder accountability
Product decisions remain connected from problem framing through architecture, implementation, release, and the operating consequences that follow.
The same operating discipline at three levels.
These cases cover process governance, automation portfolio management, and product building through Evorigo. Corporate details remain anonymized, while the decisions, constraints, and operating methods are described in enough depth to be evaluated.
View all workProcess excellence governance
A management system that gives process ownership, quality standards, improvement demand, and leadership decisions a shared operating cadence in a complex environment.
- Process governance
- Quality
- Leadership
- Data
Automation portfolio
A portfolio model for deciding when automation is justified, choosing the right intervention, and carrying ownership from discovery through support and retirement.
- Automation
- Prioritization
- Architecture
- Governance
Evorigo product building
A founder-led product practice that carries one decision loop from problem framing and scope through architecture, implementation, platform readiness, and release.
- Product
- Engineering
- Architecture
- Platform
Built from the operation outward
My path has grown from studying how work moves to leading the standards, decision systems, automation direction, and cross-functional delivery that shape it. Product building adds another layer: direct responsibility for turning a decision into architecture and working software.
View experienceCurrent
Process & Quality Coordinator
Financial services institution
Leads process excellence, quality, governance, and automation direction. Turns transformation priorities into clear ownership, decision routines, standards, and delivery across functions.
- Process and quality governance
- Automation portfolio direction
- Cross-functional leadership
- Data-informed operating decisions
Independent venture
Founder & Product Builder
Evorigo
Defines product scope and technical decisions, with direct involvement in architecture, software development, infrastructure, security, observability, and release readiness.
- Product discovery and decision-making
- End-to-end technical architecture
- Software and platform delivery
- Security and operational readiness
Technical range with an operating purpose
I use technology to change a specific operating condition: reduce manual coordination, improve decision quality, make a control observable, create a reliable service, or give a product room to scale. The technical foundation follows the problem, the risk, and the capability available to operate it.
Process & Automation
Make work and ownership visible, establish decision and review routines, then automate only where process stability, risk, and support make the operating case sound.
- BPMN
- SoftExpert SESuite
- UiPath
- Microsoft Power Platform
- Workflow Automation
- Process Governance
Data & Intelligence
Structure operational evidence so leaders and systems can use it for decisions, monitoring, reliable services, and analysis that changes what happens next.
- Python
- PostgreSQL
- Redis
- Power BI
- Data Analysis
- AI
Product Engineering
Carry a product decision into consistent mobile, web, service, and API implementation without losing the user need, operating constraint, or release boundary that justified it.
- Flutter
- Dart
- TypeScript
- NestJS
- Django
- APIs
Platform & Delivery
Build delivery environments that are repeatable, observable, recoverable, and proportionate to the product risk, team capability, and support commitment.
- Docker
- Cloudflare
- CI/CD
- Linux
- Observability
- Cloud Storage
Architecture & Security
Define trust boundaries, authentication, data flows, failure behavior, abuse controls, and resilience mechanisms while architecture is still being shaped.
- Authentication
- API Security
- Queues
- Caching
- Rate Limiting
- Infrastructure Design
Founder & Product Builder at Evorigo
At Evorigo, I take direct responsibility for product decisions. I define the problem worth solving, narrow the scope, choose the architecture, contribute to implementation, and account for security, infrastructure, observability, and release. Each initiative is described according to its actual maturity, with the reasoning behind its decisions open to evaluation.
Visit EvorigoEV
Define the user, operating problem, and evidence needed for the next decision before selecting the technical foundation.
Make product, architecture, security, cost, and delivery trade-offs visible while they can still be changed.
State clearly whether an initiative is a concept, prototype, active development effort, or production system.
Working notes on decisions that survive delivery
My writing examines the decisions that determine whether transformation lasts after launch: ownership, prioritization, exception handling, adoption, architecture, support, and the discipline to change course when the evidence does not support the original plan.
InsightsTransformation as an operating system
How ownership, decision rights, management cadence, evidence, and feedback loops turn isolated improvement projects into a capability the organization can operate repeatedly.
Automation portfolio design
How to evaluate process stability, value, risk, data quality, dependencies, maintainability, support, and adoption before deciding whether automation is the right intervention.
Product judgment for internal systems
How product decisions improve tools for operations and regulated environments by clarifying users, constraints, outcomes, release boundaries, and the evidence needed for the next iteration.
Complex challenges need an operating model that works across functions.
A useful first conversation starts with the real context: what is failing, who owns the consequence, which constraints matter, and what decision needs attention.