Small IT projects in government — the fast-track route Joint Secretaries and Directors can use without floating an RFP (2026)

Every government officer reading this knows the pattern. You take charge of a department / division / branch / cell. Within weeks you spot three or four small but obvious gaps — a paper register that should be a web form, a quarterly report that takes two weeks of manual Excel work, an internal approval chain that loses files, a citizen-facing complaint inbox that nobody reads. None of these are crore-scale projects. Each one is a focused 4-8 week build. Each one would change life materially for your team.

And then nothing happens. Because the institutional reflex is: "we'll need an RFP, we'll need stakeholder consultations, we'll need budget approval, we'll need empanelment, we'll need GeM, we'll need Secretary's nod." Six months later you're transferred. Your successor inherits the same gaps and the same plan-to-do-something-about-it.

This article is the corrective. There are legitimate, audit-clean, fast routes within your own delegated financial powers to commission small custom IT work without any of the apparatus above. The General Financial Rules 2017 explicitly contemplate this; the Delegation of Financial Powers Rules (DFPR) authorises it; CVC and CAG audit it routinely. The only requirement is to do it correctly.

What follows is the playbook. It's written for officers — peer to peer. No marketing hype. Specific provisions, specific value bands, specific documentation, specific pitfalls.

The two documents that govern this

1. General Financial Rules 2017 (GFR)

The Ministry of Finance's bible for government procurement. Rules 144 onwards cover procurement of goods + services. The relevant rules for our purposes:

• Rule 154 — Petty cash purchases (very small)
• Rule 155 — Purchase by Three Quotations (₹25K to threshold ~₹2.5L)
• Rule 159 — Purchase through GeM
• Rule 161 — Purchase through Limited / Single Tender enquiry
• Rule 173 — Procurement of services (consultancy, software development, etc.) — broadly mirrors goods rules with adjustments for service-specific nature

2. Delegation of Financial Powers Rules (DFPR) — central, plus department-specific

Each Ministry / Department / PSU has its own DFPR table (or its equivalent — "Schedule of Delegation of Financial Powers"). These specify what financial commitments each level of officer can sanction without higher approval. Crucially, DFPR limits scale with rank AND vary between revenue/capital, recurring/non-recurring, and category of expenditure.

Knowing your own DFPR limits is the single most useful piece of homework for this entire playbook. Ask your DDO (Drawing & Disbursing Officer) or your Finance / Accounts wing for the latest version applicable to your post.

What financial powers does your post have? (indicative — verify your own DFPR)

Numbers vary widely by Ministry / department / scheme / capital-vs-revenue head. But broadly, central-government-equivalent indicative powers in 2026 look like:

For PSUs: the equivalent ladder is GM / DGM / DM / AGM with broadly similar bands but typically higher absolute limits (PSUs run with more financial autonomy). Refer to your PSU's own SoD (Schedule of Delegation).

States: each state has its own DFPR. UP, MH, KA, TN, GJ, RJ, MP, AP, TS, KL each have their own table. Check your state's Finance Department circular.

The three fast-track routes

Route A — Petty Procurement under GFR Rule 154 (under ₹25,000)

Direct purchase from any vendor with simple receipt. No quotations needed. No tender. No formal contract — a one-page work-order suffices.

What you can build for under ₹25K: A landing page. A single web form. A basic Google Sheet automation. A WhatsApp-driven information bot. A simple PDF-form generator. Useful for a 1-week sprint to test an idea before scaling up.

The catch: ₹25K is not enough for any meaningful custom dev work in 2026 if you want it done well. Use this only for true POCs.

Route B — Three Quotations under GFR Rule 155 (₹25K – ₹2.5L) ⭐ The Workhorse

This is the single most useful door for officers wanting to ship small modules fast. The process:

1. Define the scope on a single sheet of paper. What the system should do, who uses it, what it integrates with, when you need it. Half a page. Don't over-specify; you're not writing an RFP.
2. Identify three vendors. Two known competent firms + one you want to try. Or all three new vendors if you don't have prior relationships. They do not need to be on GeM. They do not need to be MSME. They do need to be a registered Indian Pvt Ltd / LLP with PAN + GST.
3. Email the scope to all three. Ask for a fixed-price quote within 7-10 days. Specify deliverables, timeline, payment terms.
4. Receive the three quotes. Compare on technical fit + price.
5. Select L1 of qualified bidders. Document your comparison. If you don't pick L1, document the technical justification.
6. Issue work order. Standard template — your dept's DDO will have it. Specify: scope, deliverables, milestones, payment, confidentiality, IP ownership (insist on source-code transfer), warranty, exit terms.
7. Vendor builds, you review at milestones, you sign UAT, vendor invoices, you sanction payment.

What you can build for ₹50K – ₹2.5L: A focused single-purpose internal application. Examples we've actually built in this band:

• A complaint tracker for one division (₹85K)
• An online leave-application form for 200 employees (₹1.2L)
• A monthly performance dashboard auto-generated from existing Excel feeds (₹1.5L)
• A field-inspector mobile app with photo + GPS upload for 60 inspectors (₹2.2L)
• A citizen-facing micro-site for a specific scheme with online application form (₹2L)
• A WhatsApp-bot for citizen FAQs trained on your departmental scheme document (₹1.8L)

Timeline: 4-8 weeks from scope to delivery. Total officer time: ~15 hours over the build cycle.

Route C — Single Tender / Nomination under GFR Rule 161 (above ₹2.5L)

For projects above the Rule 155 threshold but where you have justification to nominate a specific vendor. Used when:

• Vendor demonstrates unique fit (capability, prior PoC, specific technical expertise)
• Continuity from a prior pilot (you piloted with them under Rule 155, now scaling up)
• Time urgency (statutory deadline, emergency response, board-meeting commitment)
• Confidentiality / sensitivity (strategic-sector procurement)

The justification note (PN): Document why competitive tender doesn't work for your case. Cover (a) why standard GeM/competitive vendors don't fit (with documented evaluation), (b) why this vendor uniquely fits, (c) how cost-reasonableness was validated (e.g. cost-benchmarked against three GeM-listed comparables), (d) approvals obtained.

Approval ladder: Director can sanction up to ₹5L typically; JS up to ₹25L; AS up to ₹1cr; Secretary above. Vigilance clearance often required above ₹50L.

The Pilot-to-Scale Pattern (the most powerful pattern for officers)

This is how to legitimately commission a multi-crore eventual system without ever floating an RFP yourself:

1. Year 1, Month 1-2: Pilot one module under Route B (₹2L). E.g. attendance for one division. Single-vendor selection by quoting + comparison + work-order. Officer signs off on his own DFPR.
2. Year 1, Month 3-4: Vendor delivers excellently. You issue completion certificate + reference letter. Internal users love it.
3. Year 1, Month 5-7: Scope a second module — say, leave management for the same division (₹2.5L). Same vendor. Sanctioned by the same officer under the same Route B / Rule 155.
4. Year 1, Month 8-10: Third module — payroll integration (₹2.4L). Same pattern.
5. Year 1, Month 11-12: Fourth and fifth modules. By now, you have a working integrated 5-module system across one division built incrementally for ~₹12L total — without ever floating an RFP.
6. Year 2: Either (a) continue incremental modular expansion under Route B for additional features, or (b) when the system proves itself and you want to scale to other divisions, prepare a formal Rule 161 nomination justification using the strong reference from Year 1 — typically approved at JS/Director level.
7. Year 2-3: The system is now department-wide. Cumulative spend ₹40-60L, all sanctioned within delegated powers, all justified by documented prior delivery, all auditable.

Annual Maintenance Contract (AMC) — the recurring-cost route

An additional and underused tool: once you have a system live, the post-launch maintenance contract is its own GFR procurement and can be sanctioned at officer level under recurring-expenditure DFPR. AMCs typically run 5-15% of build cost per year. So a ₹15L system has a ₹1-2L/year AMC — well within Director / JS recurring-expenditure powers — that funds continuing improvements, statutory updates, hosting, support.

This is how a system stays alive over multiple postings: each successive officer continues the AMC, the vendor keeps maintaining + improving, the institutional capability compounds.

The 5 mistakes officers make that trigger vigilance flags

1. Picking the vendor before getting quotes

Document the vendor selection logic. Show that quotes were genuinely received from three vendors. If quotes are received only from one, get it on record (with email evidence) why the other two didn't quote. Save all email chains.

2. No written scope / deliverables

The scope sheet you sent the vendors must be in your file. Without it, the vigilance question becomes: "what exactly did we get for ₹2.5L?" With it, the answer is on paper.

3. Payment without UAT sign-off

Standard rule: vendor invoices only after milestone delivery + UAT. Officer signs UAT only after actually testing. Skipping UAT to clear vendor invoice fast is a vigilance flag.

4. No source-code / IP transfer clause

If the work order doesn't say "source code shall be transferred to the department on final delivery", you may lose the asset when vendor exits. Insist on this clause. Open-source delivery is preferable.

5. Repeated single-vendor sanctions over months without reason

If you commission 4 small projects in a year all to the same vendor, vigilance might ask why. Pre-empt by maintaining a vendor-rotation register or by documenting why each subsequent project was a continuation of the prior (the pilot-to-scale pattern, when documented, satisfies this).

Documentation kit — what should be in your file for every small IT procurement

For every Rule 155 procurement you sanction, the procurement file should contain:

1. The original problem statement / why this work is needed (1 page note)
2. The scope of work sent to vendors (1-2 pages)
3. Email evidence of invitation to all three vendors
4. The three quotes received (or evidence why fewer received)
5. Comparative statement (price + technical evaluation)
6. Selection note (why L1 / why technical-L1 if not L1 by price alone)
7. Sanction note signed by you under DFPR
8. Work order issued to vendor
9. Milestone-wise delivery acceptance / UAT sign-off
10. Invoice + payment sanction
11. Project-completion certificate
12. Source-code / artefact handover acknowledgement

This file should hold up to any future vigilance / CAG audit. If all 12 elements are in place, the audit will close cleanly.

Why Big Helpers fits this segment

We are designed for exactly this market. Specifically:

Small modules, fast turnaround

Our typical engagement is 4-12 weeks for a single module. We don't do 18-month enterprise builds. We ship the small thing the officer needs during their posting.

Direct partner engagement (no account managers)

You talk to Kashvi (Partner) directly. She doesn't pass you to a junior. There's no sales chain, no PMO theatre. The person you brief on Monday is the person co-ordinating delivery on Tuesday.

Open-source delivery, source code on day one

You own the asset. We deliver under MIT / Apache 2.0. You can hire any other vendor to maintain it. No vendor lock-in. Audit-friendly.

Hosted on YOUR infrastructure

On-prem / NIC cloud / MeghRaj / your private VLAN — your choice. Source code + data never leave your control. Crucial for sensitive deployments.

Pricing in your DFPR sweet-spot

Most of our pilot engagements come in at ₹1.5-2.5L — directly within Director / Deputy Secretary financial powers. Multi-module builds at ₹5-25L map to JS / AS powers. We deliberately structure quotes to fit the procurement route, so officer doesn't need to escalate above their own delegation.

NDA-first, then specifics

NDA before any project-specific discussion. Standard practice. Background-checked engineering team for sensitive work. Indian-citizen-only engineering for strategic-sector deployments.

2026 stack with AI-augmented dev

Modern frameworks (Laravel · Node.js · React Native · PostgreSQL) + LLM-assisted coding workflow → 3-5× faster delivery than 2019-era practice, lower cost, better-tested code. See how this works.

Three concrete examples (anonymised) of officers who shipped during their posting

Example 1 — Joint Secretary, central Ministry, ₹2.2L pilot in 6 weeks

JS in a central Ministry needed an internal complaint-tracking system for the Minister's office to triage citizen letters. Standard NIC software didn't fit the routing logic she needed. RFP would have taken 6 months. Under Rule 155, she invited three vendors, picked L1, work-ordered ₹2.2L, system delivered in 6 weeks. Used by the office for 18 months till her transfer. Successor extended via AMC. Vendor: us.

Example 2 — Director, state PSU, ₹4.5L MIS dashboard in 8 weeks

Director (Operations) of a state PSU needed a daily MIS dashboard pulling data from 4 source systems, distributed to 12 senior officers via WhatsApp. Big-vendor quote: ₹38L + 14 months. Under Rule 155 + state DFPR, he sanctioned ₹4.5L (slightly above the central Rule 155 threshold but within his own DFPR which was ₹5L). Three quotes obtained; we won as L1. Built in 8 weeks. Saved his finance team ~12 hours / week of manual report consolidation. He was later transferred and successor continued the system under AMC.

Example 3 — Deputy Secretary, autonomous body, ₹1.4L citizen micro-site in 4 weeks

DS in an autonomous body needed a public-facing micro-site for a specific awareness scheme (Hindi + English, mobile-first, online application form, scheme-status tracking). Society's procurement bye-laws permitted direct three-quotation contracting up to ₹2L. We delivered for ₹1.4L in 4 weeks. The micro-site has had 47K visits in 6 months and ~3,200 online applications.

None of these officers needed Secretary's clearance, none floated an RFP, none waited for GeM bids. All three procurements have stood up to internal audit + CAG inspection. Total officer time invested per project: 12-20 hours over the build cycle.

The bigger pattern — why officer-led incremental procurement is healthier than RFP-led big-bang

The standard objection to officer-level small procurement is: "shouldn't IT investment be planned strategically through proper RFPs?" Strategically — yes, for big systems. But the bulk of useful government IT improvement is incremental, contextual, and best done by the officer in the seat who actually understands the workflow. Big RFPs:

• Take 6-18 months to procure
• Get filled with feature-creep from every stakeholder consultation
• Produce systems that don't fit any specific user well
• Lock the department into one vendor for 5+ years
• Cost 5-10× what the same functionality costs incrementally

Officer-led incremental procurement:

• Ships in 4-8 weeks
• Solves one specific problem well
• Is owned and championed by the actual user
• Can be replaced / extended / discarded easily
• Costs a fraction of equivalent enterprise-RFP

The Indian government has historically over-favoured the first model and under-used the second. Officers have more procurement power than they realise. Use it.

Closing thought

You'll be in your post for two to three years. There are five things you wish your department did better. Three of those can be solved by small custom IT modules sanctioned within your own DFPR. None of them needs an RFP. None of them needs Secretary's nod. None of them needs GeM. All of them need a half-page scope, three quotations, a work-order, and 6 weeks of vendor delivery.

Pick one. Ship it before you transfer.

Big Helpers builds custom government IT in exactly this band — 4-12 week pilots, ₹1.5L–₹25L scale, open-source delivery, on your infrastructure. WhatsApp Kashvi at +91 99939 82666 — NDA before any specifics. — Kashvi

Related reading

• Big Helpers Government & PSU programme
• Government procurement without GeM or MSME — 7 routes
• Vendor lock-in: hidden ₹crores
• NIC eHRMS alternatives
• Open-source government IT strategy
• Custom attendance without Aadhaar
• AI in government IT delivery