About
Enterprise AI has an evidence problem. We are the correction.
The gap between what enterprise AI promises and what it delivers is not a model problem. Models improve every quarter. It is a delivery problem: programmes advance on enthusiasm, get judged on demos, and close on narratives instead of numbers.
The correction is unpoetic: thresholds in writing before work begins, an exit gate closing every phase, and a standing willingness to recommend against ourselves when the evidence points that way. A programme advances one proven phase at a time, and nothing it has passed gets walked back. The name comes from luna, and the waxing moon marks the phases — a mnemonic for that rule, not the argument for it.
Operating principles
Evidence over enthusiasm
Every claim we make inside an engagement is tied to an artifact — a measurement, an evaluation result, a signed baseline. If we can’t evidence it, we say so and downgrade the claim.
Senior people only
Small teams of people who have shipped in enterprise conditions. No leverage pyramids, no bait-and-switch between the pitch team and the delivery team.
The honest no
We recommend stopping when the evidence says stop, including when stopping ends our own billable work. It is the most expensive thing we do, and the reason our yes is worth something.
Progress never walked back
Phases advance only through passed gates, so nothing we report as done has to be quietly undone later. Status at LUNTA is a fact, not a mood.
Your data stays yours
Client data lives in client systems, under client controls. We design for auditability and exit from day one — including exit from us.
Who you work with
LUNTA is a small, senior practice. Engagements are staffed by people who have shipped AI and platform work inside large organisations — telecom, ERP, and e-commerce environments across Europe and the Middle East — and who then had to operate what they built. That last part is the selection criterion: carrying the consequences of a system after go-live is a different education from designing one.
The practice was founded by three practitioners out of that same discipline, and engagements are led by them.
That is a claim, not evidence. We would rather say so than let it sit here doing the work of proof — an unnamed background cannot be checked, and a page that asked you to take one on trust would be doing the exact thing this practice exists to correct.
LUNTA is new. The method is not — it is the delivery discipline its founders assembled over years of that work, written down and made contractual: thresholds before work, gates between phases, and the honest no when the evidence says stop.
So the site carries no biographies and no headshots. A marketing page is the wrong instrument for judging whether people are any good — but the method, the terms, the assurances, and the reasoning can be judged, and all of that is already published.
What you can examine before any conversation
- The delivery method, in full
Five phases, five exit gates, and the named artifacts each gate requires.
- The commercial terms
Phase-by-phase pricing, gate criteria annexed to the contract, and termination at every gate.
- The assurance table
What we hold, what we do not hold, and how cross-border processing works.
- The reasoning, in public
The arguments this method is built on — ungated, and open to disagreement.
All four are published rather than gated, and none of them needs a call. The names and dates behind the claim above arrive in the first conversation — the only place a claim about people can actually be tested — and we will tell you there, plainly, what we can and cannot yet offer by way of a referee.
Where we are
- New York, NY · United StatesUS Eastern
- Connecticut · United StatesUS Eastern
- Cairo · EgyptEastern European
The practice operates from the United States and Egypt, and delivery is remote-first. How that works across a border is answered here rather than left to be discovered mid-engagement.
- One accountable lead, on your hours
- Every engagement names a single lead who is answerable for it and who works to your business hours. Not a rota of coordinators passing the thread between them, and not a pitch team handing you to someone else after signature.
- A working day that opens in Cairo and closes in New York
- The Cairo and US bases sit about seven hours apart, so where an engagement is staffed from both, it covers European and US Eastern hours with people already on it. That is a handover rather than a free extra shift — it is written down, and the accountable lead owns both ends of it.
- Jurisdiction-constrained staffing
- Where your data may not leave a jurisdiction, we staff the engagement accordingly or tell you plainly that we cannot. The answer comes before the contract, not after someone notices in week three.
- Processing locations named in the DPA
- Where an engagement involves personal data originating in the EEA or the UK, the transfer mechanism and the exact processing locations are named in the data processing agreement before any transfer.
- On-site presence, agreed per engagement
- Remote-first is the default, not a policy against travelling. Where the work needs people in the room, the presence is scoped and priced with the phase rather than assumed by either side.