Yerko AcuñaEngineering · Leadership · EIRL
ESDownload CV
Menu
Leer en españolDownload CV

Software consultancy

A direct path from operational problem to working system.

Desarrollo de Software Yerko Acuña EIRL works with organizations that need thoughtful discovery, senior implementation, and continuity after launch.

Describe a projectView company case

Good fit

For organizations that need continuity between decisions and delivery.

The strongest results come with direct access to the people who understand the operation and a willingness to prioritize by value and risk.

A focused software practice for organizations whose workflows have outgrown spreadsheets, disconnected tools, or an inherited system that no longer fits.

Every engagement keeps discovery, architecture, implementation, deployment, and ongoing improvement connected through one accountable technical lead.

  • Operational platforms and internal systems
  • Modernization of existing applications
  • Integrations and traceability workflows
  • Projects that need senior ownership across the stack

Services

A clear scope, with depth where the system requires it.

Services can be engaged as a focused phase or connected into a complete software delivery.

Discovery and software architecture

Turn an operational problem into a shared domain model, a realistic scope, and an architecture the future team can maintain.

Best suited for

  • New internal or customer-facing platforms
  • Processes still coordinated through spreadsheets and manual handoffs
  • Teams that need to de-risk a build before committing to implementation

Typical deliverables

  • Workflow and requirements mapping
  • Domain and data model
  • Architecture and integration plan
  • Prioritized delivery roadmap

End-to-end full-stack delivery

Design and build a complete web application with one technical line of responsibility from interface to production.

Best suited for

  • Organizations that need a focused senior delivery partner
  • Operational software with complex roles and workflows
  • Projects where frontend, backend, data, and deployment must move together

Typical deliverables

  • Responsive web interface
  • Backend services and access controls
  • Database design and migrations
  • Automated production deployment

Modernization and integrations

Move an existing system forward without discarding the operational knowledge encoded in it.

Best suited for

  • Legacy application migrations
  • New APIs around existing workflows
  • Government, identity, document, or cloud-service integrations

Typical deliverables

  • Legacy behavior and dependency assessment
  • Incremental migration strategy
  • API and integration implementation
  • Compatibility and rollout plan

Production delivery and continuity

Make deployment, operational feedback, and continued improvement part of the product rather than an afterthought.

Best suited for

  • Applications approaching their first production release
  • Teams replacing manual deployments
  • Systems that need a practical ongoing improvement path

Typical deliverables

  • Containerized deployment
  • CI/CD workflow
  • Environment and release strategy
  • Technical handover or continued development plan

Process

Move in useful increments without losing the complete context.

Each stage produces verifiable decisions and reduces uncertainty before expanding the commitment.

  1. Understand the operation

    Map actors, decisions, exceptions, evidence, and constraints before designing screens.

  2. Define boundaries and scope

    Turn the workflow into a shared domain model, architecture, and delivery sequence.

  3. Build and validate

    Deliver working vertical slices that connect interface, services, data, and integrations.

  4. Deploy and evolve

    Automate delivery, learn from real use, and leave a maintainable path forward.

Commitments

What should remain after delivery.

  1. A clear technical and delivery scope

  2. Architecture matched to the real operating constraints

  3. Production-ready deployment and handover

  4. A maintainable base for continued development

Production evidence

A long-term relationship with a real operation.

The company case connects discovery, development, deployment, and continued evolution through one line of technical responsibility.

Fishing operations2022–PresentPrivate engagement

Yerko Acuña EIRL

Dipromar operations and traceability system

Dipromar Seafood Company

A custom operational platform that centralizes fishing-plant workflows and creates a continuous traceability record.

Outcome

Moved core workflows out of disconnected spreadsheets.