About us

Enterprise systems, with the operation in view

Hyperspace develops enterprise and public-service systems across Odoo, municipal finance and citizen services, EPMS and loyalty program management. Our Map–Build–Run approach connects the requirement, the implementation and the responsibilities after delivery.

Founded
2014
Head office
Gurugram
Solution areas
04
EPMS modules
08

What we are

A build-and-run shop for enterprise and public-service systems. We work on the records, systems and responsibilities behind an operation: an Odoo requirement, a municipal finance transition, an EPMS module scope or a loyalty program's rules.

The four solution areas are Odoo Systems, Municipal & Public-Service Systems, EPMS — Enterprise Management System — and Loyalty Program Management. What holds them together is the method: map the requirement, build the system, and agree who runs it.

We are deliberately plain about a few things. The scope is written down before Build starts. What you receive at handover is named in it. And results are published only when there is a baseline and a method to report against.

Who you actually meet

The first conversation is with the person who handles that solution area. They ask about the current system and the requirement before anything is scoped or priced.

What we don't claim

No partner badges we can't show a right to, no country coverage we haven't agreed, and no compliance guarantees. Credentials are confirmed in writing on request.

How we behave

Four commitments, each one testable

Not values. Things you can hold us to, and notice when we fail.

The scope is written before Build

The requirement, dependencies and acceptance criteria are agreed in writing. The duration and fee are set for the engagement, not assumed from a template.

What you keep is named

Code or configurations, access, documentation, data definitions, training and handover materials are listed in your scope. Third-party licences are documented separately.

Run means an agreed owner

Either a support arrangement or a documented transfer to your team, with the receiving owner, supported components and remaining issues written down.

Evidence before claims

We publish what we did and what can be inspected. Numbers appear only with a baseline, a period and a method behind them.

First conversations

One desk per solution, plus the managing partner

Each desk handles first conversations for its solution area. They are where the contact form and a callback route to.

Aarav Bhatnagar

Managing partner

Co-founded the firm. Signs off every scope and handover plan personally.

Since 2014

Odoo desk

Odoo systems

Handles first conversations about Odoo requirements, including international enquiries.

Solution 01

Municipal systems desk

Municipal & public-service systems

Handles first conversations about municipal finance, revenue and citizen-service systems.

Solution 02

EPMS desk

EPMS — Enterprise Management System

Handles first conversations about EPMS module scope and how the records relate.

Solution 03

Devika Raghavan

Loyalty program management

Founding engineer on the first loyalty ledger we shipped. Still reviews every exchange reconciliation design.

Solution 04

How we got here

From one ledger to four solution areas

Dates are added here as each piece of work is approved for publication.

2014

Hyperspace founded in Gurugram, starting with the customer record behind a loyalty ledger.

MCD

Financial, citizen, revenue, tax, accounting and service-system work, including the transition from single-entry to double-entry accounting.

2026

Four solution areas: Odoo Systems, Municipal & Public-Service Systems, EPMS and Loyalty Program Management. Map–Build–Run stays the method.

Office

Gurugram, head office

International Odoo enquiries are welcome. Where we can deliver is confirmed for each engagement, not implied by an office list.

Gurugram

HQ

Gurugram, India

operations@hyperspace.works

Working together

Start with the requirement. Map the rest together.

New requirements
operations@hyperspace.works
Existing engagement
Use the support route agreed in your scope.