
Mobile recruitment platform · Mar 2022 – Sep 2022
TalentOjo
Referral, tracking, and evaluation flows for a talent management mobile app.
Read case study
Software engineering studio · Pune, India
Mobile apps, websites, backend services, integrations, and Spring Boot upgrades, engineered carefully, explained plainly, and handed over in a state your team can keep building on.
Starting with code. Built to include more.
Future ambitions, not current services.
Used in real projects
What we do today
Four focused services, each grounded in work we have actually delivered. We would rather do a few things properly than list everything we could attempt.
React Native apps with clear screens, reliable API and Firebase integration, and a build you can publish to the Play Store.
React Native · JavaScript · Firebase · REST APIs
Fast, accessible Next.js and React websites, from business sites to catalogues and dashboards, built to be found in search and easy to maintain.
Next.js · React · TypeScript · Tailwind CSS · Vercel
Planned, tested upgrades of Spring Boot services and their dependencies, so older Java applications stay supported, secure, and deployable.
Java · Spring Boot · REST APIs · PostgreSQL
APIs, third-party integrations, workflow automation, and test automation that remove manual steps and make systems easier to operate.
Java · Spring Boot · Activiti · PostgreSQL · Python · Robot Framework
Selected work
Products and systems we have contributed to as part of delivery teams. Each case study states the role we played, so you know exactly what the work shows.

Mobile recruitment platform · Mar 2022 – Sep 2022
Referral, tracking, and evaluation flows for a talent management mobile app.
Read case study

School communication app · Sep 2022 – Jan 2023
Group messaging and notification workflows connecting parents, teachers, and administrators.
Read case study

Workflow automation backend · Apr 2023 – Oct 2023
A Spring Boot and Activiti backend that runs predefined business workflows and connects them to incident response.
Read case study

Quality automation · Feb 2023 – Apr 2023
Reusable Robot Framework suites that made assertion checks repeatable and reports readable.
Read case study
How we work
Clear scope, visible progress, and a clean handover. You always know what is being built, why, and what state it is in.
We talk through the business problem, the people affected, and what already exists: code, tools, constraints, and deadlines.
We agree on scope, priorities, and what “done” means, in writing, before any build work starts.
We build in small, reviewable increments and share progress you can try, not just status updates.
Functionality, edge cases, performance, and accessibility are checked against what was agreed.
We deploy, document, and hand over code, credentials, and notes so your team is never locked out.
Where agreed, we continue with improvements, upgrades, and fixes as your needs change.
Engineering standards
Principles we apply on every engagement. They are habits, not certifications, and we will tell you plainly where a project falls short of them.
Why “i.include”
An old Indian story tells of the kasturi mrug, the musk deer, who wanders the forest searching for a fragrance without realising it comes from within itself.
Our mark, a pair of antlers around an “i”, is a reminder of it. Good work rarely starts with something borrowed from elsewhere. It starts with curiosity, capability, and the willingness to build. We apply that to your product, and to ourselves: we start with software today, and keep learning so we can include more tomorrow.
Questions
Software engineering: mobile app development with React Native, websites and web apps with Next.js and React, backend APIs and integrations, workflow and test automation, and Spring Boot upgrades. Our wider ambitions do not change that this is what we deliver today.
Yes. A lot of valuable work is improving, upgrading, or extending software that already exists. We start by reviewing the code and setup, then propose changes that fit it.
After an initial conversation and, where relevant, a review of existing code. We break the work into defined parts and agree on scope in writing before starting. We do not publish fixed prices because every project differs.
Yes, where the service provides documented API access. We review limits, costs, and credentials with you first, and keep secrets out of source code.
Ongoing improvements, upgrades, and fixes can be agreed as a follow-up engagement. Every delivery includes handover documentation either way.
Send a short description of what you need using the contact form or by email. Include your current stack and timeline if you know them.
Start a conversation
A few sentences are enough to begin. We will ask the right follow-up questions.