Harshit Kunwar

Approvals should show the diff that will land, not the sentence that asked for it. Building post-call execution for CS teams. Ex Adobe, New Relic.

[Harshit Kunwar @HrshitKunwar]

I build the part of the GTM stack that runs after the customer call: the follow-up, the CRM update, the ticket, each shown to a person before it ships.

First workflow is free. After that, $500 flat per build.

If your CS team still re-types call notes into four tools, DM me.

[Harshit Kunwar @HrshitKunwar]

Rebuilt https://t.co/ZqoYYLEc2Z in a day. Binned two versions on the way.

Studied New Relic, copied the system not the colours. Tried 3 palettes, black won.

17 hrs, 266 files, 15 commits. Read off the git log.

https://t.co/ZqoYYLEc2Z

[Harshit Kunwar @HrshitKunwar]

@Goura_vk Sending anything to a customer. Not because email is special, but because it can't be pulled back: deleting the record afterwards doesn't unsend it, and their reply is now part of the deal. Internal field updates I'd let it do all day. The line is reversibility, not task type.

[Harshit Kunwar @HrshitKunwar]

@levie The constraint that shows up before compute is review. One person prompting checks each answer. A thousand background agents writing to the CRM can't each get a human look, so the real question is which actions are reversible enough to skip review and which still need a diff.

[Harshit Kunwar @HrshitKunwar]

@jasonlk The line that matters is "presumably that's the only one." A board they chose to share is a courtesy, not an audit. The log of what each agent changed has to live somewhere neither of them can edit, or you only see the conversations they decided to show you.

[Harshit Kunwar @HrshitKunwar]

Made one form field required. Leads went to zero for four days.

Traffic was growing the whole time. The leak: a chat teaser sitting on top of the submit button on phones.

Fix is live. Check the form before you blame the traffic.

https://t.co/ZqoYYLEc2Z

[Harshit Kunwar @HrshitKunwar]

@eladgil Dollars are the right scoreboard, with one catch: they lag. An engine chasing a metric can take a bad customer-facing action today, and you see it in the number weeks later. Time-to-notice per type of action is what should decide which ones run unattended.

[Harshit Kunwar @HrshitKunwar]

Every approval screen I've used logs approve or reject and throws away the reason.

An edit shows what changed. A rejection is the one moment someone says the rule out loud: "never promise a date before eng signs off."

Keep the because. That's where the expertise lives.

[Harshit Kunwar @HrshitKunwar]

@hnshah Even with call notes, the stated loss reason is a declaration. "Went with Jira on price" is the polite exit. The evidence I trust is behavioral: what we promised during the deal and whether it actually got done before they decided. That trail usually explains the loss better.

[Harshit Kunwar @HrshitKunwar]

@MartinGTobias Not gonna pitch
https://t.co/bXr5ClQ1c8

[Harshit Kunwar @HrshitKunwar]

@d_gundyrev https://t.co/y091bJi8AW

[Harshit Kunwar @HrshitKunwar]

@suraj_sharma14 https://t.co/y091bJi8AW

[Harshit Kunwar @HrshitKunwar]

@eriknewsha https://t.co/y091bJi8AW

[Harshit Kunwar @HrshitKunwar]

@NWischoff https://t.co/y091bJi8AW

[Harshit Kunwar @HrshitKunwar]

@Twiggie119 @X https://t.co/y091bJi8AW

[Harshit Kunwar @HrshitKunwar]

@sweatystartup https://t.co/y091bJi8AW

[Harshit Kunwar @HrshitKunwar]

@TanmayS_Chauhan https://t.co/y091bJi8AW

[Harshit Kunwar @HrshitKunwar]

@iAnujVarshney https://t.co/y091bJi8AW

[Harshit Kunwar @HrshitKunwar]

@naval https://t.co/y091bJi8AW

[Harshit Kunwar @HrshitKunwar]

@businessbarista https://t.co/y091bJi8AW

[Harshit Kunwar @HrshitKunwar]

@leopardracer https://t.co/y091bJi8AW