Services

Evidence before commitment. One owner throughout.

We work out what will run within your constraints, show the evidence before you commit, assemble the right delivery capability, and stay accountable after go-live.

From first question to supported service

Start with an assessment. Each step is independently useful, and you can stop at any of them.

Engagement journey Four stages: Assess gives a decision, Pilot gives evidence, Deploy gives a service, Operate gives ongoing support. You can stop after Assess or Pilot, for example to stay hosted. Performance Rescue is a separate entry for existing deployments that joins at Deploy. Stop: stay hosted, or not yet A valid, paid-for outcome Performance Rescue for existing deployments 01 Assess → Decision 02 Pilot → Evidence 03 Deploy → Service 04 Operate → Support Engagement journey Assess gives a decision, Pilot gives evidence, Deploy gives a service, Operate gives support. You can stop after Assess or Pilot. Performance Rescue joins at Deploy. Stop stay hosted / not yet Rescue existing deployments 01 Assess → Decision 02 Pilot → Evidence 03 Deploy → Service 04 Operate → Support
Each stage stands on its own and ends in something you can use. Stopping after an assessment or pilot is a normal, paid-for outcome.

Also available

Prices in USD. Excludes hardware, taxes and third-party licences. Final price is fixed in a written scope before work starts.

Where processing happens

We pin this down at intake and never quietly substitute one for another. A system is not offline if extraction, embeddings or authentication still need the internet.

On-device

Processing happens on the user's own computer or phone. Nothing is shared between users unless you build that in.

On-premises

Processing happens on infrastructure your organisation owns and operates, in your building or your colocation space.

Private hosted or hybrid

Explicitly approved external infrastructure, or a defined mix, with every external flow named in writing.

How we're paid

Managed delivery

We own the engagement and bring in vetted specialists where needed. You pay for the outcome; we stay responsible for the work, including what subcontractors deliver.

Buyer-side sourcing

You contract directly with hardware, hosting or implementation suppliers. We charge for evaluation, procurement coordination and acceptance testing, and compare quotes against the same scope.

Ongoing operation

A defined monthly service to keep an accepted deployment useful and supportable, with clearly bounded responsibilities.

Referral fees: if a supplier pays us a referral fee, we tell you in writing before you buy. It never decides the recommendation. Editorial & commercial policy.

Dipankar Sarkar · Engagement owner, Neul Labs Limited
One named person is accountable for scope, commitments and acceptance on every engagement, including work delivered with specialist partners.

Frequently Asked Questions

Do you only recommend local deployment?

No. We sell a working outcome under your constraints. Local inference is one way to deliver it. Staying hosted, or moving only one workload, are legitimate recommendations.

How do you make money if you recommend against migrating?

Assessments are paid, fixed-fee deliverables, so a "no" is still a complete piece of work. Implementation, managed support and partner programmes are priced separately.

Do suppliers pay you referral fees?

Where a supplier pays a referral fee, we disclose it in writing before you buy, and it never decides the recommendation. You can always buy directly from the supplier.

Are your prices fixed?

The figures on this page are starting points. Every engagement gets a written scope with a fixed price, assumptions and exclusions before work starts.