Proposals and RFP Answers a Buying Committee Can Sign

Several people read a large proposal, each one part, and any one can stop it. In a formal RFP there is a gate before any of them. A State Bank of India RFP of June 2024, for IT maintenance, shows how hard it can be (opened 1 Nov 2026). Its "Technical Bid shall not contain any price information", or it "will be rejected". A responsive bid conforms "in toto, without any deviation". And "No Bidder shall contact the Bank on any matter relating to its Bid" from bid opening to award. A private bank may be softer. Read yours line by line.

Inside the rules, proposals stall in three ways: written for the champion, carrying claims nobody can source, or carrying commitments delivery never agreed.

My record: Happay, Vice President Marketing, Nov 2019 to Jan 2022: 161% ARR growth, +178% enterprise deal size, 65 to 72% marketing-sourced pipeline.

The method is yours, and a spreadsheet carries most of it. If you hold a past bid or an answer library, start there. The tools save drafting, and each output is a first draft you check.

I have shown the assembly step in public: at the IndoSales Bengaluru meetup on 11 April 2026, Sales Proposal Builder made a "6-slide pitch deck" in "under 3 minutes". On its brand styling I wrote: "The last 30% is human fine-tuning." (LinkedIn, 15 Apr 2026) That was a pitch deck. An RFP answer leaves far more to people, as the bid below shows.

This is my reading of the regulator's pages, not legal advice. Confirm the text with compliance, and re-check the pages before you send. Outside Indian banks, keep the clause table and change its sources.

The Reserve Bank of India's outsourcing directions for commercial banks, issued on 28 November 2025, repealed the existing outsourcing directions, which on my reading takes in the 2023 IT text. Small finance, payments and regional rural banks sit outside them.

Ask which route your deal takes, through the RFP's query channel. Chapter IV covers "material outsourcing of IT services", and the bank's policy sets the parameters. A fintech partnership can fall under Chapter III. Software bought "on a licence or subscription basis" sits outside Chapter IV, but "cloud computing services" sit inside it, so on my reading a subscription fee alone does not take a SaaS bid out. Take that to counsel. Arrangements outside these directions can fall under the cybersecurity directions of 31 July 2026, which still require "right to audit by the bank".

On Chapter IV, expect the bank's "right to conduct audits", extended to sub-contractors; regulator inspection; prior consent to sub-contractors; "storage of data only in India (as applicable)"; and termination with the "ability to orderly transfer" to another provider. One clause has a clock: the bank reports an incident to the regulator "within six hours of detection by the service provider". Continuity plans must be "tested periodically", and the policy needs "a clear exit strategy".

Payment data must be "stored in systems located only in India, except in cases clarified herein", and that reaches "third party vendors". If hosting, logs or support touch another country, find out before you answer.

Vendor risk review runs beside the RFP, so start its pack in week 1, and state go-live as dependent on the bank's timeline.

Step 1. Read the RFP, then decide whether to bid

About this example. TBX is a real company. TBX has not reviewed this guide. This is a worked example with public and illustrative inputs, not a client result. Facts about TBX come from public sources, linked alongside with the date I checked them. Every number marked illustrative, and every product line, capability, customer type, price, rollout and RFP rule in the bid, is an input I chose to show the method. None is TBX's data or pricing, and the tool outputs are exercise results, not TBX's real strategy.

TBX describes itself as "a financial infrastructure company". It took the TBX name in June 2026. In August 2025, as TransBnk, it raised a $25 million Series B, and reported more than 220 clients and work with more than 40 banks (company-reported).

If you ran go-to-market at a company like TBX, a bank RFP is a likely bid. The illustrative one: a mid-sized private sector bank wants API-based escrow and virtual accounts for corporate clients. Its rules are alongside.

First, bid or no bid. My questions: did you help shape the requirements, do you know the buyer, can you pass every must-have, and is the deal worth the effort? Here the open answer is the bank reference the RFP requires. Secure it, with permission, before you commit.

Then copy every requirement into a compliance sheet, in the RFP's order, with an owner. The format decides the sections; the seats decide what you say inside them. Put your win case where it scores: why you, against the in-house build and any rival. Send route and format questions in writing, inside the window, to the named officer only.

Step 2. Draft the executive summary, and rewrite it last

The first table alongside prints every field that shapes the text. All of it is illustrative except the labelled company-reported counts, the product line is my wording, and "the fastest bank integration in India" is a test line. I also set tone to consultative and your_sector to fintech.

The section writer, run for the executive summary with the c_suite audience, returned a frame around those inputs. Its "Before you send" list flagged the superlative and the client count. Rewrite the opening, as in the second table, and replace its merchant measures, such as "payment success rate", with this RFP's. Rewrite again last, once the sections are settled.

Step 3. Write the price and risk sections, then the clause table

Same inputs, two more runs: pricing justification and risk mitigation. Pricing came back identical for c_suite, procurement and technical. So fitting each seat is your edit.

With the same inputs on 4 November, the risk section opens "Supplied risks and controls for the Bank" and includes the India data-location and audit-trail requirements. It leaves probability and impact unassessed, and control owners and acceptance evidence unknown. It repeats the rollout as a proposed control for every row, so delivery and compliance still need to supply the control that meets each requirement. Build the clause table from the RFP and the regulator's text, then attach the control owner and acceptance evidence to each row.

The recorded pricing section's cost row reads "Spend that stops (payment success rate)"; write the bank's own cost line, such as staff time on reconciliation.

Check your price arithmetic too. My illustrative Rs 1.2 crore for 5 million calls is Rs 2.40 a call, against Rs 0.50 above the allowance. Say what the fee covers beyond calls, or change the rate.

Step 4. Give technology and finance their own sections

For technology I ran the section writer with the implementation plan section type and the technical audience. It printed my rollout line, then an example table that finishes in week 12, so delivery writes the real one.

For finance I ran the ROI business case builder with customer_name "the Bank", the solution line from step 2, cost_reduction as the value driver, the annual fee of 12,000,000, a current annual cost of 30,000,000 and a 60% expected improvement. All are illustrative and in rupees, though it prints a dollar sign, and the last two stand in for the bank's. The same inputs on 4 November returned annual value of 18,000,000, ROI of 50% and a payback ratio of 8.0 months.

The live tool describes that payback as "a simple annual price divided by annual value ratio, not a cash-flow forecast". Its conservative case now says "No payback: annual value does not exceed the recurring annual price". ROI and three-year net value still exclude one-time implementation costs, and this input has no field for the illustrative Rs 40 lakh fee or the agreed rollout and payment dates.

Use the monthly cash forecast alongside for the bid decision. The illustrative value beats the fee by only Rs 5 lakh a month, so rebuild it from go-live, about month 3.2. Starting the fee at go-live brings break-even from month 18 to month 11. In year one, with the fee from kick-off, illustrative value of about Rs 1.32 crore meets a cost of Rs 1.6 crore: a loss of about Rs 28 lakh.

Check the driver too. The buyer's first ask is new products, so on my reading its case rests on client revenue against an in-house build, not on reconciliation staff. And the illustrative target cuts hand matching by about 83%, from 30% to 5%, while this run uses 60%. Pick one basis.

You may never see the bank's figures before award, and you must not go round the RFP to get them. So state no return in the bid. List the numbers that decide it, for the bank to fill.

Step 5. Assemble, then run the commitment pass

I ran Sales Proposal Builder with the first three sections, the public facts and no brand sample. What came back kept my illustrative prices, rollout and targets, left deliverables, terms and legal text as placeholders, removed "the fastest bank integration in India" under its rule "NEVER claim competitive superiority without evidence", and turned the value table into four numbers for the bank to fill. It is a model run, so yours will differ.

It still carried lines nobody agreed. So run a commitment pass by hand, on human drafts too. Put your inputs beside the draft, and for every deliverable, promise and stated cause ask which input says it. If none does, strike it or have its owner agree it. Here it found ten lines.

The second assembly took the pass results, the technology section, the clause table and the RFP's rules. It gave a technical bid with no price, with compliance and deviation sheets, and a separate commercial bid. Both runs stopped at text.

Step 6. Check every claim before it goes out

Input to Claims fact check: both bids, and my named sources: the three public sources, the 2025 and 2026 directions and the payment data FAQ. The register came to 78 rows: 30 verified, 27 as pasted, 9 weaker than written, 4 unverified, 2 contradicted and 6 others.

A June 2026 press release says "Today, TBX serves 200+ clients". That is a floor and shows no fall from 220, so give both figures with dates and ask for the current count. "virtual accounts" and a "white-label" portal were "Not found on the pages I opened". TBX may well offer both; the product team confirms or the words go.

The check reads only what you name. For your own company, the product head and finance outrank any public page. An early draft of this bid cited the 2023 direction, whose page still loads with no repeal notice, so look for what replaced any rule you cite.

Step 7. Map each seat to its line, then run the send test

My suggested rule: write one line per seat, the sentence it must be able to accept without asking you anything.

Then the send test. Do not hold a bid for lines only the buyer can close, and do not go round the RFP to close them. Sort every open line into three lists, as alongside. Yours close before filing. What only the buyer knows goes on the sheet the RFP allows. The rest closes after award.

Where the RFP allows no deviation, a stated assumption can cost you the bid. Use the query window instead. If it has closed, the bid owner decides: answer as asked, or withdraw.

This is the point where I would want a second pair of eyes: a bank deal needs senior ownership before the send test. Bring me your win case, seat map, clause exceptions and commitment register, and we will work it through in 45 minutes.

1. Read your live RFP, then decide bid or no bid.
2. Build the compliance sheet, and send route and format questions through the RFP's channel.
3. Run the section writer once per section, then rewrite each for its seat.
4. Assemble, run the commitment pass, and sort every open line into the three lists.
5. Run Claims fact check on your own sources, and file when the first list is empty.

1. Using your own structure, not the RFP's.
2. Answering security with a generic risk table, not a control per clause.
3. Trusting a tool's rule against invented commitments.
4. Stating a figure without its date, or citing a rule without checking it is in force.
5. Filing with your own placeholders open, or going round the RFP's channel.

• One B2B Deal From MEDDPICC Discovery to a CFO-Ready ROI Case and a Dated Close Plan
• How to Hold Price in Late-Stage B2B Negotiation Without Losing the Champion
• Trust-Led Enterprise Selling in Fintech: Selling Payments Infrastructure to Banks Through Every Review
• All 30 guides