How Long Is a B2B Sales Cycle? A Guide for Türkiye

In Türkiye, the B2B sales cycle depends on the complexity of the product and the size of the customer. It usually takes 2–6 weeks with small businesses, 1–3 months with mid-sized companies, and 3–9 months or longer with enterprises and holding groups. Three variables shape this timeline the most: deal size, the number of people involved in the decision, and how early the procurement department gets involved. Factors specific to Türkiye, such as budget cycles, currency fluctuations and public holidays, often add a few more weeks.

Still, the question "how many days on average?" isn't very useful on its own. What really matters is knowing how long your own cycle takes, which stage drags it out, and what steps can shorten it. In this guide, we use concrete examples to cover typical timelines in the Turkish market, the local factors that lengthen the cycle, how to measure your own cycle, and practical steps to shorten it.

Typical B2B sales cycle length by segment

The ranges below are general observations from teams selling B2B in Türkiye. It is perfectly normal for your numbers to fall outside these ranges, depending on your industry and product.

Small businesses (1–50 employees): 2–6 weeks. The decision-maker is often the business owner. A software subscription or service package costing a few thousand lira per month can close after a single meeting and a short trial.
Mid-sized companies (50–500 employees): 1–3 months. A department head, finance approval and sometimes an IT review are usually involved. Proposal revisions and contract negotiations take up a large share of this time.
Enterprises and holding groups (500+ employees): 3–9 months, sometimes up to 12. Additional layers come into play, such as procurement, legal, information security, vendor onboarding and group-company approvals.
Public institutions and tender-based purchases: These often exceed 6 months because they depend on budget planning and tender calendars. It's not unusual for more than a year to pass between first contact and payment.

As deal size grows, the cycle gets longer in an almost linear way. A tool costing 5,000 TL a month and a transformation project worth 2 million TL a year don't go through the same sales process. That's why it makes sense to track separate cycle lengths for different product packages, even within the same company.

What exactly does the sales cycle cover?

Before you start measuring cycle length, you need to clearly define its start and end points. Otherwise, every rep on the team will give you a different number, and comparing them becomes impossible.

What is the starting point?

Three starting points are commonly used:

First contact: The day the cold email is sent or the first call is made. For outbound-heavy teams, this shows the full picture, but it can inflate the cycle because it also counts the weeks with no response.
Qualified opportunity (SQL) creation: The moment the prospect's need, budget and timing are confirmed. This is the most widely used starting point and the best one for comparisons.
First meeting: The day of the discovery call. It's easy to apply, but it also includes unqualified meetings.

What is the end point?

The end point is usually considered the day the contract is signed. Some companies instead use the day the first payment is received or the day the customer actually starts using the product. In Türkiye, procurement and accounting processes can cause a 30–60 day delay between signature and first payment, so if you're planning cash flow, we recommend tracking these two dates separately.

Whichever definition you choose, consistency is what matters. If you haven't clearly defined the stages in your CRM, defining your sales pipeline stages correctly is a good place to start. If stage definitions are vague, your cycle measurements won't be reliable either.

What local factors lengthen the sales cycle in Türkiye?

The average timelines you read about in global sources don't always map directly onto Türkiye. The local market's unique dynamics can add significant time to the cycle.

Budget cycles and the year-end effect

Many mid-sized and large companies plan their budgets in the autumn, typically between October and December. An enterprise prospect you first contacted in September may say, "Let's put this in next year's budget," and push the decision to January or February. On the other hand, some companies want to use up unspent budget at year-end, leading to unexpectedly fast closes in December. Being aware of both effects helps you interpret your pipeline correctly against the calendar.

Public holidays and the summer period

Decision-making slows noticeably in the weeks around Eid al-Fitr (Ramazan Bayramı) and Eid al-Adha (Kurban Bayramı). In years when the holiday stretches to 9 days with bridge days, you can lose two full weeks. Decision-makers being on leave in late July and August also lowers close rates over the summer. It's no surprise when a deal you sent a proposal for in June slips into September.

Currency fluctuations and pricing uncertainty

For software and services priced in foreign currency, exchange rate movements make customers cautious. If the rate shifts two weeks after you send a proposal, either the customer has to get re-approval or you have to revise the proposal. Either way, the cycle gets longer. Fixed proposals in TL, valid for a set period, are one way to reduce this delay.

A relationship-driven buying culture

In Türkiye, trust and personal relationships play an important role in B2B purchasing decisions. A face-to-face meeting, a mutual connection or a reference customer can shorten a persuasion process that would take weeks through digital touchpoints alone. Conversely, an unknown brand trying to move forward by email alone will see a longer cycle.

Procurement and vendor onboarding

In enterprises, the procurement department steps in even after technical and commercial approval has been secured. They ask for vendor registration forms, a tax registration certificate, a certificate of activity, a data processing agreement under KVKK (Türkiye's personal data protection law) and sometimes information security questionnaires. A sales team that doesn't have these documents ready from the start may wait another 3–6 weeks on a deal it considered "almost closed."

Holding and group-company approvals

If you're selling to a company that belongs to a holding group, the decision may not end with that company's management. Group IT, central procurement or holding board approval all lengthen the process. Asking "Who from the holding side is involved in this decision?" during the discovery call prevents surprises later on.

How do you measure your own sales cycle?

General ranges give you a sense of scale, but you need your own data to make decisions. With the steps below, you can produce a reliable measurement in a few hours.

Export the deals won in the last 12 months. Pull the creation date, close date, deal value, customer segment and source (inbound, outbound, referral) for each opportunity from your CRM.
Calculate the number of days for each deal. Subtract the creation date from the close date.
Use the median instead of the average. A few 300-day enterprise deals will drag the average upward. For example, say your 10 deals took 18, 22, 25, 30, 34, 38, 41, 47, 120 and 260 days. The average comes out to 63.5 days, while the median is 36 days. The median reflects your typical deal far more accurately.
Break it down by segment. Calculate small, mid-sized and enterprise customers, as well as inbound and outbound sources, separately. Outbound opportunities often take longer than inbound ones because the customer isn't actively looking yet.
Review lost deals too. Knowing at which stage and on which day lost opportunities dropped out answers the question, "When should we walk away?"
Calculate time per stage. Instead of the total cycle length, look at the number of days spent in each stage. The bottleneck is usually concentrated in a single stage.

Cycle length means little on its own; it should be evaluated alongside the number of opportunities, average deal size and win rate. The pipeline velocity formula, which brings these four metrics together, lets you see in numbers how every improvement in cycle length affects revenue.

Which stage loses the most time?

Let's take a hypothetical team selling software to mid-sized customers in Türkiye, with a median cycle length of 60 days. The breakdown by stage might look like this:

Discovery call to demo: 7 days
Demo to proposal: 10 days
Proposal review and revisions: 21 days
Procurement and contract: 18 days
Signature: 4 days

In this table, 39 of the 60 days are spent in post-proposal stages. No matter how much the team speeds up its demos, the real gains lie in the proposal and contract processes. The situation is similar at many companies: the sales team spends its energy on early-stage contacts, while deals sit quietly after the proposal is sent.

Common bottlenecks include:

Post-proposal silence: The proposal is sent, there's no follow-up, and the customer goes back to their internal priorities.
Single-contact dependency: All communication runs through one contact; when that person goes on leave or leaves the company, the process stalls.
Decision-makers joining late: Finance or IT gets involved at the end of the process and asks questions that should have been answered at the start.
An unprepared contract process: The customer reviews the legal documents from scratch, and revisions take weeks.

Running a systematic lost opportunity analysis to see which stage stands out among lost deals lets you identify the bottleneck with data instead of guesswork.

How do you shorten the sales cycle?

Shortening the cycle doesn't mean rushing the customer. The real goal is to eliminate unnecessary waiting time in the buying process. The methods below are practical in the Turkish market and have a direct impact.

1. Start with the right customer

The fastest-closing deals come from companies that best match your ideal customer profile. Spending four months on a company whose industry, size and needs don't fit, only to lose the deal, hurts both your cycle average and your morale. Narrowing your target list with clear criteria puts fewer but faster-moving opportunities into your pipeline. B2B SaaS companies looking for outside help to define the right target market and generate qualified opportunities can explore SAAS Corner's outbound sales and lead generation service.

2. Qualify in the first meeting

Use a framework like BANT (budget, authority, need, timing) or MEDDIC to find answers to these questions in the first meeting:

Is there an allocated budget for solving this problem, or does a budget need to be created?
Who will be involved in the decision, and who gives final approval?
How does your procurement process work? Is vendor registration required?
By what date does this project need to go live, and why?

The "why" in the last question is critical. Needs that aren't tied to a concrete date keep getting postponed.

3. Build a mutual action plan

Before reaching the proposal stage, put together a simple timeline with the customer: technical evaluation date, finance approval, legal review, vendor registration, signature and start date. Keep this plan in a shared document and update it at every meeting. When customers set their own dates, the process becomes much more predictable.

4. Build relationships with multiple people

Relying on a single contact is one of the most common risks that lengthen the cycle. In an enterprise deal, aim to stay in touch with at least 3–4 people: the user, the department head, finance and IT. Reaching the right people requires up-to-date, complete contact data. This is where a systematic B2B data enrichment process helps, filling in missing job titles, phone numbers and email addresses so you can engage with multiple stakeholders more easily.

5. Have procurement documents ready from the start

Keep your tax registration certificate, certificate of activity, authorized signatory list, standard contract template, KVKK data processing agreement and information security policy ready in a single folder. Being able to send them the same day the customer asks saves weeks at the contract stage. It's even a good habit to ask during the discovery call, "Which documents will your procurement team request?" and send them early.

6. Automate post-proposal follow-up

Leaving follow-up to the rep's memory after a proposal is sent causes deals to quietly go cold. You can set up a follow-up sequence triggered the moment a proposal is sent: a short check-in email on day 3, a document answering frequently asked questions on day 7, and a call task on day 12. These sequences are easy to build in your CRM or with tools like n8n. By the same logic, sequence design matters at the first-contact stage too; getting the number of steps in an outbound email sequence right shortens the time to the first meeting.

7. Speed up post-meeting tasks

After every meeting, a summary, next steps and owners should be sent to the customer the same day. Reps often put this summary off until the next day or never send it at all. AI-powered note-taking and summarization tools close this gap by preparing a draft summary and follow-up email as soon as the call ends. Saving a day or two after each meeting adds up to a full week over a process with 5–6 meetings.

8. Simplify pricing

Proposals with numerous options, add-on modules and special discounts lead to long internal discussions on the customer's side. Offering two or three clear packages, a TL price valid for a set period and a clear start date speeds up the decision. If you have to price in foreign currency, state the exchange rate lock terms clearly in the proposal.

Is shortening the cycle always the right move?

No. Making cycle length a goal on its own can lead to the wrong behaviors. Reps may focus only on small deals that close quickly, avoid large and strategic opportunities, or offer unnecessary discounts to close faster.

The right approach is to track cycle length alongside other metrics:

If average deal size drops as the cycle shortens, you may have simply shifted the problem rather than solving it.
If win rate drops as the cycle shortens, deals may be moving to the proposal stage without sufficient qualification.
If customer churn rises as the cycle shortens, deals may be closing without expectations being managed properly.

It's healthier to treat cycle length as one of these metrics when evaluating sales team performance. Knowing your cycle length accurately also forms the foundation of your revenue forecasts: in a segment where deals close in 90 days on average, counting revenue from opportunities opened this quarter in the same quarter will systematically skew your forecasts.

Example scenario: Cutting the cycle from 75 days to 50

The scenario below is a fictional example designed to show how these methods work together.

Imagine an Istanbul-based company that sells maintenance management software to manufacturers. Its target customers are factories with 100–400 employees, and its average annual deal size is around 400,000 TL. Its median cycle length is 75 days.

A stage-by-stage analysis reveals the following:

Customer responses after the proposal take 25 days on average.
Vendor registration and the contract process take 20 days on average.
More than half of the opportunities have only a single contact, usually the maintenance manager.

The team makes three changes:

It asks about the procurement process in the first meeting and invites the plant manager and the finance lead to the demo. The average number of contacts per opportunity rises from two to four.
It standardizes its document package. Vendor registration documents, the standard contract and the KVKK text are sent directly to the procurement team after the demo. The contract stage drops from about 20 days to 10.
It sets up an automated post-proposal follow-up sequence. The sequence consists of emails, call tasks and a short ROI calculation prepared specifically for the plant manager. Post-proposal waiting time falls from 25 days to about 15.

As a result, the median cycle length drops from 75 days to about 50. The same sales team can close more deals in the same amount of time, and revenue forecasts become more reliable. What stands out here is that none of these changes required pressuring the customer; all of them aimed to reduce waiting time in the process.

Frequently asked questions

What is the average B2B sales cycle in Türkiye?

There's no single average; the timeline varies with customer size and deal value. In general, cycles run 2–6 weeks for small businesses, 1–3 months for mid-sized companies, and 3–9 months or more for enterprise customers. The most accurate figure is the median you calculate by segment from your own CRM data.

Should you use the average or the median when calculating the sales cycle?

The median is more accurate. A few very long enterprise deals pull the average upward, making your typical deal look longer than it really is. The median shows the time within which half of your deals close, which makes it more reliable for planning.

Why do outbound opportunities take longer than inbound ones?

In outbound, the customer isn't actively looking yet; it takes time for them to recognize the need, allocate a budget and kick off internal approval processes. In inbound, the customer has already completed some of these steps by the time they find you. That's why you need to measure cycle length for the two sources separately.

Does sales automation really shorten the cycle?

Yes, when applied in the right places. The biggest impact comes in stages where waiting time builds up, such as post-proposal follow-up, sending meeting summaries quickly, filling in missing contact data and task reminders. Automation doesn't change the customer's decision process, but it largely eliminates delays on the sales side.

Conclusion

In Türkiye, the B2B sales cycle can range from a few weeks to more than a year. What matters is not memorizing a general average, but measuring your own cycle by segment and stage, seeing where time is lost and focusing on those points. Teams that account for local factors such as budget cycles, public holidays, currency uncertainty and procurement processes, start with the right customer, build relationships with multiple decision-makers and don't leave post-proposal follow-up to chance can shorten their cycles meaningfully.

If you want to measure your sales cycle, identify bottlenecks and speed up your follow-up processes with AI-powered automation, schedule a call with Sales Corner to assess your team's needs together.