Skip to content
Dorvo Labs — Dorvo Labs LLP

Dorvo Labs LLP · AI product lab · India & international

AI systems that show their working.

Dorvo Labs is the small lab behind Dorvo and Dorvo Logistics. Everything we build runs to one set of rules: AI where it persuades, deterministic code where it must be right, a person at every approval, and a record nobody can rewrite.

or write to team@dorvolabs.com

One action, end to endIllustrative
AI proposesProposesModel unavailableDraft quotationRead enquirySummarise a threadWrite follow-upClassify an enquiryYour workflowGuardrailsNumbers · schema · policyDraft changed the price — rejectedChanged the price — rejectedDeterministic engineEnginePrice set by code, not by AIPrice by code, not AIDeterministic template · AI not consultedTemplate · AI not consultedA person approvesApprovesLeadershipApproved · LeadershipAppend-only ledgerLedger
  1. AI proposes — The model drafts the words; the price comes from code
  2. Guardrails — Numbers and policy are checked by code, not by the model
  3. Deterministic engine — Same input, same answer — code, not a model
  4. A person approves — A named person signs, and it is recorded
  5. Append-only ledger — History is never edited; corrections are new entries

What we build

What we build — and what every build ships with.

Research, design and delivery of AI-native software, for clients in India and internationally. Every system below ships with an audit trail, a person at every approval and a path that works when the model is down. Where a line is advice rather than software, it says so.

ServiceWhat it isShips with
01

Agentic AI systems

Agents that read, draft, classify and propose — with a fixed set of tools, a budget and a stop condition. What an agent may touch is written down before the first line of code.

Audit trailApprovalsFallback
02

Autonomous workflows & intelligent automation

Enquiry inboxes, quotation pipelines, approval chains, document generation. Long-running flows that survive a restart and leave a record at every step.

Audit trailApprovalsFallback
03

AI-native products

Full products, from data model to mobile app, designed so the model is a feature of the system rather than the system itself.

Audit trailApprovalsFallback
04

Cloud platforms & in-region deployment

Deployed in the region your data must stay in. In-region deployment in Doha or Dammam is already built into Dorvo.

Audit trailApprovalsFallback
05

Custom software & integration

Your ERP, accounting, CRM or messaging stays where it is. We build what is missing and connect it through documented APIs, with every exchange logged.

Audit trailApprovals
06

Consultancy & technical support

An engineer looks at your process and tells you, in writing, what to automate, what to keep deterministic and what should stay human. After go-live, support from the people who built it.

In writing

Engineering rules

Six rules every system we ship obeys.

Not aspirations. Each one lives somewhere concrete — a deterministic engine, a workflow state, a vault — and each one is running in the products you can open today.

  • AI where it persuades

    The model drafts the words of a quotation or a follow-up. It drafts; it does not decide.

    In the products: the quotation text the AI drafts

  • Deterministic code where it must be right

    Prices, margins, load plans. Engines compute them from your own data — the same answer for the same input, every time. The AI never sets a price.

    In the products: the pricing and load-planning engines

  • A person approves

    Consequential actions — a quotation going out, a price sent to a customer — wait for a named person. Two stages: Sales, then Leadership.

    In the products: two-stage approvals

  • Nothing is ever overwritten

    Versions, approvals and history are append-only. A correction is a new entry, never an edit.

    In the products: the immutable audit trail

  • An outage never blocks business

    Every AI feature has a deterministic fallback. If the model is down, the work still goes through — by the deterministic route.

    In the products: the deterministic fallback when AI is down

  • Confidential by rule, not by screen

    Costs live in a leadership-only vault — not behind a tab someone might find.

    In the products: the leadership-only cost vault

The Dorvo family

The rules, shipped.

The Dorvo platform was built to run a real engineering business end to end — and still does. Both products are live; open either.

PRODUCT HISTORY — APPEND ONLY

  1. CRMEnquiry capturein production
  2. CRMCosting and dual PDFsin production
  3. CRMTwo-stage approvalsin production
  4. CRMAppend-only audit trailin production
  5. CRMDeterministic fallback when AI is downin production
  6. CRMEnglish and Arabic, iOS and Androidin production
  7. LOGEnquiries read from email and WhatsAppin production
  8. LOG3D load planningin production
  9. LOGVendor rate cards with a hard margin floorin production

How we engage

Fixed scope. Weeks, not years.

The Dorvo platform installs in an 8–10 week programme. Client work is scoped the same way: one written scope, one production date. The people who scope it build it — and answer the email after.

  1. Step 1:

    Scope

    We write down what the system will do, what the AI may touch and what it may not, and who approves what. You have it as a document before anything is built.

    Deliverablea written scope

  2. Step 2:

    Build

    Deterministic engines and the data model first, on your real data. The AI layer goes on top, fenced from the figures it must not set, from day one. You see working software as it grows, never a reveal at the end.

    Deliverablerunning software, not slides

  3. Step 3:

    Prove

    Runs beside your current process on live work. Approvals wired, audit trail on, fallback tested by switching the model off.

    Deliverablea rehearsed go-live

  4. Step 4:

    Ship & stand by

    Production, handover and support from the engineers who built it. Scope changes and decisions during the build are recorded, not re-negotiated from memory.

    Deliverableproduction, and the people who built it

India · Gulf · international

Already handled in production.

We are an Indian LLP and our products are proven in the Gulf. The conventions below are running in the products today — we do not learn them on your project.

Gulf currencies — DorvoThe Gulf working week, built in — DorvoArabic interface at dorvo.app/ar — DorvoDoha or Dammam — DorvoEnquiries read from the channels customers use — Dorvo LogisticsiOS and Android apps — DorvoCustomer proposal and internal costing — DorvoPriced from real rate cards, never below the floor — Dorvo LogisticsThe right truck, the right load — Dorvo LogisticsSales, then Leadership — DorvoCosts, visible to leadership only — DorvoWork continues when the model is down — Dorvo

We do not publish client names. Ask us and we will tell you what we can.

Are we a fit?

Anywhere a wrong number costs money.

We are most useful where a process has a number that must be right and a moment when someone must sign. Read both columns before you write.

Good fit

  • A workflow that runs on email, WhatsApp and spreadsheets, and should run on software.

    That is the shape of problem the Dorvo platform was built to solve.

  • A place where a wrong number costs money — a price, a margin, a load.

    A model where it helps, deterministic code where the money is, a record under both.

  • One small team from the first call to support.

    The people who scope it build it. There is no delivery team behind the sales team.

Better served elsewhere

  • A large bench of developers on time-and-materials.

    We run small fixed-scope programmes. A staffing firm will serve you better.

  • A chatbot to demo rather than a process to run.

    We build software that has to survive month six.

  • A firm date before anyone has looked at the problem.

    Scope comes first so that the date we give you is one we keep.

Start here

Bring us one workflow you don't fully trust yet.

A quotation that still goes out on a spreadsheet. An approval that lives in someone's chat. An inbox nobody wants to own. Tell us the process, who touches it, and the number that must never be wrong. An engineer reads it — and comes back with what we would automate, what we would keep deterministic, where a person must approve, and a straight answer on whether we are the right people.

Talk to the team

Read by an engineer, not a sales queue. No form, no bot.

What to include

  • The process, in a paragraph
  • Who touches it
  • Where it breaks

Enquiry received · read by a person · appended.

Prefer to see it first?

Open dorvo.app or logistics.dorvo.app. Everything on this page is running there.