Human Centric Works
From stone to systems.
We started as an architectural consultancy. We’ve grown into a full-lifecycle building solutions practice — engaged from a project’s earliest feasibility study through design, delivery, and successfully running what gets built. Software sits at the center of that lifecycle: the system coordinating a building’s people, money, and decisions is what makes it work, or quietly breaks it. AORMS, our first product, is that system.
Founded and operated from Hospet, Karnataka, India.
The Brief
Why we build this way
Architecture, first
Our founder trained and practiced as an architect, and kept meeting the same problem: good work, slowed down by tools that were never built for how a studio actually runs.
The practice widened
What began as an architectural consultancy grew into something broader: a full-lifecycle building solutions practice, engaged from a project’s earliest feasibility study through design, delivery, and its life after handover — not just the drawings in between.
The software is the heart of the building
Across that whole lifecycle, one thing decides more outcomes than any single design choice: the system coordinating the people, money, and decisions behind the building. Get that system wrong, and even strong architecture is undone by missed approvals, drifting budgets, and work that never gets recorded. Get it right, and it’s the difference between a project that succeeds and one that quietly breaks down. That belief is what this company is built on.
So we build the record instead
Every product we ship replaces borrowed tools with one operating record, built around the discipline that actually uses it — starting with our own.
How we work
One practice, the whole lifecycle
We don’t hand your project off between stages. We stay on it from the first feasibility number to the software your team runs the finished building on.
01 — Feasibility
Know before you commit
Site, budget, and program feasibility worked out before a single drawing locks you into a decision.
02 — Design & delivery
Architecture through to site
Design, permits, and site supervision carried through construction — coordinated on one record, not scattered across consultants.
03 — The software backbone
Nothing drifts
AORMS runs the fees, approvals, and site record, so the office and the site are always looking at the same number.
04 — Running it well
Past handover
The record doesn’t end at handover — it’s what keeps the building operating the way it was designed to.
Products
What we’ve built
The lifecycle above isn’t a pitch — it’s built and running. Six products shipped so far, each solving a real gap we hit ourselves, spanning the AEC ecosystem outward. Source is open under github.com/HolagundiWorks for anyone evaluating how it’s built.
AORMS
The command center for architecture practice. Built for architects, not adapted from generic project software — every client, project, fee, and drawing lives on one record, precise and always current. Cloud-only, GST/TDS compliant by design, with ESTI, a built-in AI agent that answers only from the firm’s own data.
leos
Offline-first desktop School Management System — a modern “school
operations cockpit,” reimagined from openSIS. Tauri + React/Mantine +
Rust/SQLite, with a portable, LAN-ready .schoolpkg file so a
school’s whole record travels with it, not a server.
AQC — BBS Studio
A native Windows Bar Bending Schedule generator, built to IS 456 cutting and estimation rules — the reinforcement detailing a building’s structural delivery runs on, worked out precisely instead of by hand.
PDF-to-Markdown/CSV desktop conversion tool, built for the Knowledge Bank portal pipeline.
Dependency-free spatial vector-store engine — binary codec + uniform-grid
spatial index — the storage core behind AAD’s .vdb databases.
The same approach — study where a specialised profession’s tools fail, then build the record it actually needs — applied beyond architecture. Nothing announced yet.
Selected clients
Projects we’ve worked on
Where the practice started — real clients, real briefs, mostly around Hospet.
Founder
Vishwabhiram D Holagundi
Trained as an architect at Gogte Institute of Technology; spends most days now designing the systems building projects run on. The observation was the same at every stage of the lifecycle — good work, slowed down by tools that never evolve with it — so the practice widened rather than changed: from architecture into full-lifecycle building solutions, with software as the thing that actually decides whether a project holds together.
Writes in public about the shift, mostly on one question: what a firm loses when the record of a decision lives in a WhatsApp thread instead of a system built to hold it.
Get in touch.
Licensing, partnerships, or press — reach out directly. We’re a small team and read every message ourselves.