Onsite Case Study —
Vecttor Buildtech
A project management consultancy does not manage one client. It manages several simultaneously, each expecting their project data to be completely separate from every other client’s work.
That separation is straightforward to promise. It is considerably harder to deliver when your operational system is a collection of Excel files, WhatsApp groups, and shared registers — where data from different projects mixes together the moment a team member enters the wrong row or sends an update to the wrong group.
Vecttor Buildtech, a Maharashtra-based PMC and contracting firm, was managing multiple concurrent client projects when this exact challenge became the daily reality for Durgesh Jagtap and his team.
When you manage projects for different clients, every financial record, every operational update, and every expense entry must belong unambiguously to the right client and the right project. Excel files create a version and access problem — the separation depends entirely on team discipline with file naming conventions, which is difficult to maintain consistently under active project execution pressure.
Maintaining separate WhatsApp groups for each client project creates a reporting problem. Durgesh Jagtap needed a system where the separation between client projects was structural — built into the platform itself, not dependent on team discipline with group message management and file naming conventions.
| What was broken | What Onsite replaced it with |
|---|---|
| Excel files per client with no structural separation | Separate company workspaces within one Onsite account — data isolated at platform level |
| WhatsApp groups per project generating unstructured updates | Operational data flowing into the correct client workspace automatically |
| Manual compilation before every client report | Reports generated directly from the relevant workspace — no extraction, no cross-referencing |
Vecttor Buildtech now manages multiple concurrent client projects on Onsite with each client’s data fully separated at the platform level. The operational overhead of maintaining that separation — which previously consumed significant team time through manual Excel management and WhatsApp group discipline — has been eliminated.
Data management and reporting for each client project is handled directly from Onsite, producing reports that are accurate because the underlying data was clean from the point of entry rather than cleaned up at reporting time.
The shift from Excel and WhatsApp groups to Onsite did not just make reporting faster. It made the data itself more reliable — which is what a PMC firm’s clients are ultimately paying for.
| Area | Before Onsite | After Onsite |
|---|---|---|
| Client data separation | Manual, discipline-dependent | Structural, platform-enforced |
| Expense tracking | Excel files per client | Separate workspaces per client |
| Operational updates | WhatsApp groups per project | Onsite per project, per workspace |
| Report generation | Manual compilation, hours of work | Generated directly from platform |
| Multi-project overview | Not available from one place | All projects from one login |
From one Onsite account with fully separated data environments for each client.
Multiple Excel files, separate WhatsApp groups, and scattered registers across all active client projects — replaced by one platform.
Reports pull directly from clean workspace data — no extraction, no cross-referencing, no reformatting before sharing.
By eliminating the manual compilation process that previously required extracting, cross-referencing, and reformatting data from multiple sources before any client report could be produced.
No expense entry, operational update, or report from one client workspace is visible in or accessible from another client’s workspace.
one platform, with clean data for each
If your PMC or contracting firm manages projects for multiple clients and currently handles the separation through Excel file naming and WhatsApp groups, Onsite’s Add-on Companies feature gives you that separation at the platform level — so every client’s data is clean from the point of entry.