AVAILABLE FOR NEW PROJECTS · FREE CONSULTATIONAVAILABLE FOR NEW PROJECTS · FREE CONSULTATIONAVAILABLE FOR NEW PROJECTS · FREE CONSULTATIONAVAILABLE FOR NEW PROJECTS · FREE CONSULTATIONAVAILABLE FOR NEW PROJECTS · FREE CONSULTATIONAVAILABLE FOR NEW PROJECTS · FREE CONSULTATION
ABOUT

A small team

Kaxbe operates from Chiquimula, Guatemala, and works remotely for clients in Guatemala and across Latin America. It is a small team, trained in computer systems engineering, with in-house capability in full stack development, backend and applied artificial intelligence. Previous work spans the public, cooperative, academic and private sectors.

4

Sectors: public, cooperative, academic and private

100%

Of projects are delivered with their source code

COMMUNITY

Beyond the projects

Organizers of FLISOL Chiquimula, co-instructors of open university extension courses, and contributors to the engineering journal at CUNORI. We work with free software and take part in the community that sustains it.

// STACK
Angular
Spring Boot
PostgreSQL
DSpace
Koha
Odoo
Docker
Cloudflare
PROCESS

Software isn’t judged the day it ships, but two years later

Four stages with verifiable deliverables. None begins before the previous one is approved.

Start a project
  1. // 01

    Elicitation and analysis

    We identify every stakeholder and gather requirements through interviews, observation of the current process and document review. What the system must do is separated from how it must behave, and conflicts between areas surface before they turn into rework.

  2. // 02

    Specification and validation

    Requirements are documented in verifiable form and put through formal review with the client. No development starts until that document is approved: fixing a requirement at this stage costs a fraction of fixing it once the system is built.

  3. // 03

    Design, construction and verification

    The architecture derives from the approved requirements, not the other way around. It is built in increments, and each one is verified against its specification before moving on, so deviations surface in weeks rather than at the end.

  4. // 04

    Evolution and change management

    Requirements change: that is planned for, not improvised. Every request is assessed for impact and cost, kept versioned, and incorporated traceably, without degrading what already works.

CONTACT

Tell us what you need