chapter 01 · 2020
A studio, not an agency
Founded in Chennai on a simple split: fewer clients, deeper engagements, and engineers who stay on a project long enough to care how it ages.
Chennai, India · since 2020
A studio, not an agency.
Fewer clients, deeper engagements, and engineers who stay on a project long enough to care how it ages.
every number shows its working
scroll
fig. 01 / 04
6+
Years building
Founded in 2020, headquartered in Chennai, India.
says who? — this →
How an engagement is scoped
- Design or audit engagement3wks
- MVP, design to deployment12wks
- Enterprise platform24wks
Delivered in two-week sprints, with a named lead engineer throughout.
fig. 02 / 04
50+
Products shipped
Across the seven practice areas we staff in-house.
says who? — this →
What we ship
- Web applications
- SaaS platforms
- MVPs
- AI features
- Design systems
- Backend & cloud
- Blockchain
- Maintenance
Every engagement transfers 100% of the IP to you on completion.
fig. 03 / 04
12
Verticals served
From fintech and logistics to healthcare and education.
says who? — this →
Sectors we have delivered into
- FinTech
- Logistics
- Healthcare
- Education
- Retail & D2C
- Real estate
- Manufacturing
- Hospitality
- Media
- Non-profit
- Professional services
- Public sector
Sector detail is generalised — client identities stay under NDA.
fig. 04 / 04
10+
Countries served
Overlap hours built into the sprint, not bolted on after.
says who? — this →
Where the working day overlaps
- APAC8h
- India (IST)9h
- Europe9h
- US East8h
We move our hours to meet yours rather than the other way round.
The practice, year by year
Six years, drawn end to end.
chapter 02 · 2021 – 2022
Design and engineering, one team
Design stopped being a phase that finished before development started. Design systems, component libraries and pattern work moved in-house so the thing that shipped matched the thing that was drawn.
chapter 03 · 2022 – 2023
Building for scale, not demos
Cloud-native backends, CI/CD, staging environments and monitoring became part of every build rather than a line item. Launch stopped being a one-time event clients were left to maintain alone.
chapter 04 · 2024 – 2025
AI where it earns its place
Retrieval pipelines, vector stores, chunking strategy and evaluation harnesses — the parts that decide whether an AI feature works. Most disappointing AI fails at retrieval, not at the model.
chapter 05 · 2026
Distributed by design
Clients across US, European and APAC timezones, served by building overlap hours into the sprint cadence. Live project status, approvals and invoices in a client portal, so nobody waits on a status email.
- 20202020
- 20212021 – 2022
- 20222022 – 2023
- 20242024 – 2025
- 20262026
A letter from the founder
Anyone can write the code.The discipline is deciding what not to build.
Tawheed Ahamed
Founder & Chief Executive Officer
“It fails in the scoping call.”
¶ 1 of 4
- 2020
- Founded
- 7
- Practices
- 10+
- Countries
Most software does not fail in production. It fails in the scoping call — in the moment nobody is willing to say that a feature is not worth the six weeks it will cost. By the time that decision reaches an engineer it has already been made, and everything downstream is just an expensive way of honouring it.
We built this firm around having that conversation early, out loud, and in writing. It is why scope is agreed before anyone opens an editor, why change requests carry a number rather than a shrug, and why we will tell a client that the codebase they have just inherited needs a rewrite — even when the smaller, more comfortable engagement would have been far easier to sell.
It is also why the engineer who architects your system is still the engineer answering your questions a year later. Continuity is not a perk we offer. It is the only way software stays understandable long enough to be worth maintaining.
We are not trying to win every brief that comes past us. We are trying to build the handful of systems that are still running, still fast, and still making money for someone in five years — and to be the firm they call when it is time to build the next one.
Tawheed Ahamed
Founder & Chief Executive Officer
Two ways a project runs
The difference is where the line round “us” falls.
- 01 End-to-end delivery
- 02 Team extension
We own the outcome.
We assign a product manager, lead engineer, designer and the developers the build needs, then ship it in two-week sprints against a written scope.
- Named product manager and lead engineer from day one
- Two-week sprints with a demo at the end of each
- Fixed-bid against an estimated effort
- Tests and documentation handed over with the source
best for — A defined product you want built and delivered.
The delivery loop
It is a loop, not a line.
stage 01 of 06
Scope
A call to understand goals, constraints and the systems you already run.
Nothing is billed until the written proposal is signed off.
Seven practices
Drawn before they are built.
Websites & Web Applications
Digital experiences that convert
4-8 weeks
SaaS Platforms & MVP
Launch your product lightning fast
6-12 weeks
AI-Enabled Solutions
Intelligence that transforms
8-16 weeks
UI/UX Design
Experiences users love
4-6 weeks
Backend & Cloud
Infrastructure that scales
6-10 weeks
Ongoing Maintenance
Always online, always secure
Ongoing
Blockchain & Web3
Trust in a Trustless World
12-24 weeks
All seven, in detail
What each practice ships, and how long it takes.
have a look
Selected work
Every one of them still running.
Not for a client
We have been the client too.
Two of the things we have shipped, nobody commissioned. We wrote the brief, argued ourselves out of half of it, paid for the parts we got wrong and answered the support mail. It is the shortest way we know to say that we understand what a late change costs you.
we paid for oursWhat we hold ourselves to
Each one is checkable against the contract.
Master services agreement — extract
run the highlighter over one- § 01You own everythingOn completion and settlement, all source code, assets and intellectual property transfer to your organisation. This is a contract clause, not a promise on a website.100% IP transfer
- § 02No surprises in writingScope changes adjust timeline and cost in writing before any work starts. We do not silently absorb scope creep, and we do not silently bill for it either.Written change requests
- § 03You know who is building itYou will know your lead engineer and product manager by name before the contract starts. Any team change mid-project is communicated in advance, not discovered after.Named engineers
- § 04We will tell you not toWhen we audit an inherited codebase and the honest answer is "this needs a rewrite", we say so — even when the smaller engagement would have been easier to sell.Honest technical reads
- § 05Security is not a phaseEncryption, dependency auditing, OWASP practice and least-privilege access are built into the pipeline from the first commit. We can architect to HIPAA, SOC 2 or GDPR where a project needs it.OWASP from day one
- § 06Built to be handed overUnit and integration coverage on critical paths, plus architecture and setup documentation, delivered as part of the work rather than quoted as an extra.Tests and docs included
initialled by both sides, every time6 clauses shown
Left on the board
Rated 4.9 by the people we built for.
“Exceptional team to work with. They delivered our enterprise web application ahead of schedule and the code quality was fantastic.”
Rahul M.Enterprise web application · 2 months ago
“I did an internship here and the mentorship was incredible. Very structured learning and real-world project exposure. Highly recommend for students!”
Sarah JenkinsInternship programme · 4 months ago
“IVN transformed our legacy systems into a modern cloud architecture. Their deep technical expertise in React and Node is very impressive.”
Vikram S.Legacy cloud migration · 1 month ago
Reviews left on our Google listing
every one of them realWant to know what we would tell you not to build?
Send the scope. A lead engineer replies — usually with questions rather than a quote.
- Within one business day
- NDA before any details
- No sales funnel