Home › Case study › Grivaa Capital
Case study · Financial services · New DelhiHow I Digitised Operations at Grivaa Capital
Grivaa Capital is a New Delhi investment-advisory firm. I joined as their developer in May 2026 and have since built the software the team runs on day to day — a multi-brand content command centre, a task and time-tracking system, and an AI research dashboard — alongside the four public websites the business is found on.
The situation
An advisory firm running three brands, with the operational work spread across separate tools and manual steps.
- Content ran across three brands with no shared workspace — drafting, scheduling and analytics lived in different places, and AI credentials were the kind of thing teams end up sharing.
- Task and time tracking depended on people remembering — any system that needs a separate “start timer” button stops being used within a week.
- Content research was done by hand — watching competitors and working out what performed was slow, so it happened rarely.
- Four public sites had to be findable — finance and legal queries are contested, and the sites needed a structure search engines could actually read.
My role
Web Developer & AI Automation Specialist at Grivaa Capital, from May 2026. I own these systems end to end: scoping the problem with the team, designing the data and permission model, building, deploying and maintaining. The internal tools run on the company’s own infrastructure rather than on a third-party SaaS.
The systems I built
Three internal products, in production and used by the team. Internal tools open a sign-in screen — they are real systems, not public demos.
The public web properties
Four live sites I ship and maintain for the firm — build, structure, schema, sitemaps and Search Console indexing. Open any of them.
What changed
Stated as what the systems do today, not as marketing figures. Everything here is checkable against the systems themselves.
- Three brands run from one workspace instead of content, scheduling and analytics living in separate tools.
- Nobody shares AI credentials. An approved prompt library and per-model usage control replaced passing keys around.
- Publishing has an owner. A writer can draft; only the founder can publish — enforced by role-based access, not by convention.
- Time is tracked without anyone logging it, because the clock is tied to the Kanban card move.
- Content research runs on a schedule rather than on demand, and arrives as email reports and a Google Sheet.
- Four public sites are live with sitemaps, schema and Search Console configured — each one linked above and open to check.
Stack
FAQ
Is this work verifiable?
The four public websites are linked above and open normally. The three internal systems are real production tools used by the Grivaa Capital team, so their links open a sign-in screen rather than a demo — that is what an internal system looks like. Screenshots of each are on the work section of my portfolio.
What exactly was your role?
Web Developer & AI Automation Specialist at Grivaa Capital since May 2026. I designed and built these systems end to end and continue to maintain them. Full history is on my résumé.
Can you build something similar for my business?
Yes — internal tools, custom CRMs, client portals and approval workflows are the work I do most. Tell me the process you run by hand and I’ll scope it. See AI automation or full-stack development.
Do you work with financial-services businesses?
Yes. Grivaa Capital is an investment-advisory firm, and the work covers both their internal operations and their public, compliance-sensitive web presence.
Running your business on spreadsheets and manual steps?
That is exactly the problem these systems solved. Tell me what your team does by hand and I’ll tell you what is worth building.