Engineering for Clients, From a Team That Ships Its Own Products
Twelve service lines, one way of working: two-week sprints with a demo each time, your cloud account, your source code, and the IP transferred to you on final payment.
Build
Software people use every day, designed and engineered by one team.
-
SaaS product development
A multi-tenant product from architecture to go-live, built the way we build our own.
End-to-end SaaS platform engineering, from architecture to go-live. We build products designed for multi-tenancy, observability and scale from day one.
Whether you are shipping an MVP to validate an idea or scaling an existing product to enterprise customers, the rigour is the same: a typed end-to-end stack, automated CI/CD, audit logs, role-based access control and security hardening built in.
What is included
- Architecture and data model
- Multi-tenancy and billing
- Backend and frontend
- Deployment, monitoring, scaling
CAPilot and YesDoctor run on exactly this foundation.
Discuss saas product development -
Web application development
Portals, dashboards, internal tools and customer-facing web apps in React and TypeScript.
Bespoke web applications shaped to how your business already works, not the other way around. Client portals, admin panels, dashboards and public-facing platforms.
Every project ships with a considered UI design system and a precise frontend. We integrate with what you already run, your CRM, ERP, accounting tools or identity provider, and disappear into the workflow.
What is included
- React and TypeScript frontends
- Server-rendered apps where speed matters
- Client portals and admin panels
- Accessibility and performance budgets
JDR ARMS, the CIB&RC registration portal, is a web application built this way.
Discuss web application development -
Mobile app development
Android and iOS apps in React Native, with offline support and push notifications.
Field, customer and staff apps for Android and iOS from one codebase in React Native, with native modules where the device matters: camera, GPS, Bluetooth, background location.
We design for Indian conditions: patchy networks, shared devices, low-end phones. Offline-first data, small bundles and clear sync states are the default, not an add-on.
What is included
- React Native for Android and iOS
- Offline-first data and sync
- Push notifications and deep links
- Play Store and App Store release
VidyaPilot’s parent and driver apps are built on this stack.
Discuss mobile app development -
UI and UX design
Research, flows, design systems and high-fidelity screens, designed for the people who will use them daily.
Product design grounded in how the work is actually done: interviews at the desk, flows drawn before screens, and a design system so the product stays consistent as it grows.
We design for the clinic receptionist, the CA’s article clerk and the bus driver as carefully as for the owner, because those are the people who decide whether software gets used.
What is included
- User research and journey maps
- Wireframes and prototypes
- Design system and components
- Usability testing
Connect and automate
The parts that make software work in the real world: devices, other systems and AI that acts.
-
AI and agentic automation
Assistants that answer from your data, remember decisions and carry out multi-step work.
Personal AI assistants and agents built into the software people already use. They answer from your own records, keep the reasoning behind past decisions, and carry out routine multi-step work within the limits you set.
We work with the major model providers and with local models where data must not leave the premises, and we build the retrieval, memory and integration layers that make an assistant trustworthy rather than merely fluent.
What is included
- Assistants inside your product
- RAG, memory and decision logs
- Workflow agents with approvals
- Private and offline deployment
CAPilot AI and YesDoctor AI are live examples.
Discuss ai and agentic automation -
IoT and embedded systems
Hardware, firmware and cloud for devices in the field: sensors, displays, GPS and announcement systems.
The full stack for connected devices: hardware selection, firmware, MQTT or HTTP edge connectivity, device provisioning, real-time dashboards, alerting and command-and-control flows. Built for fleets in production, not lab demos.
Our current work includes GPS fleet tracking for school transport and passenger information and announcement systems for rail, where displays, audio and the control software have to be engineered and tested together.
What is included
- Hardware and firmware design
- MQTT and edge connectivity
- Real-time dashboards and alerts
- Field commissioning and support
VidyaPilot’s school bus tracking (STIS) runs on this work.
Discuss iot and embedded systems -
API and system integration
REST and GraphQL APIs, payment gateways, WhatsApp, Tally, GST portals and third-party SaaS.
Connecting systems so a platform works in the real world: public and partner APIs, payment gateways, messaging channels and the government and accounting systems Indian businesses depend on.
We document every API, version it, and monitor it. Integrations are built to survive the other side changing, with retries, idempotency and clear failure reporting.
What is included
- Public and partner APIs
- Payments (Razorpay, Stripe)
- WhatsApp, email and SMS
- Tally, GST and Income Tax portals
YesDoctor’s WhatsApp desk and CAPilot’s GST workflows are built on this work.
Discuss api and system integration -
Data engineering and BI
Pipelines, warehouses and dashboards that executives actually open.
Data infrastructure that turns raw signal into decisions: ETL pipelines, warehouses, document extraction and reporting layers over the systems you already run.
We design for the questions the business asks on Monday morning, not for the diagram. Every dashboard ships with the definitions behind each number written down.
What is included
- ETL and data warehousing
- Document extraction and classification
- BI dashboards and scheduled reports
- Data quality and lineage
Run and assure
Keep it secure, tested and running, with the engineers who built it still on the account.
-
Cloud, DevOps and security
Azure infrastructure, CI/CD, monitoring and hardening that holds up under an audit.
Production-grade Azure infrastructure with CI/CD pipelines, monitoring, observability and security hardening built in. We treat security and compliance as features, not afterthoughts.
Migrating from a legacy host, setting up zero-downtime deploys or passing an enterprise security audit: we ship infrastructure that holds up under scrutiny, with DPDP Act, IT Act and GDPR-aware patterns by default.
What is included
- Azure, AWS or GCP infrastructure
- CI/CD with GitHub Actions
- Monitoring and alerting
- Security review and hardening
-
Hardware and software testing
Functional, performance, security and field testing, for software alone or for devices and software together.
Independent testing for systems we build and for systems you already have. Test plans written from requirements, automated regression suites, load and performance testing, and security review before release.
For hardware products we add bench and field testing: environmental and electrical checks, firmware test harnesses, end-to-end trials with the real displays, sensors and networks, and acceptance test reports your customer can sign.
What is included
- Test plans and acceptance criteria
- Automated regression and load tests
- Security and penetration review
- Hardware bench and field trials
-
Maintenance and support
Defined response times, monitoring, upgrades and the same engineers who built the system.
Keeping software running is most of its life. We offer support contracts with defined response times, proactive monitoring, security patching, dependency upgrades and small improvements each month.
The engineers who built the system stay on the account, so a 2 a.m. incident is handled by someone who knows why the code is the way it is.
What is included
- SLA-backed support contracts
- Monitoring and incident response
- Security patches and upgrades
- Monthly improvement hours
We run CAPilot and YesDoctor in production ourselves, under the same discipline.
Discuss maintenance and support -
Technical consultancy and R&D
Architecture reviews, technology selection, discovery sprints and a roadmap you can execute.
Senior engineering judgment when you need it. Architecture reviews, technology selection, scalability planning and emerging-tech R&D.
For early-stage teams we run discovery sprints that turn a vague idea into validated MVP scope. For established teams we audit existing systems, find the scaling bottlenecks and produce a 6 to 12 month technical roadmap.
What is included
- Architecture and code review
- Discovery sprint and MVP scope
- Legacy modernisation plan
- Proof of concept builds
How We Engage
Every project starts with a free scoping call and ends with a written scope, timeline and an itemised number. No price list, because no two of these systems are the same.
- Sprints
- Two-week sprints with a working demo at the end of each one.
- Timelines
- A focused MVP takes 8 to 12 weeks. A full platform takes 3 to 6 months.
- Ownership
- Full IP and source code transfer to you on final payment, written into the Statement of Work.
- Commercial models
- Fixed price, time and materials, or a dedicated team. Every proposal itemises PM, QA and DevOps.
- Stack
- .NET 8, React with TypeScript, SQL Server and Azure by default. We say so during scoping if your project needs something else.
- Hardware and field work
- IoT devices, field testing and support contracts are scoped after a short discovery, because the bill of materials and the sites decide the plan.
How a Project Runs
- 1
Discovery
A scoping call, then a written scope, timeline and itemised number. No obligation.
- 2
Architecture
Data model, tenancy, integrations and infrastructure decided and documented before code.
- 3
Build
Two-week sprints. You see working software every sprint, not a reveal at the end.
- 4
Launch
Production deployment on your cloud account, monitoring in place, source code handed over.
- 5
Grow
Support contracts with defined response times. The engineers who built it stay on the account.
Industries We Have Built For
Our own products are in accounting, healthcare, education and retail, so those are the domains where we start with the most context.
- Accounting and legal
- Healthcare and clinics
- Education
- Retail and pharmacy
- Fintech
- Transport and mobility
- Enterprise software
- Startups and SMEs
Frequently Asked Questions
How much does custom software or SaaS development cost?
It depends on scope, and we would rather give you a real number than a range from a website. After a free 30-minute scoping call you get a written scope, a timeline and an itemised estimate, with project management, QA and DevOps as visible lines. The biggest cost drivers are the number of user roles, third-party integrations, compliance requirements and, for IoT work, the hardware and the sites. We offer fixed price, time and materials, or a dedicated team.
How long does it take to build a SaaS product?
A focused MVP takes 8–12 weeks. A full-featured platform takes 3–6 months. We work in two-week sprints and demo working software at the end of every sprint, so you see progress continuously rather than at a single hand-over.
What technology stack does TulsiX use?
Our default stack is .NET 8 (C#) for the backend, React with TypeScript for the frontend, SQL Server for data and Microsoft Azure for hosting, CI/CD and monitoring. We run our own products on this stack. If your project needs something different, such as Node.js or PostgreSQL, we say so during scoping rather than forcing a fit.
Which engagement models do you offer?
Three: fixed price for well-defined scopes, time and materials for evolving products, and a dedicated team for long-term engagements where you want consistent velocity. Every proposal itemises project management, QA and DevOps so there are no hidden line items.
Who owns the code and IP?
You do. For custom development, full intellectual-property ownership transfers to you on final payment, and this is written into the Statement of Work before work begins. We hand over source code, infrastructure configuration and documentation.
Do you work with clients outside India?
Our clients today are in India, and our team is in Faridabad (NCR) and Mathura. Delivery is already remote-first: written sprint updates, shared issue tracking and direct access to the engineers. That works just as well for a team outside India, so if you are abroad, write to us and we will agree overlap hours for your time zone.
Do you provide support after launch?
Yes. Post-launch support contracts cover monitoring, security patches, dependency updates, bug fixes and small enhancements, with defined response times for production incidents. The engineers who built your product stay on the account.
Can you take over or modernise an existing application?
Yes. We start with an architecture and code review, document the risks, and then propose either incremental modernisation or a phased rebuild. Common cases are legacy PHP or .NET Framework systems moving to .NET 8 and Azure, and single-tenant apps being converted to multi-tenant SaaS.
Get a written scope for free
A 30-minute call with the founder, then a scope, a timeline and an itemised number in writing. No obligation.