The founder of a small startup gets the email she has been waiting for in the second week of December. Her champion at a mid-sized logistics company writes that the operations team wants to keep the product after the pilot. Then comes the bad news: the CFO wrapped up budget season last week, and the 2027 plan has no line for the product. The champion suggests they revisit the purchase next fall, which for a startup means a year of runway spent waiting.
Nobody on the founder's team asked about the buyer's planning calendar back in September. At most companies with a calendar fiscal year, department heads draft spending requests in October and defend them in November. Finance trims those requests, and the executive team approves a plan that has money waiting in January. Everything outside that plan competes for a small discretionary pool or waits for the next cycle.
If you run sales at a startup and have pilots ending this quarter, you can still avoid that email. The fix is a handful of questions on your next calls and a one-page document your champion can paste into a budget request. Below is how the buyer's planning cycle works, what to ask, how to write the document, and what to do if you find out too late.
Budget season is the period when a finance team decides what each department can spend next year. For buyers on a calendar year, it usually starts in early October and ends by mid-December. The dates shift from company to company, but the process tends to move through four stages.
For a vendor, the useful fact is that each stage has a deadline. The champion's request has to enter the first stage before that deadline passes, or it waits a year. A startup that learns the calendar in December is asking the buyer to reopen a finished plan. Few finance teams will do that for a vendor they have never paid before.
Startups miss budget season for ordinary reasons, and most trace back to who the founder talks to. The product is rarely the problem, and the user on the other side is often happy with it.
Every item on that list ends in the same place. The champion walks into planning meetings without a written request, and nobody on the vendor side asked whether one existed.
Recent CFO surveys suggest many companies will fund new technology, but that money usually goes to vendors a department head has already written into a request. Gartner surveyed more than 300 CFOs in October 2025 about their plans for the coming year. More than half planned to raise their sales and IT budgets for 2026, and 75% planned higher technology budgets.
Grant Thornton's March 2026 CFO survey release pointed the same way. It reported that CFOs are speeding up technology spending as AI momentum grows. Those figures describe last year's cycle, while the 2027 cycle is happening at your prospects right now.
Even so, a bigger technology budget does not spread evenly across every vendor that ran a good pilot. Finance funds the requests a department head wrote down and defended with an outcome the CFO cares about, such as fewer overtime hours or a faster month-end close.
In October, then, a founder needs two facts about each open deal: whether a request exists, and who is writing it. Founders who wait for the champion to raise the subject usually hear about it after the plan closes.
The simplest way to learn a buyer's planning calendar is to ask, once the buyer confirms the problem is real. Most champions will explain how planning works at their company, because the answer helps them too. Ask about process and dates before dollar amounts, because a champion tends to hear a calendar question as help and a price question as pressure.
Five questions cover what a startup needs to know, spread across a discovery call and a pilot check-in:
Ask these on a live call, because the champion's tone tells you as much as the answer does. A champion who says "I'll have to check" is being honest, and you can follow up in writing later. If the champion has never heard of a 2027 request process, they may sit too far from the budget. In that case, ask for a meeting with the manager above them.
Record the answers where the whole team can see them, such as a CRM field or a shared deal note. If you build a mutual action plan with buyers, add the submission deadline as a dated step the champion owns.
A finance reviewer has a short list of questions about any software request. Requests that answer them in advance move faster through review. The first question is what the problem costs today, whether in staff hours or lost deals.
Next, the reviewer wants a name: who inside the company will own the result? Price comes after that, including the full annual amount and whether the purchase replaces a tool already in the budget. Startups often lose at this stage because the champion's request describes the product and says little about the problem.
Finance sees a list of capabilities from a vendor nobody inside has worked with, so the request drops below the line. Written around a cost the department already feels, the same request reads like a fix for a known issue. A reviewer who sees the operations lead's own description of the problem has less reason to doubt it.
The business case is the document your champion pastes into the budget request or brings to the planning meeting. It should fit on one page, and most of its sentences should come from things the buyer said on calls. Finance trusts language from inside the company, and the champion can defend words they said themselves. Four steps produce a draft the champion can edit in an afternoon.
Go back to the discovery call and find the moment the buyer described the problem in their own terms. Use that phrasing in the first paragraph, with the speaker's name and role if the champion agrees. A line like "our dispatchers rebuild the route plan by hand every Monday" does more work than vendor copy.
Buyers often estimate the cost of a problem out loud during discovery, even when the estimate is rough. Quote that estimate and credit it to the person who said it. A figure from the operations lead survives finance review better than one from the vendor. If nobody has put a cost on the problem yet, ask the champion and their manager to estimate one.
Finance wants one person accountable for the result and a clear date when the spending begins. Name the owner the champion suggests and the single metric that person will report on. Then tie the start date to a real event on the buyer's calendar, such as the first week of Q1. A date that matches a planned process change also makes the request look thought through.
List the full annual cost, including onboarding and any services, so finance sees no surprise in March. Then add a short paragraph, written from the buyer's side, on what happens if the company waits a year. Usually the problem continues, and the team keeps paying for it in the terms from step two. Keep the tone factual, because a finance reader discounts anything that sounds like a sales deck.
Writing the request is half the work, because the champion still has to defend it without you. As we covered in our guide to champion development, an internal seller needs material and practice as much as belief.
Before the planning meeting, hold a short prep call and walk through the questions finance will likely ask. Find out which other requests compete for the same money, since the champion usually knows. Your case should then explain why this one comes first. Give the champion a short answer to "can this wait a year," because finance asks it about most new vendors.
Offer to join a call with the budget owner if the champion wants support, but let the champion decide. Some finance teams want to hear from the vendor directly. Others see a vendor in the room as a sign the department head can't explain the purchase alone, and your champion will know which kind of finance team they have.
By late November, most champions in your pipeline will say they are working on the budget. The real difference shows up in specifics, mostly names and dates. Use the table below in pipeline review to sort each deal before it enters the Q1 forecast.
| Signal | Polite maybe | Real 2027 line item |
|---|---|---|
| Budget timing | "We'll sort it out in the new year" | Champion names the submission deadline |
| Request owner | Nobody named | Champion or their manager wrote it |
| Business case | Your deck, forwarded as is | One page in the buyer's words, edited by the champion |
| Amount | "Depends on pricing" | A specific annual figure in the request |
| Economic buyer | Never on a call | Joined a call or reviewed the case |
| Next step | "Let's reconnect in January" | A dated review meeting on both calendars |
| After the plan closes | Silence | Champion confirms the line survived |
Most deals show a mix of both columns in October, and that is normal. By mid-December, a deal still in the left column belongs in next year's pipeline, and the forecast should say so. When the founder moves it early, reps spend December on deals that can still close, and the board sees a Q1 number that holds up.
Missing budget season does not always mean waiting a full year, but the options get narrower. Work through these four with the champion before you give up on the deal.
Whichever path you take, write down the date the next budget season opens at that company. Then set a reminder for six weeks before it, so the champion starts next year's request in August.
The hard part of budget season selling is tracking what each buyer said about money and timing across many calls. Startup founders and account executives often hear the planning calendar once, and the detail never reaches the CRM. Rafiki AI is a conversation intelligence platform that records and analyzes sales calls. Several of its capabilities map directly to the steps above.
Smart Call Summary captures what each call covered, including the deadlines and names a buyer mentions. Then Smart CRM Sync writes those details into the deal record. It fills methodology fields such as BANT budget or MEDDIC economic buyer, plus any custom deadline field.
While drafting the business case, you can use Ask Rafiki Anything to find the moment a buyer named the cost. After a pilot check-in, Smart Follow Up drafts the recap email, a good place to confirm the deadline in writing.
For pipeline review, a sales leader can use Gen AI Reports to see which deals have a recorded budget conversation. Smart Call Scoring scores every call against your methodology, so the leader can check whether reps ask the calendar questions. Rafiki AI connects to Salesforce, HubSpot, Zoho, Pipedrive, Freshworks, and Monday.com. It also transcribes calls in more than 60 languages, which helps teams that sell to buyers abroad.
Before Friday, list every open deal and active pilot that could close in the first half of 2027. Next to each one, note whether you know the buyer's submission deadline and who writes the request. Any blank becomes the first question on your next call with that champion. Deals with a deadline in the next three weeks get a business case draft this month.
Start with the champion who has already put a cost on the problem, since that draft is the easiest. Then block an hour in the second week of December to ask each champion whether the line survived. Their answers will show which deals belong in the Q1 forecast and which need a fallback path.
Rafiki AI's conversation intelligence platform starts at $19 per seat per month, with no seat minimum. That lets a founder start with the few people who run sales calls today. Start a free trial before your next round of pilot check-ins, so the budget answers from those calls reach your CRM. If you'd like to see it on your own calls first, book a demo with our team.
For companies on a calendar fiscal year, budget season usually runs from early October to mid-December. Department heads draft requests in October, and finance reviews them in November before the plan locks. Companies with a different fiscal year follow the same pattern a few months before their year starts. The safest move is to ask each buyer for their own dates.
Ask about the process and the calendar before you ask about amounts. A question like "when does your team submit 2027 requests, and who writes yours?" helps the champion plan. Most people answer it openly for that reason. Save dollar figures until the champion confirms the problem is worth solving next year.
A good business case starts with the problem in the buyer's own words and the cost the buyer estimated. Add a named owner with one metric, then the full annual price and a start date tied to the buyer's calendar. Finish with a short, factual paragraph on what happens if the company waits a year.
You still have options, though each one is smaller than a full line item. Ask whether the department has discretionary money or whether your product replaces a tool with its own budget. You can also ask when the company reforecasts. If none of those work, agree on a limited first phase and set a reminder for next year's planning window.
Start for free — no credit card, no seat minimums, no long contracts. Just better sales intelligence.
