Hi, I’m Roshan.

I’m a Bangalore-based programmer and consultant with over a decade of experience building AI-powered SaaS and recommendation engines, as well as a variety of internal systems for edtech organizations and non-profits. One thing I’ve noticed is that most breakdowns in a business come from the mess that builds up around existing technology, not because of a missing piece of technology.

You know the mess I mean: That Google Sheet that turned into a partial CRM, the Zapier workflow that was set up last fall, the AI tool the creator added right after the last demo, but nobody thought to add documentation. Everything works. Until it doesn’t.

That’s the problem I solve today, helping solo founders and small agencies, accounting firms, consultancies, etc. I’ll come into your world and map out the mess, figure out what’s most likely to break first, fix that part, and document the rest so it’s clear how things fit together — and nobody has their knowledge trapped in their own head.

You’re probably familiar with one or more of these scenarios:

  • Your team tracks leads in a spreadsheet with one tab for each month and doesn’t know how it’s integrated with the email and CRMs used by other parts of the team.
  • You’ve deployed some Zapier workflows that nobody fully understands, so errors that come up are hard to troubleshoot and fix.
  • Members of the team tried out a new AI tool without approval, so nobody really knows what data it has access to.
  • If the one person who knows the most about the tools leaves the company, nobody else will be able to hold it all together.
  • Operations are still built for a three-person company, even though you’ve grown to a dozen or more.

If that sounds like two or three of the things currently going on in your organization, come explore how I work and what outcomes you can expect,have a look at how I work. I also take on built-from-scratch projects like new websites or internal apps when that’s what’s needed. Either way, reach out!

See how I work →

I also write about all of this in public: the systems I find, the failure modes that repeat, and how I think about fixing them. The blog is the long-form stuff; the notes are me figuring things out as I go.