A useful sales development representative job description tells a SaaS hiring team what the SDR will own: which customers to approach, what to qualify and when to bring in an account executive. It also clarifies the support behind the role.
Start with the sales motion. Are you building your first outbound process, qualifying demo and trial enquiries, scaling a proven approach or prospecting into complex accounts?
These four SDR job description templates help SaaS founders and sales leaders turn that decision into an agreed role brief.
Choose your SDR template
- Building your first outbound process
- Qualifying inbound demo and trial demand
- Scaling an established outbound motion
- Prospecting into complex SaaS accounts
Before writing: agree the SaaS role brief
Use this checklist with the hiring manager before listing responsibilities:
- Product and use case: What does your software help customers do, and which problem should the SDR be able to discuss?
- Ideal customer profile (ICP) and buyers: Define the account types, user roles, decision-makers, territory and relevant buying triggers.
- Lead source: Specify outbound prospecting, demo requests, trial or free-account signals, event follow-up, or an agreed mix.
- Qualification standard: Agree on the fit, use case, and buying context needed for a sales conversation. A free signup alone is not your definition of qualification.
- Handoff and boundaries: Name the account executive (AE) or team that accepts the opportunity, the information required, and who handles technical evaluation.
- Support: Confirm the manager, product training, coaching, account data, tools and sales process already in place.
Compare “generate leads” with “qualify demo enquiries from [ICP], establish [use case and buying context], and hand accepted opportunities to [AE team].” The second version gives your hiring manager and recruiter a clearer brief.
If your company uses both SDR and BDR titles, settle the responsibilities first. Our SDR vs BDR comparison covers the distinction.
What real SaaS SDR job descriptions make clear
Company-written listings are useful references for scope and specificity—not templates to copy wholesale. Two examples illustrate different sales motions:
LaunchDarkly: inbound does not mean waiting for demo requests
“This is not a purely reactive lead-response role.”
LaunchDarkly’s inbound SDR listing combines demo, pricing and trial enquiries with event follow-up and proactive engagement of interested accounts. It also names the teams involved in routing and conversion.
What to borrow for your brief: Identify the actual lead sources and follow-up responsibilities. If your inbound SDR must also contact engaged accounts, say so—and define which work takes priority.
Junior AI: name the buyer and the research required
Junior AI’s SDR listing describes a bootstrapped company selling software to investment and consulting teams. The role includes account research, stakeholder mapping, and tailored outreach, along with developing outbound playbooks.
What to borrow for your brief: Describe the buyers and the preparation needed to reach them. “Research investment firms and map relevant stakeholders” is more informative than “identify new business opportunities.”
Use funding stage as context, not a template selector
Whether your SaaS business is bootstrapped or at Series A, B or C, choose the template around the work. Junior’s brief is a useful reminder that bootstrapped does not automatically mean simple prospecting. We recommend assessing sales-process maturity, lead source, and account complexity rather than assigning one SDR profile to each funding stage.
Examples reviewed in October 2026. Job listings can change or close; these references illustrate role design, not current vacancy recommendations.
Write the role brief before the job advert
Copywriting for Recruiters, Mitch Sullivan’s training business, makes a useful distinction: “Job adverts are marketing. Job descriptions are not.”
Start by documenting the role accurately. Then use those facts to write an advert that gives a relevant candidate a reason to consider it. Specify the challenge, the manager’s involvement, and what the business can genuinely offer. Replace “unlimited progression” with an approved development arrangement, and “exciting growth” with the actual work the hire will help deliver.
The templates below are role briefs for employers to adapt. A short candidate-facing advert example appears separately at the end.
Copyable SaaS SDR job description: the shared foundation
Copy this foundation and add one of the four role modules that follow. Replace every bracketed field, remove options that do not apply, and have the hiring manager approve the complete brief.
The AI responsibilities below are options for teams using approved AI tools, not universal requirements for every SDR. Keep only the tasks your team actually expects. These are practical tool-use skills; coding or building AI systems is not required.
Role details
Job title: Sales Development Representative — [inbound / outbound / named-account focus]
Company and product: [Company] provides [SaaS product] to help [customer group] address [specific business problem or workflow].
Customers and buying context: The target accounts are [ICP and territory]. The main users are [roles], and the buying decision usually involves [buyer roles]. Customers purchase through [subscription or usage-based model]; the SDR should understand [relevant evaluation process, existing-tool context and buying triggers].
Reporting to: [manager’s role]. Working with [account executives, marketing and other relevant teams].
Location and working arrangements: [location, remote or hybrid arrangement, required working hours or time-zone overlap, and any travel].
Employment: [employment type and agreed working hours].
Compensation: [base range, currency and pay period]; [variable compensation and the outcomes it rewards]; [on-target earnings where applicable, with the target assumptions]; [confirmed benefits].
Responsibilities shared across the role
- Record relevant prospect information, activity and next steps in [CRM].
- Explain the product’s relevant use cases using approved messaging, without promising unconfirmed features or outcomes.
- Apply [qualification criteria], including [customer fit, business problem, current approach and evaluation context], and document the reason for qualification, disqualification or follow-up.
- Provide [receiving team] with the prospect’s use case, stakeholders, relevant trial or demo context, open questions and agreed next step before each handoff.
- Use approved outreach channels, customer information and tools in line with company policies.
- Share prospect feedback and recurring objections with [manager/team].
Support and role boundaries
The company provides [product and buyer training], [access to the software or a demo environment], [data and prospecting tools], [coaching owner and cadence] and [access to sales or technical specialists].
The SDR owns [defined prospecting and qualification scope]. [Named role] owns pricing, proposals, negotiation and closing. Integration, security and implementation questions beyond the SDR’s training go to [AE, solutions engineer or specialist]. [Named team] owns onboarding, renewals and account expansion unless explicitly included in this role.
Set product fluency at the level needed for an initial buyer conversation. Do not require an engineering background or technical-demo ownership unless the role genuinely needs it.
Performance review: [review cadence], with separate expectations for [ramp period] and ongoing performance. The role-specific measures appear below.
Template 1: Building your first SaaS outbound process
Use this module when targeting, messaging or prospecting workflows still need testing. Confirm who will guide the work. Hiring an SDR does not resolve an undefined customer problem or replace sales leadership.
Role purpose and scope
Create qualified sales conversations about [product use case] with [target accounts and buyers], and help [founder or sales leader] develop a documented outbound approach. Initial focus: [market, segment and channels]. [Sales leader] owns the targeting strategy and commercial decisions.
Role-specific responsibilities
- Research prospects against the initial customer profile agreed with [sales leader].
- Test approved messages and outreach sequences, recording the audience, approach and response.
- Use [approved AI tools] to organise account research and prepare message variations for agreed outreach tests. Verify the account facts and edit each message for relevance before use.
- Conduct initial conversations to understand [business problem], the prospect’s current tools or workaround, and whether evaluating a software subscription is relevant.
- Arrange qualified next steps with [founder or account executive] and capture the information needed for follow-up.
- Review results with [manager] and document useful changes to targeting, messaging and workflow.
Essential requirements and trainable skills
Required: Evidence of researching unfamiliar businesses, writing relevant outreach, following through on conversations and using feedback to improve. [Specify prior prospecting experience if independent execution is essential.]
Trainable: [Product knowledge, market terminology and the selected CRM or prospecting tools]. Where AI tools are used, learn to give clear instructions, check suggested research against reliable sources and turn generated drafts into relevant outreach.
Success measures and support
During [ramp period], success means [product and customer understanding milestones], usable prospect records and documented outreach tests. Ongoing measures are [held qualified meetings], [sales-accepted opportunities] and [agreed improvements supported by test results].
[Manager] provides [review cadence], access to [customer conversations or subject specialists] and decisions on which tests to continue. Targets will be reviewed against [agreed evidence and review date].
Template 2: Qualifying inbound demo and trial demand
Use this module when your SaaS business has a defined flow of enquiries or engaged product users to qualify. Distinguish a demo request from a trial signup or content download: decide which signals deserve sales follow-up and which belong in nurture or self-service support.
Role purpose and scope
Convert relevant interest from [demo requests, pricing enquiries, trials, product-qualified leads or events] into qualified sales conversations for [team]. Coverage includes [territory, working hours and lead categories]. [Named owner] defines any product-usage threshold used to assign leads.
Role-specific responsibilities
- Prioritise and respond to assigned leads within [agreed response expectations during covered hours].
- Research the account and review its enquiry, stated use case and available trial or product-engagement context before follow-up.
- Use [approved AI tools] to summarise enquiry context and prepare tailored follow-up drafts. Check summaries against the original enquiry and CRM records, and ask the prospect about missing information rather than treating an AI inference as a confirmed need.
- Establish [customer fit, business need, evaluation timing and other agreed criteria]. Separate a user exploring the product from a buyer evaluating a team or company purchase.
- Route qualified prospects to [account executive/team] with clear notes and an agreed next step.
- Route support requests to [support team], and return unsuitable, duplicate or not-yet-ready leads to [disqualification, self-service or nurture process], recording the reason.
- Report recurring lead-quality and routing issues to [marketing or revenue operations owner].
Essential requirements and trainable skills
Required: Clear customer communication, purposeful questioning, accurate record-keeping and the ability to prioritise an assigned queue. [Add relevant customer-facing experience where necessary.]
Trainable: [Product knowledge, lead-routing rules, qualification framework and CRM workflows]. Where AI tools are used, learn to review generated summaries and responses for accuracy, distinguish stated needs from assumptions and handle customer information under company policy.
Success measures and support
Measures include [response expectations], [qualification completeness], [held qualified meetings] and [conversion to sales-accepted opportunities]. Results are reviewed by lead source and quality, with [manager] responsible for resolving routing or capacity issues.
The company provides [lead-source visibility], [routing ownership], [coverage arrangements] and [coaching cadence].
Template 3: Scaling an established SaaS outbound motion
Use this module when the target customer, value proposition and core outreach process are already defined. The role adds execution capacity and improves an existing approach.
Role purpose and scope
Build a consistent flow of qualified sales conversations about [product and use case] in [territory or segment], using [established outbound approach]. The SDR supports [account executive or team] and owns [assigned accounts or prospecting coverage].
Role-specific responsibilities
- Prioritise assigned accounts against [ICP and territory rules], using relevant signals such as [team growth, a new initiative or a known software evaluation].
- Execute agreed calling, email and other approved outreach sequences, connecting [product use case] to the account’s relevant business priorities.
- Use [approved AI prospecting tools] within the existing outreach process to prepare account-specific messages and support follow-up. Review suggested contacts, personalisation and product claims before use, and flag inaccurate outputs to [manager].
- Qualify prospects against [criteria] and arrange the appropriate next step with [account executive].
- Follow up on missed meetings and deferred opportunities within [agreed ownership rules].
- Review conversion at each stage with [manager] and test agreed improvements.
- Coordinate account activity with [sales and marketing teams] to avoid conflicting outreach.
Essential requirements and trainable skills
Required: Evidence of consistent prospecting, relevant written and verbal outreach, organised follow-up and accurate opportunity records. [Specify demonstrated performance in a comparable motion if the role requires prior SDR experience.]
Trainable: [Company product, segment-specific messaging and unfamiliar tools]. Where AI-assisted outreach is part of the role, develop proficiency in the approved tools and in checking message quality, contact relevance and CRM accuracy. Require prior tool experience only if independent use is needed from the start.
Success measures and support
After [ramp period], measures are [held qualified meetings], [sales-accepted opportunities] and [agreed conversion measures]. Activity expectations are [channel-specific expectations justified by the motion].
The company supplies [account data], [playbook], [tools], [account executive alignment] and [manager coaching].
Template 4: Prospecting into complex SaaS accounts
Use this module when account research, multiple stakeholders or technical context materially shape the work. Match the seniority to the judgment required; an enterprise label alone does not define the experience needed.
Role purpose and scope
Create relevant conversations within [named accounts or target segment] through account research, stakeholder mapping and coordinated outreach with [account executives]. The priority is [business problems or use cases] among [buyer groups].
Role-specific responsibilities
- Research account priorities, existing software context, relevant changes and potential use cases before outreach.
- Map likely users, business sponsors, decision-makers and relevant IT or procurement stakeholders, distinguishing verified information from assumptions.
- Use [approved AI research tools] to organise account information and draft stakeholder-specific outreach. Verify company developments and stakeholder roles against reliable sources, and do not present inferred buying priorities as facts.
- Develop account-specific outreach with [account executive], using approved product and commercial information.
- Engage relevant stakeholders and capture their different needs, interests and involvement.
- Record integration, security, procurement or implementation questions and bring in [AE, solutions engineer or specialist] rather than make unsupported commitments.
- Maintain shared account notes and coordinate next steps with the account owner.
Essential requirements and trainable skills
Required: Evidence of thorough business research, concise tailored communication and sound judgment when speaking with [buyer group]. [Specify technical or industry knowledge only where required for effective initial conversations.]
Trainable: [Product detail, internal account-planning process and specialist tools]. Where AI tools are used, learn to check source quality, spot unsupported conclusions and adapt generated research or messages to each stakeholder. Follow company rules on confidential account information.
Success measures and support
Measures include [relevant stakeholder engagement], [held qualified meetings] and [sales-accepted opportunities], alongside [account-research quality and agreed coverage]. Pipeline contribution follows [documented attribution rules].
The company provides [named-account priorities], [account executive planning time], [specialist access] and [research tools].
Before advertising: check the requirements and scorecard
A clear brief should be ready to assess candidates against—not just ready to post. Use this final check:
- Requirements match the work. Replace “excellent communicator” with the task: explaining a use case, asking qualification questions or writing relevant outreach.
- Trainable skills are separate. Require prior SaaS, sector or technical experience only where the work needs it. For an entry-level hire, name the coaching and product training available.
- Meeting and opportunity measures are defined. A booked meeting, a held meeting and a sales-accepted opportunity are different events. State what counts and who records acceptance.
- Targets fit your sales motion. Set them from your capacity and conversion evidence, with separate ramp milestones. Agree attribution before including pipeline value; do not copy another company’s activity quota.
- Mixed-role priorities are explicit. Define what happens when inbound demand competes with outbound work, and who resolves lead-routing or capacity issues.
- Employment details are approved. Confirm compensation, currency, location, working hours, time-zone coverage and support. Add the approved application and accessibility information, replace every bracketed prompt and obtain hiring-manager approval.
For sourcing, assessment and onboarding after the brief is agreed, continue with our SDR hiring guide.
Optional: turn the brief into a candidate-facing opening
Once the facts are agreed, lead the advert with the work and the conditions around it. For the first outbound template, an original opening could read:
Our [SaaS product] helps [customer group] solve [specific problem]. We’re hiring an SDR to develop outbound conversations in [market], working directly with [manager]. The starting point is [what already exists]. You’ll have [confirmed tools and coaching], while helping us test [what still needs to be learned].
Use only details your team can stand behind. The complete advert can then explain the responsibilities, requirements, compensation and application process.
Hiring an SDR for your SaaS team? Share your sales motion, hiring market and team structure with UltraTalent.


