The Funding Gap DPACO Identified
Maharashtra’s APMC (Agricultural Produce Market Committee) regulatory framework directed capital funding exclusively toward market infrastructure — trading halls, weighing facilities, auction platforms, cold storage. For decades, the financial architecture of APMC development operated within this boundary. Farmer welfare facilities — places where farmers could rest, eat, and stay overnight during multi-day market visits — existed outside the funded category entirely.
This was not an oversight. It was a structural feature of how APMC funding was categorised under Maharashtra’s agricultural marketing legislation. The category simply did not exist. A facility for farmers required a new policy mechanism to be built at all.
DPACO’s project leadership identified this gap through direct engagement with APMC committees across Maharashtra. The intelligence came from the ground — from PMC experience on APMC market complexes, from conversations with APMC committee members, and from the recognition that a consistently unmet need, across multiple APMCs, constituted a policy opportunity rather than a project-by-project problem.
“Infrastructure projects do not begin at tender. They begin at the moment someone identifies a gap that government has yet to formalise. The Shetkari Bhavan scheme existed as a DPACO proposal for months before it existed as a government programme.”
Structuring the Policy Proposal
Before approaching government, DPACO developed the full framework — because a policy proposal without financial architecture is a suggestion, not a scheme. What DPACO brought to the meeting with the Minister of Agriculture was a complete proposal package:
A new funding category — formally defined, with the regulatory language required for inclusion in APMC committee budgets under the Maharashtra Agricultural Produce Marketing (Development and Regulation) Act.
A per-unit budget structure — ₹1.5 crore per Shetkari Bhavan location, developed from a standard design brief covering the amenities (dormitories, canteen, sanitation, storage), construction parameters, and area requirements. The figure was not an estimate. It was a costed brief that DPACO had validated against actual construction rates across Maharashtra’s districts.
A replicable design standard — a standard architectural brief that could be adapted to each APMC location without requiring individual design commissions. The standard brief reduced time-to-approval, reduced inter-APMC inconsistency, and made the scheme fundable across multiple locations simultaneously.
A PMC model — a defined framework for how project management consultancy would be structured across multiple APMC jurisdictions simultaneously, with consistent quality standards and centralised documentation.
Government Adoption
The Minister of Agriculture reviewed the proposal. The scheme was adopted as Maharashtra government policy. APMC committees began receiving earmarked funding under the Shetkari Bhavan category for the first time. A new line item appeared in Maharashtra’s APMC capital allocation framework.
The adoption process required DPACO to navigate multiple government departments: the Agriculture Department, which oversees APMC policy; the Finance Department, which approves new budget categories; and the individual APMC committees, which required their own committee resolutions to access the new funding stream. DPACO coordinated this process because DPACO had designed it to be coordinated — the proposal had anticipated the approval pathway.
Government adoption in Maharashtra’s agricultural sector is not a single event. It is a cascade: state policy adoption → individual APMC committee resolution → budget allocation → procurement mandate. DPACO’s 45-year experience with this cascade — across water supply, transport, municipal, and now agricultural infrastructure — compressed the timeline significantly.
17 Agreements — Managing Scale
DPACO was appointed PMC across 17 APMC locations across Maharashtra. Each location required an individual PMC agreement with that APMC committee — a separate procurement, a separate scope definition, a separate project management mandate. Simultaneously.
The operating model DPACO developed for Shetkari Bhavan PMC operates across four axes:
Standardised Documentation
A single set of baseline project documents — scope of work, PMC reporting format, progress milestone structure, quality checklist — adapted for each APMC’s specific site conditions and committee requirements. Standardisation at the document level means each location’s project management is consistent without requiring a separate documentation team per site.
Centralised Technical Review
All structural, architectural, and MEP reviews for the 17 locations pass through DPACO’s central technical team. Site-level supervisors manage daily execution; technical review and approval authority is centralised. This prevents quality variation across locations without multiplying senior technical headcount.
Parallel Government Coordination
Each APMC committee has its own procurement cycle, committee approval process, and government interface. DPACO’s institutional relationships — developed over decades of APMC engagement — allow parallel coordination across all 17 committees without the coordination overhead that would paralyse a firm without these relationships.
Unified Reporting
A single consolidated progress report covers all 17 locations, formatted for the Agriculture Department’s monitoring requirements. Individual APMC committees receive location-specific updates. The Agriculture Department receives the consolidated picture. DPACO produces both from a single data collection process.
“By the time competitors were aware the programme existed, DPACO was already PMC across 17 locations. The institution that originates the scheme is the institution that delivers it.”
The Playbook — Applied Elsewhere
The Shetkari Bhavan model is structurally replicable. The core logic: identify a funding gap within an existing government sector, design the policy mechanism and financial framework, propose directly to the appropriate government decision-maker, and position for PMC appointment on the resulting programme. DPACO has applied this logic across transport (the MSRTC BOT framework), water (the MJP source-to-tap programme), and urban infrastructure (APMC market complex redevelopment).
For a government body, developer, or institutional authority with an infrastructure need that does not yet have a funded policy mechanism — this is the DPACO entry point. The question is: does a workable policy mechanism exist? If it does, DPACO manages within it. If it does not, DPACO designs one.