Signal
Blue square section markers and shaded skill labels organize the prospecting record above a broad work history.
Before sending: Read wrapped contacts and the final handoff bullet on every continuation page.
Sales · Account research and qualified meetings
A Business Development Representative resume should explain how you choose accounts, start relevant conversations and hand useful context to sales. Distinguish activity from meetings that actually happened, and show how your team decided a handoff was qualified. A large pipeline number is unhelpful if its stage, period and your contribution are unclear.
By Resumize · · Sources and scope
Three designs · one example
These previews use the same layouts as the builder, with identical example content. Open a full preview to inspect the text and spacing.
Fictional candidate, employers, education and results. The optional portrait is AI-generated. Use your own evidence and photo; the example is not inserted into your resume.
Blue square section markers and shaded skill labels organize the prospecting record above a broad work history.
Before sending: Read wrapped contacts and the final handoff bullet on every continuation page.
A restrained left-aligned header and single column keep meeting definitions close to their evidence.
Before sending: Use specific section labels so the simple layout still distinguishes projects from paid work.
A navy sidebar holds identity and supporting details beside the work-history column.
Before sending: Check a long email in the narrower rail and read every continuation page before applying.
“Use” opens signup with that design and photo preference selected for the builder. A free account is required. Free-plan PDF downloads include a watermark; see current plans for paid options. Photo conventions vary; follow the employer’s instructions and local expectations.
Signal uses blue square section markers and shaded skill labels above a broad work history. Essential keeps a restrained single column. Harbor places contact details and supporting information in a dark left rail. Compare how each carries the same account-research and handoff evidence, especially when a contact or bullet wraps.
The default has no photo. Each design shows the same fictional career, and its button keeps the exact design, photo preference and Business Development Representative role through signup. The example career and portrait are not added to your account. A free account is required; free-plan PDF downloads include a watermark. These previews show paid-plan output.
Jordan Ellis, both employers, the college, dates and results are original fiction. The 555 phone number and example.com destinations are placeholders. The optional AI-generated portrait is illustrative. Replace all personal facts with your own; the example is a writing exercise, not a real applicant testimonial.
Business Development Representative | B2B Software
jordan.ellis@example.com · +1 312 555 0152
Work examples: https://example.com/jordan-ellis
Business development representative supporting B2B software outreach through account research, relevant phone and email conversations, and documented sales handoffs. Tracks booked, held and accepted meetings separately, keeps Salesforce records current and uses feedback from Marketing and Account Executives to improve follow-up.
Account research · Outbound phone and email · Prospect qualification · Salesforce · Meeting handoffs · CRM data quality · Outreach sequence review · Inbound lead routing
Northmere Workflow Systems · Chicago, IL
March 2023–Present
Alderbridge Business Software · Evanston, IL
July 2020–February 2023
Bachelor of Arts in Business Communication · Lakeshore Vale College · Illinois
August 2016–May 2020
Coursework in business research, communication and spreadsheet analysis.
BDR · Northmere Workflow Systems
January 2026–March 2026
Salesforce · Call notes · Shared documentation
Created a reference for recording workflow context, stated timing and the next agreed action after a first conversation. Reviewed example handoffs with two Account Executives and kept meeting acceptance separate from later opportunity or revenue reporting.
Begin with the territory, customer type and stage you supported. Jordan researches B2B software accounts and qualifies first conversations. An Account Executive owns later sales follow-up; the resume does not claim contract negotiation, closed revenue or the entire sales cycle. BDR and SDR titles can overlap, so let the actual vacancy define the work rather than assuming one title always means outbound.
The employer examples illustrate different markets. Health-E Commerce emphasizes researched partner contacts, CRM quality and meetings for senior sales. Rackner describes early federal-market outreach and explicitly separates it from formal capture and proposal ownership. Innodata seeks research and qualification in Physical AI. These are three current US examples, not a representative survey or a requirement to know every sector.
For account research, name the evidence you used to judge fit and the buyer role you sought. A company announcement can justify a relevant question; it does not confirm budget or purchase intent. In discovery, describe what you learned and the next action the prospect agreed to, without turning an unanswered question into a qualified opportunity.
Before outreach, separate three decisions: is the company in the assigned segment, does the person hold a relevant role, and is there a reason to ask about this workflow now? Record the source and uncertainty for each. A parent company and subsidiary may share a brand but need different account ownership. Check for an existing account owner or duplicate contact before treating a new name as a fresh prospect.
Treat CRM correction as a documented change, not silent cleanup. Keep the original value, the permitted source, the date checked and the reason for the update. A role mismatch is different from a stale email or a wrong-fit company. In the example, 27 corrections describe a review of 220 assigned records; they do not imply the remainder is guaranteed accurate or ready to contact.
Use reply categories to choose the next action. A wrong-person reply may need a research correction; an explicit no-fit answer may close the record under team rules; a timing objection may support a dated follow-up. An unanswered email does not establish an objection. Review message changes with the team and keep any experiment population separate from ordinary outreach before claiming an improvement.
Every after statement below is exactly one of the six bullets in the base work history. The numbers are fictional. Use the structure to make your own responsibility and evidence clear; replace every invented fact.
Before: Prospected lots of new customers.
After: Researched 90 assigned software accounts in the second quarter of 2026, recording business fit, relevant operations contacts and source links in Salesforce before beginning outreach.
Why it works: A defined cohort and selection evidence explain the work before the first call. Researching an account does not mean it became a lead.
Evidence to check: Assigned account list, quarter, fit criteria, permitted source links and your CRM changes.
Before: Generated 30 demos and closed new revenue.
After: Ran personalized phone and email follow-up for that account cohort; booked 30 first meetings and recorded 24 held meetings in the second quarter of 2026, excluding reschedules and duplicate bookings.
Why it works: Booked and held meetings are different stages. The statement defines its cohort and counting rules without taking credit for an Account Executive closing a deal.
Evidence to check: Dated meeting records, cancellations/reschedules, deduplication rule and the quarter covered.
Before: Delivered highly qualified opportunities.
After: Captured the prospect use case, current workflow, stated timing and agreed next step for each held meeting; Account Executives accepted 21 of the 24 handoffs for follow-up against the team qualification checklist.
Why it works: The sales team acceptance criterion and denominator make qualification assessable. An accepted follow-up is not a signed contract or guaranteed pipeline value.
Evidence to check: Qualification checklist, meeting notes, acceptance status and AE ownership of subsequent stages.
Before: Optimized messaging with data.
After: Reviewed replies and call notes with Marketing each week, separated wrong-fit accounts from no-response contacts and revised two outreach sequences with the sales manager before reuse.
Why it works: Shows what was reviewed, which distinctions mattered and who approved the change. No causal conversion lift is claimed from a small test.
Evidence to check: Reply categories, reviewed sequence versions and sales-manager feedback.
Before: Kept the database 100% accurate.
After: Checked 220 assigned contact records against permitted company sources, corrected 27 role or company mismatches and logged the source and review date for each correction.
Why it works: A finite record review supports specific corrections, rather than an unsupported accuracy claim for the entire CRM.
Evidence to check: Assigned record export, original and corrected fields, source permission and review dates.
Before: Responded instantly to every lead.
After: Routed 38 of 42 sampled inbound inquiries within one business day in April 2022; documented four exceptions and handed product questions to the relevant sales colleague.
Why it works: The period, sample and exceptions prevent a local service measure from becoming a universal promise. Routing is kept separate from resolving every inquiry.
Evidence to check: Arrival and routing timestamps, business-day definition, sample selection and exception notes.
This guide emphasizes account selection, data quality and useful outreach decisions. For a worked quota and pipeline-cohort example, read the Sales Development Representative guide. Employers divide BDR and SDR work differently; neither title creates a universal inbound or outbound boundary.
Jordan’s summary names account research, phone and email outreach, Salesforce and documented handoffs. Those strengths appear in the history. A new BDR can lead with customer conversations, research or organized follow-up from a real prior role. A more experienced applicant can add territory planning, coaching or accepted opportunities when supported. Do not borrow a senior title or a quota from an example.
Keep the funnel definitions beside the result: 30 booked meetings, 24 held, and 21 accepted handoffs in one quarter describe different stages of the same cohort. They are not 75 separate wins. Quota attainment needs the actual target, measurement period and ramp rules. A pipeline amount also needs stage and attribution; neither a scheduled meeting nor estimated opportunity value establishes closed revenue.
| Skill | Evidence to gather | Fictional example |
|---|---|---|
| Account research | Account fit, buyer roles and dated sources. | 90 assigned accounts in a defined quarter. |
| Phone and email outreach | Relevant reason to contact and follow-up record. | Two reviewed sequences, not a universal script. |
| Qualification | Agreed criteria and recorded next step. | 21 of 24 held-meeting handoffs accepted. |
| Salesforce / CRM | Fields maintained and review population. | 27 corrections within 220 assigned records. |
| Sales collaboration | AE and Marketing feedback with ownership clear. | Weekly review of replies and call notes. |
| Inbound routing | Sample, business-day definition and exceptions. | 38 of 42 inquiries routed within one business day. |
The fictional degree supports communication and research; it is not a BDR license. Requirements differ: Rackner states no specific degree is required, while Innodata allows a degree or equivalent professional experience. Read the location and eligibility details in the opening. An applicant without the listed sector background should show relevant learning and transferable work without claiming experience they do not have.
If you completed CRM or sales training, use its exact title and issuer and distinguish completion from ongoing study. The example has no certification. For a first role, a labeled research exercise can show how you select ten accounts and write two relevant opening questions. Do not report simulated outreach as customer meetings, and do not contact people or expose private prospect data merely to populate a portfolio.
A software opening may value workflow discovery; a partner role may emphasize identifying decision-makers; a federal-market role may require learning a different buying process. Select the responsibilities you have performed. Use truthful terms such as prospecting, cold calling, outreach, account research and qualification when the vacancy uses them. A long keyword list cannot demonstrate judgment or guarantee an ATS result.
Handle objections as information: identify whether the prospect lacks fit, timing or a relevant problem, then show how you recorded or routed that conclusion. A useful no-fit decision can protect sales time. Keep negotiation support, upselling, forecasting and social selling only when you can explain the work you actually did; do not promote a first conversation into ownership of an existing customer account.
The long-contact Signal example changes only the resume email and work-examples URL, with the photo on. Jordan’s identity, phone, career and projects are unchanged. Read the address to its final characters and open the complete destination; a shortened link label should not hide a wrong URL.
Open page 1 at full size
Open page 2 at full sizeBusiness Development Representative | B2B Software
jordan.ellis.business-development-work-examples@example.com · +1 312 555 0152
Work examples: https://example.com/jordan-ellis/work-examples/account-research-and-qualified-meeting-handoff-notes
Business development representative supporting B2B software outreach through account research, relevant phone and email conversations, and documented sales handoffs. Tracks booked, held and accepted meetings separately, keeps Salesforce records current and uses feedback from Marketing and Account Executives to improve follow-up.
Account research · Outbound phone and email · Prospect qualification · Salesforce · Meeting handoffs · CRM data quality · Outreach sequence review · Inbound lead routing
Northmere Workflow Systems · Chicago, IL
March 2023–Present
Alderbridge Business Software · Evanston, IL
July 2020–February 2023
Bachelor of Arts in Business Communication · Lakeshore Vale College · Illinois
August 2016–May 2020
Coursework in business research, communication and spreadsheet analysis.
BDR · Northmere Workflow Systems
January 2026–March 2026
Salesforce · Call notes · Shared documentation
Created a reference for recording workflow context, stated timing and the next agreed action after a first conversation. Reviewed example handoffs with two Account Executives and kept meeting acceptance separate from later opportunity or revenue reporting.
The expanded Signal record keeps every base field and adds an earlier outreach internship, an account-research checklist and the inbound-routing review. Read each page through the final project. Keep the sample and exception definitions attached to the routing result instead of shortening them into an instant-response claim.
Open page 1 at full size
Open page 2 at full sizeBusiness Development Representative | B2B Software
jordan.ellis@example.com · +1 312 555 0152
Work examples: https://example.com/jordan-ellis
Business development representative supporting B2B software outreach through account research, relevant phone and email conversations, and documented sales handoffs. Tracks booked, held and accepted meetings separately, keeps Salesforce records current and uses feedback from Marketing and Account Executives to improve follow-up.
Account research · Outbound phone and email · Prospect qualification · Salesforce · Meeting handoffs · CRM data quality · Outreach sequence review · Inbound lead routing
Northmere Workflow Systems · Chicago, IL
March 2023–Present
Alderbridge Business Software · Evanston, IL
July 2020–February 2023
Willowbend Event Services · Chicago, IL
June 2019–August 2019
Bachelor of Arts in Business Communication · Lakeshore Vale College · Illinois
August 2016–May 2020
Coursework in business research, communication and spreadsheet analysis.
BDR · Northmere Workflow Systems
January 2026–March 2026
Salesforce · Call notes · Shared documentation
Created a reference for recording workflow context, stated timing and the next agreed action after a first conversation. Reviewed example handoffs with two Account Executives and kept meeting acceptance separate from later opportunity or revenue reporting.
BDR · Northmere Workflow Systems
August 2025–October 2025
Salesforce · Company research · Spreadsheet review
Documented how to distinguish company fit, individual role relevance and a speculative buying signal. Used a manager-reviewed account sample to record sources and unanswered questions, without treating public research as confirmed purchase intent.
Sales development assistant · Alderbridge Business Software
April 2022–May 2022
CRM timestamps · Spreadsheet analysis · Routing notes
Reviewed the 42-inquiry April sample with the sales coordinator, recorded routing timestamps and documented the four exceptions. The review measured assignment speed rather than response quality, opportunity conversion or closed revenue.
Choose a length that keeps relevant evidence readable. Remove repeated duties before cutting a result’s definition. A second page can be useful; an isolated heading, detached date or missing qualifier needs attention regardless of page count.
The resume analyzer gives advisory feedback. Use the bullet point generator for drafting help, then verify every suggestion. Follow the employer’s requested file type; a design cannot guarantee parsing, interviews or an offer.
Name the customer or market, relevant outreach and research skills, and a supported contribution. Keep early-stage pipeline work separate from closing ownership.
Booked and held meetings, accepted handoffs, cohort conversion and defined quota attainment can help when their period, denominator and counting rules are clear. Never invent a target or claim an AE’s closed revenue.
Some employers accept transferable experience or do not specify a degree; others state education preferences. Read the individual opening and show actual customer communication, research and follow-up evidence.
Use the space needed for relevant, readable evidence. An early-career record may fit one page; a fuller history can need two. Remove repetition before removing the definition behind a result.
Use the opening’s wording when truthful: prospecting, account research, cold calling, CRM, Salesforce, lead qualification and meeting handoff. A keyword alone does not prove the skill.
Signup keeps the exact design, photo preference and Business Development Representative role. A free account is required. Free-plan PDF downloads include a watermark; these examples show paid-plan output. The fictional career and portrait are not added to your account.
Prepared by Resumize with AI-assisted research and drafting. Three direct employer descriptions were read with full responsibilities and Apply forms on October 29, 2026: US benefits-partner development, US federal-market outreach and US deep-tech prospecting. Their specific targets, sectors and location requirements belong to those openings. They inform work categories rather than a universal BDR checklist. No private CRM data, application submission or hiring-outcome test was used. Openings can change.
Read October 29, 2026. Remote United States with EST hours; benefits-partner prospecting, researched contacts, CRM quality and qualified-meeting handoffs. Employer-specific meeting targets are not universal BDR benchmarks. Current full description and Apply/application form directly retrieved with HTTP200; no publication date displayed.
Read October 29, 2026. Remote US with DC/San Antonio/Boston preferences; early-career federal-market outreach and account research. The vacancy separates initial pipeline development from formal capture/proposal ownership and does not require a specific degree. Current full description and application form directly retrieved with HTTP200; no publication date displayed.
Read October 29, 2026. Remote United States; Physical AI and robotics account research, relevant technical contacts, discovery and qualified-meeting coordination. Deep-tech familiarity is specific to this opening, not a universal BDR requirement. Current full description and Apply/application form directly retrieved with HTTP200; no publication date displayed.