A guesstimate is an approximate value found by using common sense and basic assumptions, and the word comes from combining guess and estimate. It is used when finding an exact number is difficult or not possible.
In this method, a big or unclear problem is divided into smaller parts, reasonable assumptions are made for each part, and simple calculations are used to get a close answer, such as estimating how many buses run in a city each day by considering the number of routes, trips per route, and average buses used.
Guesstimates are commonly used in interviews, business decisions, and real-life problem solving where quick and reasonable answers are required.
Common Approaches Used in Guesstimates
There are two basic approaches that are commonly used to solve guesstimate problems. Depending on the question, either of these methods can be applied.
- Top-down approach: This method starts with a large number, such as the population of a city or country, and gradually narrows it down by applying logical assumptions and percentages until the required estimate is reached.
- Bottom-up approach: This method begins with a small, known unit, such as one store, one theatre, or one customer, and then builds up to the final number using averages, counts, or frequency.
The Guesstimate Framework: A 6-Step Guide
A guesstimate is best solved using a clear framework. Instead of guessing randomly, you focus on understanding the problem, making logical assumptions, and reaching a reasonable estimate using simple math.
Let’s apply this framework to an example:
“Estimate the number of movie tickets sold per day in Bengaluru.”
Step 1: Understand the Problem Clearly
The first step is to understand exactly what is being asked. Here, we need to estimate the number of movie tickets sold per day, not revenue or footfall in malls. The goal is to arrive at a reasonable daily figure, not an exact number.
At this stage, avoid calculations and focus only on understanding the requirement.
Step 2: Ask Preliminary and Clarifying Questions
Before making any assumptions, it is important to clearly define the scope of the problem so there is no confusion later.
You: “Before I proceed, I’d like to clarify a few details to make sure I’m estimating the right thing.”
You: “Should I consider only Bengaluru city limits, or include nearby areas as well?”
Interviewer: “Let’s consider only Bengaluru city.”
You: “Okay. Are we counting all movie tickets sold, including both online bookings and offline counter sales?”
Interviewer: “Yes, include both.”
You: “Understood. Should I assume this estimate is for a typical weekday, or should I consider weekend numbers?”
Interviewer: “Assume a typical weekday.”
You (Summarizing): “Alright. So I’ll estimate the total number of movie tickets sold both online and offline within Bengaluru city on a typical weekday.”
Interviewer: “That’s correct.”
This ensures the problem is clearly defined and agreed upon.
Step 3: Break the Problem into Smaller Parts
Now, divide the problem into logical components using a top-down approach.
We can structure the estimate as:
Total Daily Tickets Sold = (Population of Bengaluru) × (% of people who go to movie theatres) × (Average number of movies watched per person per week) ÷ (7 days)
This breakdown turns a large question into a simple and structured calculation.
Step 4: Make Reasonable Assumptions
Since exact data is not available, we make sensible assumptions and clearly explain them.
- Population of Bengaluru: Assume 1.2 crore (12 million) people.
- People who watch movies in theatres: Not everyone goes to theatres. Considering working professionals, students, and families, assume 30% of the population watches movies in theatres.
12,000,000 × 30% = 3,600,000 people
- Movie-watching frequency: Some people watch movies often, others rarely. On average, assume 2 movies per month, which is roughly 0.5 movies per week.
These assumptions are realistic and easy to justify.
Step 5: Use Simple Calculations
Now perform the calculation using round numbers.
- Weekly ticket sales: 3,600,000 × 0.5 = 1,800,000 tickets per week
- Daily ticket sales: 1,800,000 ÷ 7 ≈ 2,57,000 tickets per day
So, the guesstimate is around 2.5 lakh movie tickets sold per day in Bengaluru.
Step 6: Do a Sanity Check
Finally, check whether the number feels realistic.
Bengaluru has a large number of theatres and multiplexes. If each theatre sells a few hundred tickets daily, reaching 2–3 lakh tickets across the city seems reasonable. The biggest variable here is movie-watching frequency, which can change due to weekends, festivals, or popular releases.
As a cross-check, this estimate could also be validated by calculating based on the number of theatres and average tickets sold per show.
Let’s work through an example.
Estimate the number of Ola and Uber cabs actively operating in Delhi NCR on a typical day.
Explanation -
The Guesstimate Framework
We solve this problem using the following six steps:
- Understand the problem clearly
- Ask preliminary and clarifying questions
- Break the problem into smaller parts
- Make reasonable assumptions
- Perform simple calculations
- Do a sanity check
Step 1: Understand the Problem Clearly
The objective is to estimate:
The number of Ola and Uber cabs that are active (i.e., taking passenger rides) in Delhi NCR in a single day
At this stage:
- No assumptions are made
- No calculations are performed
- We only identify what needs to be estimated
The problem clearly asks for a daily operational count, not total registrations or lifetime numbers.
Step 2: Ask Preliminary and Clarifying Questions
Before making any assumptions, it is important to clearly define the scope of the problem so there is no confusion later.
You: “Before I proceed, I’d like to clarify a few details to ensure I’m estimating the right thing.”
You: “Should I consider only Delhi city, or should I include the entire Delhi NCR region as well?”
Interviewer: “Include the entire Delhi NCR region.”
You: “Are we counting only app-based cab services like Ola and Uber, or should local taxis and autos be included too?”
Interviewer: “Only Ola and Uber.”
You: “Should I estimate the total number of registered cabs, or only the cabs that are actively running and taking rides in a day?”
Interviewer: “Only the active cabs.”
You: “Should I assume this estimate is for a typical weekday, or should I factor in weekends and festival days?”
Interviewer: “Assume a typical weekday.”
You (Summarizing): “Alright. So, I will estimate the number of Ola and Uber cabs that are actively operating and taking passenger rides across the entire Delhi NCR region on a typical weekday.”
Interviewer: “That’s correct.”
This ensures the problem is clearly defined and agreed upon.
Step 3: Break the Problem into Smaller Parts
We use a top-down, demand-based approach.
To estimate total daily rides, we:
- Start from the population
- Identify potential cab users
- Split demand into peak and non-peak hours
- Adjust for cab availability (occupancy)
Step 4: Make Reasonable Assumptions
Population Assumption
- Total population of Delhi NCR ≈ 33 million (3.3 crore)
We first divide the population based on living regions:
- Rural / Semi-urban population: 19.8 million
- Urban population: 13.2 million
Rural / Semi-Urban Population based on Income
- Upper income: 1.98 million
- Middle income: 5.94 million
- Lower income: 11.88 million
Assumptions:
- 12% of rural upper-income users take cabs
- 10% of rural middle-income users take cabs
- Lower-income usage is negligible
Calculations:
- Rural upper users = 1.98 × 12% ≈ 0.238 million
- Rural middle users = 5.94 × 10% ≈ 0.594 million
Total rural cab users ≈ 0.83 million
Urban Population based on Income
- Lower income: 2.64 million
- Middle income: 6.6 million
- Upper income: 3.96 million
Assumptions:
- 12% of urban middle-income users take cabs
- 25% of urban upper-income users take cabs
- Lower-income group is ignored
Calculations:
- Urban middle users = 6.6 × 12% ≈ 0.792 million
- Urban upper users = 3.96 × 25% ≈ 0.99 million
Total urban cab users ≈ 1.78 million
Total Potential Cab Users per Day
0.83 (rural) + 1.78 (urban) ≈ 2.6 million
So, ~2.6 million people generate cab demand per day.
Step 5: Perform the Calculations
Peak vs Non-Peak Hour Split
Cab demand varies throughout the day.
- Peak hours: 45%
- Non-peak hours: 55%
Calculations:
- Peak demand = 2.6 × 45% ≈ 1.17 million
- Non-peak demand = 2.6 × 55% ≈ 1.43 million
Occupancy Adjustment
Not all demand converts into completed rides.
- Peak hour occupancy ≈ 45%
- Non-peak hour occupancy ≈ 25%
Effective rides:
- Peak rides = 1.17 × 45% ≈ 0.53 million
- Non-peak rides = 1.43 × 25% ≈ 0.36 million
Total Daily Cab Rides
0.53 + 0.36 = 0.89 million rides
So, approximately 890,000 rides occur per day.
Convert Rides into Number of Cabs
Assume: Average rides per cab per day ≈ 10
\frac{890,000}{10} = 89,000
So, the guesstimate is around 89,000 Ola and Uber cabs running daily in Delhi NCR.
Step 6: Do a Sanity Check
Finally, check whether the number feels realistic.
Delhi NCR has extremely high daily travel demand across offices, airports, and commercial areas.
If each Ola or Uber cab completes around 8–10 trips per day, having 80,000–90,000 active cabs would generate roughly 7–9 lakh rides daily, which appears reasonable.
Variations can occur due to weekends, weather, or festivals. A quick supply-side check using average trip duration also supports this estimate.