Business Development Sales Process: How to Build One

Your Monday pipeline review lists forty opportunities. Twenty of them are a single email reply, with no budget, no date, and no named buyer. The rep sits in Mexico City. The prospect is a US hiring manager who asked about Spanish-speaking engineers three weeks ago and went quiet after Friday afternoon.

That is a business development sales process failing in public. Stages live on a slide, but nothing stops a polite reply from becoming pipeline. A time-zone gap turns the first response into the next business day. The shortlist was often built before anyone on your team spoke to the buyer.

Fix the sequence, the proof a buyer can find before contact, the minute an inquiry lands, and the note that travels with a handoff. Then staff the work with people who can run it.

Defining the Stages and Exit Criteria Your Pipeline Needs

Run the business development sales process as a sequence of measurable stages, not as a pile of calls and emails. Apollo's pipeline guidance treats the common set as prospecting, qualification, needs analysis, proposal, negotiation, and closed-won or closed-lost. A prospect who replies does not earn the next stage.

Exit lines on one São Paulo deal

A fintech in São Paulo wants twelve Spanish-speaking backend engineers for a payments rebuild. The CRM record should change only when the exit line is true.

Prospecting exits when the account matches the ideal customer profile and a decision-maker is named. The VP of Engineering is on the record, and the company already hires engineers in Brazil. There is no meeting yet, and that is fine.

Qualification exits when you have confirmed fit, a credible business need, buying authority, budget, and timeline. The VP confirms headcount, a third-quarter start, and a contractor budget with finance. "Sounds interesting" stays in prospecting.

Needs analysis exits when pain and stakeholders are written down and a next step is booked. The note lists the stack, the Spanish requirement, and that legal in São Paulo reviews contractor terms.

Proposal exits when the buyer has reviewed a scoped offer and objections on rate or notice period are logged, not guessed.

Negotiation exits when commercial or legal terms are moving. Redlines in the thread count. "We're looking at it" does not.

Closed-won or closed-lost exits on a signed agreement, or on a written reason plus a nurture or lost code. Onboarding owns the account after signature.

The chart above compresses that path into five boxes you can scan in a review. The sixth outcome, closed-lost, still needs a code so dead deals stop inflating the forecast.

Practical rule: If the exit line is blank, the deal stays put. Counting it makes the Monday review look healthy and hides the real work.

Managers then compare stage health instead of activity volume. The fintech either has authority and a date, or it goes back to prospecting.

Sourcing and Qualifying Leads Before Outreach Begins

Stage design does not create demand. Qualified demand for an employer-facing team comes from inbound forms, referrals, hiring signals such as a company posting many roles in one country, and event lists. Each source needs a rule that separates a marketing-qualified lead from a sales-qualified opportunity.

An MQL has a plausible account and a stated interest. An SQL has a named problem, a person who can buy or sponsor, a rough budget, and a timeline. Interest without those four facts stays with marketing.

Buyers often decide before they talk

Buyer research summarized by Responsive reports that 90% of B2B buyers research before contacting a vendor. 2025 6sense buyer data found that 95% of winning vendors were already on the buyer's shortlist on day one of formal evaluation, while the average global buying cycle shortened from 11.3 to 10.1 months. A shorter cycle is not an easier sale. Buyers drop vendors earlier and hand more of the comparison to their own research, including AI-assisted search.

More cold outreach will not fix a missing shortlist. Build evidence they can find first.

Country coverage: which markets you staff, not a vague map of Latin America.

Time-zone overlap: hours that match a US or European hiring manager.

Bilingual talent: English and Spanish, or English and Portuguese, by function.

Salary transparency: ranges where you can stand behind them.

Proof by country and role: time-to-fill, retention or quality signals, and the trade-off between remote, hybrid, and onsite.

A US logistics company comparing Bogotá and Medellín is a useful test. If your page cannot say how those cities differ on commute, bilingual depth, and overlap with Eastern Time, you are not on the day-one list. The sales conversation never starts.

Qualification checklist before anyone dials

• Account fit: industry, headcount, and a hiring pattern you can serve.
• Problem: a role, a country, and a reason the current channel is failing.
• Authority: the person who owns the req, plus who signs.
• Money and date: a range and a start window, even if rough.
• Pre-contact asset used: which proof the buyer could have seen.

Track shortlist inclusion and qualified inbound conversations, not only reply rate. Reply rate rewards noise. Shortlist rate tells you whether the evidence worked.

Designing an Outreach Cadence and Response Speed

Who you target and when you answer are different jobs. Speed is a process rule, not a courtesy.

Harvard Business Review research on 2,241 U.S. companies, covered in the Vida write-up of that test, found that firms contacting a lead within one hour were nearly seven times more likely to qualify it than firms waiting an additional hour, and more than 60 times more likely than firms waiting at least 24 hours. Among companies that responded within 30 days, the average response time was 42 hours. Only 37% answered within an hour, and 23% never answered.

Treat response time as a stage-level KPI. Route employer inquiries to a named owner, fire an alert, and log every touch in the CRM. For a marketplace hiring across Latin America, a buyer in New York and an owner in São Paulo can lose the active hour to the clock unless the rule is explicit.

A 14-day cadence in the buyer's morning

Schedule each touch for the prospect's local morning in Mexico City, Bogotá, or São Paulo. A 9 a.m. note in Chicago that lands at 6 a.m. in Mexico City gets ignored, then looks "followed up" in your CRM.

Day 0, first email. Name the exact request in the first sentence. A logistics firm asking about Medellín engineers should see Medellín, not a generic LATAM pitch.

Day 1, one call. Same contact, one short voicemail. Do not leave three.

Day 3, one proof point. A salary band, a time-to-fill note, or a remote versus onsite trade-off. Not a second copy of the first email.

Day 7, LinkedIn. A short note tied to the earlier email. No pitch deck in the request.

Day 14, a direct close. Ask whether to continue or close the lead. Silence after a clear question is an answer.

H2's guide to sales cadences is a useful check on spacing and message jobs if you later add touches. Extra messages only help when each one carries new evidence. A ninth "just checking in" trains the buyer to ignore you.

Set the inbound standard in minutes, not in "same day." If the owner is offline, the backup owner gets the alert. Measure the hour, not the intention.

The short walkthrough below shows how a team turns that first-hour rule into a habit instead of a slogan.

Speed keeps the evaluation window open. It does not replace qualification, discovery, or the relationship. A fast, empty email still loses to a slightly slower note that cites the buyer's actual req.

Handing Off From SDR to Account Executive Without Losing Context

The leak after a good cadence is usually internal. A sales development rep in Mexico City spends two weeks confirming that a US product company needs eight bilingual QA engineers, has a budget band, and wants offers out before a September release. The account executive accepts the meeting, opens a blank page, and asks the same questions again. The buyer repeats the stack, the cities, and the deadline. Trust drops. The timeline resets by a week.

That re-discovery is expensive because the buyer already did the work once. They will not do it twice with patience.

What the AE must receive before accepting

An opportunity is sales-qualified only when the note already holds:

• Pain: the roles, the countries, and why the current channel failed.
• People: economic buyer, day-to-day sponsor, and anyone in legal or finance.
• Money: the range discussed, labeled as a range, not a promise.
• Date: start window and any hard release or board date.
• Promises: what the SDR said you would and would not do.

Give the AE a short acceptance window, for example the next business morning in their city. If they decline, they write one reason the SDR can use: wrong ICP, no authority, budget fiction, or timeline that is really "someday." "Not a fit" is not a reason. The rejected lead goes back to nurture or closed-lost. It does not sit in both people's pipelines.

The AE should never need to rediscover what the SDR already confirmed. The first AE call starts at the open question, not at the company overview.

Write the handoff as five lines in the CRM, not as a slide. If a line is missing, the SDR keeps the lead. That feels slower for a day and saves the deal.

Tracking the KPIs That Show Where Deals Stall

Call counts hide the stall. A rep can hit activity targets while the same deals sit in qualification for a month. Stage conversion and time in stage show where the process breaks.

B2B funnel benchmarks compiled by SHNO put conversion at about 31% from lead to MQL, 13% from MQL to SQL, 30% to 59% from SQL to opportunity, and 22% to 30% from opportunity to customer. These are diagnostic thresholds, not quotas. A collapse at MQL-to-SQL usually means weak qualification rules, thin lead context, or a broken marketing-to-sales handoff. A weak opportunity-to-customer rate points at discovery, proposal, pricing, or closing.

Published B2B timing ranges from Landbase put discovery at roughly two to three weeks, qualification at one to two weeks, proposal development at two to four weeks, and negotiation or closing at two to six weeks. A deal parked in qualification well past that range should be requalified, moved to nurture, or closed-lost. It is not reliable pipeline.

Stage conversion and time-in-stage benchmarks

Stage transition or stageBenchmark rangeWhat a weak result usually signalsLead to MQLAbout 31%Targeting or form quality is offMQL to SQLAbout 13%Loose rules or a bad handoffSQL to opportunity30% to 59%Discovery never earned a real next stepOpportunity to customer22% to 30%Proposal, price, or close is failingDiscovery2 to 3 weeksMeetings without a documented painQualification1 to 2 weeksDeals advancing on replies aloneProposal2 to 4 weeksOffer not reviewed, or scope keeps movingNegotiation2 to 6 weeksLegal or commercial terms are stuck

CRM timestamps let you compare those ranges across Mexico City, São Paulo, Bogotá, Buenos Aires, and Santiago without relying on anecdotes. A longer cycle in one city may be legal review, not a lazy rep.

Review five numbers each week, together: response time, contact rate, qualification rate, meetings booked, and opportunity conversion, plus revenue won when the month closes. The Social Search on pipeline reporting is a practical reference for reading stage movement instead of activity totals. One ugly stage is a better meeting topic than a green activity dashboard.

Choosing Tools and Staffing Models for the Team

A spreadsheet works while one or two people can see every row. It fails when follow-ups depend on memory and managers cannot audit who said what. A CRM plus sequencing and call recording costs more and only pays off if the team lives in one record: account, contacts, hiring demand, role volume, and the handoff between outreach, onboarding, and renewal.

The useful difference is not a feature list. It is whether a manager in another city can open the fintech account and see the exit criteria, the promises, and the last touch without asking in Slack.

Who should run the first conversation

In-house, one city. You keep message and data. You also inherit local salary, office habits, and a narrow time-zone window. This fits a single territory with a simple quota.

Nearshore SDRs in Mexico City, Bogotá, or Buenos Aires cover US and European mornings, and they can sell in English plus Spanish or Portuguese. Quota design gets harder because territory, language, and buyer seniority all change the job. A bilingual SDR selling into the United States from Mexico City or Bogotá is not the same hire as an entry-level rep selling only inside Argentina or Brazil.

An agency starts faster and owns less of your data and your voice. Use it for a burst of coverage, not as the system of record.

A 2025 LATAM hiring-market report lists sales development representative pay at about $2,000 to $3,500 per month plus commission. Treat that as a budgeting start, then check country, experience, language, territory, and quota complexity. Job posts should say whether the figure is base salary or on-target earnings, when commission starts, and which metric pays: qualified meetings, accepted opportunities, or revenue.

Employers comparing those packages can use LATOjobs employer resources while they look at technology and business roles by country. State the split in the post so candidates in Mexico and Brazil are not guessing.

Launching Your First 30 Days Without Overbuilding

Do not buy a full stack before the stages work. Four weeks is enough to see the first real drop.

Week one. Write the stages and exit criteria. Agree, in one page, what an MQL is and what an SQL is. If two managers disagree, the CRM will lie.

Week two. Set routing, the one-hour response standard, and the 14-day cadence. Name a backup owner for Mexico City, Bogotá, and São Paulo mornings.

Week three. Put the five-line handoff note into live deals. Review the first accepted and rejected opportunities. Every rejection needs a reason the SDR can learn from.

Week four. Pull stage conversion and time in stage. Pick the single worst drop. Fix that rule before you add tools, territories, or headcount.

A process is only as good as its exit criteria.

This week, draft one SDR or AE job post that states base and commission separately, names the metric that pays, and names the cities the person will cover. Then read the live hiring pages for the markets you sell into, such as Mexico or Brazil, and check that your own proof matches what those buyers can already see.

LatoJobs is a job marketplace where employers post sales, business development, and other LATAM roles and where bilingual professionals compare opportunities with salary detail when employers disclose it. If you are staffing the process in this guide, start with a clear base-and-commission post and review current openings on LatoJobs.