Founding Senior Business Development Manager, Wealthroute (Remote)
Forbes Advisor · Wilmington, DE · 3 wk ago
RemoteRemoteSalesFull-time
We need to output HTML fragment with sections for headings present in posting: About The Role, What You’ll Do, What Success Looks Like, What We’re Looking For, Preferred Experience, Growth Opportunity, About Wealthroute maybe? The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to parse the posting and produce sections for headings that have substantive content. The posting includes sections: About The Role, About Wealthroute, What You’ll Do, Help Build the Wealthroute Sales Function, Develop the Market, Partner Internally, What Success Looks Like, What We’re Looking For, Preferred Experience, Growth Opportunity. Also there is a mission statement at top (maybe not a section). We need to decide which headings to use. The allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples, but we can use other headings if they match content? Probably we should map content to those standard headings where appropriate. For instance, "About The Role" maps to "About the role". "What You’ll Do" could be Responsibilities. "What Success Looks Like" maybe Qualifications? Actually success metrics maybe not a standard heading; but we could treat as "Requirements"? Not exactly. "What We’re Looking For" could be Requirements or Qualifications. "Preferred Experience" could be Qualifications. "Growth Opportunity" maybe not a standard heading; could be omitted or put under something else? The instruction: Prefer a few substantive sections over many thin ones. So we might combine some.
We need to preserve all substantive information. So we need to include all content, but we can group under headings.
We must not include boilerplate like EEO statement at end; remove that.
We must not include duplicated lines.
We need to output only HTML fragment.
Let's extract substantive content:
Mission/intro paragraph: "At Forbes Advisor, our mission is to help readers turn their aspirations into reality. We arm people with trusted advice and guidance so they can make informed decisions they feel confident in and get back to doing the things they care about most. We are an experienced team of industry experts dedicated to helping readers make smart decisions and choose the right products with ease. Forbes Advisor boasts decades of experience across dozens of geographies and teams, including Content, SEO, Business Intelligence, Finance, HR, Marketing, Production, Technology and Sales. The team brings rich industry knowledge to Forbes Advisor's global coverage of consumer credit, debt, health, home improvement, banking, investing, credit cards, small business, education, insurance, loans, real estate and travel."
That's substantive but not under a heading. Could be a preamble
before any heading.
Then "About The Role" heading with paragraph.
Then "About Wealthroute" heading with paragraph.
Then "What You’ll Do" heading with bullet list (multiple paragraphs each starting with a bold phrase). We need to convert to
- .
Then "Help Build the Wealthroute Sales Function" heading with bullet list.
Then "Develop the Market" heading with bullet list.
Then "Partner Internally" heading with bullet list.
Then "What Success Looks Like" heading with bullet list (each starting with bold phrase).
Then "What We’re Looking For" heading with bullet list (some bullet points).
Then "Preferred Experience" heading with paragraph.
Then "Growth Opportunity" heading with paragraph.
We need to decide which headings to map to allowed list.
We could use:
About the role
(for About The Role)
About Wealthroute
(maybe not in list but we can still use? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use for section headings (e.g. ...)". Likely they expect us to use those standard headings where applicable, but we can also use others if needed. However they say "include a section ONLY when the posting has real, specific content for it". So we can include About Wealthroute as a section.
But to be safe, we could map About Wealthroute under "About the role"? No, that's distinct.
Better to follow the instruction: use h3 for section headings (examples given). So we can use any heading we want, as long as it's h3. The examples are just examples. So we can use headings like About the role, About Wealthroute, Responsibilities, etc.
Thus we will produce sections:
- About the role (from About The Role)
- About Wealthroute (from About Wealthroute)
- Responsibilities (combining What You’ll Do, Help Build the Wealthroute Sales Function, Develop the Market, Partner Internally) maybe as one Responsibilities section with sub-sections? But we need to preserve all detail; we could keep separate subheadings within Responsibilities using ? Not allowed? Only h3 mentioned. But we could keep separate h3 sections for each of those categories: Responsibilities could be split into multiple h3s like "Build and Manage the RIA Sales Pipeline", "Own the Full Sales Cycle", etc. However the instruction says prefer a few substantive sections over many thin ones. So maybe combine them under one Responsibilities section with - capturing all duties. But we need to preserve the grouping? The instruction says preserve ALL substantive information; not required to keep original grouping. So we can combine all duty statements into a single list under Responsibilities.
Similarly, Requirements/Qualifications could combine What We’re Looking For and Preferred Experience.
Success metrics maybe could be under "Qualifications"? Not exactly. Could be under "What Success Looks Like" as its own section; but we could treat as "Requirements"? Not appropriate. Better to keep as its own section maybe "Success Metrics". But not in examples. However we can still use h3 for any heading.
Thus we will produce sections:
About the role
...
About Wealthroute
...
Responsibilities
- ... (all duty statements)
What Success Looks Like
- ... (success metrics)
Requirements
- ... (What We’re Looking For)
Preferred Qualifications
...
(or ul if list)
Growth Opportunity
...
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now extract content.
Let's copy the relevant paragraphs.
About The Role:
"Forbes Advisor is seeking a Founding Senior Business Development Manager to help build and scale Wealthroute, our financial advisor lead-generation business. This is a hands-on, full-cycle sales role focused primarily on building partnerships with Registered Investment Advisor (RIA) firms and other wealth management organizations across the United States. As the founding business development hire for Wealthroute, you will not only own the sales cycle from prospecting through signed agreement and activation, but also help shape the partner acquisition strategy, sales process, messaging, targeting, and operating model as the business grows. The successful candidate will identify and source prospective partners, build a strong pipeline, conduct outreach, lead sales conversations, communicate Wealthroute’s value proposition, negotiate commercial terms, and drive prospects through signed agreement and activation. This is an opportunity for an experienced business development professional to have an outsized impact on an early-stage growth business and help build a scalable sales function from the ground up. As Wealthroute scales, there may be opportunities to take on broader responsibilities and help build and lead a larger business development organization."
About Wealthroute:
"Wealthroute connects financial advisory firms with prospective clients generated through high-intent paid search traffic. Our goal is to build a scalable network of high-quality financial advisor partners that can serve consumers looking for professional financial advice while creating a meaningful and growing acquisition channel for participating firms."
What You’ll Do (list items):
- Build and Manage the RIA Sales Pipeline
Identify and source prospective RIA firms and wealth management partners across the United States.
Build and continuously expand a target account list using existing Forbes Advisor resources, prospecting tools, industry research, referrals, and other sourcing methods.
Prioritize prospective partners based on fit, capacity, business model, and growth potential.
Maintain an organized and actionable sales pipeline.
Develop a repeatable sourcing approach that can scale as Wealthroute grows.
- Own the Full Sales Cycle
Conduct outbound prospecting through email, phone, LinkedIn, referrals, and other channels.
Generate qualified meetings with prospective RIA and wealth management firms.
Lead discovery and sales conversations.
Clearly communicate the Wealthroute value proposition and explain how the program can help firms acquire new prospective clients.
Understand partner needs, economics, capacity, and potential objections.
Manage follow-up and move opportunities efficiently through the sales process.
Negotiate commercial terms in coordination with internal leadership.
Drive opportunities through signed agreement and initial activation.
Coordinate a smooth handoff to the appropriate account management or operating team following launch.
- Help Build the Wealthroute Sales Function
Help define and refine the Wealthroute sales playbook.
Develop best practices for targeting, outreach, qualification, pitching, objection handling, negotiation, and partner activation.
Test and improve messaging based on market feedback.
Help establish the processes, tools, and reporting needed to manage the sales pipeline effectively.
Identify opportunities to make the partner acquisition process more scalable and repeatable.
Contribute to the design of the future Business Development organization as Wealthroute grows.
- Develop the Market
Build a strong understanding of the RIA and wealth management ecosystem.
Identify new segments, partner profiles, and sourcing opportunities.
Develop relationships across the financial advisor community.
Gather feedback from prospective partners and communicate market insights back to the Wealthroute team.
Help refine messaging, positioning, partner requirements, and the overall commercial approach based on market feedback.
- Partner Internally
Report directly to the Head of Financial Services Owned Products.
Work closely with leadership on commercial strategy, target accounts, pricing, and partner prioritization.
Coordinate with Marketing and Paid Search teams to understand partner capacity and growth requirements.
Work with Operations and other internal teams to support partner onboarding and activation.
Provide regular reporting on pipeline, meetings, agreements, partner feedback, and sales performance.
What Success Looks Like (list items):
- Building a consistent pipeline of qualified RIA and wealth management prospects.
- Generating qualified sales meetings.
- Converting opportunities into signed agreements.
- Activating new financial advisor partners.
- Increasing partner capacity available to Wealthroute.
- Developing
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and produce sections for headings that have substantive content. The posting includes sections: About The Role, About Wealthroute, What You’ll Do, Help Build the Wealthroute Sales Function, Develop the Market, Partner Internally, What Success Looks Like, What We’re Looking For, Preferred Experience, Growth Opportunity. Also there is a mission statement at top (maybe not a section). We need to decide which headings to use. The allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples, but we can use other headings if they match content? Probably we should map content to those standard headings where appropriate. For instance, "About The Role" maps to "About the role". "What You’ll Do" could be Responsibilities. "What Success Looks Like" maybe Qualifications? Actually success metrics maybe not a standard heading; but we could treat as "Requirements"? Not exactly. "What We’re Looking For" could be Requirements or Qualifications. "Preferred Experience" could be Qualifications. "Growth Opportunity" maybe not a standard heading; could be omitted or put under something else? The instruction: Prefer a few substantive sections over many thin ones. So we might combine some. We need to preserve all substantive information. So we need to include all content, but we can group under headings. We must not include boilerplate like EEO statement at end; remove that. We must not include duplicated lines. We need to output only HTML fragment. Let's extract substantive content: Mission/intro paragraph: "At Forbes Advisor, our mission is to help readers turn their aspirations into reality. We arm people with trusted advice and guidance so they can make informed decisions they feel confident in and get back to doing the things they care about most. We are an experienced team of industry experts dedicated to helping readers make smart decisions and choose the right products with ease. Forbes Advisor boasts decades of experience across dozens of geographies and teams, including Content, SEO, Business Intelligence, Finance, HR, Marketing, Production, Technology and Sales. The team brings rich industry knowledge to Forbes Advisor's global coverage of consumer credit, debt, health, home improvement, banking, investing, credit cards, small business, education, insurance, loans, real estate and travel." That's substantive but not under a heading. Could be a preamble
before any heading. Then "About The Role" heading with paragraph. Then "About Wealthroute" heading with paragraph. Then "What You’ll Do" heading with bullet list (multiple paragraphs each starting with a bold phrase). We need to convert to
- .
Then "Help Build the Wealthroute Sales Function" heading with bullet list.
Then "Develop the Market" heading with bullet list.
Then "Partner Internally" heading with bullet list.
Then "What Success Looks Like" heading with bullet list (each starting with bold phrase).
Then "What We’re Looking For" heading with bullet list (some bullet points).
Then "Preferred Experience" heading with paragraph.
Then "Growth Opportunity" heading with paragraph.
We need to decide which headings to map to allowed list.
We could use:
About the role
(for About The Role)About Wealthroute
(maybe not in list but we can still use? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "usefor section headings (e.g. ...)". Likely they expect us to use those standard headings where applicable, but we can also use others if needed. However they say "include a section ONLY when the posting has real, specific content for it". So we can include About Wealthroute as a section. But to be safe, we could map About Wealthroute under "About the role"? No, that's distinct. Better to follow the instruction: use h3 for section headings (examples given). So we can use any heading we want, as long as it's h3. The examples are just examples. So we can use headings like About the role, About Wealthroute, Responsibilities, etc. Thus we will produce sections: - About the role (from About The Role) - About Wealthroute (from About Wealthroute) - Responsibilities (combining What You’ll Do, Help Build the Wealthroute Sales Function, Develop the Market, Partner Internally) maybe as one Responsibilities section with sub-sections? But we need to preserve all detail; we could keep separate subheadings within Responsibilities using
? Not allowed? Only h3 mentioned. But we could keep separate h3 sections for each of those categories: Responsibilities could be split into multiple h3s like "Build and Manage the RIA Sales Pipeline", "Own the Full Sales Cycle", etc. However the instruction says prefer a few substantive sections over many thin ones. So maybe combine them under one Responsibilities section with
- capturing all duties. But we need to preserve the grouping? The instruction says preserve ALL substantive information; not required to keep original grouping. So we can combine all duty statements into a single list under Responsibilities.
Similarly, Requirements/Qualifications could combine What We’re Looking For and Preferred Experience.
Success metrics maybe could be under "Qualifications"? Not exactly. Could be under "What Success Looks Like" as its own section; but we could treat as "Requirements"? Not appropriate. Better to keep as its own section maybe "Success Metrics". But not in examples. However we can still use h3 for any heading.
Thus we will produce sections:
About the role
...
About Wealthroute
...
Responsibilities
- ... (all duty statements)
What Success Looks Like
- ... (success metrics)
Requirements
- ... (What We’re Looking For)
Preferred Qualifications
...
(or ul if list)Growth Opportunity
...
We need to ensure we don't include filler like "commensurate with experience". Not present. Now extract content. Let's copy the relevant paragraphs. About The Role: "Forbes Advisor is seeking a Founding Senior Business Development Manager to help build and scale Wealthroute, our financial advisor lead-generation business. This is a hands-on, full-cycle sales role focused primarily on building partnerships with Registered Investment Advisor (RIA) firms and other wealth management organizations across the United States. As the founding business development hire for Wealthroute, you will not only own the sales cycle from prospecting through signed agreement and activation, but also help shape the partner acquisition strategy, sales process, messaging, targeting, and operating model as the business grows. The successful candidate will identify and source prospective partners, build a strong pipeline, conduct outreach, lead sales conversations, communicate Wealthroute’s value proposition, negotiate commercial terms, and drive prospects through signed agreement and activation. This is an opportunity for an experienced business development professional to have an outsized impact on an early-stage growth business and help build a scalable sales function from the ground up. As Wealthroute scales, there may be opportunities to take on broader responsibilities and help build and lead a larger business development organization." About Wealthroute: "Wealthroute connects financial advisory firms with prospective clients generated through high-intent paid search traffic. Our goal is to build a scalable network of high-quality financial advisor partners that can serve consumers looking for professional financial advice while creating a meaningful and growing acquisition channel for participating firms." What You’ll Do (list items): - Build and Manage the RIA Sales Pipeline Identify and source prospective RIA firms and wealth management partners across the United States. Build and continuously expand a target account list using existing Forbes Advisor resources, prospecting tools, industry research, referrals, and other sourcing methods. Prioritize prospective partners based on fit, capacity, business model, and growth potential. Maintain an organized and actionable sales pipeline. Develop a repeatable sourcing approach that can scale as Wealthroute grows. - Own the Full Sales Cycle Conduct outbound prospecting through email, phone, LinkedIn, referrals, and other channels. Generate qualified meetings with prospective RIA and wealth management firms. Lead discovery and sales conversations. Clearly communicate the Wealthroute value proposition and explain how the program can help firms acquire new prospective clients. Understand partner needs, economics, capacity, and potential objections. Manage follow-up and move opportunities efficiently through the sales process. Negotiate commercial terms in coordination with internal leadership. Drive opportunities through signed agreement and initial activation. Coordinate a smooth handoff to the appropriate account management or operating team following launch. - Help Build the Wealthroute Sales Function Help define and refine the Wealthroute sales playbook. Develop best practices for targeting, outreach, qualification, pitching, objection handling, negotiation, and partner activation. Test and improve messaging based on market feedback. Help establish the processes, tools, and reporting needed to manage the sales pipeline effectively. Identify opportunities to make the partner acquisition process more scalable and repeatable. Contribute to the design of the future Business Development organization as Wealthroute grows. - Develop the Market Build a strong understanding of the RIA and wealth management ecosystem. Identify new segments, partner profiles, and sourcing opportunities. Develop relationships across the financial advisor community. Gather feedback from prospective partners and communicate market insights back to the Wealthroute team. Help refine messaging, positioning, partner requirements, and the overall commercial approach based on market feedback. - Partner Internally Report directly to the Head of Financial Services Owned Products. Work closely with leadership on commercial strategy, target accounts, pricing, and partner prioritization. Coordinate with Marketing and Paid Search teams to understand partner capacity and growth requirements. Work with Operations and other internal teams to support partner onboarding and activation. Provide regular reporting on pipeline, meetings, agreements, partner feedback, and sales performance. What Success Looks Like (list items): - Building a consistent pipeline of qualified RIA and wealth management prospects. - Generating qualified sales meetings. - Converting opportunities into signed agreements. - Activating new financial advisor partners. - Increasing partner capacity available to Wealthroute. - Developing
- capturing all duties. But we need to preserve the grouping? The instruction says preserve ALL substantive information; not required to keep original grouping. So we can combine all duty statements into a single list under Responsibilities.
Similarly, Requirements/Qualifications could combine What We’re Looking For and Preferred Experience.
Success metrics maybe could be under "Qualifications"? Not exactly. Could be under "What Success Looks Like" as its own section; but we could treat as "Requirements"? Not appropriate. Better to keep as its own section maybe "Success Metrics". But not in examples. However we can still use h3 for any heading.
Thus we will produce sections: