RevOps Solutions Specialist
Curvion Blue · Albuquerque, NM · 2 wk ago
On-siteBusiness Development$72k–$100k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we have "About Us" but we should not repeat job title as heading. The page already shows title. We need sections: About the role? The posting includes "Position Overview: RevOps Solutions Specialist". That's essentially about the role. Also "Core Outcomes", "General Expected Duties", "Compensation & Logistics". Also maybe "About Us" could be considered "About the company"? Not required but could be a section? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content for About the role (position overview). We have Responsibilities (General Expected Duties). We have Qualifications? The "You SHOULD apply..." and "You SHOULD NOT apply..." are like qualifications/requirements. Could treat as Requirements. Also we have Compensation & Logistics includes Pay (OTE) and Schedule. Also Benefits? Not mentioned. So we can have sections: About the role, Responsibilities, Requirements, Pay, Schedule. Also maybe "Core Outcomes" could be part of Responsibilities or separate? Could be considered "Key Outcomes". But instruction prefers few substantive sections over many thin ones. Could combine Core Outcomes into Responsibilities or About the role. Probably better to have About the role (position overview), Responsibilities (general expected duties + core outcomes), Requirements (should/should not apply), Pay (OTE), Schedule (Monday-Friday 9-6). Also location remote could be included in a short p maybe under About the role or separate? Could add a small paragraph about location remote.
We must not include boilerplate like EEO etc. Not present.
We must not repeat job title as heading. So no
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content for About the role (position overview). We have Responsibilities (General Expected Duties). We have Qualifications? The "You SHOULD apply..." and "You SHOULD NOT apply..." are like qualifications/requirements. Could treat as Requirements. Also we have Compensation & Logistics includes Pay (OTE) and Schedule. Also Benefits? Not mentioned. So we can have sections: About the role, Responsibilities, Requirements, Pay, Schedule. Also maybe "Core Outcomes" could be part of Responsibilities or separate? Could be considered "Key Outcomes". But instruction prefers few substantive sections over many thin ones. Could combine Core Outcomes into Responsibilities or About the role. Probably better to have About the role (position overview), Responsibilities (general expected duties + core outcomes), Requirements (should/should not apply), Pay (OTE), Schedule (Monday-Friday 9-6). Also location remote could be included in a short p maybe under About the role or separate? Could add a small paragraph about location remote.
We must not include boilerplate like EEO etc. Not present.
We must not repeat job title as heading. So no RevOps Solutions Specialist
. Use headings for sections.
We need to preserve all substantive information. Must not invent or summarize away detail. Must not omit details like specific duties, etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
Curvion is a high performance RevOps & sales augmentation agency ... (the About Us paragraph). Then position overview paragraph.
But we need to ensure we include all About Us content. The About Us paragraph is long; we must preserve it. Then position overview paragraph. We could combine them in oneor split? Probably one
containing both paragraphs. Then Responsibilities: combine Core Outcomes and General Expected Duties. Could be a
- list. Need to preserve all duties. Let's extract list items from Core Outcomes and General Expected Duties.
Core Outcomes bullet points:
- Prospective client needs are translated into clear RevOps solutions
- Sales opportunities are properly scoped before they reach implementation
- SOWs accurately define the solution, deliverables, and expectations
- Pricing reflects the actual complexity and requirements of the engagement
- Proposed solutions are technically sound and operationally realistic
- Sales and delivery remain aligned throughout the deal cycle
- Clients understand what Curvion is recommending and why
- New projects enter implementation with clear scope and minimal ambiguity
General Expected Duties list:
- Participate in sales discovery calls to understand prospective clients' sales processes, systems, challenges, and goals
- Audit and evaluate prospective clients' HubSpot environments and broader RevOps infrastructure
- Identify gaps across CRM architecture, sales processes, automation, reporting, integrations, and operational workflows
- Translate discovery findings into recommended RevOps solutions
- Design solution architecture and implementation plans
- Determine project scope, deliverables, dependencies, and requirements
- Build SOWs, scopes, proposals, and other sales enablement materials
- Partner with sales leadership to develop project pricing based on scope and complexity
- Collaborate with delivery teams to validate technical feasibility and implementation requirements
- Support sales conversations by answering technical and RevOps questions
- Communicate complex technical solutions in clear, business-focused language
- Maintain alignment between what is sold and what can actually be delivered
- Support the handoff from closed deal to implementation
- Continuously improve Curvion's RevOps solution frameworks, scoping methodology, and pricing models
We need to ensure no duplication. Some items overlap (e.g., "Translate discovery findings into recommended RevOps solutions" appears both in Core Outcomes and Duties; but we should keep only once? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines: we should remove duplicated lines. So we need to deduplicate. Let's list unique items.
Let's compile set:
1. Prospective client needs are translated into clear RevOps solutions
2. Sales opportunities are properly scoped before they reach implementation
3. SOWs accurately define the solution, deliverables, and expectations
4. Pricing reflects the actual complexity and requirements of the engagement
5. Proposed solutions are technically sound and operationally realistic
6. Sales and delivery remain aligned throughout the deal cycle
7. Clients understand what Curvion is recommending and why
8. New projects enter implementation with clear scope and minimal ambiguity
9. Participate in sales discovery calls to understand prospective clients' sales processes, systems, challenges, and goals
10. Audit and evaluate prospective clients' HubSpot environments and broader RevOps infrastructure
11. Identify gaps across CRM architecture, sales processes, automation, reporting, integrations, and operational workflows
12. Design solution architecture and implementation plans
13. Determine project scope, deliverables, dependencies, and requirements
14. Build SOWs, scopes, proposals, and other sales enablement materials
15. Partner with sales leadership to develop project pricing based on scope and complexity
16. Collaborate with delivery teams to validate technical feasibility and implementation requirements
17. Support sales conversations by answering technical and RevOps questions
18. Communicate complex technical solutions in clear, business-focused language
19. Maintain alignment between what is sold and what can actually be delivered
20. Support the handoff from closed deal to implementation
21. Continuously improve Curvion's RevOps solution frameworks, scoping methodology, and pricing models
Note: "Translate discovery findings into recommended RevOps solutions" appears as #1? Actually #1 is similar but not exactly; #1 is about prospective client needs translation; #12? Actually we have "Translate discovery findings into recommended RevOps solutions" as a duty; we didn't include it yet. Let's add:
22. Translate discovery findings into recommended RevOps solutions
But note #1 is similar but not identical; we keep both as they are distinct: one is outcome, other is duty. Keep.
Now Requirements: from "You SHOULD apply..." and "You SHOULD NOT apply...". We need to capture qualifications. Let's extract bullet-like statements.
You SHOULD apply to this role if:
- You have agency, consultancy, or client-services experience
- You’ve preferably worked for a HubSpot Solutions Partner, HubSpot agency, RevOps agency, CRM consultancy, or similar organization
- You’ve worked with multiple clients and HubSpot environments
- You know HubSpot extremely well and have built real-world systems
- You understand how sales teams actually operate, not just how CRMs work
- You’ve participated in discovery, solution design, scoping, or technical sales conversations
- You can look at a client's sales operation and quickly identify gaps and opportunities
- You can translate a business problem into a technical and operational solution
- You have experience creating SOWs, proposals, scopes, implementation plans, or project estimates
- You understand how to evaluate project complexity, effort, resources, and pricing
- You’re comfortable working alongside sales throughout the deal cycle
- You can explain technical concepts to executives and non-technical decision makers without making their eyes glaze over
- You can balance what the client wants, what they actually need, and what Curvion can realistically deliver
- You enjoy being the bridge between sales and delivery
You SHOULD NOT apply to this role if:
- Your HubSpot experience has only been internal to one company
- You have no agency, consulting, or client-services experience
- You’ve never worked across multiple client environments
- You know HubSpot but don't understand sales or RevOps
- You don't enjoy discovery conversations or client interaction
- You've never had to scope a project or define deliverables
- You aren't comfortable thinking about project effort and pricing
- You need someone else to tell you what solution to recommend
- You prefer staying completely behind the scenes
- You’re uncomfortable being accountable for what gets sold and scoped
We need to preserve all. Could combine into a single list of requirements (positive) and maybe a separate list of disqualifiers? But we can just list all as requirements (including negatives as "should not"). However instruction: use
- for any list of duties/requirements/benefits. So we can make a
- for Requirements, containing all these statements. Might be long but okay.
Pay: OTE: $72,000 - $100,000 annually, Additional Compensation: Bonus opportunities, Compensation Range: $72K - $100K (duplicate). We need to preserve all substantive info, not duplicate. So we can note: OTE $72,000 - $100,000 annually; bonus opportunities; compensation range $72K - $100K. Could combine.
Schedule: Monday-Friday, 9:00 AM-6:00 PM.
Location: Remote (maybe include in About the role paragraph or separate short p). Could add a
Location: Remote.
maybe under About the role or as its own section? Not required heading. We must not create Benefits section unless posting states them. Not present. Now produce HTML. We'll have:About the role
About Us paragraph... Position Overview paragraph... Location: Remote.
But we need to ensure we include all About Us text exactly. Let's copy: "About Us Curvion is a high performance RevOps & sales augmentation agency that installs and deploys enterprise-grade, AI-driven revenue engines and selling systems for our clients. Think of a lead generation based marketing agency…. But focused on sales! We design and install complete sales systems from sales processes and GTM strategy to CRM setup all the way to fully outsourced sales engagements. Then we enhance those systems with AI enabled tools and battle tested playbooks, and finally, we provide highly trained sales talent to help our clients execute so their revenue engine runs faster, scales efficiently, and performs consistently. In short, we build and power modern, AI-driven sales systems that help companies grow with clarity and control." Then position overview: "Position Overview: RevOps Solutions Specialist The RevOps Solutions Specialist sits at the intersection of sales, RevOps, HubSpot, and solution design. You’ll work directly in the sales process to understand prospective clients' current sales operations, identify gaps and opportunities, and translate those findings into a clear RevOps solution. You need to know HubSpot extremely well, but this role is much bigger than HubSpot. You’ll help determine what systems, workflows, automations, integrations, processes, and operational infrastructure a client actually needs. From there, you’ll help scope the project, define deliverables, build the SOW, and develop pricing. In other words, you’re the person who helps turn: "Here's our sales problem." into: "Here's what Curvion should build, here's how we'll build it, and here's what it will cost." You’ll work closely with the sales and delivery teams throughout the deal cycle, helping ensure that what we sell is technically sound, properly scoped, commercially viable, and deliverable. This is an agency role. You’ll work across multiple prospective and active client environments, each with different sales processes, systems, and business requirements. Experience working in a client-services environment is critical. Ideal background: HubSpot Solutions Partner, HubSpot agency, RevOps agency, CRM consultancy, or similar technology
- for any list of duties/requirements/benefits. So we can make a