Kurtech Innovations Private Limited

Software that keepsthe whole place running.

We build the operational systems organisations depend on — ERP and hospital management, AI camera search, and automation shaped to your process.

?which purchase orders have been sitting unapproved for more than a week

resolves through approvals ledger ageing rule one view, one owner
Real questions each system answers — illustrative, not live data

The company

Kurtech
Innovations.

We build operational software — the systems an organisation actually runs on, every single day.

Most of our clients already own software. What they don't own is software that fits. A hospital running three systems that refuse to talk to each other. A factory whose real stock figures live in one person's spreadsheet. A campus sitting on thirty days of camera footage nobody can search.

We build what closes those gaps — and we build it around the way the work is already done. Your registers, your formats, your codes, your approval chain. Software that argues with the process loses, every time.

Three products so far, all of them live: an ERP and hospital management system, Vantage for camera search, and automation pipelines built to order. Each is deployed, in daily use, and still growing.

  • What we buildOperational software — planning, records, search and automation
  • Who we build forHospitals and trusts, manufacturing units, campuses and the offices behind them
  • Live todayThree products, deployed and in daily use
  • DeploymentOn-premises, private cloud or hybrid — decided by your constraints
  • HandoverDocumentation and admin access, always. You can run it without us

What we've built

Three products,
already running.

Every one of them began as a problem a real organisation couldn't solve with the software it already had. All three are deployed and in daily use.

Built & deployed

Kurtech ERP + HMS

One system.
Every department.

Procurement, stock, pharmacy, beds, billing, payroll and books — every one of them writing to the same record.

One event — recorded once, arriving at every desk that needs it

Most institutions run two or three systems that don't talk. The pharmacy knows what it dispensed, billing knows what it charged, and reconciling the two costs somebody a day every week. We build one system where dispensing a strip of medicine is a clinical event, a stock movement and a billable line at the same instant — entered once, right on every desk that needs it.

Nine departments, one record

Scoped to your institution — a district hospital, a manufacturing unit and a four-campus trust need very different sets. Keep scrolling.

Procurement

From indent to receipt

Indents, vendors, purchase orders, approval chains, goods receipt against order.

which POs are past our agreed terms

Inventory

Stock that reconciles

Stock by location, batches and expiry, issue and return, reorder levels that actually fire.

what expires in the next thirty days

Outpatient

Registration to follow-up

Registration, queue and token, consultation notes, prescriptions, follow-up scheduling.

how long did OPD wait today, by hour

Inpatient

Live bed state

Admission, bed occupancy in real time, transfers, clinical orders, nursing records.

is bed 14B free, and who was discharged from it

Pharmacy

Dispensing against stock

Prescriptions, dispensing that decrements real stock, substitutions, returns.

what did we issue to ward 3 against what we billed

Diagnostics

Request to signed report

Requests, sample tracking, results capture, signed reports attached to the record.

which samples have been pending over four hours

Billing

Tariffs, claims, settlement

Tariffs and packages, scheme and insurance claims, settlements, receipts.

which claims are stuck, and with whom

People

Roster to payroll

Roster and shifts, attendance, leave, payroll inputs that come from the roster itself.

who is on duty in casualty tonight

Books

Close the period

Ledgers, cost centres, period close, statutory reports built from the same records.

what did ward 3 actually cost last month

Inside the system

One event.
Four ledgers.

This is the whole argument for a single system, in one worked example. A nurse dispenses one strip of medicine. Watch what it becomes.

14:22 Paracetamol 500 mg · 1 strip · dispensed to bed 14B, Ward 3 entered once, by the nurse at the point of care
  • ClinicalAdministration recorded against the patient's chart and the prescribing order closed out
  • StockOne strip off Ward 3 floor stock, batch B‑4471, expiry 03/27 — reorder level checked on the way past
  • BillingBillable line added to the admission at the scheme's tariff, ready for the claim
  • BooksCost posted to Ward 3's cost centre, so the month-end figure needs no reconstruction

No re-entry. No overnight sync. No spreadsheet holding the truth in between.

What decides whether a rollout works

  • The migration is the projectYears of existing records have to arrive clean and reconciled. We budget for it honestly at the start, because it is the part that sinks rollouts — not the software.
  • One department at a timeNo rip-and-replace. We go live in phases, usually starting with stores or pharmacy, so a bad week never takes the whole institution down with it.
  • Run parallel before you cut overThe old process and the new one run side by side until the numbers agree for a full cycle. Only then does the old one stop.
  • Train on your own recordsNobody learns a system from sample data. Your staff train on your wards, your vendors, your tariffs — from the first session.

The honest constraint: an ERP is only as good as what people actually enter. A system that makes correct entry slower than the workaround will lose to the workaround. That is a design problem, and we treat it as one.

Built & deployed

Kurtech Vantage

Describe it.
Find it.

Search CCTV footage by typing what you're after, in plain words — on the cameras you already own.

search
idle
  • Running a search…

Synthetic scene, generated in the browser — an illustration of the interface, not real footage

Most video analytics only finds what it was trained to find: a person, a car, a helmet. That list gets locked in months before the thing you actually needed to look for ever happens. Ask for anything outside it — a ladder left against the scaffold, the van that came back a third time — and you're back to scrubbing footage by hand at midnight. Vantage has no list.

What you can ask for

Five kinds of question, one search box.

People

Someone, described

Not an identity — a description. What they wore, what they carried, where they went, when.

the person in the high-vis jacket who came to gate 2 twice this morning

Objects

A thing, where it shouldn't be

Equipment left out, a vehicle parked long, stock moved off its floor mark.

a ladder left standing against the scaffold overnight

Hazards

A condition, not an alarm

The states your safety officer would flag on a walk — found on every camera at once.

anyone on the gantry walkway without a helmet

Occurrences

Something that happened

An event described by what it looked like, not by a rule somebody wrote in advance.

a vehicle reversing into the loading bay after hours

Standing

A question that keeps running

Save any search and it re-runs as new frames arrive — the same question, now watching.

tell me whenever this happens again

Inside Vantage

How the search
actually works.

Your question and every recorded frame get turned into the same kind of data. That one trick is what lets you search hours of video with a sentence. Scroll to follow a question through it.

  1. 01Cameras recordLive feeds plus everything already sitting on your recorder. No new hardware to get started.
  2. 02Frames become embeddingsFrames pass through an encoder and are stored as vectors — a space where things that look alike end up sitting close together.
  3. 03Your question joins themThe sentence you type goes through that same encoder, into that same space. This is the step that makes an unplanned question possible.
  4. 04Closeness becomes a rankingThe distance between your question and every indexed frame is just a number — so results arrive already sorted, each with its camera, timestamp and frame.
  5. 05Save it and it keeps watchingSave the search and it keeps running, testing every new frame as it arrives and flagging the ones that match.
01 — cameras recording
CAMERA FEEDS live and recorded SHARED ENCODER pictures and words into one space frames stored VECTOR INDEX every frame, searchable YOUR QUESTION written in plain words text compared RANKED MATCHES camera, timestamp, frame, closeness nearest first standing query — re-runs as new frames arrive CAMERA FEEDS YOUR QUESTION frames text SHARED ENCODER pictures and words into one space embedded VECTOR INDEX every frame, searchable nearest first RANKED MATCHES camera, timestamp, frame, closeness standing query — re-runs as new frames arrive
The mechanism, precisely. Because a picture and a sentence land in the same space, the closeness between them is a number you can sort by — which is why a question nobody planned for can still be asked, months after the footage was recorded.

What decides whether it works on your site

  • Where the cameras pointResolution, angle and lighting set the ceiling on what any system can recover. We survey what you've already got installed before promising anything about it.
  • How the question is writtenA sharp description finds far more than a vague one. Teaching your team how to ask is part of the deployment, not an afterthought.
  • The review loopMark the wrong matches and the query sharpens. A search nobody corrects stays exactly as good as its first guess.
  • Where it's allowed to runFootage often can't leave the premises. Vantage deploys on-premises, private cloud or hybrid — decided by the constraint, not the convenience.

No benchmark numbers on this page, deliberately. Accuracy on your site depends on your cameras and your questions, so we tune and measure it during a paid pilot on your own footage rather than quote a figure from somebody else's.

Built & deployed

Kurtech Pipelines

Stop retyping
the same numbers.

If somebody on your team is copying data out of one system and into another, that's a pipeline waiting to be built.

Most records pass straight through. The ones that don't go to a named person, with the reason attached

The shape of a pipeline

Five stages. The fourth is where most automation quietly fails — so we build that one first.

Stage 01

Trigger

A form lands, a threshold is crossed, a clock strikes, a device goes quiet.

Stage 02

Extract

Pull the fields out of whatever they arrived inside — a scan, an email, a portal, a spreadsheet.

Stage 03

Validate

Check against the rule the organisation already applies. Most records pass straight through.

Stage 04

Route the exception

The ones that fail go to a named person with the reason attached — never into a silent queue.

Stage 05

Act and record

Post it, file it, notify, raise the next document — and log who, what and when for the audit.

  • A document becomes a recordScans, emails and forms read, checked and posted into the system that should have had them in the first place.
  • Two systems that never agreed to talkA bridge between the software you bought and the software you inherited, kept in step without anyone retyping.
  • A threshold becomes a messageStock, expiry, ageing approvals, silence from a device — noticed before a person notices.
  • A report that builds itselfThe weekly assembly job, run on schedule, with exceptions flagged at the top rather than buried on page four.

Automation you can't audit is just a faster way to be wrong. Every pipeline we build leaves its own trail: what ran, what it decided, and what it refused to decide.

Method

How we work.

  • Scope against the process, not the brochureWe start by watching how the work is really done — including the parts that quietly happen on paper because the software made them harder.
  • Build on the records you already keepYour registers, your formats, your codes. A system that demands a whole new vocabulary on day one gets quietly abandoned by month three.
  • Deploy where it has to livePatient records and camera footage often can't leave the building. On-premises, private cloud or hybrid — your constraint decides, not our convenience.
  • Hand over the keysDocumentation, admin access and a real handover. You should be able to run it, extend it or walk away — without needing our permission.

In the making

More already
in the works.

The three products above keep growing, and several more are in active development. Here is where the work is heading next.

In development

Vantage across sites

One question put to every campus at once, with saved searches that follow a subject from one site's cameras to the next.

In development

Deeper into the institution

More ERP and HMS modules, built in the order real deployments ask for them — not the order a roadmap guessed at.

In development

Sector-shaped editions

Versions of what we've built already, pre-fitted to how a particular sector actually works — so your deployment starts far closer to done.

Commissioned

Whatever you need next

Work commissioned by one organisation that turns out to be worth building properly for everyone. Bring us the problem and it might become the next product on this page.

If the thing you need isn't on this page, say so. Our roadmap comes out of those conversations far more often than it comes out of a planning meeting.

Contact

Tell us what's
slowing you down.

The best first message is the thing that quietly eats your team's time every week. Tell us what it is and we'll tell you honestly whether it's a week of work or a quarter.