Your technology team, without hiring a technology team.

Companies that already run on software but don't have — and don't want — an IT department. Usually between 20 and 300 people: big enough that a broken process costs real money, small enough that hiring three engineers makes no sense.

If you already have an internal team, it works too: we come in as extra capacity on the fronts they can't reach.

Four things, at every tier:

• 01

  Custody. Your sites, apps and integrations under our responsibility. Maintenance, security, daily backups, 24/7 monitoring.

• 02

  Development. From the Operations tier up, development requests in a queue: one active at a time on Operations, two on Tech as a Service. We prioritize them together in the roadmap meeting. On Essential, minor edits: text, images or a form.

• 03

  Monitored automations. Flows that run by themselves still break. We watch them and fix them.

• 04

  Someone who answers. With a response time committed in writing, not "as soon as possible."

Because hourly billing turns the relationship into surveillance and rewards us for taking longer. You end up counting minutes instead of results, and we end up justifying time instead of solving things.

We charge for committed capacity: you know exactly what you get each month, and we know exactly what to reserve.

An improvement, integration or module that fits in about a week of work. If it's bigger, we split it into several requests.

Requests go into a queue and are worked first in, first out: when one closes, the next one starts. Send as many as you like — what's committed is how many move at the same time, not how many fit in a month.

New projects of larger scope, quoted separately. Third-party licenses and hosting. Content creation.

We say it here instead of in the fine print, because surprises on an invoice are the fastest way to lose a client.

• 01

  Same working day. Mexico City runs on US Central time. No overnight handoffs, no waiting until tomorrow for an answer.

• 02

  The same people. You work with the engineers who built your system. No rotating bench.

• 03

  Everything in English, in writing. Roadmap meetings, documentation, tickets. Nothing important happens in a language you don't read.

Yes, after a technical review. If inherited code makes the service level we promise impossible to sustain, we tell you before signing, not after.

That review is useful even if you don't hire us: you keep an honest assessment of what you actually have.