Products

Software that fits how you already work — in any sector.

Heliosync builds software, SaaS platforms, AI systems, automation and digital infrastructure for any sector where technology can solve a real problem — affordable enough for one organisation to run, and adapted to how that one actually works. Four products so far — three live, one in development — plus the AI and engineering work that runs alongside them. Everything here carries its real status: nothing is listed as finished before it is.

The problem

Existing business software is often expensive, rigid and designed around generic workflows rather than the actual needs of individual organisations. Many businesses and institutions also continue to manage parts of their operations offline.

What we are building

Heliosync digitises those workflows through affordable, customisable software that can be adapted to a customer’s specific requirements — and brings the rest of their operations into one centralised digital system.

What we build

The offering is the engineering, not the sector.

Software, SaaS platforms, AI systems, automation and digital infrastructure, built for any sector where technology can solve a meaningful problem. The constraint was never the industry. It is whether the problem is real, whether we can build the thing properly, and whether the organisation that needs it can afford to run it.

Build technology for the problem, not technology for one industry.

Sectors we build for

To be explicit: that is scope, not a track record. It names the sectors Heliosync builds for, not sectors it has delivered in. Everything actually built sits below with its real status — three live products and one still in development. Nothing else on that list has a client or a deployment behind it yet, and none will be claimed before it does.

Built so far

What that looks like once it is built.

Four products out of the same practice, in four different sectors — healthcare, education, legal and retail — because that is where the first problems came from, not because the work stops there. Three are live, one is in development. Each is built for a single clinic, school, firm or shop, and adapted to how that one actually works rather than to a generic workflow.

Healthcare

Live

Dental HMS

A management system for dental practice — appointments, treatment records, billing and inventory in one clinical workflow. Being implemented with a dental clinic, and available to deploy now.

Dental practices run on scheduling and on records that have to be correct years later. The system is built around that pair rather than around a generic CRM: chair-side charting, treatment plans that carry their own history, and billing that reconciles against what was actually done.

APPOINTMENTSODONTOGRAM · 32TREATMENT → INVOICEPRACTICE LOADCHARTPLANINVOICE
Illustrative system schematic — how the parts connect, not a screenshot.

Education

Live

Heliosync SchoolOS

A unified digital layer for an entire school rather than a back-office system: student records, academics, examinations, finance, transport, communication and the school's own public website, connected end to end. Deployable now, with a live demo.

An ERP can manage a school. SchoolOS is designed to connect one. Everything you would expect from a school ERP sits inside it, and around that sits the rest of the institution — six role portals for management, administrators, teachers, students, parents and staff, each seeing only its own surface, over a single record that travels from admission to reports without being typed twice.

ACADEMIC YEARATTENDANCEEXAM CYCLEFEE RECONCILIATION3 TERMST1T2T3EXDUEPAIDLEDGER
Illustrative system schematic — how the parts connect, not a screenshot.

Legal

Live

JurisCore

Legal research and drafting for Indian advocates and law firms — plain-English search across High Court judgments, research answers whose every citation links to the judgment, AI first drafts exported to Word, and a workspace for each matter. Live, in early access for law firms.

A query like “WPC cases in 2026 in all courts” is read for case type, court, year and party, and run across the judgments of 25 High Courts at once; Supreme Court judgments are being added. Counsel AI answers from the judgments it retrieves, Review Matrix pulls the same fields from every document in a matter into one table, and matter files stay in the firm's own Google Drive. Each firm works in its own private workspace.

QUERY · PLAIN ENGLISHHIGH COURTS · 25COUNSEL AI · CITED ANSWERDRAFT STUDIOMATTER · FIRM’S OWN DRIVE“WPC CASES IN 2026 IN ALL COURTS”CASE TYPECOURTYEARPARTYJUDGMENTJUDGMENTFIRST DRAFT.DOCXFILESNOTESHEARINGS
Illustrative system schematic — how the parts connect, not a screenshot.

Commerce

In development

Retail POS

Point of sale and inventory for independent retail, designed to keep working when the connection does not.

A till that stops when the internet does is not a till. The design priority is offline-first operation with reconciliation on reconnect — the difference between software a shop tolerates and software a shop trusts.

TILLCLOUD LEDGERLINK DOWNSYNCEDLOCAL QUEUE
System design preview Illustrative schematic of a product still being built. Not a screenshot, and not a mock-up of one.

Healthcare

Live

Dental HMS

Dental practices run on scheduling and on records that have to be correct years later. The system is built around that pair rather than around a generic CRM: chair-side charting, treatment plans that carry their own history, and billing that reconciles against what was actually done.

APPOINTMENTSODONTOGRAM · 32TREATMENT → INVOICEPRACTICE LOADCHARTPLANINVOICE
Illustrative system schematic — how the parts connect, not a screenshot.
  • Appointments Scheduling is one of the two things the system is built around, not a calendar bolted to a database.
  • Treatment records Charting happens at the chair, and a plan carries its own history rather than being overwritten.
  • Billing Reconciles against what was actually done, which is the only version that survives a dispute.
  • Inventory Consumables live in the same workflow instead of in a second system nobody updates.

Education

Live

Heliosync SchoolOS

An ERP can manage a school. SchoolOS is designed to connect one. Everything you would expect from a school ERP sits inside it, and around that sits the rest of the institution — six role portals for management, administrators, teachers, students, parents and staff, each seeing only its own surface, over a single record that travels from admission to reports without being typed twice.

ACADEMIC YEARATTENDANCEEXAM CYCLEFEE RECONCILIATION3 TERMST1T2T3EXDUEPAIDLEDGER
Illustrative system schematic — how the parts connect, not a screenshot.
  • Student records Admission is where a record starts, and every later screen reads the same one rather than a copy of it.
  • Academics Classes, sections, subjects, timetables, lessons and homework — the structure the school year is actually taught in.
  • Examinations Exams, marks and results sit on the academic structure rather than being reports generated beside it.
  • Finance Fee structure, payments, expenses and payroll on the same calendar as the terms.
  • Six role portals Management, administrators, teachers, students, parents and staff each see their own surface of one system.
  • The school website The public site is part of the product, so the front door and the office are not two separate systems.

Legal

Live

JurisCore

A query like “WPC cases in 2026 in all courts” is read for case type, court, year and party, and run across the judgments of 25 High Courts at once; Supreme Court judgments are being added. Counsel AI answers from the judgments it retrieves, Review Matrix pulls the same fields from every document in a matter into one table, and matter files stay in the firm's own Google Drive. Each firm works in its own private workspace.

QUERY · PLAIN ENGLISHHIGH COURTS · 25COUNSEL AI · CITED ANSWERDRAFT STUDIOMATTER · FIRM’S OWN DRIVE“WPC CASES IN 2026 IN ALL COURTS”CASE TYPECOURTYEARPARTYJUDGMENTJUDGMENTFIRST DRAFT.DOCXFILESNOTESHEARINGS
Illustrative system schematic — how the parts connect, not a screenshot.
  • Judgment search Ask in plain English. The query is read for case type, court, year and party, and run across 25 High Courts at once. Supreme Court judgments are being added.
  • Counsel AI Research answers grounded in the judgments retrieved for the question, and every citation links to the judgment it came from.
  • Reading judgments An AI summary of each judgment, a chat with it and a treatment check — with binders, bookmarks and a citation map to keep research together.
  • Draft Studio AI first drafts of legal documents, exported to Word (.docx) for the advocate to finish.
  • Review Matrix Define the columns once and the same fields are pulled from every document in a matter into one table, exported as CSV. Document review and scan & translate (OCR) sit beside it.
  • Matters Files, notes, hearing dates and reminders in one workspace per matter, with the files stored in the firm's own Google Drive — and each firm in its own private workspace.

Commerce

In development

Retail POS

A till that stops when the internet does is not a till. The design priority is offline-first operation with reconciliation on reconnect — the difference between software a shop tolerates and software a shop trusts.

TILLCLOUD LEDGERLINK DOWNSYNCEDLOCAL QUEUE
System design preview Illustrative schematic of a product still being built.
  • Point of sale The till is the product. Everything else is arranged around keeping it working.
  • Inventory Stock moves as the sale is rung up, not on a nightly job that can miss.
  • Offline-first The local device is the source of truth while the link is down, so the shop never waits on a router.
  • Reconciliation When the connection returns the queue drains in order, and the ledger ends up the same either way.

Retail POS is in development. The diagram is how the parts are intended to fit together — a design, not a running interface. There is no screenshot here because there is nothing finished to photograph, and we would rather show the structure than invent a screen.

Four is what exists. Further products are planned but unnamed, and the sectors listed further up are scope rather than schedule — we will name either when it is real. The diagrams above are system schematics: they show how the parts connect, which is the part that exists first. Screenshots follow once the interfaces are finalised — we would rather show nothing than a mock-up of a screen that does not exist.

Capabilities

Work that is not a packaged product.

Most of what an organisation needs is not something anyone already sells it. These three are how the same engineering reaches a problem with no product behind it yet — listed as peers rather than as features of the software offering, because that is what they are. The same practice moves between all of them, and across every sector named above.

AI Solutions & Automation

Agents, automation and intelligent systems wired into the tools a business already runs on — built to behave sensibly when they are uncertain, not only when they are right.


Start a conversation

Custom Engineering

Enterprise applications and bespoke software built to a specific operational problem, with the architecture chosen before the framework.


Start a conversation

Digital Humans & AI Media

Synthetic presence, generative media and photoreal characters — the practice behind Shanaya and the research programme being built around her.


Meet Shanaya

Work with us

Building something that needs to be right.

Partnerships, research collaboration, investment, or a role on the team — the door is the same one.