Software systems for businesses that run on operations.

Focused, reliable software for teams that manage customers, field work, inventory, service, and daily operations.

Focus
Operations-led businesses
Product
MARC
Built for
Field, service, inventory
Based in
India

Vertical software for work that has to move correctly.

Array96 builds around the handoffs that decide whether a service business feels in control: customer context, field work, stock movement, documents, and reporting.

Service work stays owned

Tickets, preventive visits, escalations, and field assignments stay tied to a responsible person and next action.

Inventory matches the job

Spares, serial numbers, documents, and warranty checks are connected to the service work they support.

Managers see the backlog

Reporting answers what is pending, what moved, and which customer commitment needs attention.

MARC makes a medical equipment dealer's day accountable.

MARC by Array96Systems is sales, service, and asset tracking for medical equipment dealers. It connects service tickets, preventive maintenance, warranties, AMC/CMC contracts, inventory, sales workflows, documents, and field engineers into one operational system.

What the product replaces

Status buried in WhatsApp threads, stock updates split across spreadsheets, and service history reconstructed only after a customer asks.

View MARC product

Run service work

  • Tickets
  • Preventive maintenance
  • Field engineers

Control commercial coverage

  • Warranties
  • AMC / CMC contracts
  • Sales workflows

Keep records aligned

  • Inventory
  • Serial numbers
  • Spares movement

Close the paperwork

  • Documents
  • Visit notes
  • Reporting

Practical software, built from the workflow outward.

Array96 does not start with an admin dashboard and work backwards. The build starts where the operating risk is highest: handoffs, ownership, service history, inventory, and reporting.

  1. Map the real day

    We start with how tickets, calls, spares, documents, and customer commitments move through the team.

  2. Ship the smallest useful system

    The first release covers the work that needs accountability now, then expands only when the process proves it.

  3. Keep control inside the product

    Tenant isolation, role clarity, and operational reporting are treated as product requirements, not late add-ons.

A good fit when operations are already outgrowing informal tracking.

The current focus is narrow on purpose. Array96 works best where the daily workflow is specific enough to deserve its own system.

  • Medical equipment dealers coordinating service, contracts, inventory, and field engineers
  • Field-service-heavy businesses with work split across calls, chats, sheets, and documents
  • Small and mid-sized teams that need operational control before they need a broad ERP
  • Teams ready to replace spreadsheet-and-WhatsApp tracking with one accountable system

Building something operationally complex?

Tell us where the workflow is breaking and what your team needs to control.

The first conversation covers

  • Which workflow is breaking first
  • What data and documents already exist
  • Where a focused first release should stop