Technology

Technology is a means. The problem is the point.

Two decades of databases, telecom systems, business software, companies and AI have left Rohit with a practical view: technology earns its place only when it solves a problem that a business, an organisation or a person genuinely has.

Rohit in a dark suit standing in a modern office corridor
Engineer, founder and technology lead since 2011.

Technology philosophy

Start with people and process, end with technology

Quick answer

What is Rohit's approach to technology?

Rohit treats technology as the last layer of a solution rather than the first. He begins with the people who do the work and the process as it really runs, then examines the data and systems, and only then decides whether automation or AI will help. The aim is a solution people will use every day, not an impressive demonstration.

Much of this view was formed in telecom back offices, where a fraction of a percent of wrongly rated calls could mean a large billing dispute, and in small businesses, where a counter clerk would abandon any software that slowed down a queue. Both environments punish technology that ignores how people actually work.

It is also why hype words rarely appear in Rohit's proposals. A plain description of what a system will do, what it will not do and what it depends on is more useful to a decision maker than any adjective.

Five layers of a technology problem, from people to intelligence A stack of five layers. People: who does the work and who is affected. Process: the real steps and exceptions. Data: what is recorded and how reliable it is. Systems: applications, integrations and security. Intelligence: automation, models and AI where they genuinely help. An arrow shows the order of enquiry running from people down to intelligence. People Who does the work, who decides, who is affected Process The steps, exceptions and hand-offs as they really happen Data What is recorded, where it lives, how reliable it is Systems Applications, integrations, security and operations Intelligence Automation, models and AI, where they genuinely help ORDER OF ENQUIRY
The order of enquiry used on technology problems: people and process are understood before data, systems and intelligence are designed.

Areas of expertise

Where the technology work sits

A broad range, held together by one habit: understanding the operation before changing it.

AI and intelligent systems

Useful AI is mostly careful engineering

Rohit's first model was a neural network trained by backpropagation to predict sunspot activity, during a 2004 internship at IIT Roorkee. The tools have changed beyond recognition since then. The core discipline has not: know what the model has learned, know where it will fail, and design the system around both.

Generative AI has made it possible to read, summarise, classify and draft at a scale that was impractical a few years ago. In organisations that translates into real gains: faster handling of documents and emails, better search across internal knowledge, first drafts that a skilled person can correct in minutes rather than write in hours.

The same systems also produce fluent mistakes. So the practical questions are always about design. Which tasks tolerate an occasional error that someone will catch? Where does the model get its facts? Who reviews the output, and how is that review made easy rather than a formality? What is logged, and who can see it?

Answering those questions well is less dramatic than a demo, and far more valuable.

Full page: AI and intelligent systems

Illustration of connected nodes and data paths glowing blue across a dark network map
Agentic systems link many steps, tools and data sources, which is why their boundaries need designing as carefully as their abilities.

Agentic AI

How much should an AI agent be allowed to do?

AI agents plan steps, call tools and act. Rohit's work on agentic systems, including the implementation of Workologix for one of the leading logistics companies in the United States, uses a simple ladder to decide how much autonomy each task gets.

  1. Inform

    The agent gathers and summarises information. A person decides everything.

  2. Suggest

    The agent proposes an action with its reasoning. A person chooses.

  3. Prepare

    The agent drafts the action in full. A person approves before anything happens.

  4. Act and report

    The agent acts on low risk, reversible tasks and reports every action for review.

  5. Act within limits

    The agent acts alone inside tight, monitored boundaries, with automatic escalation.

The default rule

Agents can prepare, draft and check. Anything that moves money, changes customer records, communicates externally or affects someone's health needs a named person to approve it, at least until the system has earned a higher level with evidence.

Full page: agentic AI and autonomy

Software, enterprise systems and transformation

The foundations under every intelligent system

AI sits on top of software, data and processes. When those are weak, AI makes the weakness faster. Most of Rohit's career has been spent on the foundations.

Software engineering and architecture

Rohit's engineering background runs from Oracle schema design and PL/SQL through Unix automation to application architecture for multi-location businesses. The lessons are old and still ignored: model the data carefully, because it outlives every screen; design for the exception, because that is where support calls come from; and keep systems understandable by the next person who has to change them.

Since 2011 his teams have built software for distributors, multi-location clinics, hotels and restaurants, schools and an international franchise network. Each domain looked different on the surface and turned out to share the same underlying problems: identity, inventory, money, schedules and permissions.

  • Data models that match how the business actually works
  • Integration planned from the start, not bolted on
  • Clear audit trails for anything involving money or records
  • Performance at the moment of use: the counter, the front desk, the ward
  • Documentation and handover that survive staff changes

Full page: software and digital transformation Full page: business and intelligent automation

Technology consulting

Advice that includes when not to build

Rohit advises organisations on AI adoption, agentic systems, automation, software architecture and technology strategy, directly and through RCode Intelligence.

Good consulting often saves money by stopping a project, narrowing it, or replacing a custom build with an existing tool. The questions below usually decide more than any technology comparison. Details of previous work and selected references are available on request.

Discuss a technology question

Full page: technology consulting

Technology website RCode Intelligence Rohit's professional technology practice: artificial intelligence, agentic systems, intelligent automation and data science. rcode.in
A team at their desks while one person sketches a process flow on a glass whiteboard

Questions asked early in a consulting conversation

  1. What problem costs you the most today?

    In time, money, errors or customer frustration, and how you know.

  2. What happens if nothing changes?

    Sometimes the honest answer is that nothing urgent does.

  3. Who will use the solution every day?

    And what they currently do instead.

  4. What data exists, and how reliable is it?

    AI and automation inherit every flaw in the data.

  5. What would a wrong output cost?

    This decides how much human review a system needs.

Entrepreneurship and product thinking

Building companies from Roorkee since 2011

Starting a technology business in a small Indian city teaches product thinking quickly, because every customer is close enough to tell you exactly what is wrong.

Rohit co-founded Acmez Business Solutions with Dr. Aarzoo Saini on 6 April 2011, and the business was incorporated as Acmez Technologies Pvt. Ltd. in 2017. AARHIT Systems followed the same year, then Webyfied Global in 2024 and Sciematics Insights and AIIT Roorkee in 2025. Each was started to meet a specific need rather than simply to add another company.

Product thinking, in this experience, is mostly about restraint: shipping the smallest thing that solves a real problem, watching how it is used, and resisting features that only one loud customer requested.

  • Sell the problem you solve, not the technology you use
  • Support calls are the best product research available
  • Small, steady customers build durable businesses
  • Hire people who can learn, then teach them well
  • Keep the founder close to the code and the customer

See the ventures

Emerging technologies

Following new technology without chasing it

New tools arrive every month. The useful filter is whether a tool changes what a real organisation can do, at a cost and risk it can carry.

Cloud and web

Sensible hosting, modern web applications and the discipline to avoid needless complexity.

Data and analytics

Clean, owned data first. Dashboards and models only make sense once the numbers can be trusted.

Cybersecurity awareness

Access control, backups, updates and staff awareness: the basics that prevent most incidents.

What comes next

Smaller specialised models, AI on local devices and better evaluation methods, watched with interest and tested before trusted.

Teaching and mentoring

Teaching technology by building it

Rohit founded AIIT Roorkee in 2025 to teach practical AI and IT skills, guide student research and projects, and help learners prepare for work.

The teaching approach mirrors the consulting approach. Students start from a problem, build something that runs, find out where it breaks and fix it. Theory matters, and it sticks better when it arrives as the explanation for something a student has just seen fail.

Mentoring conversations with early career engineers and founders tend to return to the same themes: learning fundamentals that outlast frameworks, writing clearly, and understanding the business around the code.

Rohit also gives talks and workshops on these subjects; topics and formats are on the Media page.

Full page: teaching and mentoring

Ask about mentoring

Two engineers at a workstation, one pointing at code on the screen while explaining it to the other

For students

What should a technology student learn first?

Programming fundamentals, data structures, databases and networking, followed by one real project taken all the way to deployment. AI tools are most useful to people who already understand what the generated code is doing.

For professionals

How should an experienced engineer approach AI?

As a new layer on existing skills rather than a replacement for them. Retrieval, evaluation, prompt design and agent limits are learnable engineering topics, and system design experience makes them easier to do well.

Insights

Technology insights

Essays on AI, software, transformation and building companies.

All insights

Questions

Questions about Rohit's technology work

What areas of technology does Rohit work in?

Rohit works in software engineering and architecture, enterprise applications, business process automation, digital transformation, artificial intelligence including generative AI and agentic AI, technology consulting and technology education. His background includes Oracle database development, Unix scripting and telecom OSS/BSS implementation.

What is agentic AI?

Agentic AI describes AI systems that pursue a goal through several steps: planning, using tools such as search, databases or other software, checking intermediate results and deciding what to do next. Unlike a single question and answer exchange, an AI agent acts. That makes clear limits, logging and human approval for consequential steps essential.

Does Rohit offer technology consulting?

Yes. Rohit advises organisations on AI adoption, agentic systems, intelligent automation, software architecture and technology strategy, mainly through RCode Intelligence and the companies he co-founded. Details of work and selected references are available on request.

How does Rohit decide whether AI is the right tool?

He starts with the process rather than the technology: who does the work, where errors and delays happen, what data exists and how costly a wrong answer would be. AI is recommended where the task tolerates occasional mistakes that can be caught, where there is enough reliable data, and where a person can review consequential outputs. Where rules or simple software will do, those are preferred.

Conversations

Working through a technology decision?

Share the situation in a few lines: the organisation, the problem and what has been tried. Rohit reads every message personally.

  • AI adoption
  • Agentic AI
  • Automation
  • Architecture
  • Technology strategy
  • Training
↑ ↓ to move, Enter to open, Esc to closeSee all results