Aparna Kaushik Design Group LLP

How GreyCube Implemented Open-Source ERPNext to Unify CRM, HR, and Project Management for Aparna Kaushik Design Group LLP

 · 10 min read

By Greycube · ERPNext Implementation · Architecture & Design

Aparna Kaushik Design Studio had the portfolio of a mature firm and the backend of a startup. Attendance was tracked in Excel. Site visits were logged in diaries. Project documents lived across drives, notebooks, and memory. Greycube stepped in to implement ERPNext — an open-source, modular platform that brought CRM, HRMS, project management, and accounts onto one system. No proprietary lock-in. No fragmented tools. Just one source of truth for a studio ready to scale.

1The Challenge: Disconnected Operations in a Connected World

When Greycube first engaged with Aparna Kaushik Design Studio, the operational picture was familiar to anyone who has worked with fast-growing creative firms. The studio had a biometric device at the entrance — but the data stayed there. Attendance was manually transferred into Excel at the end of each week. Leave applications arrived via WhatsApp. Birthday reminders were whoever happened to check social media that day.

Project management was even more fragmented. Drawings sat in Google Drive. Meeting notes lived in the principal architect's diary. Site observations were scribbled in field notebooks. Expense receipts were stuffed in envelopes. The master project tracker was an Excel sheet that three people often had open simultaneously, each saving their own version.

And then there was the revenue leakage. Site visits — some complimentary, some billable — were tracked informally. The studio had no visibility into how many free visits a project had consumed, how many should have been invoiced, or what the total cost of site supervision was. Billing relied on memory. Memory is not a system.

2The Approach: Modular, Open-Source, No Lock-In

Greycube's approach was simple: do not force the studio into a rigid, proprietary box. ERPNext is open-source, modular, and built on the Frappe framework — which means it can be configured to match how a business actually works, rather than forcing the business to adapt to the software.

The implementation was phased. Greycube started with the areas causing the most friction — HRMS and project document management — then expanded into CRM, accounts, and the site visit billing workflow. Each module was configured, tested with real users, and refined before moving to the next. No big-bang deployment. No disruption to ongoing projects.

Why ERPNext? Open-source architecture means no licensing walls, no vendor lock-in, and full ownership of data. For a growing studio, that flexibility matters.

3HRMS & Payroll: From Manual Entry to Automated Sync

The biometric device was not the problem. The gap between the device and the system was. Greycube configured ERPNext to sync attendance data directly from the biometric hardware, eliminating the weekly ritual of manual Excel transfers.

Before

  • Biometric data exported manually every week
  • Attendance tracked in multiple Excel sheets
  • Leave balance calculated by hand
  • Birthdays remembered (or forgotten) casually
  • Payroll processed with conflicting file versions

After Greycube's Implementation

  • Biometric syncs directly with ERPNext in real time
  • Attendance auto-processed and validated daily
  • Leave policies auto-enforced by the system
  • Automated birthday reminders and team alerts
  • Payroll generated in a few clicks, error-free

Attendance & Leave Flow — Automated Post-Implementation

👤
Employee Check-in
Biometric device
Auto Sync
Direct to ERPNext
📊
Attendance Logged
Real-time records
🎂
Smart Triggers
Birthdays, leave balance, payroll

Today, when an employee punches in, ERPNext knows. When someone applies for leave, the system checks their balance against company policy automatically. And every morning, the team gets a gentle nudge about whose birthday it is. Small thing? Maybe. But culture is built on small things — and Greycube made sure the system supported it.

4Project Document Management: One Workspace, Every Document

Ask any architect where the site photos from a project six months ago are, and watch them mentally scroll through a maze of folders, notebooks, diaries, and WhatsApp chats. At Aparna Kaushik's studio, project information was everywhere — and therefore, nowhere.

Greycube configured ERPNext's project module to serve as a single, living workspace for every engagement. Each project now holds its sales order, purchase invoices, site visit logs, expense claims, and all associated documents in one place. No more asking "Where did we save that?" The answer is always: "In the project."

Document Consolidation — Greycube's Configuration

Google Drive Folders
Project Workspace
Handwritten Diaries
Project Notes & Comments
Field Notebooks
Site Visit Logs
Receipt Envelopes
Linked Expense Claims
Excel Trackers
Project Dashboard

The open-source nature of ERPNext meant Greycube could customize document workflows exactly to the studio's needs — linking drawings, approvals, and revisions directly to project records without paying for expensive add-ons or being locked into a vendor's roadmap.

5Site Visits & Billing: Closing the Revenue Leak

Here is a truth every service business knows but rarely admits: sometimes you do work you forget to bill for. Site visits were the invisible leak at Aparna Kaushik's studio. Some visits were complimentary (part of the design fee). Others should have been billed separately. But without a clear system, the line blurred.

The old way: Site visits were noted anywhere — diaries, WhatsApp, memory. Billing happened (or did not happen) based on whoever remembered to raise an invoice. Greycube fixed this with a structured workflow.

Site Visit Workflow — Configured by Greycube

👷
Project Manager
Reviews & approves request
🏛️
Principal Architect
Final authorization
📅
Site Booking
Scheduled & confirmed
🚗
Site Visit
Execution & logging
📝
Expense Claim
Post-visit billing linked to project

Greycube built this workflow directly into ERPNext. Every site visit now follows an approval chain: project manager first, then principal architect. Only then is the visit booked. After completion, the team files an expense claim — which automatically links back to the project, the sales order, and the financial records.

For the first time, the studio can see exactly how many site visits a project has consumed, how many were free, how many were billable, and what the total supervision cost is — all in real time. The invisible leak is now visible, measured, and controlled.

6CRM & Selling

In a design studio, every lead is a potential relationship that could last years. A client who walks in for a kitchen renovation today might return for a full home redesign tomorrow. But when lead information lives in someone's inbox, or on a sticky note, or in a phone's contact list, that long-term view disappears.

Greycube configured ERPNext's CRM module to give the studio one place for every prospect, enquiry, quotation, and follow-up. Now, when a lead calls after two years, the team does not scramble. They open the lead record and see the full history — every conversation, every quotation, every site visit, every project that followed. Because ERPNext is open-source, Greycube could extend the CRM with custom fields and reports specific to the architecture business, without waiting for a vendor's product roadmap.

7Accounts

Perhaps the most powerful change was the simplest to describe: for the first time, the studio could look at a project and see its full financial picture. What was the original sales order? What purchase invoices have been raised? What expenses have been claimed? What is the profitability?

Previously, this information was scattered across accounting software, Excel files, and memory. Greycube unified it all in ERPNext. A sales order flows into a project. A project accumulates purchase invoices and expense claims. The accounts team works with real data, not reconstructed data. And at month-end, the reports practically generate themselves.

8The Bigger Picture: Why Open Source Matters

It is tempting to measure digital transformation in features checked off a list. But at Aparna Kaushik's studio, the real wins were quieter — and they were made possible by choosing an open-source platform.

Because ERPNext is open-source, Greycube could customize workflows without licensing restrictions. The studio owns its data completely. There are no per-user fees that punish growth. And if the studio needs a new feature tomorrow, Greycube can build it — no waiting for a vendor's quarterly release cycle.

Time Recovered
Hours spent on manual data entry now go into design
🔍
Visibility
Every project's health visible in real time
🤝
Trust
Clients see organized, professional operations
💰
Revenue
No more unbilled site visits or missed claims
😊
Culture
Birthdays remembered, leaves fair, team happy
📈
Growth
Open-source systems that scale without licensing walls

9Looking Ahead

Aparna Kaushik Design Studio still designs with passion, sketches with freedom, and dreams with ambition. The difference is that now, the business side of their business runs as beautifully as their interiors. And that is what Greycube's ERPNext implementation made possible — not replacing the human touch, but giving it room to breathe.

For other architecture and interior design firms facing similar growing pains, the message is clear: you do not need to trade creativity for control. You just need the right system — implemented by a team that understands both the software and the business.

About Greycube

Greycube specializes in ERPNext implementation, customization, and support for businesses across industries. From workflow design to data migration to ongoing optimization, Greycube helps organizations turn operational chaos into clarity.

Best ERPNext / Frappe Professional Services

Services worth the Value !


No comments yet.

Add a comment
Ctrl+Enter to add comment