atum

SERVICES · DEVELOPMENT

Operations that outgrew the spreadsheet.

We build the applications and automations your process actually needs. Nearshore software development out of Mexico City: fixed scope, week-long cycles, and the code ends up in your name.

Cycles
Weeks
IP
Client-owned
Overlap
Full US workday

THE STARTING POINT

It almost always starts the same way.

There is a shared spreadsheet nobody fully understands anymore, three people keeping it alive by hand, and a critical process that depends on none of them taking vacation at the same time.

The ERP does not cover it. Off-the-shelf software covers most of it, and the missing part is exactly what makes you different. Building it internally sits behind six other priorities on your own roadmap, and in the meantime your team is the one that looks slow.

That is where we come in.

WHY NEARSHORE

Same day, same hours, no handoff.

  • Two hours, maximum

    Mexico City is UTC−6 year-round. That puts us within two hours of every time zone in the continental US — one hour from Central. There is no overnight queue between your question and our answer.

  • Native bilingual, both directions

    The engineer writing the code is the one on the call. Nothing passes through a coordinator whose job is translation, and no requirement loses its meaning on the way to the keyboard.

  • In the room when it matters

    Direct flights from most US hubs. Kickoffs, workshops and go-lives can happen in person without a two-day journey and a visa process.

  • Legal and commercial proximity

    Contracting between the US and Mexico is routine, invoicing is straightforward, and the USMCA framework governs the commercial relationship. Your counsel has done this before.

  • Senior engineers only

    Small team, no bench, no pyramid staffing. The people you meet in the first call are the people who build it.

ON VIDEO

The same argument, on video.

A narrated walkthrough of how we work: where the problem usually starts, what we build first, and whose name the product ends up in. The piece is in Spanish, narration and on-screen text alike. It has audio, and it starts only when you ask it to.

WHAT WE BUILD

Five kinds of work. All of them end in production.

Web and mobile applications

PWAs and hybrid apps, installable without going through app stores. They run on the device your people already carry.

Internal platforms and employee portals

Day-to-day operational tools: intake, approvals, case files, shift boards. Designed to be used eight hours a day without friction.

AI process automation

Document classification and extraction, assisted responses, quality control across volumes no human team can review. With explicit criteria and a human checkpoint where it counts.

Integrations with existing systems

ERP, CRM, payroll, corporate directory, banks and legacy systems with awkward APIs. We do not open by asking you to replace what you have.

Conversational assistants

On the web and on WhatsApp, scoped to your content and your rules, with traceability of what was answered and from which source.

HOW WE WORK

Three commitments, and all three are verifiable in the contract.

  • Fixed scope, short deliveries

    We agree the scope before we start and cut it into cycles measured in weeks. Every cycle ends with something working that you can use and react to. No single deliverable at month six.

  • You own the product

    Intellectual property, source code and data are assigned to you as each delivery is paid. Repository, credentials and infrastructure can sit in your accounts from day one if you prefer.

  • Operations are optional

    We can stay on to monitor, fix and evolve under a service agreement. Or we hand off to your team with documentation, transition and a support window. That is your call, not a clause.

PROCESS

From first call to production.

  1. 00 · First call

    Thirty minutes. You describe the problem; we tell you whether it is ours to solve. If it is not, you hear that on the call.

  2. 01 · Discovery

    We watch the process where it happens and talk to the people running it, not only the people who own it. You get a written scope and a plan broken into cycles.

  3. 02 · Build cycles

    Frequent releases to an environment you can open yourself. One review per cycle, with the application on screen, not a status report.

  4. 03 · Go-live

    Deployment, monitoring, user training and a stabilization window.

  5. 04 · Operate or hand off

    A service agreement with committed response times, or a documented handoff to your team.

STACK

What we build with.

We are not stack-agnostic for the sake of it — we pick what we can operate for years. When your organization already has a standard, we work inside it.

Frontend
Strict TypeScript, Astro, React, PWA
Backend
Node and Python, typed APIs, queues and scheduled jobs
Data
PostgreSQL, vector search, real-time analytics
AI
Language models with retrieval over your own content, plus continuous evaluation
Infrastructure
Containers, continuous deployment, observability and verified backups
Quality
Strict types, automated tests and mandatory code review

SECURITY

What we can actually claim.

Architecture designed in line with ISO 27001 controls and the SOC 2 trust services criteria. Atum holds no certification under either framework. We phrase it that way because your risk team is going to check, and because a vendor who stretches the truth here stretches it everywhere else.

  • Encryption in transit and at rest.
  • Least-privilege access with mandatory multi-factor authentication.
  • Audit logging of access and changes.
  • Backups with tested restores, not just scheduled ones.
  • A data processing agreement whenever we handle personal data on your behalf.

WHO WE WORK WITH

Where this fits.

Mid-size and large organizations in banking, insurance, education and multi-site corporates, in the United States and Mexico. The projects that go well share three things: an owner who can decide, a problem with a name on it, and a date that matters.

  • Banking and financial services
  • Insurance
  • Education
  • Multi-site corporates
  • Retail and branch networks

United States · Mexico

NEXT STEP

Tell us what you need.

With a description of the process and a target date, we can tell you on the first call whether it is feasible, how many cycles it takes, and what we would need from your side. If we are not the right team for it, you hear that on the same call.