Software · Automation · AI
Start a project
Start a project

Investment ranges

Knowing what it costs to start also reduces uncertainty.

We publish ranges so you can determine whether there is a fit before investing time in meetings. These are not rigid packages: final pricing depends on scope, risk, data, integrations, infrastructure and third-party services.

Tell us about your project Compare solutions

Engagement formats

Six ways to start or continue.

We choose the format based on how clear the problem is, the size of the change and whether software already exists and needs to evolve.

01 · 5–7 days · MXN $18,000

Operational Blueprint

For an important problem whose scope is not yet clear enough to price implementation responsibly.

  • Includes: process map, friction, users/roles, risks, automation opportunities, dependencies and prioritized roadmap.
  • Outcome: an executable foundation for deciding what to build, automate or integrate and in what order.
  • Best when: several teams are involved, key decisions remain open or uncertainty is too high for a fixed implementation scope.
  • It is not: a free audit or a large quotation disguised as discovery.
02 · 2–4 weeks · from MXN $45,000

Automation & AI Sprint

For automating one concrete, measurable process without transforming the entire operation at once.

  • May include: rules, integration, OCR, extraction, classification, assistants, approval-first agents, alerts and logs.
  • Outcome: one working process with clear acceptance criteria.
  • Best when: the flow is understood and the pain is in repetitive execution.
  • Go deeper: critical process automation.
03 · 6–12 weeks · from MXN $95,000

Operational Software

For replacing a fragmented operation with a dedicated system for users, rules, data and follow-up.

  • May include: CRM, internal portal, workflows, dashboards, documents, permissions, integrations and mobile where it adds value.
  • Outcome: a usable operational core with defined scope.
  • Best when: spreadsheets, chats and isolated tools are already creating errors, rework or loss of visibility.
  • Go deeper: custom operational software.
04 · 10–20 weeks · from MXN $220,000

Operational Platform

For multi-team operations or B2B products with multiple modules, roles, integrations and a broader evolution path.

  • May include: modular architecture, multiple experiences, critical integrations, automation, traceability and phased releases.
  • Outcome: an operational platform delivered in stages, not an uncontrolled big-bang launch.
  • Best when: scope exceeds a single workflow and the system has real operational dependency.
  • Note: final size is defined by phases, risk and integrations; the published range is an entry point.
05 · monthly or project · from MXN $55,000/month

Product Engineering

For existing products that need a senior layer of architecture, evolution, AI, integration or release engineering.

  • May include: technical review, modernization, focused refactoring, integrations, security, CI/CD, observability and AI enablement.
  • Outcome: an executed technical roadmap with accountability for quality and product continuity.
  • Best when: the product works, but debt, architecture or delivery is already slowing the next stage.
  • We do not sell: simple hourly body leasing without technical ownership.
06 · monthly · from MXN $18,000/month

Continuous Optimization

For maintaining and evolving a solution after launch without restarting a project relationship for every change.

  • May include: support, prioritized improvements, observability, small changes, automations and operational evolution.
  • Outcome: continuity and gradual improvement based on real usage.
  • Best when: a delivered solution already exists and needs a stable evolution cadence.
  • Scope: defined according to criticality, required SLA, change volume and infrastructure.

What moves price

Cost changes because of real complexity, not buzzwords.

Scope and roles

Number of workflows, profiles, permissions, screens, variants and level of required customization.

Data and integrations

Data quality, available APIs, migrations, legacy systems and third-party dependencies.

Operational risk

Criticality, security, availability, traceability, approvals, rollback and continuity requirements.

AI and infrastructure

Models, volume, privacy, storage, cloud, external services and variable operating costs.

Before you buy

What these prices do and do not mean.

  • Yes: these are commercial anchors for determining initial economic fit.
  • Yes: a final proposal should specify scope, deliverables, exclusions, phases and acceptance criteria.
  • No: infrastructure, API/model consumption, licenses and third-party services are not automatically included.
  • No: complex projects do not become standard packages; if the context needs discovery, we will say so before pricing implementation.
  • Principle: we prefer reducing scope over degrading quality or promising a date/price we cannot sustain.

Next step

If the range makes sense, tell us the context.

The initial request helps us understand whether there is a fit and what the right next step is. If scope is clear, we move toward a proposal; if it is not, we will tell you whether a Blueprint makes sense.

Start a project Compare solutions