Octran

About Octran

Why we’re building
Octran.

Your CRM knows contacts, accounting knows invoices, and the inbox knows conversations, but your team still has to reconnect the work. Our first product, Octran Nexus, is being built to keep recurring operations in context.

Meet the team →Our vision

Nexus MVP in development. We’re seeking design-partner conversations around one recurring mid-market workflow.

Four perspectives. One shared context.

The operating pattern

One shared record of
what is really happening.

Capture a company’s operational reality, map it into a typed, living graph, and let governed agents work on top of it, with the humans who own the business approving anything that matters.

Understand the work.

Start with the records, relationships and exceptions behind a recurring task. Give the team a shared picture before preparing its next step.

  • Customerswho, history, open conversations
  • Recordsinvoices, documents, work orders
  • Ruleswhat may be prepared, what needs review
  • Exceptionswhat broke before, and who decided
A company’s knowledge, connected around the work

Build around real work

Product and engineering begin with the recurring tasks inside a business.

Build

Bring the perspectives together

Customer understanding and operating context inform the same working picture.

Connect

Keep responsibility with people

AI prepares the work. The people responsible stay in control of important decisions.

Review

Shared context. Human judgment.

The conviction our whole team builds around.

Our conviction

Built to be trusted in the moments that matter.

The standards we use to decide what Octran should show, automate, and leave for an operator to decide.

3

principles, no exceptions.

Honest

Honest by construction

Illustrative workflows are labeled illustrative. We show what is known, what is prepared, and what still needs a human decision.

Reviewable

Reviewable by design

Routine preparation can move quickly. Customer messages, bookings, payment reminders and other consequential steps stay with an approver.

Context

Context over novelty

The useful part is the connected business context around a task. Models can change; the work record and its boundaries should remain clear.

Important actions stay visible and reviewable before they leave the workspace.

The people building it

Small team.
Shared conviction.

Our four-person team is building around one conviction: AI should prepare the work, while the people responsible for a business stay in control of the decisions.

SC

Swarnim Chaudhuri

CEO & Co-Founder

SB

Swastik Biswas

CTO & Co-Founder

IK

Ishhan Kheria

Operations Executive & Co-Founder

PC

Pratham Choubey

Sales Executive

HOW THE TEAM WORKS

Different perspectives.
One clear handoff.

Our four-person team connects customer understanding, product and engineering around the work businesses actually do.

01

Understand

Start with the people doing the work.

Listen to the workflow owner. Learn the records, recurring tasks and exceptions before deciding what to build.

  • Workflow owner
  • Recurring task
  • Real constraints
02

Shape

Turn understanding into product scope.

Agree the information needed, the prepared output and the review point. A useful handoff carries those decisions together.

  • Permitted context
  • Prepared output
  • Review point
03

Build

Learn from a focused first version.

Build the agreed workflow with the team, then use their feedback to decide the next step.

  • Focused MVP
  • Team feedback
  • Next decision
Output A workflow worth buildingThe business owner keeps the important decisions.

Bring one recurring workflow.

Tell us what your team keeps chasing and what should stay under your approval.

Request early access →Careers →