Elevator Pitch Examples That Earn a Reply

You meet someone who might hire you, buy from you, or introduce you to the right person. They ask, “What do you do?” You have enough time for an answer, but not for your whole history. A rehearsed slogan can sound empty; a long explanation can lose the opening. The useful answer gives the listener a concrete picture and a reason to ask one more question.

An elevator pitch is a short introduction meant to begin a relevant conversation. Its length and content depend on whom you are speaking to and why. Salesforce describes it as a brief explanation of what you or your organization offers a particular audience, with enough information to invite further discussion. That is a better target than trying to close a sale, secure a job, or explain an entire company in one breath.

The examples below are illustrative scripts, not accounts of real companies, candidates, customers, or results. They show what to include, what to leave for a later discussion, and how to change the same basic description for different listeners. Replace every product detail, credential, and claim with something true about your own situation before using a script.

Give the listener a picture before you ask for interest#

The first sentence should let someone imagine the work. If a founder says, “We are transforming local commerce through an intelligent platform,” a listener still cannot tell what a customer would buy or do. Y Combinator’s application guidance warns that abstract descriptions can leave a reader unable to picture the product. The fix is usually an ordinary noun and an observable action: “We make software that shows independent bookshops which titles need reordering.”

That narrower sentence gives up a little grandeur. It also creates useful questions: How does the shop know stock is low now? Does the software connect to its register? Who makes the final order? Those questions mean the listener understands enough to explore the idea. A grand statement may sound complete while leaving no clear place to enter the conversation.

For a company introduction, I would begin with the product, the user, and the job it helps the user do. Y Combinator’s company pitch guidance likewise starts with a simple account of what the company does. You can then add one detail chosen for the person in front of you. A shop owner may care how a reorder decision is made. An investor may ask about the size of the opportunity, the business model, or the team. The company description stays consistent; the second sentence changes.

For a personal introduction, the equivalent is the work you do, the setting in which you do it, and the kind of conversation you want next. “I work in marketing” identifies a field but gives a recruiter little to respond to. “I write product emails for small software teams, and I’m looking for a role where I can own the customer onboarding sequence” gives a clearer starting point. It remains an introduction, not a claim that this candidate has already improved anyone’s results.

The final line should fit the relationship. If you know little about a prospective customer, ask about their current process before prescribing a fix. If a recruiter has invited you to introduce yourself, name the role you are seeking. If an investor has asked for a brief description, give the company plainly and leave room for a question. Salesforce’s sales guidance recommends adapting the introduction to the listener and ending with a question that can continue the conversation. A question is useful when you genuinely want the answer, not when it disguises a sales demand.

See how the same idea changes with the listener#

Imagine an illustrative product called ShelfSignal. It helps independent bookshops review recent sales and stock levels before placing orders. Nothing here asserts that ShelfSignal exists, has customers, or improves inventory outcomes. Using one imagined product across several introductions makes the audience choice visible.

To a bookshop owner at a trade event: “ShelfSignal puts your recent sales and current stock in one view, so you can see which titles may need another order. How do you decide what to reorder today?”

The product and its use are immediately clear. The question lets the owner explain whether reordering is even a problem. I would avoid leading with a claim about lost sales or wasted hours unless I had reliable information about this particular shop. I would also avoid asking for a demonstration appointment before learning whether the owner handles purchasing.

To a bookseller who might refer you to the owner: “I work on ShelfSignal, a tool for reviewing book sales and stock before reorders. Who usually decides what your shop buys next?”

The bookseller may have no reason to discuss a buying decision, but may know who owns it. This version asks for direction instead of treating the first person met as the buyer. That small change makes the pitch more respectful and more useful.

To an investor who has asked what the company does: “ShelfSignal is software for independent bookshops that brings recent sales and stock into one reorder view. We are exploring whether shops will pay for a simpler way to plan replenishment. I can show you the workflow and what we have learned from shop owners.”

The first sentence still describes the product. The next sentence marks the proposed business model as something being explored, rather than pretending it is established. An investor may reasonably want to discuss market, alternatives, progress, and team after the opener. Sequoia Capital’s investor business-plan outline includes those topics as well as company purpose, problem, solution, and business model. That outline helps prepare for the follow-up; it is too much to recite in the first introduction.

To a potential collaborator who builds point-of-sale software: “I’m developing ShelfSignal, a reorder view for independent bookshops. I’m trying to understand which sales and stock data a shop can reliably export from its register. What does your system make available?”

The collaborator needs to understand the dependency, not hear the buyer’s sales pitch. The question is specific enough for a useful technical answer. It also makes the next step conditional: if the necessary data is unavailable, the product approach may need to change.

These examples share a stable center: a reorder view for independent bookshops. What changes is the listener’s decision. The owner decides whether the task matters. The employee may identify a contact. The investor considers whether the business merits a deeper discussion. The software partner can explain what data the product could use. If you cannot name the decision your listener might make, the pitch is probably trying to cover too much.

Use examples that match the opportunity in front of you#

A useful example has a setting and an intended next conversation. The scripts in this section are all illustrative. The people, organizations, projects, and outcomes are invented for explanation; they are not testimonials or suggested claims to borrow.

A job seeker meeting a recruiter#

“I’m finishing a degree in accounting and have worked on monthly budget reports for a student-run organization. I’m looking for an entry-level finance role where I can help prepare reports and learn the close process. What does your team expect a new analyst to handle first?”

This candidate names a real type of task before asking about the employer’s work. The example does not inflate a student assignment into a corporate finance achievement. If the candidate has never prepared budget reports, that detail must be replaced. If the recruiter is staffing a tax role, the candidate should mention relevant tax work or state an honest interest, not force the budgeting script into an unrelated opening.

A common weaker version is, “I am a passionate, results-driven graduate seeking a challenging opportunity.” It sounds like a résumé summary, but it does not tell the recruiter what the person can do or what position they want. The recruiter must do the sorting work. A short description of one task and one target role gives them a way to respond.

A professional introducing their work at a networking event#

“I help small manufacturers explain their products to distributors. Most of my work is turning technical specifications into product sheets and sales answers that a distributor can actually use. What kind of work brings you here?”

This introduction has a narrower focus than “I do communications consulting.” It also leaves the listener free to say they are a supplier, a distributor, or simply interested in the event. If the conversation shows that they are outside this field, the speaker can stop pitching and talk normally. A networking introduction is an invitation to find relevance, not a license to repeat a script until the other person shows interest.

A freelancer speaking to a possible client#

“I design booking pages for independent service businesses. I focus on showing available appointments and the information a customer needs before booking. How are people scheduling with you now?”

The client can picture the deliverable: a booking page. The speaker does not assume that the current website is broken, or promise more bookings without knowing the business. If the owner already has a satisfactory booking system, the honest response is to learn whether another need exists. A strong pitch can reveal that there is no fit; it should not make every answer sound like a problem that only the speaker can solve.

A salesperson who has a specific reason to reach out#

“I noticed your company lists training sessions on several separate pages. We build a single schedule page where people can find a session and request a place. Is combining those listings something your team has considered?”

This version works only if the observation is true and publicly visible or otherwise legitimately known. The observation explains why this company, rather than any company, is being contacted. The question tests priority. If the prospect says separate pages are intentional, the salesperson has learned something important and should not argue from a canned assumption.

For a stranger at an event, I would usually ask a broader question first: “How do people find and book your training sessions now?” The speaker may not know enough to make a credible observation. Tailoring means using what you actually know, not inventing a “personalized” problem.

A founder answering an investor’s first question#

“We make software that helps small food producers track which wholesale orders are due to ship each day. Producers enter orders once, then see a daily packing list. We are testing the workflow with producers now and want to learn whether it saves enough coordination work to justify a paid product.”

This example states a user, an action, and the stage of the business. It does not claim revenue or a market size. If the founder has paid customers, verified usage, or a different stage, those facts should replace the tentative line. Investor guidance asks founders to discuss business model and progress, but the opening should still let the investor understand the product first. Y Combinator’s pitch guidance treats the short description as the basis for later questions about market, progress, model, team, and the ask.

A founder with a written application field#

“We build software for small food producers to turn wholesale orders into daily packing lists.”

A written field may be read without the speaker there to clarify it. I would put the product and user in the first sentence, then use any additional space for facts the application actually requests. “We are revolutionizing the future of food logistics” says less. The Y Combinator application guidance favors direct, matter-of-fact wording that lets a reader understand the proposed product. An application is also different from a live encounter: there is no chance to watch the listener’s face and adjust mid-sentence.

A cold email to a possible buyer#

“Subject: Training schedule on your site

I saw that your public training dates appear on separate course pages. We build schedule pages that let visitors see available sessions together and send a booking request. If your team is considering a shared schedule, would it be useful to see a short example?”

The email does the work of an introduction in writing. The subject identifies a concrete context, the body explains the offer, and the request gives the recipient an easy choice. It makes no promise about conversion or staff time. If the sender did not check the pages, this is a bad email to send; the first sentence would be false. In a written pitch, invented familiarity is especially conspicuous because the recipient can inspect the claim before replying.

An internal project proposed to a manager#

“I want to put the current onboarding checklist and owner for each step in one shared document. New team members now receive the steps in separate messages, so it is easy for us to miss which version they saw. Could I draft one page for the next hire and ask the team to review it?”

The manager needs a small decision: whether to approve a draft and a review. This script describes the proposed artifact and the observed issue without claiming that the change will improve retention or save a quantified amount of time. If the manager already has a shared checklist, the speaker should first ask how it is used. The same principle applies outside sales: say what will change, why this listener should care, and what decision you need.

Choose the detail that earns a second question#

The hardest edit is often deciding what to leave out. A buyer may need the use case and the next practical step; a recruiter may need evidence of a relevant task; an investor may need to understand the company before asking about market and model. The opening does not have to satisfy all three. Trying to cover every stakeholder usually produces a pitch full of category labels and very few objects.

Start with a plain sentence that could survive across audiences: “We make [a specific thing] for [a specific user] to [do a specific job].” This is a drafting aid, not a compulsory script. Some people sell a service rather than a product; some candidates should begin with their work rather than a company name. The test is whether an unfamiliar listener could describe the actual work back to you. Y Combinator’s company pitch guidance suggests checking whether someone can restate a short explanation in their own words. If they cannot, add a concrete action before adding a bigger claim.

Then choose one detail because it matters to this listener. In the ShelfSignal illustration, the owner might ask which data is needed. The investor might ask whether bookshops already pay for similar tools. The integration partner might ask about register exports. Answering those questions in advance could bury the product description. Holding the detail until it is relevant gives the other person room to steer the discussion.

Use a result only when you can state what happened and whose result it was. “I redesigned the appointment page” is a description of work. “Bookings rose after I redesigned it” is a performance claim that needs a real time period, a measure, and appropriate context before it belongs in a pitch. “I increased bookings by 40%” would be worse if the number were borrowed from an example. Y Combinator’s practical pitching guidance calls for specific, truthful company information. If you do not have a measured outcome, the task and the deliverable can still make a strong introduction.

For an early product, distinguish between what exists and what you plan to build. “We are building a tool that will combine stock and sales data” is different from “Our tool combines stock and sales data.” A prototype, a trial, and a paying customer are different stages. A listener can decide whether to continue only if they understand which stage is real. This matters particularly when the next conversation involves a purchase, partnership, or investment.

Match the length to the room and the channel#

“Elevator pitch” can make people search for an exact number of seconds. The better question is what the listener has agreed to hear. A passing introduction at a crowded event needs less than an invited explanation across a meeting table. A recruiter’s written field may impose a character limit; a live question allows the listener to interrupt or ask for more. Salesforce’s guidance treats length as dependent on the setting and recommends preparing versions for different opportunities.

I would prepare a one-sentence core and a longer version with one supporting detail. The core should work when someone asks, “What do you do?” The longer version should answer the first likely follow-up for that person. This is easier to deliver than memorizing three unrelated speeches. You can stop after the core if the listener wants to speak, or continue if they ask how the product works.

For example, the core might be, “I build scheduling pages for small training providers.” The longer version might add, “The page brings available dates together and lets visitors request a place without opening several course pages.” If the listener runs a training business, ask how their bookings work. If they do not, the core has already done its job: it has made your work understandable without demanding more attention.

Read a written pitch aloud before using it in person. If it sounds like a paragraph from a brochure, replace abstract verbs with the action a person takes: enters an order, chooses a date, reviews stock, prepares a report. Pause after the first sentence. That pause gives the listener a chance to ask the question they actually have, which may be more useful than the detail you planned to deliver.

Fix the weak version without adding hype#

Many weak pitches fail because the listener cannot identify the object, user, or request. Consider the illustrative line, “We empower businesses with seamless, innovative solutions.” There is no way to tell whether the speaker sells software, consulting, equipment, or training. A repair is not a stronger adjective. It is a concrete description: “We build a page where training providers list course dates and collect booking requests.”

Another weak line starts too far back: “I have always been passionate about solving operational challenges, and after years of thinking about this issue…” The listener is waiting to hear what exists. If a founder’s experience explains a distinctive insight, that story can follow the product sentence. In the first line, name the product and user. This follows the practical order in Y Combinator’s company pitch guidance: explain what the company does before expanding into the surrounding business.

A third version claims too much: “Our platform eliminates scheduling errors for every training company.” Even if the product is real, “eliminates” and “every” demand support that a brief introduction probably cannot carry. An honest description of the function is stronger: “Our page lets a training team publish available dates in one place and review incoming booking requests.” If a verified result exists for a defined group, add it with the group and period. If it does not, leave the claim out.

An awkward ending can also undo a clear introduction. “Can I book thirty minutes on your calendar?” may be a reasonable request after the listener expresses interest, but it is abrupt if they have only heard one sentence. Ask a question that fits the moment: “How do you handle bookings now?” or “Would a sample page be useful?” If the listener gives a substantive answer, the next step can follow from it. If the listener is unavailable, a short exchange has still made the offer clear.

Finally, avoid treating a template as a substitute for knowledge of the listener. The words “for people like you” can sound personalized while revealing nothing. Name what you know: the listener owns a bookshop, recruits finance analysts, or manages training dates. If you do not know their priorities, ask. A pitch should make your side of the conversation legible and leave space for theirs.

Write one version you can actually use#

Write down the thing you make or the work you do. Add the user or employer who would recognize its value. State the task in ordinary language. Then choose the next question or request based on the encounter. This gives you a usable first draft without pretending that every audience needs the same supporting facts.

Test the sentence with someone who does not know your field. Ask them what they think you make, who uses it, and what happens next. If they answer with a different product or cannot picture a user, revise the nouns and verbs. If they understand it but want to know how it works, you have a promising opening. This is a practical adaptation of Y Combinator’s advice to check whether a reader can understand and restate a company description.

Keep a few truthful details ready, but let the listener choose which one matters. For a buyer, that might be the current workflow and what a trial would involve. For an investor, it might be progress, alternatives, and the business model. For a recruiter, it might be the exact task you performed and the role you want. Sequoia’s investor outline shows how much more belongs in a full business discussion than in its opening sentence. Preparing those answers is part of giving a good pitch; reciting all of them at once is not.

The best test comes in the conversation itself. After you give the core line, listen for the question it produces. If people repeatedly ask what the product actually is, the first sentence is still too abstract. If they ask about price, availability, your experience, or how the work is done, they have a usable picture and are moving to a real decision. Adjust the next version around that point of confusion or interest. A good elevator pitch makes the next exchange easier to have.