Our own products
Software we build and run in-house. Focused tools that solve one problem properly instead of forty problems badly.
Web and mobile apps, internal tools, automation, and AI where it actually helps. Built for other teams, and for ourselves.
Most software gets built, shipped, and quietly abandoned. We work in the opposite direction: prove the thing is needed, build the smallest version that works, then keep it alive.
Software we build and run in-house. Focused tools that solve one problem properly instead of forty problems badly.
Systems that take the repetitive work off a team's hands, connected to the tools they already use, and monitored so they don't rot.
A small number of projects each quarter for teams who need something built properly and shipped fast, by people who've already made the mistakes.
Four things we built and still run. Each one started as a problem somebody actually had, not a feature list.
An AI support co-analyst that answers from your own documentation and live operational data, and returns nothing rather than guessing when it cannot ground the answer.
Runs untrusted code without trusting it. Every submission executes inside its own disposable container, so a bad program can only break its own sandbox.
Built for the government rescue service. Admin and employee portals covering payroll, attendance, leave, tasks and announcements, with the repetitive parts handed to models.
A full-stack app deployed to Azure and AWS from the same pipeline, so neither cloud is the one that everything depends on.
Most projects don't fail. They stall, and a stalled build burns the same money as one that ships.
Four steps, in order, on every project we take. The order is the point. Most software fails because someone skipped the first one.
Find the belief the whole thing rests on, and try to break it before anyone writes code.
The least software that can answer the question honestly. Scope is cut, not padded.
Into real hands, in weeks. Nothing is learned from software nobody has used yet.
Every feature keeps its place by being used. The rest comes out.
A logistics operator running support with a team of forty. Every ticket was read twice: once to route it, once to answer it. The AI roadmap had been approved three quarters running.
Routing, summarising, drafting and a chatbot were all scheduled for the same quarter. Nobody could start one without a decision about the other three, so nobody started.
The whole roadmap rested on one untested claim: that routing was the expensive half. We checked it against six weeks of their own tickets before writing any product code.
Classification against the tags they already used. No fine-tuning, no chatbot. It has run since without a person watching it.
We take on a handful of client projects at a time so each one gets built properly. If you have an idea that needs proving, a prototype that needs to become real, or a system that keeps stalling, that's our work.
Salman founded Deadloc AI to build software that holds up after launch, the part most projects skip. He sets product direction and stays close to the engineering, so the decisions about what ships are made by someone who has to live with them.
His most recent build is ARGUS, an AI support co-analyst whose most useful property is knowing when not to answer: it grounds responses in a customer's own documentation and live operational data, and returns nothing rather than guessing.
Tell us what you're building and what's in the way. We reply to everything, usually the same day.
Already working with us? support@deadlocai.comLinkedIn