Recommender plan: Meera Kashyap
Two writers worth having, one worth dropping. Grading the plan for INSEAD MBA, HBS and ISB PGP, Aug 2027 start.
Verdict
CompetitiveCompetitive, one swap away from strong
Rohan Bhattacharya is the best writer in your file and Sunita Pillai covers the Corvane years, but Vikram Anand is a title with no first-hand view and should not be asked.
Generated on 10 October 2026 · AdcomLens · Confidential · 2,341 words
1. Who to ask
| Candidate or type | Closeness to your work | Recency | Has given you real feedback | Verdict |
|---|---|---|---|---|
| Rohan Bhattacharya, Director of Customer Solutions, Ledgerline | Direct manager, weekly, since Jul 2024; promoted you Oct 2025 | Current | Yes, the Jan 2026 criticism about rewriting your team's work | Ask first. Closest to the work and owns the hardest answer on the form. |
| Sunita Pillai, Delivery Manager, Corvane Technologies | Manager Apr 2022 to Jun 2024; made you module lead on the UK motor insurer account | Ended Jun 2024, last contact 2025 | Unclear from the file | Ask, after you check she remembers the 1,900 to 240 mismatch numbers and can name one criticism she gave you. |
| Vikram Anand, Co-founder and CTO, Ledgerline | Two levels up; saw two quarterly reviews, has not watched your work | Current but thin | No | Avoid. A CTO who can only say the implementation team matters writes a short, generic letter and signals you had nobody closer. |
| Ledgerline product manager you worked with on the multi-entity reconciliation module | Peer or near-peer who saw you contribute to product decisions, not just delivery | Current | Likely, if the collaboration was real | Ask if a school allows a non-manager slot and the person can cite specific calls, not vague praise. |
| Claims operations lead at the UK insurer in Leeds | Client side; four years of daily video calls on the claims-payment module | Ended Jun 2024 | Possibly, in the form of client pushback | Ask if you need external proof of cross-border working, since you have never lived outside India. |
| Anyone at Ledgerline who cannot be told you are applying | Not applicable | Not applicable | Not applicable | Handle first: you asked to move into product in Mar 2026 and were told to wait. Confirm Rohan already knows you are applying before the form arrives. |
2. What the form will ask
- Rating grid
- Most forms ask the writer to rate behaviours such as initiative, team leadership, communication and self-awareness against a peer group. Rohan must be able to put an incident behind every top rating he gives: 74 days to 41 days for median go-live, 14 customers live in FY26 worth 6.2 crore INR in annual contract value, three of five engineers hired by you. He should not mark you top on everything. A rating one notch below the top on a behaviour like delegation is normal and should match the January 2026 feedback story, not contradict it.
- Comparison with peers
- The writer is usually asked where you stand among people he has managed in a similar role. Rohan needs a stated comparison group, for example implementation and solutions leads he has supervised at Ledgerline since 2024, a position within it, and the reason: the only one who rewrote the bank-integration playbook rather than working inside it. Sunita's group is module leads on the claims platform at Corvane. Vague superlatives with no group named read as filler.
- The feedback question
- Expect a question on the most significant constructive feedback given to you, the circumstances and what you did with it. Rohan must be able to name January 2026, say plainly that you were rewriting your engineers' delivery plans instead of coaching them, and then describe what changed over the following months, including the engineer who now runs the hardest logistics accounts. He should not swap in a strength dressed as a flaw such as works too hard.
- Anything school specific to verify
- Number of recommenders required, whether a second professional writer is mandatory or a peer is permitted, the exact question wording, word or character limits, whether answers are typed into fields or uploaded, and how the invitation link reaches the writer. These differ between INSEAD, HBS and ISB and change between cycles. Check each school's current form yourself before you brief anyone, and tell Rohan and Sunita which format they face so no one writes 900 words for a 300 word box.
3. Incidents to remind them of
Median go-live cut from 74 to 41 days
You rewrote the bank-integration playbook and moved data checks into week one, taking the median time to go live for mid-market customers from 74 days in FY25 to 41 in FY26. This was a change to how the function works, not a push on individual deals, and it held across 14 go-lives worth 6.2 crore INR in annual contract value. Behaviour: Strategic Orientation and Results Orientation.
Use in. The rating grid and the peer comparison. Rohan watched this from the weekly go-live review and signs off the numbers.
The 1.1 crore retail-chain account that had given notice
The customer had already served notice to leave and you rebuilt its settlement mapping in nine days to keep it. The stake was a live revenue loss and a reference customer, and you were a Solutions Engineer at the time with no formal authority over the account. Behaviour: Problem Solving under pressure, with Adaptability.
Use in. The question on how you perform when something is at risk. Rohan was your manager through 2025 and saw the account stay.
The payment-mismatch checker nobody asked for
At Corvane in 2023 you traced why roughly 1,900 claim payments a month failed to match the UK motor insurer's ledger, found four causes and built a checker that brought the count to 240, ending manual correction work for an eleven-person team. Nobody assigned it to you. Behaviour: Initiative, with Problem Solving.
Use in. The initiative rating and the greatest strength question. Sunita Pillai approved the work and saw the eleven-person team stop correcting by hand.
January 2026: told you were rewriting your team's plans
Three months into managing five engineers, Rohan told you that you were editing their delivery plans rather than coaching them. You stopped editing and started reviewing. The FY26 go-live count held while you did it, which is the proof that the change was not just compliance. Behaviour: Self-Awareness.
Use in. The constructive feedback question. Only Rohan can answer this one, which is the strongest argument for asking him first.
Hiring three of five engineers, one now on the hardest accounts
You hired three of the five engineers on your team and write their reviews, and one of them now runs the hardest logistics accounts at Ledgerline. That is a hiring judgement followed by development, not an inherited team. Behaviour: Developing Others and Team Leadership.
Use in. The people leadership rating. Rohan approved the hires and sees how that engineer performs now.
Running a squad of four at Corvane with no authority
As module lead from April 2023 you ran four engineers on the claims-payment module with no say over ratings or hiring, and coordinated releases across development, testing and support plus requirement calls with the Leeds claims operations team. You got work done through influence alone. Behaviour: Influence and Collaboration.
Use in. The question on working across teams and the peer comparison. Sunita made you module lead and watched you hold the squad together.
4. The feedback story
StrengthYour file does contain a real one, which puts you ahead of most applicants. In January 2026, three months after you took over five implementation engineers, Rohan Bhattacharya told you that you were rewriting your team's work instead of coaching them. That is a specific, unflattering, believable criticism of a newly promoted manager, and it is the opposite of a strength in disguise. Do not let anyone soften it into attention to detail. The response is already in your own words: you stopped editing their plans. The part that needs filling is the proof that it lasted. Rohan needs one concrete instance he can describe, for example a delivery plan he knows you reviewed and let go unchanged even though you would have written it differently, and what happened to that go-live. The engineer you hired who now runs the hardest logistics accounts is the second piece of evidence, because you cannot hand off the hardest accounts while still rewriting the work. Give Rohan the date, the setting of the conversation and both proof points as notes. Let him choose which to use and let him keep his own words for the criticism itself, because adcom readers can tell when the applicant supplied the phrasing.
5. Brief to hand over
- Page one, top: the schools, the exact round dates you are targeting for the Aug 2027 intake, and a line saying the invitation link will arrive by email from each school after you submit your part of the application, with the sender name and the likely subject line so it is not lost in spam.
- Next: your goal in three lines in plain words. Product manager at a payments or fintech company in Europe or Singapore, then a cross-border payments business for small Indian exporters who wait up to two weeks to be paid. The writer needs this to answer why now, not to repeat it.
- Next: the questions that writer's form actually asks, copied from the school's current form, with the word or character limit beside each one. Do not make them discover the limits while writing.
- For Rohan, three incident notes in context, action, result form: the bank-integration playbook rewrite and 74 to 41 days; the 1.1 crore retail-chain account rebuilt in nine days after notice was served; the January 2026 feedback and what changed. Add the hiring of three of five engineers as a fourth if the form has room.
- For Sunita, three incident notes: the mismatch checker, 1,900 a month down to about 240 and eleven people freed from manual correction; running four engineers as module lead with no say over ratings; the Leeds requirement calls and release coordination. Cut everything from Ledgerline, because she did not see it.
- A short figures block that must agree with your resume exactly: 74 to 41 days, 14 go-lives, 6.2 crore INR ACV, 1.1 crore INR account, nine days, 1,900 to 240, eleven-person team, five direct reports, three hired. A letter that says ten go-lives when the resume says 14 damages both documents.
- A closing line telling the writer to cut any item they did not personally see and to use their own examples where they remember something better. Say it in writing, not just in the conversation.
6. What not to do
Watch- Do not draft any part of the letter, not even a paragraph Rohan can edit. Admissions readers compare letters with essays, and a file where the manager's voice matches the applicant's prose stops being independent evidence.
- Do not coach so closely that Rohan's answer on the January 2026 feedback uses your phrasing. If his version differs slightly from your essay version, that is a sign the event was real.
- Do not pick Vikram Anand for the CTO title. A co-founder who has seen you at two quarterly reviews and knows your name cannot answer the peer comparison question, and a thin letter from a senior person reads worse than a detailed one from a director.
- Do not ask by hint or over chat. Ask Rohan in a scheduled conversation, say which schools, say what you want him to be able to describe, and give him the option to decline. Same for Sunita, who you have not spoken to since 2025 and cannot approach cold.
- Do not ask anyone to mark you top on every behaviour. A straight line of highest ratings next to a feedback answer about rewriting your team's plans contradicts itself, and the grid is read against the written answers.
- Do not ask to read the letter or to see the ratings. It puts the writer in an awkward position and, at Ledgerline where you have already asked to move into product, it adds pressure to a relationship you still depend on.
7. Timeline
| Weeks before deadline | Step |
|---|---|
| 10 | Confirm Rohan already knows you are applying, given that you asked to move into product in March 2026 and were told to wait. Decide what you tell Ledgerline and when. |
| 8 | Settle the names: Rohan and Sunita. Drop Vikram. Trace Sunita's current email and role, and reopen contact with a real conversation before you ask for anything. |
| 7 | Ask both directly, in a scheduled call or meeting. Name the schools, the rounds, and the two or three things you hope they can describe at first hand. Accept a no without argument. |
| 5 | Register them in each application so the invitation emails go out, and confirm with each writer that the link arrived and opens. |
| 4 | Send the one-document brief per writer, with the current form questions and word limits, the incident notes and the figures block. |
| 3 | Light check-in by email. Ask only whether the form is clear and whether anything in the notes does not match what they remember. |
| 2 | Second check-in. If either writer has not started, offer to move them to a later round rather than accept a rushed letter. |
| 1 | Confirm both have submitted. Chase once, politely, if not. |
| 0 | Buffer only. Nothing should be outstanding on deadline day. |
8. Next steps
- Pull the current recommendation form questions, word limits and required number of writers for INSEAD, HBS and ISB from each school's own application site, and write the exact round date you are targeting at the top of your brief.
- Tell Vikram Anand nothing and simply do not ask him; instead decide this week whether the Ledgerline product manager from the multi-entity reconciliation module is close enough to the work to be a credible second or third writer.
- Write the two-page brief for Rohan and the one for Sunita as notes only, then delete any line that reads like a finished sentence for the letter.
- Before you ask Sunita, confirm she can still recall the 1,900 to 240 mismatch numbers and can name one criticism she gave you; if she cannot do either, she is a weaker choice than she looks on paper.
- Run Recommender Prep again once the form questions are in hand, and use Goals Credibility to tighten the product manager to cross-border payments goal that your writers will be asked to back.
9. Information that would sharpen this
- The exact round and deadline date you are targeting for the Aug 2027 intake at each school.
- How many recommenders each of INSEAD, HBS and ISB currently requires, and whether a peer or non-manager writer is permitted.
- The current question wording, word or character limits, and whether answers are typed into fields or uploaded, for each school's form this cycle.
- Whether Rohan Bhattacharya already knows you are applying to MBA programmes, and whether anyone else at Ledgerline must be told.
- Sunita Pillai's current employer, role and contact details, and when you last spoke to her in 2025.
- One specific instance after January 2026 where you let a team member's plan stand unchanged, with the customer and the outcome, so Rohan has proof the change lasted.
- Any criticism Sunita Pillai gave you at Corvane, with the occasion and what you did next, in case her form also asks the feedback question.
- The name and role of the Ledgerline product manager you worked with on the multi-entity reconciliation module, and how closely that person actually saw your work.