FRAUD & RISK · MODEL ASSURANCE · DECISION SYSTEMS

Production-ready AI, you can verify, line by line.

Most AI never makes it out of the pilot. It demos well, then quietly dies before production.

We build the ones that ship.

  • Real calibration
  • Clear deployment
  • Trusted model documentation
  • Seamless handoff
VERIFIED BUILD · TESTED & DOCUMENTED ·
3
PEER-REVIEWED PAPERS
2
NATIONAL HACKATHON WINS
Your repo, day one
NO LOCK-IN, NO BLACK BOXES
WE BUILD FOR TEAMS IN
Fintech E-commerce Healthtech SaaS Logistics

Set the vision. Then build it right.

We begin by understanding your business, your data, and your constraints. From there, we build solutions that are aligned with your goals, your workflows, and your long-term growth.

TIER 01 · DIAGNOSTICS & SPRINTS

Find out exactly what's needed, in under two weeks

Short, focused engagements that end in a clear, written deliverable you keep, whatever you decide next.

FIXED SCOPE · FIXED INVESTMENT
READINESS10 DAYS

Can't get your AI into production?

AI production-readiness audit

For: AI models that work in testing but aren't yet ready for production.

  • Review your model, data, and deployment strategy
  • Identify the highest-priority risks and bottlenecks
  • Receive recommendations to improve reliability, performance, and scalability
  • Design a guided launch plan with our team
Know exactly what it takes to launch with confidence.
Scope this
DATA5 DAYS

Is your data actually ready for AI?

Data readiness assessment

For: Teams preparing to build AI on data that may not be ready.

  • Assess the quality, completeness, and reliability of your data
  • Identify hidden issues before they become expensive engineering problems
  • Validate whether your data is ready—or what needs attention first
  • Receive a clear recommendation and prioritized next steps
A few days of validation can save months of rework.
Scope this
ASSURANCE10 DAYS

Security reviews stalling your deal?

Enterprise AI Evidence Package

For: Teams preparing for enterprise procurement, compliance, or security reviews.

  • Document your model, data and intended use
  • Explain performance, limitations, and key technical decisions
  • Prepare responses to customer security and AI documentation questionnaires
  • Deliver a complete, review-ready documentation package
Clear documentation that keeps enterprise reviews moving, not your deal waiting.
Scope this
DOCUMENT AUTOMATION7 DAYS

Still entering invoices manually?

Document intelligence sprint

For: Teams spending hours entering document data by hand.

  • Automatically capture information from invoices, forms, receipts and claims
  • Keep a human in the loop only where it matters, so nothing slips through
  • Integrate structured data into your existing workflow
  • Validate performance on your own documents, not sample datasets
Spend less time entering data and more time acting on it
Scope this
TIER 02 · SYSTEMS & PARTNERSHIP

Build the system, and leave it running with your team

Multi-week engagements, structured around clear milestones. Every one ends with a documented handoff and a runbook your team can operate on their own.

MILESTONE-BASED, NOT HOURLY
FRAUD / RISK6–8 WEEKS

Fraud decisions you can't explain?

Fraud & risk engine

For: Fintechs and marketplaces that need systematic, explainable fraud decisions.

  • Detect suspicious activity in real time
  • Explain every flagged decision with clear risk factors
  • Escalate only uncertain cases for human review
  • Tune decision thresholds to match your risk tolerance
Every decision comes with a reason your team can trust.
Scope this
DATA / ETL5–8 WEEKS

One-off models that won't scale?

ML Infrastructure Setup

For: Teams ready to move from isolated models to a scalable AI foundation

  • Build reusable data and training pipelines
  • Standardize how models are trained, deployed, and integrated
  • Create reliable APIs between your product and AI services
  • Document the platform so your team can own it from day one.
Build a foundation your next model can rely on, not rebuild.
Scope this
RESCUE6 WEEKS

Pilot stalled, launch slipping?

AI Launch Rescue

For: Teams with an AI pilot that's stalled before production.

  • Identify the blockers preventing production deployment
  • Resolve integration, reliability, and deployment issues
  • Prepare your system for a production handover
  • Leave with documentation, a runbook, and a clear ownership plan
Take a step forward and launch the AI you've already invested in.
Scope this
RETAINERMONTHLY

No one watching your AI in production?

Managed ML Support

For: Teams that can't afford production AI to drift, fail, or go unmaintained.

  • Monitor model performance and data quality to catch issues early
  • Maintain and improve models as your business evolves.
  • Keep documentation and technical decisions up to date
  • Get direct access to a dedicated ML engineer who knows your system
Ongoing support that keeps your AI reliable, without a long-term contract.
Scope this

Code you own, fully documented

We work in a repository inside your own organisation, so the code and models are yours throughout. Every system is delivered with inline documentation, architecture decision records and a handoff guide, so your team can operate, maintain and extend it with confidence. Prefer a self-contained, containerised deployment instead? We can hand off that way too. No lock-in, no proprietary runtime, no black boxes.

Clarity you can count on

Every engagement runs on the same clear terms, agreed up front and written into the statement of work. From the first call to the final handoff, you always know the scope, the timeline and exactly where things stand.

01

A defined scope, up front

Every engagement is defined upfront with a clear scope, timeline, and investment. If an unforeseen challenge emerges, we communicate them early and agree on the next steps together.

02

Your diagnostic carries into the build

Choose to move forward within 60 days, and your diagnostic becomes the first phase of the engagement. The insights, decisions, and investment carry seamlessly into the build.

03

Your repository, from day one

Development happens in your GitHub or GitLab organization using your repository. Your code, history, and documentation belongs and remains with you when the engagement is complete.

04

Named engineers on every call

The two people who write the code are the two people you talk to. No account manager, no handoff to someone you have never met.

05

A shared checkpoint in week one

The first week is a checkpoint we reach together, where we confirm scope, data and direction. If the fit is not right for either side, you can pause the engagement and we return your investment in full.

06

Guaranteed overlap with your hours

Our team is based in Mumbai with daily overlap across US Eastern, Central European and APAC time zones, giving you reliable access for live discussions and regular progress updates.

From scope to shipped, in four steps

VerifTrix follows the same sequence on every engagement, so you always know what's next.

01

Scope honestly

We size the problem, flag risks, and give realistic timelines, with no padding and no guesswork.

02

Build & test

Models and systems are built incrementally, with tests written alongside the code, not after.

03

Document everything

Architecture, decisions, and trade-offs are written down so your team isn't dependent on memory.

04

Hand off clean

Deployed and explained, so your team can operate and extend it without us in the room.

Three systems, in full technical detail

Our portfolio features systems we've designed and engineered ourselves. They offer a clear view into our technical approach, architectural decisions, and the trade-offs behind building production-ready software.

EXPAND ANY PROJECT · PROBLEM · CONSTRAINT · BUILD · OUTCOME · STACK
Bias-aware, automated dermatological triage engine
CLINICAL TRIAGE & DECISION SUPPORT · Internal build, DermaTrust AI

Bias-aware, automated dermatological triage engine

THE PROBLEM

Clinical networks face severe bottlenecks in diagnosing skin lesions, but deploying standard AI is dangerous. Existing deep learning models suffer from “majority-class collapse”: they achieve high nominal accuracy by blindly guessing common, benign conditions while missing rare, malignant melanomas. Worse, those models behave as uncalibrated black boxes, returning false 99% confidence scores even on blurry or non-clinical images, which destroys physician trust the first time it happens.

THE CONSTRAINT

The system could not act as an autonomous diagnostic tool because of liability and regulatory risk; it had to function purely as a triage assistant. Doctors required visual, interpretable evidence for every algorithmic decision. And the entire deployment had to operate under strict HIPAA and GDPR constraints, where protected health information could not be permanently stored on the inference server.

WHAT WE BUILT

An end-to-end clinical decision support system built for safety-first routing. We engineered a multi-expert vision ensemble (EfficientNet, DenseNet, ViT) and wrapped it in aggressive MLOps guardrails. Instead of emitting a bare prediction, we implemented Monte Carlo Dropout to compute epistemic risk, making the system aware of its own uncertainty. We added a dual-gate out-of-distribution firewall that mathematically rejects anomalies (blurry photos, non-skin inputs) before inference rather than guessing at them. We then deployed this behind a high-throughput interface with a doctor-in-the-loop active learning database, letting attending physicians override the model and stamp decisions onto airgapped, cryptographically hashed PDF reports.

High-throughput
scan intake
OOD firewall
(anomaly reject)
Multi-expert ensemble
EfficientNet · DenseNet · ViT
MC Dropout
risk scoring
Triage queue
accept / flag / reject
Doctor authorization
& active learning log

OUTCOME

Eradicated the majority-class bias, so rare malignancies were caught rather than averaged away, while uncertain scans were routed automatically to the top of the human expert’s queue. The result is a clinically usable, legally defensible triage tool that keeps learning from physician overrides, reaching a well-calibrated macro F1 of 0.75+ on unseen pathology data.

STACK

PythonPyTorchOpenCV (spatial activation mapping)StreamlitSQLite (active learning)
Explainable expense fraud and anomaly engine
FRAUD / ML · Internal build, Autoverse

Explainable expense fraud and anomaly engine

THE PROBLEM

Corporate finance teams spend enormous time manually auditing expense reports, while rule-based systems fail to catch novel or compound fraudulent patterns. When a transaction is flagged, auditors lack the immediate context to understand why it is suspicious, which turns every flag into a research task and creates a severe bottleneck in review.

THE CONSTRAINT

The system had to be built on entirely unlabeled financial data, which rules out standard supervised classification. It also could not emit a black-box probability score: it needed to be interpretable enough that a non-technical auditor could understand the reasoning behind a flag and make a decision in seconds rather than escalate it.

WHAT WE BUILT

An unsupervised anomaly detection engine that models transaction behaviour to isolate outliers without needing historical fraud labels. We layered a natural-language interface over the statistical engine so the system explains its own logic in the reviewer’s vocabulary, then packaged it into a real-time auditing dashboard where reviewers can interrogate the data conversationally.

Transaction
data
Preprocessing
pipeline
Isolation Forest
model
Generative AI
explanation layer
Streamlit auditing
interface

OUTCOME

Isolated complex expense anomalies that rule-based filters missed, materially reducing the manual review bottleneck. Because every flagged transaction arrives with a generated natural-language explanation, auditing teams make faster and more confident decisions without needing any data science training.

STACK

PythonIsolation ForestGoogle Generative AIStreamlitMongoDB
Enterprise TBML (trade-based money laundering) detection engine
FINTECH & COMPLIANCE AUTOMATION · Internal build, TradeStream

Enterprise TBML (trade-based money laundering) detection engine

THE PROBLEM

Global trade hubs face a compliance bottleneck: thousands of commercial invoices processed by manual inspection. Traditional rule-based systems are brittle and miss sophisticated trade-based money laundering tactics such as over-invoicing or deliberate misclassification of goods. Meanwhile, business stakeholders reject black-box machine learning outright, because a flagged transaction without an explanation is not a signal, it is a roadblock.

THE CONSTRAINT

The tool could not operate as an uninterpretable black box; compliance teams required human-readable risk drivers to satisfy regulatory obligations. The architecture had to handle wildly inconsistent PDF layouts, maintain strict audit trails for every human override, and include idempotent, persistence-ready state management so nothing was lost or double-counted across server restarts.

WHAT WE BUILT

An end-to-end AI gateway pairing a multimodal LLM for unstructured extraction with a custom Isolation Forest anomaly engine for financial risk profiling. We built an explainable risk-driver layer that parses feature variance into human-readable warnings, so a compliance officer sees why a shipment scored the way it did. The system carries an audit-ready telemetry ledger capturing the full provenance of every transaction, extraction, risk scoring, and final human intervention, backed by an idempotent, disk-persisted cache for enterprise-grade stability.

PDF
ingestion
Multimodal LLM
extraction
Isolation Forest
risk engine
XAI risk
drivers
Audit
ledger

OUTCOME

Automated compliance screening for high-value trade documents, cutting manual review overhead while keeping full transparency through explainable risk mapping. The system produces clean, structured audit ledgers exportable for regulatory reporting, and measurably reduces the false-positive intervention rate that makes most screening tools unusable.

STACK

FastAPI (enterprise gateway)PythonGoogle Gemini (multimodal extraction)Isolation ForestReact.jsDocker
VerifTrix icon

One rule: nothing ships unchecked

VerifTrix is a specialist machine learning studio with roots in research. That shapes how we approach every engagement. Evaluation design, calibration, bias analysis, and clear architectural documentation are built into our process from the start. We focus not only on model performance, but also on understanding its limitations, defining when it should defer, and designing systems with evaluation and maintainability in mind.

  • Reviewed before delivery
  • Documented, not just deployed
  • Built to hand off cleanly to your team
  • Scoped honestly, no padded timelines

Two engineers. Both of us, on every call.

VerifTrix is a specialist machine-learning studio, run by the two engineers who do the work. No account managers, no offshore handoffs, no layers between you and the people writing the code. When you talk to us, you are talking to the team building your system.

Prasiddhi Agarwal

CO-FOUNDER · ML ENGINEER | VERIFTRIX

Works on graph learning, fraud and phishing detection, and making risk models explain themselves. Leads fraud, anomaly detection and forecasting engagements at VerifTrix.

  • Machine Learning Research Intern   ·   IIT Patna.
    Contributed to building an interpretable Ethereum phishing detection pipeline (GraphSAGE + LightGBM).
  • Web Developer Intern   ·   Oggn Technologies.
    Developed machine learning solutions and web applications, with experience spanning computer vision, data engineering, and full-stack development.
  • First place   ·   NPCI Hackathon.
    A deep reinforcement learning framework for dynamic toll-lane allocation, recognized by India's national payments infrastructure body.
  • First place   ·   Catnip Hackathon.
    Item-level sales forecasting using Prophet, LangChain and a deployed conversational interface.
  • BTech, Artificial Intelligence & Machine Learning, Mumbai University.

Aryan Satam

CO-FOUNDER · ML ENGINEER | VERIFTRIX

Works on computer vision, evaluation design and the data layer underneath models. Leads data pipelines, model assurance and document intelligence engagements at VerifTrix.

  • Machine Learning Research Intern   ·   DJSCE
    Contributed in development of production-oriented computer vision systems for automated medical image analysis, combining model evaluation with reliable AI pipelines.
  • Published Research   ·   International Conference (ICTEAH 2026)
    Co-authored a research paper accepted at an international conference, contributing to IoT-based healthcare solutions for elderly patient monitoring.
  • Data Analyst   ·   Visual Labs IT Services
    Worked on production data pipelines, dashboarding, and analytics for live client engagements, transforming operational data into reliable business insights.
  • Technical Trainer   ·   SNDT University Affiliated Institution
    Delivered python and data analytics training, making complex technical concepts accessible to non-technical audiences.
  • BTech, Electronics & Telecommunication, Mumbai University.

The questions you'd ask on the call anyway

We would rather answer these before you spend thirty minutes finding out.

Who runs VerifTrix, and who actually does the work?

VerifTrix is a two-person studio founded by Prasiddhi Agarwal and Aryan Satam, based in Mumbai, India. We are both engineers with published, peer-reviewed research and hands-on experience with machine learning.

There is no offshore handoff: the people you talk to are the people who write the code. Every engagement runs on a defined scope and a single agreed investment, set before we begin, so you get complete clarity on the outcome, the process, and the commitment from day one. That level of transparency is the foundation of the trust we build.

Are the projects in your Work section client engagements?

No. Every project in our Work section is an original build designed and engineered by our team. We share them because they provide a genuine look at our engineering standards, architectural thinking, and the decisions that shape production-ready systems.

Who owns the code and the models, and how is everything delivered?

You own everything, from the first commit. By default we work in a dedicated repository inside your own GitHub or GitLab organisation, with access granted to us for the length of the engagement, so the code and models are yours as they are written. If you would rather not grant repository access, we can deliver a self-contained, containerised (Docker) handoff instead, whichever suits your team.

There are no recurring licence fees for anything we build; it is yours outright. Any third-party services your system relies on, such as an LLM API or cloud infrastructure, run on your own accounts and keys, so that usage stays under your control and in your name. Every system is delivered with documentation and a handoff guide, so your team can operate it independently.

How do you handle time zones?

We are based in Mumbai and hold a minimum of four hours of live overlap each working day with US Eastern and Central European time. That window is when you can reach us directly for calls and quick decisions. The build itself runs on our hours, and the final handoff happens on the date we agree together. Written updates land before your morning, every day an engagement is active.

How do you handle NDAs and sensitive data?

We sign an NDA, yours or a mutual one, before any data moves. Wherever possible we start on synthetic or de-identified samples, and for sensitive or regulated data we work inside your environment rather than copying it into ours.

We are selective about highly regulated data, such as health records, and take it on only when there is a clear, well-governed handling process on both sides. Designing systems around strict data constraints is familiar territory for us, and you can see one example in the DermaTrust write-up above.

How does pricing work?

Every project follows a structured engagement model with defined scope, structured milestones, and transparent commercial terms. An initial investment secures project commencement, while the remaining balance is settled upon completion of the project.

You get a real number and a real timeline on the first call. We do not bill by the hour, and we do not pad estimates to leave room for surprises.

What if our team has never worked with an outside ML studio before?

That is the usual case, and it is exactly why we start with a diagnostic rather than a build. A short, focused engagement gives you a written deliverable, a working relationship and a clear sense of how we operate, all before anyone commits to a larger investment.

The first week is a shared checkpoint. We confirm scope, data and direction together, and if the fit is not right for either side, you can pause the engagement and we return your investment in full.

Tell us what's blocked

The more specific you are, the more useful our first reply is. You will hear back with an honest scope, a realistic timeline and a clear investment. And if it turns out your needs would be better served elsewhere, we will tell you upfront rather than partway through.

Reply within one business day
A working call: your problem, and how we'd tackle it

Rather just book the call?

Thirty minutes, in your timezone. Come with the problem; you'll leave with our read on it whether or not you hire us.

Book a scoping call →

WE'RE PROBABLY NOT A FIT IF

  • You need a chatbot wrapped around an existing API and nothing more
  • You have no data yet and want us to find some
  • You're comparing hourly rates rather than outcomes
  • You need a team of ten starting Monday