Who you'll be working with.
One person leads the early conversations about your business. A team takes it from there into design, engineering, launch and everything that follows.
Aditya
Aditya founded OLN Labs in Bengaluru in 2024 and leads discovery. That's the stage where a business problem becomes a scope worth building: who the users are, what the first release has to do, and what can wait for later.
He brings fourteen years across product, growth and engineering. Before OLN Labs he co-founded a bootstrapped EdTech company and scaled it to $2M ARR with no external funding. Over that time he architected real-time communication platforms, media streaming engines, code-compilation systems, virtual currencies and large social networks serving more than 20 million users.
That background shapes how discovery runs. The first questions are about how your business works and where the software will be under strain, well before anyone talks about screens.
Who handles which part.
Aditya
Works through the problem with you, looks at what you already use, and agrees where to start and what the first scope covers.
Our team
Takes the agreed scope through design, engineering, testing and launch, sharing working output at each milestone for your review.
Ongoing care
Hosting, maintenance, fixes and continued development, with the people and responsibilities for your platform agreed in advance.
The same team runs our own products.
Our team builds and runs SmartMM, SmartBDM and LessRounds, the products we own. The same people design, build and manage platforms for clients too, including the real estate system behind Easy Inventory.
Running our own products means looking after software in production every day: releases, support requests, hosting bills, the bug that only shows up on one model of phone. That habit carries straight into client work, where launch day is the beginning of the job.
Whatever the question, you'll know who answers it.
What each side brings.
From your side. One person who can make decisions about scope and priorities, and who has time set aside for milestone reviews. Access to the people who will use the software, even for an hour, because they know the exceptions nobody writes down. And access to any systems, files or accounts the work depends on.
If those three are in place, discovery moves quickly and reviews produce clear answers instead of a long thread of opinions.
From ours. A clear first scope with milestones you understand before any building starts. Working output to review at each milestone, with feedback recorded and sorted. Straight answers when something is harder than expected, raised early.
After launch, the same team stays responsible for keeping the platform running and improving it, unless you choose to take it elsewhere.
Contacts we agree on day one.
At the start of each engagement we write down where every kind of question goes.
- Who to talk to about scope and priorities
- Where milestone reviews happen and who joins from your side
- Who answers technical questions during the build
- How support issues are raised once you're live
- Who decides on change requests
- How the arrangement shifts after the first release
Will I only ever speak with the founder?
No. Aditya leads discovery. Once the scope is agreed, you work with the team handling design, engineering and delivery, through milestone reviews and the contacts set at the start.
Can you keep working with us after launch?
Yes. We can host and manage the platform and keep developing it under an arrangement we agree with you.
Are you hiring?
Open roles are listed on our careers page.
Start with a conversation.
Message us about your business and Aditya will set up the first discovery call.