Your business runs on memory. Let's fix that.
You know what needs to happen next. Your team roughly knows what they're doing. Clients are mostly happy. But somewhere in there, things are held together by one good employee, a Sunday-night spreadsheet update, and the fact that nothing has gone seriously wrong yet.
I help business owners find where the cracks are, build systems around their actual process, and bring in the right technology to make those systems run without constant intervention.
Most businesses don't have a tools problem.
Before I recommend anything, I'm going to ask you some uncomfortable questions.
- Does your team know the exact deadline for every live project right now?
- If your best person quit tomorrow, how much of your process would walk out the door with them?
- You have three different tools for tracking work. Why? What would it take to use just one?
- When was the last time you wrote down a decision you made about how the business runs?
Most business owners can't answer these cleanly. Not because they're bad operators. Because nobody has ever sat them down and asked.
That's where I start.
Four steps. In that order. Always.
Audit
I spend time understanding what is actually happening in your business, not what you think is happening. Where does work get stuck? What information lives only in someone's head? Where is the process invisible?
Design
Before writing a single line of code, I design the system. What are the steps? Who owns each one? What gets recorded, and where? Software built on a broken process is just an expensive broken process.
Build
Once the system is clear, I build the technology around it. This could be an automation that cuts three hours of manual work per week. Or a custom tool that does something no off-the-shelf product can do. The technology follows the system, not the other way around.
Handoff and Training
You and your team will know exactly how to use what I built. I don't hand over a black box and disappear.
Here's where I can make a real difference.
Operations Audit
A clear map of where your business is leaking time, money, or both. You walk away with a prioritised list of what to fix and in what order.
Workflow Automation
Repetitive tasks that eat hours every week, automated. Your team focuses on work that actually needs a human in the loop.
Custom Software
When no existing tool does exactly what your process needs, I build it. Built around your system, not the other way around.
AI Implementation
Not AI as a buzzword. Specific, practical use of AI for tasks like processing large volumes of documents, generating structured outputs, or automating research that would otherwise take days.
I'll be straight with you.
SmartAlgorhythm is young. I don't have a wall of client logos to show you. What I do have is real.
The data pipeline that was held together by prayers
At my previous organisation, data was flowing between three platforms: the internal dashboard, Freshsales, and Mixpanel. The problem was that it wasn't really flowing at all. Sales was working off numbers that didn't match what the product was actually seeing. Payment data was inconsistent because there was no tagging system. Nobody knew which number to trust.
I built a short-term fix to get accurate numbers immediately. Then I introduced a tagging system to make sure the problem wouldn't repeat. Then I went through the codebase, line by line, and fixed the root causes one by one. It was not glamorous work. It needed someone willing to go deep and stay there. By the end of it, data consistency across all three platforms was sitting at ~90%.
Current engagement
I'm finalising a contract with a business in a traditional manufacturing industry to build their internal systems.
Why I do this
Six years ago, I built a personalised email system for a Secret Santa event. It was a Google AppScript template. Nothing fancy. But I remember watching it work and thinking: I had a problem, I wrote something, and it solved the problem. I've been chasing that feeling since.
I've worked as an Analytics Manager, built products, shipped them, watched some of them fail, and learnt something useful from all of it. The most useful lesson came from a data pipeline that had no business being as broken as it was. Three platforms, no single source of truth, numbers that contradicted each other depending on who you asked. I fixed it by doing the unglamorous thing: actually understanding why it broke before touching a single setting.
That's the job, really. Not installing tools. Not running automations for the sake of looking modern. Understanding why a process breaks, and building something that addresses the root cause.
I'm based in Bangalore. I work with business owners who want to understand their operations clearly and build something that runs reliably, even when they're not in the room.