Industries · Interior design firms, design-and-build studios and furniture manufacturers
Software for interior design firms and furniture workshops
Ahrom Labs built the backend Savistar (interior design) and Saag (furniture manufacturing) run on: workers, clients, vendors and freight, projects and site visits, workshop orders, and one finance ledger for two sister companies. Each invoice carries the right company's GSTIN, and staff see only their own cash entries — enforced at the server, not hidden in the screen.
Pujan Motiwala ·
- Companies on one book
- 2 sister concerns, one client list
- Staff view of the cash ledger
- Own entries only
- Staff access to bank data
- None, refused at the server
- Vendor and freight charges
- Checked against reference rates; deviations flagged
Why do design firms outgrow spreadsheets and chat?
A design-and-build job touches clients, site visits, vendors, labour, freight and payments at once, usually spread across a spreadsheet per project and a chat group per site. The owners know how it all connects; nobody else does. Savistar and Saag — an interior design firm and a furniture workshop under the same owners — moved all of it into one system: workers, clients, vendors and freight, projects and site visits on the design side, workshop orders on the furniture side.
Can a design studio and its furniture workshop share one system?
Yes, and without the weight of a multi-company ERP. Both businesses share one client list and one combined ledger; a design job lives under Projects and a furniture order under Orders, and each invoice carries its own company's letterhead, logo and GSTIN when the PDF is generated. It's a single app modeling two business lines — a sister-concern arrangement, in Indian accounting terms — which is exactly as much structure as the business needs. See Two companies, one book.
How do you stop staff seeing the whole cash book?
By filtering at the point the data is fetched, not by hiding buttons. Staff log day-to-day cash, but their view of the cash ledger contains only the entries they created. Bank data isn't scoped for staff at all — every request for it from a staff account is refused before any query runs. Owners see everything.
How are vendor and freight overcharges caught?
Every incoming charge is compared against a known reference rate, and anything that deviates is flagged automatically — instead of trusting every bill or asking someone to audit each line by hand. It catches overcharges as long as the reference rates are kept current.
How are partial deliveries and advances tracked?
Outstanding amounts — a partial delivery, an advance against pay — are computed from the underlying transactions every time they're shown, rather than kept as a running total that can drift from the records that produced it.
What did the owners say?
"They really took the time to understand our concerns and requirements, and the system was built the way we had envisioned it. It has brought much more structure, visibility, and control to the way we operate."
— Sachi & Haripriya, owners of Savistar and Saag
Boundary
This is one shared app for two related businesses, not a multi-tenant platform: adding an unrelated third company would mean a different design, not a new setting.
The engineering notes
Decisions behind it
- Scope financial visibility by role at the query layer, not just the UI
- Flag deviations from a known reference rate, don't manually audit every charge
- Compute a balance from source transactions at read time, don't store a running total
- Optional integrations should degrade the specific feature, not the app
Talk to us about your systems.
Tell us what's held together with workarounds right now. We reply to every message ourselves.