The name, and the
person behind it.
Netrikan is a practice of one. That is a deliberate choice rather than a stage it is passing through, and it is worth understanding before you hire it.
Netrikan
Most consultancies are named after their founder, a Latin root, or an abstraction chosen to mean nothing in particular. This one is named after an idea, in a language that had a word for it long before supply chains existed.
Netrikan — from the Tamil netri (forehead) and kan (eye). The forehead eye: the third one, which sees what the other two cannot. In Tamil tradition it is the eye of perception rather than sight, and it opens on what is coming rather than what is present.
An unusual name for a supply chain practice, and that is the point. The two ordinary eyes see what has already happened — the late shipment, the listed supplier, the invoice with a duty on it that nobody budgeted for. Reporting those accurately is a real job, and it is not this one.
The work here is perceiving a constraint while it is still forming: in a backlog that has been growing for three quarters, in a qualification cycle that has quietly doubled, in a docket at an agency that has nothing to do with your industry. By the time a constraint is visible to the other two eyes, it is already in your schedule.
Venkat Venkataraman
Twenty years inside high-mix, long-lead-time manufacturing — the kind where a missed capacity or supply plan doesn't show up as a line item. It shows up as an idle line and a blown schedule.
The career has run through three industries that look unrelated from outside and are not: electronics manufacturing services, data center infrastructure, and medical devices. Each one commits capital against a date it cannot move. Each one has watched a single component decide whether that date holds.
Working across all three is what produced the method rather than diluting it. The same constraint arrives wearing different clothes each time — as an energization date in one, a regulatory submission in another, a customer's launch window in the third. Underneath the costume it is the same problem, and the signals that predict it are the same signals.
The failures were rarely a surprise in hindsight. The tell was there in the backlog, the qualification cycle, or the procurement pattern. It simply wasn't anyone's job to be reading it while the quarter was busy. Netrikan exists to make it someone's job, on a cadence, before it costs you a quarter.
What a practice of one means
Both halves of it — the part that is better for you, and the part that is a real limit.
You talk to the person doing the work
There is no team between the analysis and the conversation about it. Nobody is being trained on your bill of materials, and no partner presents findings they didn't produce.
A small number of engagements at a time
Capacity is the constraint here too, and it is the honest reason the work stays specific. A practice that took every engagement offered would produce the generic output this exists to avoid.
Sources are named, and so are their limits
Every figure carries where it came from and what kind of source that is. Where an open-market broker and a manufacturer disagree, both numbers appear — the gap between them is usually the finding.
No predictions about named companies
Exposure is assessed at material and sector level. Naming an already-listed entity is citation; predicting that a particular supplier will be listed is not defensible from public information, and it will not be done here.