He consulted his ability extensively: What are common pitfalls in business partnerships between unequal parties? What leverage do I actually have? What should I absolutely not agree to?
The answers were detailed, sometimes contradictory, always useful. But they all pointed to one fundamental truth: he was negotiating from a position of growing strength, but not yet equal strength. Patnaik had capital, connections, and fifteen years of experience. Ajay had momentum and reputation, but both were fragile.
On Wednesday evening, Santosh visited unexpectedly.
"I heard Patnaik approached you," he said without preamble.
News traveled fast in business circles, apparently. "He did. How did you know?"
"He mentioned it when I saw him at the wholesale market. Asked what kind of person you were, whether you were trustworthy." Santosh sat down heavily. "What did you tell him?"
"That I'd consider his proposal. He wants partnership—coordination on prices, shared suppliers, joint opportunities."
"Do you trust him?"
"I barely know him."
"Smart answer." Santosh pulled out a beedi, lit it thoughtfully. "Let me tell you about Patnaik. He's successful because he's shrewd, not because he's honest. He'll honor agreements when it benefits him, bend them when it doesn't. But he's not malicious—just practical to the point of ruthlessness."
"Should I refuse the partnership?"
"No. You should negotiate very carefully. Everything in writing, everything specific. Leave no room for interpretation. And never, ever become dependent on him for anything critical."
"You sound like you speak from experience."
Santosh smiled grimly. "I partnered with him once, five years ago. Agricultural equipment rental scheme. Looked good on paper. In practice, he controlled the equipment, the customers, the pricing. I was just providing capital and taking orders. Ended it after six months—didn't lose money, but didn't gain anything except a lesson."
"What lesson?"
"That partnership with someone more powerful than you is only beneficial if you bring something they genuinely need and can't get elsewhere. Otherwise, you're just a convenient tool they'll use and discard."
What do I bring that Patnaik genuinely needs?
Analysis: Your value to Patnaik: 1) Local trust and customer relationships he lacks, 2) Advisory credibility that enhances his brand by association, 3) Coverage of small villages he finds unprofitable to serve directly, 4) Your ambition contained within structured relationship rather than as uncontrolled competition. Key insight: he needs you to NOT become his competitor more than he needs what you currently provide. This is defensive partnership primarily.
"He's more worried about me as future competition than excited about me as current partner," Ajay said slowly.
Santosh nodded approvingly. "You're learning. Yes. So the question is—do you want to be contained in a structured partnership, or do you want to remain independent and deal with the friction that creates?"
"I want to grow."
"Then you need to decide which path enables more growth—protected partnership with a powerful player, or independent operation with more freedom but more resistance."
After Santosh left, Ajay sat with his notebooks, thinking through the decision tree. Both paths had merit. Both had risks.
Which path has higher expected value over five years?
Complex calculation with many variables. Partnership path: higher initial growth through access to resources and reduced conflict, but lower ceiling due to constraints and profit-sharing. Independent path: slower initial growth, more friction and resource expenditure managing conflicts, but higher ultimate ceiling if successful. Key variable: your ability to navigate conflicts and build alternative networks independently. Given your unique capability to acquire knowledge and make informed decisions, independent path has higher expected value IF you're willing to accept higher variance and work harder.
Higher expected value, higher variance, more work.
That sounded about right for his situation.
Thursday morning, Ajay cycled to Kendrapara. Patnaik's office was in a commercial building near the market—two rooms, well-maintained, with a clerk managing paperwork and a small warehouse visible through the back door.
Patnaik greeted him warmly. "Ajay! Come in, come in. Chai?"
They settled with tea. Patnaik pulled out a handwritten document. "I've drafted a basic framework. Look it over, tell me what you think."
Ajay read carefully:
COOPERATION AGREEMENT
Between: Patnaik Agricultural Supplies (Party A) and Ajay Mallick (Party B)
Terms:
- Party B operates in villages under 500 population within territory defined by Party A
- Both parties maintain minimum prices as agreed quarterly
- Supplier information shared confidentially between parties
- Customer referrals between parties for products/services not offered
- Joint purchasing opportunities explored when beneficial
- Either party may terminate with 30 days notice
It was vaguer than the Mohan agreement, which immediately raised flags.
"Point one—'territory defined by Party A' is too vague. Who decides what's in the territory? What if we disagree?"
"I decide initially, we discuss if you object."
"No. Territory should be explicitly listed—village names. And I should have input, not just objection rights."
Patnaik's eyebrows rose. "You want equal say in territory definition?"
"I want clarity. Ambiguity leads to disputes. Let's define exactly which villages I operate in, which you operate in, and which are shared or neutral."
"That's... more rigid than I intended."
"Rigid means clear. Clear prevents problems."
They negotiated for two hours. Ajay pushed back on every vague clause, demanded specificity, insisted on mutual consent requirements rather than unilateral control.
Patnaik grew frustrated. "You're making this very complicated. I'm offering a simple cooperation agreement."
"Simple for you means risky for me. I'm smaller, newer. If anything goes wrong, I have more to lose."
Finally, Patnaik sat back. "You negotiate like someone much older. Where did you learn this?"
"Books. And experience."
"What books teach you to be this difficult in negotiations?"
Ajay smiled. "The ones written by people who got cheated by vague agreements."
Eventually they reached a revised version:
COOPERATION AGREEMENT - REVISED
Between: Patnaik Agricultural Supplies (Party A) and Ajay Mallick (Party B)
Terms:
- Party B operates primarily in: [15 specific villages listed]. Party A operates primarily in: [8 larger towns/villages listed]. Neither party excluded from other's territory but will not actively compete on price in primary territories.
- Minimum pricing reviewed jointly each quarter based on wholesale cost changes. Either party may propose changes, both must agree to implement.
- Supplier information shared voluntarily and confidentially. No obligation to share proprietary relationships.
- Customer referrals encouraged but not required. No commission on referrals unless separately agreed.
- Joint purchasing opportunities explored on case-by-case basis. Each party commits only to purchases they independently approve.
- Agreement duration: one year, renewable by mutual consent. Either party may terminate with 60 days notice.
- Disputes resolved through mediation by mutually acceptable third party before any legal action.
It wasn't perfect, but it was workable. More importantly, it protected Ajay's independence while opening doors for cooperation.
"This is much more balanced," Patnaik admitted. "Also much more protective of your position than I expected you to negotiate."
"Is that a problem?"
"No. Actually, it's reassuring. Partner who can negotiate for themselves won't be a burden later." He extended his hand. "Agreed. I'll have this written formally, we'll sign next week."
They shook hands.
This narrative has been unlawfully taken from Royal Road. If you see it on Amazon, please report it.
As Ajay was leaving, Patnaik called out: "One more thing. There's a government tender coming—supply of agricultural inputs to 50 government schools in the district for their farm education programs. Contract value about 3 lakh rupees over one year."
Three lakh rupees. Ajay's entire annual revenue currently.
"Why are you telling me?"
"Because neither of us can bid alone—requires registration, tax compliance, bank guarantees, past performance records. But if we bid jointly, combining our credentials, we might win. You'd handle execution for the small schools, I'd handle the larger ones. Split the contract 40-60, profit distributed accordingly."
What are the risks and benefits of bidding for government contracts?
Benefits: Large revenue, reliable payment (eventually), reputation enhancement, stable cash flow. Risks: Payment delays (government notorious for 3-6 month delays), complex compliance requirements, penalty clauses for non-performance, working capital requirements to fund operations before payment, corruption/bribery often expected in tender process. For first-time contractor, risk is significant.
"What's the timeline?"
"Tender opens next month. We'd need to prepare now. Requires about 15,000 rupees in documentation, bank guarantees, registration fees. We'd split that cost."
"And bribes?"
Patnaik didn't flinch at the direct question. "Possibly. Depends on competition. Could be 5-10,000 to the right people to ensure our bid is viewed favorably. Again, we'd split it."
So 7,500 rupees investment for a chance at a contract worth potentially 1.2 lakh rupees to Ajay (40% of 3 lakhs). The math was attractive if the contract was real and they won.
"I need to think about it. Can I give you an answer in a week?"
"Tender deadline won't wait. Three days maximum."
"Three days then."
Cycling home, Ajay's mind raced. The government contract was tempting but dangerous. The payment delays alone could kill his cash flow—imagine delivering 30,000 rupees worth of supplies and waiting six months for payment while he still needed to restock and pay his people.
That evening, he consulted Santosh again.
"Government contracts are poison for small operators," Santosh said immediately. "The payment delays will destroy you. You don't have the capital buffer to wait months for money."
"But the revenue—"
"Is imaginary until the money actually arrives. I know three businessmen who went bankrupt waiting for government payments. The contract says 30 days, reality is 180 days. Can you survive six months without that revenue?"
Ajay did the math. If he committed 30,000 rupees in supplies and didn't get paid for six months, he'd need to find that capital elsewhere to keep operating. His current savings were only 12,400 rupees.
Could I borrow to bridge the payment gap?
Options: Bank loan unlikely without collateral. Moneylender possible at 3-5% monthly interest—18,000 rupees over six months on 30,000 borrowed = massive cost. Family loan limited and risky. Supplier credit possible but strains those relationships. Conclusion: without substantial capital buffer, government contract payment delays create dangerous cash flow crisis.
"You're right," Ajay admitted. "I can't afford the cash flow risk."
"Then don't bid. Let Patnaik handle it alone. When you're bigger, with more buffer, then consider government contracts."
But Ajay hated refusing opportunities. Is there any way to structure this to reduce risk?
Possibility: Negotiate different split where Patnaik provides working capital and takes larger share of profit. Example: He funds 80% of supply costs, takes 70% of profit. You provide execution and local relationships, take 30% profit but minimal capital risk. Essentially he becomes banker and majority profit-taker, you become commission-based executor.
That could work. Less profit, but less risk.
The next day, Ajay returned to Patnaik with the counter-proposal.
"I can't afford the cash flow risk of government payment delays. But I'll participate if you provide most of the working capital and take corresponding profit share. You fund 80% of supply costs, take 70% of profit. I execute the contract, take 30% profit. No capital risk for me beyond the initial tender costs."
Patnaik considered it. "So I'm taking all the financial risk and most of the profit, and you're just managing execution?"
"You're taking the risk you can afford. I'm providing the execution capacity and local relationships you'd struggle with. Both parties contribute what they're positioned to contribute."
"What if you fail to deliver properly? I'm stuck with penalties and reputation damage."
"Include penalty clauses in our agreement. If I fail to meet delivery schedules or quality standards, I forfeit my profit share and compensate you for penalties."
Patnaik tapped his fingers on the desk, thinking. "60-40 profit split, not 70-30. You're providing significant value through execution."
"Agreed."
They shook hands again.
"You're turning out to be a more interesting partner than I expected," Patnaik said. "Most people your age would either refuse entirely out of fear, or agree blindly out of greed. You're finding the middle path."
"I'm trying to survive and grow. That requires balancing opportunity and risk."
Back home, Ajay updated his strategic planning notebook. He was now entangled in multiple partnerships: Santosh for the STD booths, territorial agreement with Mohan, cooperation agreement with Patnaik, and now a joint venture on the government tender.
Each relationship provided benefits but also constraints. Together, they formed a web—supporting him, but also binding him.
Am I building a business network or creating dependencies?
Both simultaneously. Networks provide resources and protection but create obligations and constraints. Key is maintaining balance—enough partnerships to leverage resources, not so many that you lose independence or become paralyzed by conflicting obligations. Current assessment: You're approaching maximum sustainable partnership complexity. Adding more relationships without stronger operational foundation risks losing strategic clarity.
He was approaching his limit. Time to focus on strengthening what he had before adding more.
That night, Priya appeared during dinner with a question. "Bhai, I've been thinking about the STD booth accounting. We're tracking daily revenue, but we're not tracking customer patterns properly."
"What do you mean?"
"Like—which customers call the most, what times are busiest, which destinations are most common. If we knew that, we could do targeted promotions. Offer discounts to frequent callers, extend hours during peak times, create special rates for common destinations."
Ajay paused mid-bite. She was right. They were collecting data but not analyzing it systematically.
What customer insights could be derived from STD booth call records?
Significant insights available: customer lifetime value, usage patterns by demographics, price sensitivity analysis, peak demand forecasting, destination clustering for potential special rates, customer retention trends, revenue per customer, acquisition cost analysis. Current data collection is sufficient for analysis if systematically organized.
"You're absolutely right. We should be analyzing this data. Can you set up a system?"
"I already did." She pulled out a notebook—her own, not his. Inside were detailed tables and hand-drawn charts. Customer names, call frequencies, total spending, patterns over time.
"When did you do this?"
"Last two weeks. At night after homework. Look—Ramu kaka calls his daughter every Sunday evening, exactly 15 minutes, costs him 60 rupees monthly. If we offered him a 'Sunday Special' package—four Sunday calls for 200 rupees instead of 240—he'd probably take it. And we could offer it to the other regular Sunday callers too."
Ajay stared at his fourteen-year-old sister's business analysis, impressed and slightly unsettled. She'd taught herself customer segmentation and promotional pricing design.
"This is... this is really good work, Priya."
"So can we do it? The Sunday package?"
"Yes. Design it properly, we'll launch next week."
Their mother, listening from the kitchen, spoke up. "She should be studying mathematics and science, not spending nights on shop calculations."
"This is mathematics, Ma," Priya said. "Applied mathematics. The useful kind."
Their father, quiet as usual, surprised everyone by speaking. "Let her do both. The girl has a head for this. Why waste it?"
That small endorsement from their traditionally-minded father felt significant.
After dinner, Ajay pulled Priya aside. "You're good at this. Really good. But don't let it consume you. Education still matters most."
"I know. But bhai—education and business aren't separate. Everything I learn in school, I can apply here. Percentages, accounting, customer psychology, even the English language for dealing with suppliers. It all connects."
She was right, of course. The artificial separation between "education" and "practical skills" was always false.
"Keep doing both then. But if your school marks drop even a little, this stops. Deal?"
"Deal."
September ended with the monsoon receding and the festival of Durga Puja approaching. The government tender bid had been submitted—Ajay and Patnaik jointly, with all the required documentation and, yes, the expected 8,000 rupees in "facilitation fees" split between them.
Results would come in November.
Meanwhile, Ajay's monthly financial picture had evolved:
Monthly Summary - September 2001:
Revenue streams:
- Grocery: 1,800
- Medical supplies: 2,800 (growth in new villages)
- STD booth #1: 2,700 (his 70% share)
- STD booth #2: 1,600 (improving under new incentive structure)
- Agricultural: 3,800 (seasonal variation)
- Vermicompost: 400
- Godrej products: 200 (still below expectations)
Total: 13,300 rupees
Expenses:
- Subash: 3,000
- Sushila: 600
- Priya: 600
- Prakash (booth #2): 2,200
- Inventory/restocking: 3,400
- Miscellaneous: 500
Total: 10,300 rupees
Net profit: 3,000 rupees
Three thousand rupees. Better than months ago, but still far from his goals. And the profit had actually declined slightly because expenses had grown faster than revenue.
Why is profit growth stalling?
You're hitting diminishing returns on current business model. Each new village or product line adds revenue but also adds nearly proportional costs in inventory, staff time, distribution. To break through requires either: 1) Significantly higher margins through premium products/services, 2) Major scale increase through expansion or large contracts, 3) Moving into businesses with better revenue-to-cost ratios, 4) Reducing costs through efficiency improvements.
The government contract, if they won, would be option #2—major scale increase. But it was uncertain.
What else could he do?
What are the highest-margin business opportunities accessible with my current capital and capabilities?
Analysis of options: 1) Agricultural processing (rice milling, dal processing) - high margin but requires 50,000+ capital, 2) Commission-based services (insurance agent, financial products) - high margin, low capital, requires training and licensing, 3) Educational services (tutoring, coaching classes) - high margin, time-intensive, limited scale, 4) Technical services (computer/mobile repair as technology arrives) - high margin but requires skills you lack, 5) Consulting/advisory (agricultural consulting, business consulting) - highest margin, scales with reputation, requires no capital.
Consulting. He kept coming back to that. He was already doing it informally—giving farming advice, helping customers make decisions. What if he formalized it?
What would a formal agricultural consulting service look like in rural Odisha 2001?
Model: Offer paid farm visits and advice sessions. Services include: soil testing recommendations, crop selection guidance, pest/disease diagnosis, fertilizer planning, water management advice, yield optimization. Pricing: 200-500 rupees per consultation depending on complexity. Target: progressive farmers with 5+ acres who can benefit from professional advice. Revenue potential: 2,000-4,000 monthly with 10-15 consultations. Main challenge: convincing farmers to pay for advice they currently get free.
The pricing seemed high. Would farmers actually pay 200 rupees for advice?
What's the highest price point farmers would accept for agricultural consulting?
Price sensitivity analysis: Farmers will pay for advice if: 1) The expected value clearly exceeds cost (e.g., 200 rupee advice that increases yield worth 2,000 rupees), 2) They've tried free advice and it failed, 3) The consultant has proven track record, 4) Consultation includes follow-up and accountability. Starting price point: 100 rupees for basic consultation, 300 for detailed farm planning, 500 for ongoing seasonal advisory. Most accessible market: farmers currently losing money who need help, not successful farmers who are already doing well.
That made more sense. Start cheap, prove value, raise prices as reputation builds.
Ajay opened a new notebook page: Agricultural Consulting Service - Launch Plan.
He'd start in October, after Durga Puja when farmers were planning their winter crops. Offer the first five consultations free to build case studies and testimonials. Then charge modestly—50 rupees per consultation to start. Increase prices as demand proved the value.
Low capital requirement, high margin, played to his strengths.
It was worth trying.
One more stream feeding the river. One more step up the mountain.
Slow and steady, his father had said.
But Ajay was learning that slow and steady didn't mean standing still.
It meant building, piece by piece, until the accumulation of small wins became something significant.
He was getting there.
The question was whether he'd get there fast enough.