Skip to content
Kordian™
Services

Three lines of work. Most clients need one.

You have a process that costs you money every week. Someone re-keys the same numbers. Someone chases a count that never matches. Someone is the only person who knows how a thing gets done, and they are on leave.

What you are not sure about is whether the answer is AI, or plainer software, or nothing at all. This page is the honest version of that question. Each line below tells you what you get, what we need from you, what it costs, and when it is the wrong choice.

Not three stages of one engagement. Three separate answers.

Line 01

Software we build, own and run

AInops is an AI-based inventory and operations manager, on web and mobile. It is live, its pricing is public, and we run our own stock and jobs on it.

That last part is the only reason it belongs on this page. We can tell you how it behaves on a bad day — when a count is wrong, when the network drops in a warehouse, when nobody scans for an afternoon — because we have had those days on it. A vendor who has only ever demonstrated their software cannot tell you that.

What you get

A live account on the same product we use. Four tiers from ₹749 per month, excluding 18% GST. Two months free when you pay annually. No implementation project, no minimum term, no call required before you can start.

What we need from you

Nothing. Sign up and use it.

When this is the wrong line

If your operation does not look like stock and jobs, AInops will not bend far enough to fit it. Tell us on the call and we will point you at line 02, or at nobody.

Line 02

Built for one problem — yours

A custom build starts with one problem you can name and a cost you can feel. Not a transformation programme. One process, taken from where it is now to where it should be, in software that belongs to you at the end.

Where AI is not the better answer, we build it without AI and we put the reasoning in the finding, in writing, so you can hold us to it later. A well-shaped database query is not a lesser deliverable. It is cheaper to run, easier to hand over, and it does not drift.

What you get

Working software in your cloud and your repositories, built in two-week increments by a small named team. Something you can actually use exists before the end of the first month. Fixed price per phase, quoted from the written finding.

What we need from you

Access to the systems it touches. One decision-maker who can settle a question without a committee. An hour a fortnight to look at what exists so far.

What it costs

Fixed price per phase, invoiced on delivery of each phase rather than by the hour. A small engagement is one system, one outcome, a few weeks, one invoice. A large one is split into phases you can stop between, each priced and useful on its own. Indian clients are invoiced in ₹; European clients are quoted and invoiced in €.

When this is the wrong line

If the process is not yet agreed inside your own company, software will set the disagreement in concrete and charge you for it. Settle that first. We will say so rather than take the work.

Line 03

AI into the system you already run

The system works. It has worked for years. Somewhere inside it a person is reading, sorting, matching or deciding by hand, and that is the part that does not scale.

A retrofit adds one capability to that system and leaves the rest alone. No migration, no rewrite, no rip-and-replace sold as modernisation. Then we keep operating it, because a model that nobody monitors drifts. A retrofit nobody is watching stops being an asset and becomes a risk you have not noticed yet.

What you get

One capability, in production, monitored. Then either a monthly retainer where we monitor, retrain and fix, or a handover to your team with documentation good enough to run it without us. Both are priced before the build starts, and we do not make handover difficult.

What we need from you

Read access to the system and to the data it holds. The name of whoever currently does the work by hand — they know things the documentation does not.

When this is the wrong line

If the underlying data is wrong, AI will be confidently wrong, faster, at scale. That is a data problem wearing an AI costume. You will get that answer in the finding, before you have spent anything on a build.

Before any of it

The finding comes first

Whichever line fits, the same document sits in front of it: a few pages that state what the problem actually is, which line of work it belongs to, the price band, and where the risk sits. If AI is the wrong tool, that is the document that says so, and it is yours to keep either way.

We quote after the call, not before it. A number without a scope is a guess, and you would be right not to trust it.

How an engagement runs, in four steps →

Next step

Book the call

One call, no charge, no deck. Bring the problem in your own words and whoever owns the system it touches. You will leave the call knowing which of the three lines fits, or that none of them does.