Read FAQS

A 45-minute screen-shared session on Google Meet or Zoom. We open the real product and walk through a scenario built around how your team works, rather than a generic tour. Tell us in advance what you want assessed and we prepare that case. Afterwards you get a written summary of what was shown, what it would take and what it would cost.

No. Most useful conversations start from a problem rather than a specification. We map your current process — including the parts living in spreadsheets and WhatsApp — and write down what success has to look like before proposing anything.

No. The demo and the initial scoping conversation are free, and there is no obligation to continue afterwards.

Yes. We are based in Chennai and work remotely with clients elsewhere. Our products already support multi-language and multi-currency operation, and demos run on video calls in whatever timezone suits you.

Six practices under one delivery team: AI Solutions, Software Development, Web & Mobile Development, Creative Studio, Video Production and Digital Marketing. The people writing the software, designing the interface and running the campaign are in the same room, so nothing gets lost between agencies.

Yes. Plenty of engagements are a single piece of work — one video, one website, an SEO retainer. There is no requirement to buy a bundle.

If an existing product fits around eighty per cent of your process, buy it — we will tell you so rather than quote a build. Custom earns its cost when the process is your competitive advantage, or when no product covers your compliance obligations.

If you need push notifications, offline use or device hardware such as a camera or scanner, an app earns its keep. Otherwise a progressive web app usually reaches more people for less money and avoids app-store review delays.

Applied AI built into software people use daily — speech turned into structured clinical records, diagnostic image analysis, document extraction into your ERP, assistants that answer only from your own documents, and forecasting that feeds real planning screens. All of it is already running inside our products.

That depends entirely on direction. Ungoverned generation looks generic; a shot list with deliberate lighting, lensing and grading does not. We approve stills with you before committing to a full render, and real product footage can be composited into generated scenes.

Nine production platforms: QR Pro eVerify for pharmaceutical Schedule H2 compliance, the Auto Production Planning System for manufacturing, Advocate Pro for legal practices, Restaurant Pro for restaurants, and DentalCare Pro, PhysioFlow, AI Vet Pro and EyeCare Pro across healthcare, plus News Pro for publishing.

They are built and running. Every product page on this site describes a system that exists — which is why we can demo them live rather than showing slides.

Yes. Configuration covers most needs — roles, branches, workflows, document templates, languages and branding. Where your process genuinely differs we quote the change as development work rather than pretending configuration will cover it.

Yes. Multi-branch operation is built into the clinical and hospitality products, including per-branch permissions, separate schedules and consolidated reporting across sites.

Usually. We build documented APIs and have connected accounting, payment, messaging and lab systems before. We check feasibility against your specific systems during scoping rather than promising it blind.

Schedule H2 requires serialised, verifiable identification on pharmaceutical packaging so a consumer or inspector can confirm a pack is genuine. QR Pro eVerify handles serialisation, the digital leaflet, consumer verification and the audit trail behind it.

Against a defined scope, phased so costs attach to phases rather than arriving as one unexplained number. We give a written estimate after discovery. Retainer work such as marketing is quoted monthly.

A focused first version of a custom platform is typically eight to sixteen weeks depending on integrations and data migration. We phase delivery so something is usable well before everything is finished. A sixty to ninety second video is usually three to four weeks from approved script.

Yes. Source code, database schema and documentation are yours, in your repository. Design work is handed over as editable source files with the exports and usage guidelines. We are not interested in holding a client through access.

You do. We work inside accounts registered to your business, so if we stop working together you keep the history and the data.

No. Marketing runs in three-month cycles because that is the shortest honest window to judge a channel, and either side can stop at the end of one. Project work is bound to the agreed scope, not to a minimum term.

Two structured rounds per deliverable for design and video work, which is normally enough because we agree direction before detail. Further rounds are quoted openly rather than absorbed silently or refused.

Wherever your obligations require. Cloud hosting is the default, but the products can be deployed on infrastructure you control when data residency or internal policy demands it. We agree this during scoping, not after launch.

No. Where we use third-party models we use configurations that exclude your data from training, and for sensitive workloads we deploy models you host yourself.

Every AI output we ship is reviewable and overridable by a person, and the system records who accepted or changed it. For clinical and compliance work that audit trail is not optional — the model flags, a human decides.

Yes. Compliance-grade systems are built with immutable audit logging, versioned records, role-based permissions and regulator-ready exports. That is a requirement for GMP manufacturing and Schedule H2 work, so it is designed in from the first schema rather than bolted on.

Through role-based permissions, so a receptionist, a clinician and a branch manager each see only what their role needs. Permissions are configurable per branch where the product supports multiple locations.

Yes. Support covers monitoring, backups, an agreed response window and a roadmap that keeps moving after go-live. The terms are written into the engagement rather than left vague.

Yes, including from spreadsheets and legacy software, without losing history. Migration is rehearsed at least twice before the real run, and launch happens with a rollback ready.

Yes. Training is part of delivery, and user acceptance testing is done with the people who will actually use the system — not only with managers. You also receive a handover pack so the knowledge does not leave with one person.

You can. You hold the code, the schema, the documentation, the design sources and the ad accounts. We would rather be kept because the work is good than because leaving is difficult.

Often that is the better option, and we will say so. We audit an existing site or system first — sometimes fixing performance, structure and tracking is the cheaper and faster route than a rebuild.

Paid channels produce measurable enquiries within weeks. SEO is slower — meaningful movement typically takes three to six months. Anyone promising faster is either buying risk or guessing.