A practical starting point for evaluating collaboration.
If you are introducing me to management, recruitment or a technical team, this page brings together a summary, my CV and three cases with explicit scope. Share this page or download the documents.
Senior Power Platform consultant and React developer. I connect processes, applications and data, with attention to integrations, validation and human oversight. Founder of Optimatiza.
Areas of collaboration
Power Apps, Power Automate, Dataverse and Power BI.
React applications, APIs and system integration.
Document automation and scoped AI workflows.
Working arrangements
Senior support for teams and consulting firms.
Projects with agreed deliverables and acceptance criteria.
Fully remote roles, discussed directly.
Three cases to review
RELOJSynthetic browser demo: data freshness and publication policies. Public code.
Oficina VivaOwn project: assignment, states and task review using AI roles.
Capturista DigitalOwn prototype: invoice extraction and XLSX entry. Demo with explicit limitations.
These are own projects and demonstrations. Their evidence describes the behaviour and limitations of each implementation; it does not establish client outcomes.
Remote coordination
San Salvador, El Salvador (UTC−6). For Spain and other countries, overlap, time commitment and channels are agreed before work starts. Spanish; basic English for reading technical documentation.
Starting agreements
Scope, responsibilities, system access, confidentiality, acceptance criteria and handover. Time commitment, start date and commercial terms are confirmed for each engagement.
Evidence with technical context
Each case explains the represented problem, implementation decisions, what can be checked and what is outside its scope. Videos and demos are labelled according to their nature.
SYNTHETIC DEMO
RELOJ
Four-source data consolidation: freshness, validation and publication policies. Public JavaScript engine and a reproducible walkthrough.
Task assignment and review using AI roles, states and operational events. The case distinguishes the implementation, a historical trial and an edited video.
These are own projects and demonstrations. Their evidence describes the behaviour and limitations of each implementation; it does not establish client outcomes.
Understand the process. Goal, people, available systems, data, constraints and the problem to solve.
Define the delivery. Responsibilities, access, deliverables, tests and acceptance criteria before agreeing the scope.
Build and check. Review progress and technical decisions, validate agreed scenarios and manage changes.
Hand over and plan continuity. Documentation, delivery of artifacts and a support or evolution agreement appropriate to the engagement.
What to agree before an engagement
Responsibility and time commitment
Who prioritises, what each party owns, how progress is reviewed and what time overlap the team needs.
Data and systems
Code and account ownership, minimum access, environments, information handling and publication restrictions.
Delivery and acceptance
Deliverables, test scenarios, validation, documentation, support and change management. Licences and usage are assessed for the scope.
San Salvador, El Salvador (UTC−6). For Spain and other countries, overlap, time commitment and channels are agreed before work starts. Spanish; basic English for reading technical documentation.