Principles

Nine principles we use as a filter when something has to be decided. They apply across any project, any vertical, any technology. If an option contradicts one of them, we hesitate.

1. Results over activity

We measure by impact, not by hours worked, lines of code written, or meetings attended. What counts is what changed: revenue increased, costs reduced, problem solved.

In practice:

  • We define clear outcomes before starting.
  • We ask "what did this achieve?", not "how long did this take?".
  • We celebrate results, not effort.

2. Build over consult

We prefer to execute over recommending. Anyone can give advice. We write the code, ship the product, and deliver the solution.

In practice:

  • We do not produce slide decks that end up in a folder.
  • If we spot a problem, we propose and build the fix.
  • Our deliverables are working software, not reports.

3. Repeat to scale

We document everything. If it works, we systematize it. If it repeats, we productize it. That is how we grow without burning out.

In practice:

  • Every process gets documented the second time around.
  • We build internal tooling to automate repetitive work.
  • Patterns from Solutions become products in Factory.

4. Ambition with patience

We want to be big. We want to build the LATAM equivalent of the great tech companies. But we know that gets built step by step, not overnight.

In practice:

  • We set ambitious long-term goals.
  • We break them down into achievable milestones.
  • We do not trade quality for speed.

5. Technology with purpose

We do not adopt technology because it is fashionable. Every tool, framework, or AI model has to solve a real problem. Technology is a means, not an end.

In practice:

  • Before adopting something, we ask what problem it solves.
  • We pick boring technology when it is the right choice.
  • We use AI where it adds value, not everywhere.

6. Own your work

Each person owns their deliverables end to end. No throwing code over the wall. No "that is not my job". If you build it, you support it.

In practice:

  • We do not split into "dev" and "ops" mindsets.
  • We follow up on work after we deliver it.
  • We fix our own bugs.

7. Transparency by default

We share information openly inside the team. No information hoarding, no politics, no hidden agendas. Trust is built through transparency.

In practice:

  • Decisions are documented with their rationale.
  • Feedback is direct and constructive.
  • We admit mistakes when we make them.

8. Simplicity wins

Simple solutions beat complex ones. Simple code beats clever code. Simple processes beat bureaucratic ones. When in doubt, simplify.

In practice:

  • We remove features more often than we add them.
  • We prefer clear over clever.
  • We ask "can this be simpler?" regularly.

9. AI-native by design

AI and automation are core tools at Dinnartec. They multiply our capacity, they do not decorate our marketing. We build assuming AI is available; we ship products where AI is part of the substrate, not an add-on.

In practice:

  • We use AI agents to write, review, and ship code.
  • We automate operational work that does not need a human.
  • We design products assuming AI is available, not optional.
  • We pick AI where it adds value, ignore it where it does not.

How we use these principles

These are not decorative posters. They serve to:

  1. Decide. When we are stuck, the principle that fits best breaks the tie.
  2. Give feedback. We reference principles when reviewing work.
  3. Resolve conflicts. Shared principles are common ground.
  4. Evaluate fit. New team members must resonate with this.

These principles evolve. If something stops serving us, we change it.