Sort it out.

Custom software and AI tools for the work your existing systems don’t cover.

Connect company records, find answers across documents, track stock or handle sales enquiries. Use existing software where it fits. Build what’s missing.

See the work Discuss your project

What I build

Software for the work your team is doing by hand.

  1. Connect records and systems.

    Move records out of an old application, bring spreadsheets into a shared system, or connect information held in different tools. The work includes setting up existing software and building the parts it doesn’t provide.

  2. Find answers across messages and documents.

    The context is in your WhatsApp threads. The numbers are in your systems. Someone has to piece the answer together.

    I build tools that let you ask questions across the sources we agree to connect. For this work, the answer needs to show the messages or records behind it — and the system needs to say when it can’t establish an answer.

  3. Build tools for a specific job.

    The work can be drafting a document, recording a stock change or assessing a sales enquiry. I build the tool around who uses it, what information it needs and what should happen next.

    AI can help interpret a message or prepare a draft. A stock count or a pricing rule may only need ordinary software. I choose based on the task.

  4. How I work

    Start from how the work happens now.

    Tell me what your team is trying to do, which tools it uses and where someone has to step in. A recurring question is a useful starting point. So is a report assembled by hand, an old application that needs replacing or information copied between systems.

  5. Use what fits. Say when it isn’t worth building.

    For one client the right software already existed, so I configured it and moved the records in rather than building a replacement. For another I finished an accounting migration, reconciled it against the original, then advised against switching it on — what it replaced was cheap enough that the change didn’t pay.

    Completing a build isn’t a reason to recommend using it.

  6. Work where your team works, and make the limits clear.

    If the task belongs in WhatsApp or email, I’ll look at delivering it there; if it needs a screen to review a draft or check stock, I’ll build that. For a tool that answers questions, you can inspect the sources and see when it cannot answer; for one that acts, we agree which steps run on their own.

    Access to the data, and what it costs to run, are part of that decision.

Selected work

About

You shouldn’t need to become the technical person to get the software you need.

I’m Manas Taneja, and I work as a forward-deployed engineer: I sit with your team, learn how the work actually happens, then build and run the software inside your systems. You work directly with me throughout.

You don’t need to arrive with a technical specification. Show me the task, the tools you use now and where the work gets stuck.

Tell me what you need the software to do.

What does your team keep doing by hand? What can’t your current system do? Tell me what happens today and what you want to change.

Email me about the work Book a call Twenty minutes, on a call

hello@sortai.in New Delhi — Delhi NCR in person, everywhere else over a call.