Home / About

A small studio you can actually get on the phone.

AtinusX automates recruiting desks for agencies in the US and Canada. We are built around one idea: the person who scopes your work should be the person who builds it. No account layer, no bench of juniors, no discovery theatre before you find out what something costs.

AX

[Founder name]

[Title, e.g. Founder and principal engineer]

[Two or three sentences of operator background: the platforms you have actually run in production, the scale, and the kind of environment — regulated, enterprise, high-volume. Name real systems. This paragraph carries more weight than anything else on the page.]

  • [Years in production engineering]
  • [Certifications or platform specialisms]
  • [Previous employers or notable systems]

How we are set up

Deliberately small, and structured to stay that way.

We take a limited number of engagements at a time because the model only works if the engineer is in the room. That constraint is the product, not a stage we are trying to grow out of.

We are based in India and work with recruiting and staffing agencies in the US and Canada. That is stated plainly rather than buried: it means your builds happen overnight relative to your working day, and it means we commit to a fixed daily overlap window agreed before an engagement starts, not negotiated afterwards.

  • You work with the builder. The person on the first call writes the code and runs the handover.
  • We say no when it does not fit. If an engagement needs capability we do not have, we tell you during the audit rather than discovering it together at week nine.
  • Capacity is honest. If we cannot start when you need to start, you will hear that immediately.
  • Everything is written down. Our full method is published on the playbook page — read it before hiring us.

What we are good at

Production systems, not pitch decks.

The studio is built on production experience in enterprise environments — cloud infrastructure under real governance constraints, data integration where a failed load is a business incident, and automation wired into systems that already matter. The marketing, sales-operations and product practices grow from the same discipline: measure first, promise from evidence, write it down.

That background shapes how we scope. We assume you have an existing estate you cannot rip out, budgets that need defending internally, and colleagues who will maintain whatever we hand over. We are not going to propose a greenfield rewrite — or a bigger ad budget — as the answer to everything.

The engineer who scopes it is the engineer who builds it.

— the whole operating model, in one line

Founding clients

We are taking on a small number of founding clients.

Early engagements come with more of our attention than a later client will get, and the founding pilot is priced at $750 rather than what it will cost later. In exchange we ask to publish what we built and what it returned, with anything commercially sensitive removed and your approval before it goes anywhere. That rate disappears once we have a handful of published results.

Direct access

You work with the founder throughout, not an account manager relaying decisions.

Founding pricing

Reduced rates on the first engagement, tied to a written case study once it ships.

Influence on the roadmap

What we build for you shapes the packages we productize next.

The obvious questions

How big is the team?

Small and founder-led, with specialists brought in for defined pieces of work when a build genuinely needs them. That means you work directly with the person doing the engineering, and it also means we run a limited number of engagements at once. If we do not have capacity for your timeline, we will tell you on the first call.

What happens if you take on work you cannot deliver?

The audit stage exists precisely to catch that before you have committed to a build. If we find that the work needs capability we do not have, we say so, hand over the analysis, and do not quote for the delivery.

Why only recruiting agencies?

Because a recruiting desk runs the same handful of workflows everywhere — sourcing, CRM hygiene, scheduling, follow-up, reporting — which means the second build is faster and better than the first, and we can quote from experience instead of guesswork. A studio that automates anything for anyone learns nothing twice. We do take work outside the vertical when it is a genuine fit, but this is what we are set up to be good at.

You are in India and we are in the US. How does that work?

Most of the work is asynchronous — you describe the workflow, we build it, you review it — which suits the time gap rather than fighting it. We commit to a fixed overlap window each day for calls, agreed before the engagement starts, and to a one-working-day reply on everything else. Work lands in your accounts overnight relative to your day.

What if we outgrow you?

Then the handover we designed from day one does its job. Everything lives in your accounts, documented well enough for a larger firm or your own hires to pick up without a rewrite. No part of what we build depends on a licence, a login or a subscription that we control.

Where are you based, and do you work remotely?

We work remotely by default and on-site when a piece of work genuinely needs it — usually discovery interviews and handover sessions. Time zones are agreed before an engagement starts, not negotiated afterwards.

The first conversation costs nothing.

An hour on a call about your actual business. If we are not the right fit, we will say so and point you somewhere better.