A man drove a team of donkeys around the marketplace of Pune, dragging a plough through the dust. Then he stuck an iron rod into the ground. That was the message: this place is dead, and it will stay dead. The general who ordered it, Murar Jagdev of the Adil Shahi kingdom, was making a curse you could see with your own eyes.1
By 1630–31 the curse looked true. Pune had never been much — a kasba, a village with a weekly market where people from nearby came to buy what they needed.2 But warring armies had wrecked it, and Jagdev wrecked it on purpose when the rival Nizam Shahi was cornered after Malik Ambar died. Then the Deccan famine of 1629 to 1631 finished off whatever crops, plants, and people were left.3 What remained was wolves.
Out of that ruin came a state. Not a battle plan first — a resettlement. Before Shivaji could raise an army he needed people who would farm, build, and stay. The story of Pune's rebuilding is the story of how you turn a ghost town back into a living place, and then turn that living place into the seedbed of a kingdom. The man who started the work was Dadoji Konddev, a Brahmin agent of Shivaji's father. The boy who finished the pattern across the whole estate was Shivaji himself, still a teenager.
This is the page about how an empire begins as an agricultural recovery project.
Shahaji Bhosle held the Pune jagir — a grant of land and its revenues — but he was away soldiering for other masters. In 1636 he asked Dadoji Konddev to look after the estate. Dadoji walked into a place where every house had been burned or smashed.4
In 1642 Jijabai and the young Shivaji moved to Pune, and Shahaji's younger son officially took charge. With the mother and son living there, the work sped up.5 Dadoji's first move was a roof over their heads. He built a one-storeyed house called the Lal Mahal. Around it he laid out a small enclave named Shivapur, and around the house an orchard.6
The order of operations matters. First a home, then a garden, then the fields. Dadoji was not just repairing a town; he was planting a center — a place where the heir would grow up, where people could see that someone meant to stay. A ruler who builds his own son a house in the wreckage is making a different kind of promise than a tax collector passing through.
Two problems stood in the way: the wolves, and the empty fields. Dadoji attacked both with cash.
He declared war on the wolves. Anyone who killed one — or a tiger, or any of the other beasts prowling the ruins — would be paid for it.7 This was not sentiment. You cannot ask a family to come back and farm a place where animals will eat them. Clearing the predators was the precondition for everything else, and paying per kill turned every desperate, hungry man into a game warden.
Then he went after the farmers. Cultivators were wooed with specific offers, not vague invitations.8 The deal had moving parts:
The logic underneath all of it: lower the risk of coming back, raise the reward for staying, and make the state's income rise and fall with the farmer's. The ruler bet on the harvest alongside the man holding the plough.
No single offer did the work. They braided together.
The wolf bounty did double duty. A displaced, destitute villager who came back got cash for killing beasts before he had a single crop in the ground.13 That cash bridged the gap between arriving with nothing and the first harvest. The bounty was a stopgap wage that bought the time the lease needed.
The first-year lease and the crop split worked as a pair. The cheap first year got a man to plant; the two-thirds share kept him planting. One solved the cold-start problem, the other solved the staying problem.
The tree deal and the orchard around the Lal Mahal pointed the same direction. Shivapur's orchard was a model — proof that fruit trees could grow here again. The tree-tax then spread that model into every plot, because a man who owned one tree in ten had reason to plant ten.
And the whole bundle scaled outward through Shivaji. The teenager extended the Pune arrangements across the wider jagir, and the displaced came home. The same offers that refilled one kasba refilled a district. The pieces did not just add up; they compounded.
Look closely at the wolf bounty, because it does more than it seems.
On the surface it is pest control. Pune was overrun with wolves and other beasts; Dadoji promised money for killing them.14 Practical, obvious, done. But notice who collected the reward. Many of Pune's old villagers had been scattered and ruined. When they trickled back, the first thing they could do for money — before any field was cleared or sown — was hunt the animals.15 The bounty was the first paying job in a town with no economy.
That changes what the bounty is. It is not only safety; it is liquidity. A returning family has no crop for months. The famine had stripped them bare. Without some immediate cash, hunger or another army would scatter them again before the first sowing. The bounty handed them money on day one and tied that money to a job that had to be done anyway.
It also selected for exactly the people Shivaji would later need. The men who went into the ruins to kill wolves and tigers were the hardy, the willing, the ones who would walk into danger for a reward. The same temperament that cleared the predators would later follow a young commander into the hill-forts.
And it was honest signaling. A ruler who pays per dead wolf is telling the populace: I am spending my own money to make this place safe for you. The promise of safety was not a proclamation nailed to a post. It was cash in a hunter's hand, repeated every time another beast was brought in. The bounty bought protection and trust in the same coin.
Picture a Kunbi farmer in 1643. He fled Pune during the famine and has been drifting between villages, half-starved. Word reaches him that the kasba is being resettled, that there is cash for killing beasts and land to be had cheap. He walks back.
He finds the place changed. There is a new house — the Lal Mahal — and a small enclave around it, Shivapur, with an orchard taking root. People are about. Dadoji's men tell him the terms plainly: kill the wolves near your plot and you will be paid; take this land and pay almost nothing the first year; plant trees and one in ten is yours.
So he hunts first. He brings in two wolves, collects the reward, and eats for the first time in weeks on money he earned the day he arrived. With the predators thinning, he clears a patch and sows. He plants a row of mango and tamarind, knowing one tree in ten will be his own. When the harvest comes, the jagirdar's man takes a third and leaves him two-thirds — more than he ever kept under the old chaos.
A season later, surveyors arrive. They measure his plot, write down that he rents it, and dig a well nearby; the men who dig are paid in cash. The farmer stays. He tells a cousin two valleys over. The cousin comes too. That is the workflow — not an order, a sequence of reasons to come back and remain.
Resettlement schemes usually fail, and you can name the ways. Watch for these and you can tell a Pune from a paper plan.
Safety promised but not bought. A ruler proclaims the land is safe and does nothing about the wolves. Families do the math and stay away. Pune avoided this by paying per kill — protection you could verify.
Rent set high to grab quick revenue. A grasping administrator charges full rent year one to recoup costs fast. No one with a choice plants. Dadoji set the first year nominal and said so up front, moving the risk off the farmer.
The state takes a fixed cut regardless of yield. A flat tax bleeds the farmer in a bad year and breaks his back. The one-third/two-thirds split tied the ruler's income to the harvest, so a bad year cost both.
No reward for long work. If a man cannot own what he plants, he plants nothing that takes years. The tree deal fixed this — one tree in ten was his.
A center that signals departure. If the ruler builds nothing for himself, the populace reads it as temporary. The Lal Mahal said the opposite: the heir lives here now.
The failure mode is always the same underneath — the state keeps the risk-free position and dumps the risk on the farmer. The Pune model worked because it took the risk back.
The source is a popular biography, not a revenue ledger. [POPULAR SOURCE] Purandare gives the resettlement terms — the bounty, the lease, the tree deal, the crop split, the wells — as narrative, and quotes a line about new crops in every village without footnoting a primary revenue record on this page.16 The specific percentages (one-third, one-in-ten) should be read as the received account, plausible and consistent with Deccan practice, rather than as figures pulled from a measured assessment roll.
The chopped-arm myth. A persistent legend holds that Dadoji Konddev cut off his own arm (or a hand) as punishment after wrongly taking fruit from the orchard, as a lesson in honesty. This is folklore, not established history — flagged here as myth, the kind of morality tale that accretes around a stern administrator. The source's own treatment of Maratha legend (see the Hindawi Swaraj oath below) shows how readily such stories harden into "fact."
The forged-oath parallel. Purandare is explicit that the famous 1645 Raireshwar oath of "Hindawi Swaraj" rests on two letters now established by leading historians as latter-day forgeries, manufactured by a family in a property dispute over the Maval of Rohid Khore.17 The same skepticism the source applies there should travel to the chopped-arm tale.
Open questions. How much of the "incentive design" was Dadoji's invention versus standard practice repackaged by a sympathetic biographer? Were the tree and crop ratios uniform across the jagir or did they vary valley by valley? Did Shivaji change the terms when he extended them, or copy them whole?
Purandare's telling — administrator-as-economic-rebuilder — sits inside a long argument among Maratha historians about how the Bhosle state was actually financed.
G. S. Sardesai, the grand narrator of the New History of the Marathas, tends to read figures like Dadoji as competent, loyal stewards whose careful estate management laid the ground for Shivaji's rise. On that reading, the resettlement is continuous with later Maratha revenue reform: the same instinct — measure the land, fix the share, reward the cultivator — that would later show up in the chauth and the famous kamal assessments. Purandare converges with Sardesai here. The Pune terms are presented as the small-scale prototype of the mature Maratha revenue system.
Jadunath Sarkar, more skeptical and more attentive to the gap between claim and record, would press harder on the numbers. Sarkar's instinct was to ask where the document is, and a popular biography's clean percentages would not satisfy him. The tension is not over whether Dadoji rebuilt Pune — that he did — but over how much of the orderly "incentive scheme" is hindsight imposed on what may have been improvised, opportunistic recovery.
Stewart Gordon, in The Marathas (the New Cambridge History volume), supplies the structural correction both narrative historians can lean on. Gordon's account of Deccan land tenure stresses that the watandar–mirasdar system was already there, deeply rooted, before any Bhosle touched it. On Gordon's reading, Dadoji and Shivaji did not invent a revenue machine; they plugged into an existing one and lowered the friction — cheap leases and predator-clearing to draw cultivators back into a tenure structure that long predated them.
Convergence: all three agree the resettlement mattered and that it prefigured later Maratha fiscal practice. Tension: Purandare and Sardesai read intentional design; Sarkar would demand the ledger; Gordon relocates the genius from invention to skilful use of an inherited system. The implication is that Shivaji's "economic seedbed" was less a thing he built from nothing than a ruined version of an old system he and Dadoji made worth rejoining — which makes the achievement one of trust and incentive, not engineering from scratch.
Why connect a seventeenth-century Deccan village to business and behavioral mechanics? Because the Pune resettlement is, stripped of its costume, an incentive-design problem solved well — and incentive design is the native language of economics and the deliberate construction of loyalty is the native language of behavioral mechanics. The connections below each produce something neither history alone nor the other domain alone would surface.
The state as risk-bearing entrepreneur — a handshake to business / economics. The single sharpest move in the Pune model is the one-third/two-thirds crop split combined with the nominal first-year rent. Read this as an economist would: the state has converted itself from a fixed-claim creditor (a landlord owed flat rent regardless of outcome) into an equity partner (a co-owner whose return rises and falls with the venture's yield). This is the difference between debt and equity financing, four centuries early. A fixed rent dumps all the weather risk on the farmer and guarantees the ruler's cut — and in a famine year it produces empty fields, because no rational, starving man signs a contract that bankrupts him in a drought. The crop split instead pools the risk: the ruler accepts a smaller, variable return in exchange for actually attracting capital — here, the farmer's labor and seed. The tree deal does the same with time rather than weather: granting the planter ownership of one tree in ten is a vesting schedule, equity that pays out only if the planter stays long enough for the orchard to mature. The insight the connection produces, and which neither domain generates alone: Shivaji's state was solvent and recruitable because it priced risk like a venture partner, not a rentier. This is the structural cousin of the Arthashastra — Kingship and the Rajarshi Ideal, where the ideal king is explicitly a co-sharer in the prosperity of the realm, the state-as-entrepreneur who profits by making subjects productive rather than by squeezing them. The handshake is precise: the Arthashastra states the principle (king and subject share the upside); Pune is the principle running in a real ruined town, with measurable terms — and the convergence suggests the resettlement was Kautilyan statecraft enacted, whether or not Dadoji had ever read the text.
Loyalty as engineered, not assumed — a handshake to behavioral mechanics. The resettlement did not only refill fields; it manufactured allegiance. Behavioral mechanics asks how you reliably move a population's behavior, and the Pune sequence is a clean compliance ladder. Start with reciprocity: the wolf bounty hands a returning man cash on day one, before he has produced anything. The state gives first. Reciprocity research holds that an unsolicited initial gift creates a felt obligation, and here the "gift" is also a job — doubly binding. Then consistency: a man who has hunted for the state's coin, then leased its land, then planted its trees, has taken a series of small public steps that each commit him a little more, the foot-in-the-door escalation that ends with a settled, dependent cultivator. Then sunk investment: the planted orchard and the dug well are costs the farmer cannot carry away if he leaves, so they bind him to the place and, through the place, to its ruler. The insight neither domain alone produces: the loyalty of the Maval populace that would later carry Shivaji's rebellion was not a pre-existing cultural fact he inherited — it was, in measurable part, the downstream effect of an incentive structure that gave people a reason to come, a reason to stay, and a stake to lose. This links to Psychological Resilience and the Survival of Humiliation: a population ground down by famine and the donkey-plough humiliation of a cursed town was given a path back to dignity through productive work, and the giver of that path collected their allegiance. It also touches Religious Tolerance as Political Philosophy — the same instrumental logic that rebuilt loyalty through incentives rather than coercion later showed up in how the Maratha state managed difference: bind people by giving them a stake, not by forcing a creed.
Sharpest implication. Shivaji's kingdom is usually told as a story of forts and cavalry and daring escapes. But the state was solvent before it was armed, and it was solvent because someone solved an incentive problem in a ruined town. The military history rides on top of a revenue history, and the revenue history is really a study in how to make people choose to come back. Power followed payroll.
Generative questions.