Regional GM - Chicago (Remote)
ExecutivePlacements.com · North Wilkesboro, NC · 3 wk ago
Management$100/hrFull-time
We need to output HTML fragment with sections: About Unframe (maybe heading "About Unframe"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings as needed? Probably we should follow those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However the posting includes "About Unframe", "About The Role", "What You'll Do", "What We Are Looking For", "Nice To Have", "Why join us?". We need to map to allowed headings. The instruction: "use
for section headings (e.g. About the role...). So we will have About the role heading with the paragraph: "We're looking for a Regional GM to join our team and help drive our go-to-market motion. You'll play a pivotal role in landing our first major customers, shaping our sales playbook, and partnering directly with the VP of Sales and founder to build a high-performance revenue engine."
But we also have About Unframe description. Where to put that? Could be a preceding
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings as needed? Probably we should follow those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However the posting includes "About Unframe", "About The Role", "What You'll Do", "What We Are Looking For", "Nice To Have", "Why join us?". We need to map to allowed headings. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings, but not limited? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those exact headings when applicable. So we need to decide which sections we have content for.
We have:
- About Unframe: description of company. Could be "About the role"? No, that's about the role. There's no explicit "About Unframe" heading in list, but we could still use for "About Unframe"? The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests those are typical. Safer to use those headings only. However we need to include substantive info; we could put About Unframe under a heading like "About the role"? That would be inaccurate. Perhaps we can treat "About Unframe" as part of the role description? But better to follow instruction: Use headings from the list that match content. We have:
- About the role: we have "About The Role" section. So we can use About the role
and put the paragraph.
- Responsibilities: we have "What You'll Do" which is responsibilities. So Responsibilities
with list.
- Requirements: we have "What We Are Looking For" which is requirements. So Requirements
with list.
- Qualifications: maybe we could separate "Nice To Have" as qualifications? Or we could treat Nice To Have as "Qualifications"? The list includes Qualifications. We could put Nice To Have under Qualifications.
- Skills: maybe we could extract skills from requirements? But we could also put skills under Skills heading if we have explicit skills. The posting mentions "Entrepreneurial mindset", "Success in highly regulated industries". Could be skills. But we could also just not include Skills if not explicit.
- Benefits: we have "Why join us?" includes compensation uncapped, equity, etc. Also mention free POC etc. That's benefits. So we can have Benefits
with list.
- Pay: The posting mentions "Compensation is uncapped with aggressive accelerators. At $1M+ ACV deal sizes, this structure rewards over-performance on meaningful deals." That's pay info. So we can have Pay
with that paragraph.
- Schedule: Not mentioned (remote location). Could we infer schedule? Not given. So we should not create Schedule section.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay.
We need to ensure we don't create empty sections. For Skills, we may not have explicit skill list; we could combine some skill-like statements under Skills. But we could also omit Skills if not explicit. The instruction: "Prefer a few substantive sections over many thin ones." So better to omit Skills if not explicit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now we need to extract content precisely, preserving all substantive info, no boilerplate.
Let's parse the posting.
Full text:
Job Description Job Description Regional GM at Unframe Location: Chicago, Illinois (Remote) About Unframe Unframe is an AI-first startup helping the world's largest enterprises bring LLM-powered applications to life in days - not months. We combine the speed of a product company with the flexibility of a consultancy, helping customers move from idea to deployed AI systems faster than anyone else in the market. With over $100M in TCV secured within 12 months, and a new $50M Series B led by Highland Europe, Unframe is rapidly scaling globally alongside Fortune 500 customers, backed by Bessemer, Craft, and TLV. About The Role We're looking for a Regional GM to join our team and help drive our go-to-market motion. You'll play a pivotal role in landing our first major customers, shaping our sales playbook, and partnering directly with the VP of Sales and founder to build a high-performance revenue engine. What You'll Do Lead complex, multi-stakeholder sales cycles into highly regulated industries (FinServ, Healthcare, Manufacturing, Retail) where our on-premises capabilities provide a competitive advantage.Build pipeline from zero in an early-stage environment—identify and win strategic enterprise accounts with no hand-raisers or established playbook.Translate complex AI/ML capabilities into compelling business outcomes for C-suite stakeholders, positioning Unframe for companies seeking to "buy vs. build" AI capabilities.Architect multi-year expansion strategies and build deep relationships across IT, product, and innovation teams.Collaborate directly with the VP of Sales and founders to refine the enterprise strategy and influence the product roadmap What We Are Looking For 8+ years enterprise software sales with consistent quota over-achievement at Fortune 500 companiesProven track record closing $1M+ ACV deals in early-stage environmentsExperience selling complex technical solutions to CIO organizationsBackground in AI/ML platforms, digital transformation, enterprise data platforms, or management consultingEntrepreneurial mindset, you thrive in ambiguity, own outcomes, and build from scratchSuccess in highly regulated industries with complex compliance requirements Nice To Have Regulated industry experience, early-stage success Why join us? Compensation is uncapped with aggressive accelerators. At $1M+ ACV deal sizes, this structure rewards over-performance on meaningful deals.Our VP of Sales joined Unframe for three reasons: a founder with a proven exit, tier-one investors, and a product that's genuinely different and defensible. The GTM approach backs that up. Buyers get a free POC, tailored to their actual use case, delivered in days. No data sharing, no upfront cost, no six-month consulting engagement before anyone sees value.You'll work directly with the VP of Sales and founders, shape GTM strategy, close the deals that define our market position, and hold equity in a company with real institutional backing and momentum.We hire with intention. If you thrive in a performance culture with real backing behind you, you will win here. Ready to Build the Future? If this opportunity excites you, apply now!
We need to remove boilerplate: "Job Description Job Description", "Location: Chicago, Illinois (Remote)" maybe we keep location? It's minor metadata; we can fold into a short p or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those exact headings when applicable. So we need to decide which sections we have content for.
We have:
- About Unframe: description of company. Could be "About the role"? No, that's about the role. There's no explicit "About Unframe" heading in list, but we could still use for "About Unframe"? The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests those are typical. Safer to use those headings only. However we need to include substantive info; we could put About Unframe under a heading like "About the role"? That would be inaccurate. Perhaps we can treat "About Unframe" as part of the role description? But better to follow instruction: Use headings from the list that match content. We have:
- About the role: we have "About The Role" section. So we can use About the role
and put the paragraph.
- Responsibilities: we have "What You'll Do" which is responsibilities. So Responsibilities
with list.
- Requirements: we have "What We Are Looking For" which is requirements. So Requirements
with list.
- Qualifications: maybe we could separate "Nice To Have" as qualifications? Or we could treat Nice To Have as "Qualifications"? The list includes Qualifications. We could put Nice To Have under Qualifications.
- Skills: maybe we could extract skills from requirements? But we could also put skills under Skills heading if we have explicit skills. The posting mentions "Entrepreneurial mindset", "Success in highly regulated industries". Could be skills. But we could also just not include Skills if not explicit.
- Benefits: we have "Why join us?" includes compensation uncapped, equity, etc. Also mention free POC etc. That's benefits. So we can have Benefits
with list.
- Pay: The posting mentions "Compensation is uncapped with aggressive accelerators. At $1M+ ACV deal sizes, this structure rewards over-performance on meaningful deals." That's pay info. So we can have Pay
with that paragraph.
- Schedule: Not mentioned (remote location). Could we infer schedule? Not given. So we should not create Schedule section.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay.
We need to ensure we don't create empty sections. For Skills, we may not have explicit skill list; we could combine some skill-like statements under Skills. But we could also omit Skills if not explicit. The instruction: "Prefer a few substantive sections over many thin ones." So better to omit Skills if not explicit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now we need to extract content precisely, preserving all substantive info, no boilerplate.
Let's parse the posting.
Full text:
Job Description Job Description Regional GM at Unframe Location: Chicago, Illinois (Remote) About Unframe Unframe is an AI-first startup helping the world's largest enterprises bring LLM-powered applications to life in days - not months. We combine the speed of a product company with the flexibility of a consultancy, helping customers move from idea to deployed AI systems faster than anyone else in the market. With over $100M in TCV secured within 12 months, and a new $50M Series B led by Highland Europe, Unframe is rapidly scaling globally alongside Fortune 500 customers, backed by Bessemer, Craft, and TLV. About The Role We're looking for a Regional GM to join our team and help drive our go-to-market motion. You'll play a pivotal role in landing our first major customers, shaping our sales playbook, and partnering directly with the VP of Sales and founder to build a high-performance revenue engine. What You'll Do Lead complex, multi-stakeholder sales cycles into highly regulated industries (FinServ, Healthcare, Manufacturing, Retail) where our on-premises capabilities provide a competitive advantage.Build pipeline from zero in an early-stage environment—identify and win strategic enterprise accounts with no hand-raisers or established playbook.Translate complex AI/ML capabilities into compelling business outcomes for C-suite stakeholders, positioning Unframe for companies seeking to "buy vs. build" AI capabilities.Architect multi-year expansion strategies and build deep relationships across IT, product, and innovation teams.Collaborate directly with the VP of Sales and founders to refine the enterprise strategy and influence the product roadmap What We Are Looking For 8+ years enterprise software sales with consistent quota over-achievement at Fortune 500 companiesProven track record closing $1M+ ACV deals in early-stage environmentsExperience selling complex technical solutions to CIO organizationsBackground in AI/ML platforms, digital transformation, enterprise data platforms, or management consultingEntrepreneurial mindset, you thrive in ambiguity, own outcomes, and build from scratchSuccess in highly regulated industries with complex compliance requirements Nice To Have Regulated industry experience, early-stage success Why join us? Compensation is uncapped with aggressive accelerators. At $1M+ ACV deal sizes, this structure rewards over-performance on meaningful deals.Our VP of Sales joined Unframe for three reasons: a founder with a proven exit, tier-one investors, and a product that's genuinely different and defensible. The GTM approach backs that up. Buyers get a free POC, tailored to their actual use case, delivered in days. No data sharing, no upfront cost, no six-month consulting engagement before anyone sees value.You'll work directly with the VP of Sales and founders, shape GTM strategy, close the deals that define our market position, and hold equity in a company with real institutional backing and momentum.We hire with intention. If you thrive in a performance culture with real backing behind you, you will win here. Ready to Build the Future? If this opportunity excites you, apply now!
We need to remove boilerplate: "Job Description Job Description", "Location: Chicago, Illinois (Remote)" maybe we keep location? It's minor metadata; we can fold into a short p or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests those are typical. Safer to use those headings only. However we need to include substantive info; we could put About Unframe under a heading like "About the role"? That would be inaccurate. Perhaps we can treat "About Unframe" as part of the role description? But better to follow instruction: Use headings from the list that match content. We have:
- About the role: we have "About The Role" section. So we can use About the role
and put the paragraph.
- Responsibilities: we have "What You'll Do" which is responsibilities. So Responsibilities
with list.
- Requirements: we have "What We Are Looking For" which is requirements. So Requirements
with list.
- Qualifications: maybe we could separate "Nice To Have" as qualifications? Or we could treat Nice To Have as "Qualifications"? The list includes Qualifications. We could put Nice To Have under Qualifications.
- Skills: maybe we could extract skills from requirements? But we could also put skills under Skills heading if we have explicit skills. The posting mentions "Entrepreneurial mindset", "Success in highly regulated industries". Could be skills. But we could also just not include Skills if not explicit.
- Benefits: we have "Why join us?" includes compensation uncapped, equity, etc. Also mention free POC etc. That's benefits. So we can have Benefits
with list.
- Pay: The posting mentions "Compensation is uncapped with aggressive accelerators. At $1M+ ACV deal sizes, this structure rewards over-performance on meaningful deals." That's pay info. So we can have Pay
with that paragraph.
- Schedule: Not mentioned (remote location). Could we infer schedule? Not given. So we should not create Schedule section.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay.
We need to ensure we don't create empty sections. For Skills, we may not have explicit skill list; we could combine some skill-like statements under Skills. But we could also omit Skills if not explicit. The instruction: "Prefer a few substantive sections over many thin ones." So better to omit Skills if not explicit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now we need to extract content precisely, preserving all substantive info, no boilerplate.
Let's parse the posting.
Full text:
Job Description Job Description Regional GM at Unframe Location: Chicago, Illinois (Remote) About Unframe Unframe is an AI-first startup helping the world's largest enterprises bring LLM-powered applications to life in days - not months. We combine the speed of a product company with the flexibility of a consultancy, helping customers move from idea to deployed AI systems faster than anyone else in the market. With over $100M in TCV secured within 12 months, and a new $50M Series B led by Highland Europe, Unframe is rapidly scaling globally alongside Fortune 500 customers, backed by Bessemer, Craft, and TLV. About The Role We're looking for a Regional GM to join our team and help drive our go-to-market motion. You'll play a pivotal role in landing our first major customers, shaping our sales playbook, and partnering directly with the VP of Sales and founder to build a high-performance revenue engine. What You'll Do Lead complex, multi-stakeholder sales cycles into highly regulated industries (FinServ, Healthcare, Manufacturing, Retail) where our on-premises capabilities provide a competitive advantage.Build pipeline from zero in an early-stage environment—identify and win strategic enterprise accounts with no hand-raisers or established playbook.Translate complex AI/ML capabilities into compelling business outcomes for C-suite stakeholders, positioning Unframe for companies seeking to "buy vs. build" AI capabilities.Architect multi-year expansion strategies and build deep relationships across IT, product, and innovation teams.Collaborate directly with the VP of Sales and founders to refine the enterprise strategy and influence the product roadmap What We Are Looking For 8+ years enterprise software sales with consistent quota over-achievement at Fortune 500 companiesProven track record closing $1M+ ACV deals in early-stage environmentsExperience selling complex technical solutions to CIO organizationsBackground in AI/ML platforms, digital transformation, enterprise data platforms, or management consultingEntrepreneurial mindset, you thrive in ambiguity, own outcomes, and build from scratchSuccess in highly regulated industries with complex compliance requirements Nice To Have Regulated industry experience, early-stage success Why join us? Compensation is uncapped with aggressive accelerators. At $1M+ ACV deal sizes, this structure rewards over-performance on meaningful deals.Our VP of Sales joined Unframe for three reasons: a founder with a proven exit, tier-one investors, and a product that's genuinely different and defensible. The GTM approach backs that up. Buyers get a free POC, tailored to their actual use case, delivered in days. No data sharing, no upfront cost, no six-month consulting engagement before anyone sees value.You'll work directly with the VP of Sales and founders, shape GTM strategy, close the deals that define our market position, and hold equity in a company with real institutional backing and momentum.We hire with intention. If you thrive in a performance culture with real backing behind you, you will win here. Ready to Build the Future? If this opportunity excites you, apply now!
We need to remove boilerplate: "Job Description Job Description", "Location: Chicago, Illinois (Remote)" maybe we keep location? It's minor metadata; we can fold into a short p or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location is minor metadata; we could include in a short p at top maybe. But we could also drop it. Probably better to include a short p with location. We need to preserve all substantive information: company description, role description, responsibilities, requirements, nice-to-have, benefits/pay/equity etc. We must not include application instructions ("Ready to Build the Future? If this opportunity excites you, apply now!"). Also remove duplicated lines, cookie/navigation/legal/EEO etc. Not present. Now craft HTML. We'll start with a
for location:
Location: Chicago, Illinois (Remote)
ThenAbout the role
with paragraph from "About The Role". Actually "About The Role" is separate from "About Unframe". The instruction says use for section headings (e.g. About the role...). So we will have About the role heading with the paragraph: "We're looking for a Regional GM to join our team and help drive our go-to-market motion. You'll play a pivotal role in landing our first major customers, shaping our sales playbook, and partnering directly with the VP of Sales and founder to build a high-performance revenue engine."
But we also have About Unframe description. Where to put that? Could be a preceding About Unframe
but not in list. Perhaps we could treat it as part of About the role? But that would mix company info with role. Better to add a heading "About Unframe" as About Unframe
even though not in examples; but the instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't say we cannot use other headings; it's just examples. However to be safe, we could incorporate About Unframe into a
before the About the role heading, maybe as a general intro. The instruction: "Prefer a few substantive sections over many thin ones." So we could have a section "About Unframe" as its own heading; it's substantive. I'd include it. Thus:
About Unframe
Unframe is an AI-first startup helping the world's largest enterprises bring LLM-powered applications to life in days - not months. We combine the speed of a product company with the flexibility of a consultancy, helping customers move from idea to deployed AI systems faster than anyone else in the market. With over $100M in TCV secured within 12 months, and a new $50M Series B led by Highland Europe, Unframe is rapidly scaling globally alongside Fortune 500 customers, backed by Bessemer, Craft, and TLV.
ThenAbout the role
with paragraph. ThenResponsibilities
with- items from "What You'll Do". Need to split sentences. What You'll Do list: - Lead complex, multi-stakeholder sales cycles into highly regulated industries (FinServ, Healthcare, Manufacturing, Retail) where our on-premises capabilities provide a competitive advantage. - Build pipeline from zero in an early-stage environment—identify and win strategic enterprise accounts with no hand-raisers or established playbook. - Translate complex AI/ML capabilities into compelling business outcomes for C-suite stakeholders, positioning Unframe for companies seeking to "buy vs. build" AI capabilities. - Architect multi-year expansion strategies and build deep relationships across IT, product, and innovation teams. - Collaborate directly with the VP of Sales and founders to refine the enterprise strategy and influence the product roadmap Make each as
- .
Then
Requirements
with list from "What We Are Looking For". Items: - 8+ years enterprise software sales with consistent quota over-achievement at Fortune 500 companies - Proven track record closing $1M+ ACV deals in early-stage environments - Experience selling complex technical solutions to CIO organizations - Background in AI/ML platforms, digital transformation, enterprise data platforms, or management consulting - Entrepreneurial mindset, you thrive in ambiguity, own outcomes, and build from scratch - Success in highly regulated industries with complex compliance requirements Make each - .
Then
Qualifications
with Nice To Have items: - Regulated industry experience - Early-stage success Make each - .
Then
Benefits
with list from "Why join us?" includes: - Compensation is uncapped with aggressive accelerators. At $1M+ ACV deal sizes, this structure rewards over-performance on meaningful deals. - VP of Sales joined Unframe for three reasons: a founder with