Studio
A small studio that ships whole products.
Strategy, design, engineering, launch, and running it afterwards. One team you can name, from the first sketch to the store listing and the month after.
Start a projectWhat we build
Six things, done properly.
Intelligent chatbots that create leads and automate workflows
A conversational assistant on your site, in your product or in your team’s tools. It answers from your own material, asks the qualifying questions a good salesperson asks, captures the lead with consent, and performs the next action: a CRM row, a booked slot, a ticket, the follow-up email.
What you get
- The assistant and the knowledge source it answers from
- Integrations with your CRM, calendar or helpdesk
- An admin view of conversations and captured leads
- Guardrails, rate limits and per-conversation cost reporting
Proof. MITRA, ExamGraph’s companion: four voices, NCERT citations, action buttons that build the test it just argued for, every message costed.
RAG and knowledge systems
Retrieval over your documents, policies, catalogues or past tickets, so an assistant or a search box answers with the actual passage and a citation, never a paraphrase from memory.
What you get
- Ingestion and chunking of your corpus
- A retrieval layer: full-text, vector or both
- Citation rendering and an evaluation set built from your own questions
- Prompt caching and a cost ceiling
Proof. ExamGraph’s NCERT grounding layer: 4,185 passages, retrieval scoped to the student’s weak chapters, citation markers replaced by exact references while the answer streams.
OCR and document extraction
Scans, photographs, PDFs and legacy paper turned into structured records you can search, validate and serve.
What you get
- The extraction pipeline
- A review gate: nothing enters production unreviewed
- Figure, table, maths and notation handling where it applies
- An audit trail of every correction
Proof. 20,695 questions from 19 books, 18,956 seeds inspected in a validation pass, figures cropped and reviewed, a watermark stripped in the alpha channel.
Web apps
Next.js and React products with real backends: auth, Postgres with row-level security, payments, background jobs, and the operational plumbing nobody sees.
What you get
- A repository you own, with CI
- A design system in code
- Tests, monitoring and a runbook
Proof. ExamGraph and OpenLobe, in production.
iOS and Android apps
Native apps that share your backend with the web, published to the App Store and Google Play under our developer accounts or yours.
What you get
- The app and its API contract
- Store listings, screenshots and review handling
- TestFlight and internal-testing tracks
Proof. Enrolled on both stores; OpenLobe’s SwiftUI app in build.
Design, data and launch
The parts of a product that decide whether it feels finished: the design system, the data model, the payment flow, the release train.
What you get
- Design tokens and components
- Schema, migrations and security policies
- Release process and hand-over documentation
Proof. Razorpay billing shared safely across two products; five WebGL themes; a serve pipeline with three gates.
How we work
Four steps, in the open.
Brief — week one
We ask a lot of questions, then write a scope you can hold us to: what ships, what does not, and what it costs.
Prototype — weeks two and three
A clickable build of the core flow, so every later conversation is about something real.
Build in the open
A weekly demo, a shared repository from day one, and decisions written down where you can read them.
Launch and run
Store submission or deployment, monitoring, and a hand-over you can actually read. Stay with us afterwards or take it in-house.
Ways to work with us
Three shapes of engagement.
Fixed-scope build
A defined product or feature, a written scope, a date. Best when you know what you need.
Product partnership
We design and build a product with you over months, from research to launch and beyond.
Team extension
Our engineers and designers inside your team, on your tools, for as long as the work needs.
Stores and launch
Registered on both stores.
Philotium is enrolled in the Apple Developer Program and the Google Play Console. We handle listing assets, review, TestFlight and internal-testing tracks and release trains. We publish under Philotium, or set up your own accounts and hand them over.
Team
Who you will work with.
Philotium is led by its two founders. Both stay on every engagement, from the first call to launch and after.
Vasanth Nagarajan
Co-founder and chief architect
Vasanth leads solution architecture at Philotium. Each brief becomes a technical blueprint before any code is written: the data model, the service boundaries, where the AI sits and how the system scales. That blueprint is what keeps a product fast, secure and affordable to run as it grows.
- Solution architecture
- Data and infrastructure
- AI system design
- Technical scoping
MEng Mechanical EngineeringUniversity of Warwick, UK
D Cowsshekhar
Co-founder and head of engineering
Cowsshekhar leads engineering and delivery. He builds the production systems behind every Philotium product, from full-stack web and mobile applications to the retrieval-augmented generation (RAG) pipelines that power our chatbots and document search.
- Full-stack engineering
- RAG and retrieval
- LLM integration
- Delivery and code quality
BE Mechanical EngineeringPSG College of Technology, Coimbatore
Questions companies ask
Six things people ask before they write to us.
How long does a build take?
A focused product or feature usually ships in six to twelve weeks; a prototype you can click is in your hands in the first two or three. We write the timeline into the scope before we start, and we tell you the moment it moves.
What does it cost?
It depends on the scope, so we do not publish a rate card. After the brief week you get a written price for the scope we agreed, and it does not change unless the scope does.
Who owns the code and the accounts?
You do. The repository, the design files, the infrastructure and any developer accounts we set up for you are yours from the start, and the hand-over is written down.
Can you publish under our developer accounts?
Yes. We can ship under Philotium’s Apple and Google accounts, or set up yours and publish there, whichever your business needs.
Do you work with teams outside India?
Yes. We are in India and work with teams wherever they are; overlap hours are agreed in the brief.
What happens after launch?
You choose: keep us on to run and extend the product, or take it in-house with the runbook and a hand-over call. Either way, nothing about the code depends on us.