Essay diagnosis: INSEAD MBA motivation essay
Meera Kashyap, Implementation Manager at Ledgerline, 6 years in, 499 words against a 500-word limit
Verdict
CompetitiveThe Corvane mismatch story and the line about multi-currency settlement give this essay a voice INSEAD will recognise; one dead paragraph and a soft why-INSEAD close are the only things keeping it out of the top band.
Generated on 10 October 2026 · AdcomLens · Confidential · 3,010 words
1. The 30-second read
StrengthA tired reader finishes this and remembers one person: the engineer who spent three weekends tracing 1,900 mismatched claim payments nobody had asked her to look at, and the video call where a UK finance controller worked out her month-end would now finish two days earlier. The prompt is answered. The essay says why now (she executes a roadmap she does not set), connects it to what she has done (Corvane, then Ledgerline) and names what comes next (product management in payments, then a cross-border business for small Indian exporters). The second read with a pen finds one paragraph that could have come from any file in the pile: "I am a strong leader who cares deeply about people." It sits directly after the strongest writing in the essay and undoes some of it. The closing why-INSEAD paragraph is true but unearned: ten months, international class, two campuses. Every Indian applicant to INSEAD writes those three clauses. Everything else here is hers.
2. Prompt fit
- Asked
- Why an MBA at this point, how it connects to what you have done, and what you want to do next, in roughly 500 words.
- Answered
- All three parts, in that order, at 499 words. The motivation is argued rather than asserted in paragraph 5: she can tell a customer when multi-currency settlement will be configured, but not whether to build it, how to price it or which market to enter first. The link backwards runs Corvane claims platform to Ledgerline implementation. The link forwards runs product manager in Europe or Singapore to a cross-border payments business for small exporters.
- Gap
- The "at this point" half is answered in general terms only. The sharpest fact she has is absent: she asked to move into product in March 2026 and was told to wait a year. The why-INSEAD paragraph names no course, no campus choice, no club, no person she has spoken to, so the ten-month argument rests on speed alone and never explains how a double switch happens in a programme with no internship.
3. Reasoning and movement
- Share of the essay that explains why
- Judged, because the prompt asks about motivation. Roughly 55 percent of the words give reasons; the rest reports. That is enough, but the reasons are bunched in paragraph 5 and the last three lines of paragraph 2. Paragraph 3 (Ledgerline) is pure report: joined, now manage five, 74 days to 41, with no reason for any of it. Paragraph 4 gives neither reasons nor events.
- Does anything happen on the page
- Paragraph 2 contains the only real events: three weekends tracing mismatches, writing the checker, the video call with the finance controller. Paragraph 5 contains a recurring situation (the customer asking for multi-currency settlement) that functions almost as an event and is the second-best writing in the essay. Paragraphs 1, 4 and 7 only assert. Paragraph 3 reports results without a moment in it; paragraph 6 states goals.
- Growth arc
- Starts writing and testing code other people designed at Corvane. Changes when she sees that fixing 1,900 mismatches was not about the code but about an eleven-person team's month-end. Stands now as a manager who delivers a roadmap she has no vote in. Unfinished, and said plainly: she has never decided what to build, how to price it or which market to enter, and has never worked outside India.
- Values against the record
- The essay claims she cares about the person at the far end of a payment, and the record supports it: the Leeds controller, the ₹1.1 crore retail-chain account rebuilt in nine days, the exporters who wait two weeks. Her father, a retired bank branch manager who handled small exporters' paperwork, is where that interest began and he is nowhere in the essay. The one mismatch is paragraph 4: "a strong leader who cares deeply about people" is contradicted by her own note that until January 2026 she was rewriting her team's plans instead of coaching them, and by the fact that she has led nothing outside work since Code Saturdays ended in 2022. The claim is the weakest sentence in the file; the correction she made is the stronger story.
4. Structure map
| Paragraph | What it does | Keep / Cut / Move | Why |
|---|---|---|---|
| P1: "In today's fast-changing world of financial technology" | Tell. Industry wallpaper plus a thesis statement. | Cut to one line | Fifty-six words that no reader needs. The essay's real opening is "Every month-end, about 1,900 claim payments failed to match." Start there and buy back space. |
| P2: Corvane, the 1,900 mismatches, the checker, the call with the controller | Event, then reflection. The strongest paragraph. | Keep whole | It shows initiative nobody assigned, a named problem with a number, and a reason the work mattered to a person. This is what the reader will quote back at interview. |
| P3: Joined Ledgerline, now manage five, 74 days to 41 | Report. Three facts in four lines. | Keep, rebuild | It carries the career move with no reason attached. The resume already has these numbers. The essay must say what she decided here, not what the result was. |
| P4: "I am a strong leader who cares deeply about people" | Tell throughout. No event, no name, no date. | Cut entirely | Sixty-five words of adjectives that could sit in any file. Cutting it funds every addition below and removes the only place a reader doubts her. |
| P5: "However, I have reached the limit of what I can learn from where I sit" | Reasons. The multi-currency settlement line does the work of a whole paragraph. | Keep, move up | This is the argument of the essay. It currently arrives after the reader has been slowed by P4. |
| P6: Product manager in Europe or Singapore, then cross-border payments for small exporters | States goals. Short term is generic, long term is specific and hers. | Keep, sharpen short term | "A payments company in Europe or Singapore" names nothing. The long-term goal has a number (two weeks) and a customer; the short-term one has neither. |
| P7: Why INSEAD plus "At 28, with six years of experience" | Tell. Three standard clauses and a defensive closing line. | Rebuild | Ten months, international class, two campuses are in every INSEAD essay. And at 29 on arrival with six years in, she is the class average, so defending her age spends the last sentence on a non-issue. |
5. Specificity audit
Watch"I am a strong leader who cares deeply about people" (P4)
The whole paragraph asserts dependable, hard-working, leads by example, empowers the team, goes the extra mile. None of it is attached to a person, a date or a decision, so an admissions reader discounts all of it and reads the rest of the essay more sceptically. It is also the one claim her own file partly argues against.
Mitigation required
Replace it with the January 2026 moment: her manager told her she was rewriting her team's plans instead of coaching them, and she stopped editing their plans. Add the one consequence she already has on file, that an engineer she hired now runs the hardest logistics accounts. Two or three sentences, event first, no adjectives.
"In today's fast-changing world of financial technology" (P1)
The opening sentence tells the reader nothing about Meera and delays the only story that will make her memorable by fifty-six words. In a 500-word limit already fully spent, that is more than ten percent of her allowance given to a sentence any applicant could write.
Mitigation required
Open on the month-end mismatches at Corvane and let the thesis arrive later, in paragraph 5 where the reasoning already sits. Keep at most one clause of setup: six years between an IT services claims platform and a Series C payments company.
"I joined Ledgerline as a solutions engineer in 2024 and now manage the five-person team" (P3)
This is the pivot of her career and the paragraph treats it as logistics. The reader is not told why a solutions engineer became an implementation manager, what she changed, or why implementation turned out to be the wrong seat for her ambition. Without that, the move from services to product company reads as a job change rather than a choice.
Mitigation required
Use what she already did: she rewrote the bank-integration playbook and moved data checks to week one, and that is what took the median from 74 days to 41. Say in one sentence that she could fix how a thing was delivered but never whether it should exist. That single contrast sets up paragraph 5.
"I want to work as a product manager at a payments company in Europe or Singapore" (P6)
No segment, no company type, no problem. The reader cannot tell whether she means cross-border payouts at Adyen-scale infrastructure or reconciliation tooling at a small SME lender, and the two require different preparation. On a ten-month programme with no internship, a vague short-term goal is the thing the committee probes hardest.
Mitigation required
Name the product surface she already knows, settlement and reconciliation for cross-border flows, and name two or three real employers in Amsterdam, London or Singapore that run it. She should be able to say why that surface rather than consumer payments, drawing on the 22 integration guides and the multi-entity reconciliation module she helped build.
"Its class is the most international of any business school" and "its campuses sit in the two regions I want to learn" (P7)
These are brochure lines and the committee has read them several thousand times. They also waste the one credible claim she has, which is that she has never lived outside India and knows it. A school chosen for reasons anyone could state reads as a school chosen by ranking.
Mitigation required
Replace with one specific element she can honestly cite, for example the campus exchange she would take and which direction, and one thing she will contribute, which is four years of daily work with a Leeds claims operations team and a view of payments plumbing most consultants in the class will not have. If she has spoken to an INSEAD student or alum about the product recruiting path, name what she learned from it.
"At 28, with six years of experience and my first team behind me, I know what I do not know" (P7)
The closing sentence defends an age and an experience level that need no defending at INSEAD, where the average is 29 and six years, and it ends on a formula rather than a reason. It also leaves the hardest question of her file untouched: why ten months rather than two years for a switch of both function and country.
Mitigation required
Use the March 2026 fact instead: she asked to move into product at Ledgerline and was told to wait a year, and would rather spend that year changing what she is qualified for. That sentence answers why now, why not internally, and why a short programme, in one move.
6. Experience read
At 29 on arrival with six years in, Meera is the INSEAD class average, not an outlier, so the essay should stop explaining her age and start using her seniority. What reads above par is the team: five direct reports, three of whom she hired, with review and allocation authority since October 2025. Most of the engineer and consultant pool arrives with project leadership and no hiring or ratings authority. The essay mentions the five-person team once, in a subordinate clause, and never shows her making a people decision. That is the clearest unforced loss in the file. What cuts the other way is the double switch, function and geography, on a ten-month programme with no internship, and the fact that she has never lived or worked outside India. The essay admits the second honestly in paragraph 5, which is good, but treats it only as a deficit. The missing sentence is the one that turns six years of implementation into the reason she will recruit well: she has spent four years inside a UK insurer's claims operations and two inside bank integrations, so she knows what breaks in a payment before a product manager does. Say that, then say what ten months must deliver that six years could not.
7. Voice and language
Watch- Delete "In today's fast-changing world of financial technology". It is the most common opening sentence in the fintech applicant pool.
- Delete the whole adjective stack in P4: results-driven thinking, "dependable, hard-working and always willing to go the extra mile", "leading by example", "empowering my team to do their best work". This is resume-summary language, and it also appears verbatim in tone in her resume SUMMARY, which should go too.
- "the ability to combine technical depth with business judgment has become more important than ever" is consultant-speak with no subject. Cut it; paragraph 5 proves the same point with a real example.
- "What stayed with me was not the code" is her best sentence. Keep the rhythm; the short declarative is her natural voice and it disappears whenever she tries to sound like an applicant.
- "I know what I do not know" is a formula. She has the specific version two paragraphs earlier: she cannot say whether to build multi-currency settlement, how to price it or which market to enter first.
- "Within two quarters the monthly count was 240" is good: passive-free, dated, numbered. "We have cut the median time to go live from 74 days to 41" hides who did what behind "we"; she rewrote the playbook, so say so.
- "I am a strong leader" and "My colleagues know me as" both ask the reader to take her word for it. Every claim in this essay that survives should be carried by something that happened.
8. How it sits with the rest of the file
- Resume overlap, Corvane: the essay and the resume both carry 1,900 mismatches down to 240 and the eleven-person team. The figures agree. The resume says the checker ended manual correction work entirely; the essay says the controller's month-end finished two days earlier. Both can be true, but pick one framing per document and let the essay keep the human one.
- Resume overlap, Ledgerline: 74 days to 41 appears in both. The resume also carries 14 go-lives worth ₹6.2 crore and the ₹1.1 crore retail-chain save in nine days, which the essay wisely leaves out. Do not import them. The essay should carry the reason behind the playbook rewrite, which the resume cannot hold.
- Timeline check: the essay says "for two years I wrote and tested code that other people had designed" and places the mismatch work in 2023, by which point the resume shows her as Module Lead from April 2023 leading four engineers. Nothing is false, but a reader may wonder whether this was weekend initiative by a coder or work she could have assigned. One clause fixes it.
- Only this essay, the resume and the profile were supplied. No recommender notes and no second essay were in the inputs, so this was read against the resume alone.
- Across the set she should check three things: that the Ledgerline director or CTO is briefed to confirm the coaching change from January 2026 rather than repeating the 74-to-41 number, that no other document repeats the Corvane checker story as its centrepiece, and that the age stated in any essay matches the intake she applies for, since she turns 29 before an August 2027 start.
- The father who ran a bank branch and handled small exporters' paperwork is in her profile and in no document the committee will see. It is the origin of her long-term goal and the essay is the only place it can live.
9. Rewrite plan
- The essay is at 499 of 500 words, so every addition must be paid for. Cut paragraph 4 entirely, all 65 words, and cut paragraph 1 to a single clause of setup. That frees roughly 110 words.
- Open paragraph 1 on the Corvane month-end mismatches. No industry framing, no thesis sentence.
- Rebuild paragraph 3 with the decision, not the result: the playbook rewrite, data checks moved to week one, and the fact that she could change how things shipped but never whether they existed.
- Spend 40 of the freed words on one people moment: the January 2026 feedback, stopping the rewriting of her team's plans, the engineer she hired who now runs the hardest logistics accounts.
- Sharpen the short-term goal in paragraph 6: name settlement and reconciliation as the product surface, and name two real employers in Amsterdam, London or Singapore.
- Add one line linking her father's branch work with small exporters to the long-term goal. One sentence, no sentiment.
- Replace the three brochure clauses in paragraph 7 with one specific INSEAD element and one thing she brings: four years inside a Leeds claims operation and payments plumbing most of the class has never seen.
- Band-mover: replace the closing age sentence with the March 2026 fact, that she asked for product and was told to wait a year, and would rather spend that year changing what she is qualified for. That single swap answers why now, why not internally and why ten months.
10. Next steps
- Make the cuts first, paragraph 4 and the opening, before writing a single new sentence, so the revision is built inside the 500 words.
- Run Goals Credibility on the short-term product goal to pin down the payments segment and name two or three real target employers in Amsterdam, London or Singapore before you rewrite paragraph 6.
- Run Personal Story on the January 2026 coaching feedback and on your father's branch work with exporters, to decide which belongs in this essay and which belongs elsewhere in the file.
- Put the revised draft through Essay Doctor and check that reasons still make up more than half the words after the new material goes in.
- Use Recommender Prep so your Ledgerline director confirms the hiring, ratings and coaching change rather than repeating the 74-to-41 figure the resume already carries.
11. Information that would sharpen this
- Which intake and round you are applying to, since an August 2027 start makes you 29 on arrival and the essay currently says 28.
- Named target employers and the specific payments product surface you want, beyond "a payments company in Europe or Singapore".
- Any INSEAD-specific element you can honestly cite: campus choice and exchange direction, a course, a club, or a student or alum you have actually spoken to.
- Your title at the time you built the Corvane checker, Senior Engineer or Module Lead, so the "nobody had asked me to" claim is unambiguous.
- What the engineer you hired now does in detail, and what changed in your team after you stopped editing their plans.
- Whether a second essay or recommender notes exist, so overlaps with the Corvane story can be checked across the set.