Before You Automate, Draw the Process on Paper
A practical method for digital transformation: map the real process, find the friction, redesign with the team, then choose automation or AI.
Technology
Technology consulting, including when not to build
Rohit advises organisations on AI adoption, agentic systems, automation, software architecture and technology strategy, directly and through RCode Intelligence.
Quick answer
Quick answer
What does a consulting conversation with Rohit look like?
It starts with the problem rather than the technology: what is costing the most today, what happens if nothing changes, who will use the solution daily, what data exists and how reliable it is, and what a wrong output would cost. Those five answers usually decide more than any comparison of tools, and they often lead to a smaller project, a different project, or none at all.
Questions asked early
What problem costs you the most today?
In time, money, errors or customer frustration, and how you know.
What happens if nothing changes?
Sometimes the honest answer is that nothing urgent does.
Who will use the solution every day?
And what they currently do instead.
What data exists, and how reliable is it?
AI and automation inherit every flaw in the data.
What would a wrong output cost?
This decides how much human review a system needs.
How the work is usually shaped
Most engagements are short and specific: a second opinion on a plan, an assessment of where AI or automation would actually pay, an architecture review before a build, or a period of hands on work with an existing team. Good consulting often saves money by stopping a project, narrowing it, or replacing a custom build with a tool that already exists.
Rohit stays close to the engineering. The advice comes from someone who still designs systems, still reads logs, and still has to live with the consequences of a poor decision in his own companies. Details of previous work and selected references are available on request.
Insights
Related essays
What Technology Leadership Means in a Small Company
What technology leadership looks like in small organisations: making architecture decisions, growing people, managing risk and staying close to customers.
Fifteen Years of Building Software for Everyday Businesses
Lessons from building business software since 2011 for distributors, clinics, restaurants, hotels and schools: customers, simplicity, support and staying power.
Questions
Questions about technology consulting
Which organisations does Rohit work with?
Small and medium organisations that do not have a large technology team, and larger teams that want an outside opinion on AI and automation. The common factor is a real operational problem rather than an interest in technology for its own sake.
Is advice available for a single decision?
Yes. A focused conversation about one decision, such as whether to build or buy or how much autonomy to give an agent, is often the most useful form of help.
Conversations
Have a question about this?
A short message with some context is the best way to start.
- Technology consulting