Skip to content

About i.include

Starting with code. Built to include more.

i.include is a software engineering studio based in Pune, India. Today we build and modernize mobile apps, websites, and backend systems. The name reflects where we want to go next.

The kasturi mrug

In a story told across India, the musk deer, the kasturi mrug, catches a beautiful fragrance and spends its life searching the forest for its source, never realising the fragrance comes from within itself.

We take a simple lesson from it. Businesses often look elsewhere for answers they could build themselves, with the right help. Engineers often assume the solution is the next tool or framework, when it is usually careful thinking about the problem in front of them.

Our mark, a pair of antlers around an “i”, is a reminder of that idea: discover the capability that is already there, then develop it into something real.

Focused today. Open tomorrow.

“i.include” means we do not believe in a fixed ceiling on what we can learn to do. Over time we hope to include other creative and technical disciplines. For now, we are deliberately focused on software engineering, because that is where our experience and evidence are.

What we deliver now
  • Mobile apps
  • Websites & web apps
  • Backend & APIs
  • Upgrades
  • Automation
Where we may grow
  • Intelligent automation
  • Design
  • Audio
  • Film

Who you will work with

i.include is led by Sunil Otale, a software engineer with hands-on experience across React Native, Next.js, Java and Spring Boot, workflow automation, and test automation. The work listed on this site comes from that experience.

Sunil Otale on LinkedIn (opens in a new tab)

How we hold ourselves accountable

Maintainable over clever
Clear structure and naming, so the next developer, ours or yours, can understand and change the code.
Secure by habit
Secrets stay out of source code, inputs are validated, and dependencies are kept current.
Tested where it matters
Automated checks guard critical behaviour; we tell you plainly what is and is not covered.
Fast and accessible
Performance and accessibility are designed in from the start, not patched in before launch.
Transparent decisions
Technical trade-offs are explained in plain language, so you can make informed choices.
Documented handover
Every engagement ends with notes on how things work, how to run them, and what to watch.

Have a project in mind?

Tell us what you are building or what needs fixing. We can work out the sensible next step together.

Discuss your project