Why I'm doing this

It took me seven years to build Hoovu's internal dashboard. With a day of focused attention, I think I can help a senior person inside another company build the equivalent — and they'll be better positioned to extend and customize it than any external vendor.

About me

I studied at Stanford and taught in the CS department there for two years. Since 2019 I've been running Hoovu Fresh, a B2B flower supply chain across nine Indian cities, 365 days a year, in a perishable, low-margin industry. We've scaled it profitably with a corporate team of fifteen.

I use AI constantly as a founder. Since March I've been running free “hang with AI” sessions and have worked with about 40 people; there's a WhatsApp group of around 150 building things together. This feels like a great way to extend that same experiment.

Recce days

The best workshops are built on real material. Before the build day I now spend a recce day — sometimes two — deep inside your business with your team: sitting with how things actually run and pulling out the raw detail (the systems, the spreadsheets, the workarounds, the quiet friction) that's what makes what we build genuinely useful instead of generic.

These days are real work, and they mean I'm giving your company a good deal more than a single day — so I've changed my policy accordingly: recce days are now part of the engagement and charged like any other day. Most engagements end up being one or two recce days plus the build day.

How a day works

Six hours on site — five of work, one for lunch.

• A two-to-three hour session where I explain how I use AI day to day, with examples from Hoovu. Happy to walk anyone through the Hoovu dashboard — brief intro here.
• Roughly two hours of guided building, with a one-hour break in the middle so multiple departments can work in parallel.
• At minimum, a 1:1 with one senior person.
• The lunch break is also when AI can train on your data or run a longer build, so we're not burning paid time on it.
• Best done in your office so we can pull people in for feedback and connect to internal systems.

This is the build day; the recce day or two above come before it. If we scope something on the day that genuinely needs more time, we can add another build day — each billed separately at the same ₹1 lakh, paid same-day. Either way, the goal is to walk away with something working that you can keep building on yourself.

I'm committing fully to the time we book and I'll be ready to start on the dot. In return, the start and end times are fixed in advance. If the day starts late on your end, the end time doesn't shift, and I'm not able to stay longer to make up for it. Waiting around is a poor use of both our time, and I'd rather we honor the window we agreed on so the work stays focused.

What I need from you

• One senior management person with me throughout. This is non-negotiable. Without their insight the dashboard isn't valuable, and that part can't be outsourced.
• We build on your machine, so you own it end to end from minute one.
• The more frankly that person can speak about how the company actually works — existing systems, pain points, what's broken — the better the output.

Pricing

• ₹1 lakh per day — recce days and the build day alike.
• Most engagements come to ₹2–3 lakhs: the build day plus one or two recce days, depending on how much ground we need to cover first.
• Recce days are agreed up front and charged as part of the engagement — they're where I commit real time to understanding your business.
• If we add a build day and it's working, you pay after the first — only if it was useful and you want me back.
• Payment is same-day, per day. Both of us have better things to do than chase an invoice.
• Outside Bangalore, I also bill travel and accommodation at cost. I'll always try to group trips or stay with friends to keep it small, but every so often that isn't possible.
• The rate isn't negotiable. The structure isn't either.

This is a pilot, which is why I'm taking the risk on the build day. The structure only works if both sides honor it.

Logistics

• Conference room, a monitor I can share my screen to, a whiteboard, internet.
• Happy to sign an NDA — yours, a standard one, or one Claude drafts for us.
• If you can share context beforehand — documents, ERP access, sample data — great. I prep for a session either way and it makes the day more specific. If it's thousands of documents, AI can read through them.
• Don't share anything you wouldn't share with a consultant. You can show things on your screen so sensitive docs never leave your system — that's the point of building on your laptop.
• If you'd rather, we can discover pain points during the session through voice notes from older management, in-person interviews, JDs, orientation docs, existing emails and Excel sheets — but that uses up time. With good prep we can have a working prototype in the first hour.

Afterward

The tools live on your system. You can extend them, customize them, pay for the APIs directly without me as a middleman. During the session I'll show you how Claude itself can help you debug and extend what we built, so you genuinely don't need me to keep going.

If we do more than one day together, you can message me anytime after and I'll do my best to help.

Demos I build on the day

I'll usually try to build a small working demo during the session itself — it's the fastest way to get a room to see what's possible and win the team's buy-in. When I do, I'll hand you the Claude Code prompt behind it so you can rebuild it yourself.

The demo project itself, though, I'll either take down within a week or scope separately. When I build something on the fly to make a point, I do it on my own API keys and my own database — turning that into something production-ready that your team can actually rely on is a whole separate project, with real time and effort behind it. I'm glad to do it if you decide you want it: just say the word and I'll scope it and send you pricing. Otherwise, the prompt should get you most of the way there yourself.

From the field

• One day on the factory floor at Bliss Aerospace Case study · Precision manufacturing — a production planning dashboard, built in a day

Get in touch

Fill this in and I'll get back to you. Or write directly to rhea@rosebazaar.in.

A quick heads-up before you do: most engagements run ₹2–3 lakhs — the build day plus one or two recce days where I deep-dive with your team — at ₹1 lakh per day, paid same-day. Outside Bangalore, travel and accommodation are billed at cost.