Senior Growth Consultant (GovCon)
Unanet · United States · 1 mo ago
RemoteRemoteConsulting$99k–$119k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description. We need headings for sections present: About the role (maybe intro), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Let's parse.
Content:
- Intro: "Unanet is seeking a Senior Growth Consultant to help our government contracting (GovCon) customers improve how they find, pursue, win, and manage growth opportunities. This is a business-led consulting role, not a configuration-only software implementation role. You will help customers connect business goals, growth strategy, capabilities, processes, people, data, and technology into a practical operating model. You will serve as a trusted advisor to our customers while leading hands-on delivery across multiple concurrent projects."
That's about the role.
- "What Success Looks Like" paragraph: could be part of responsibilities? Might be considered responsibilities.
- "What You’ll Do" list of duties: many bullet-like sentences. Should be a
- list under Responsibilities.
- "Who You Are": list of experience requirements: could be Requirements or Qualifications.
- "Your Differentiators (preferred, not required!)": could be Skills or Preferred Qualifications.
- "Your First 90 days": maybe not a standard section; could be omitted or placed under Responsibilities? Probably not needed.
- "Our Values": could be omitted as boilerplate? It's values but not required; maybe we can include as a section? The instruction: include a section ONLY when posting has real, specific content for it. Values are specific but maybe not needed; but we could include as a section "Our Values". However typical sections list includes Benefits, Pay, Schedule. We have Pay: salary range given. Benefits: mention employee equity, discretionary bonus, eligibility to participate in benefits plans, link. So we can have Benefits and Pay sections.
Schedule: not mentioned. So omit Schedule.
We need to avoid repeating job title as heading. So no heading for Senior Growth Consultant.
We need to use
for section headings. We need to output only HTML fragment. Let's craft sections:
About the role
Unanet is seeking a Senior Growth Consultant to help our government contracting (GovCon) customers improve how they find, pursue, win, and manage growth opportunities. This is a business-led consulting role, not a configuration-only software implementation role. You will help customers connect business goals, growth strategy, capabilities, processes, people, data, and technology into a practical operating model. You will serve as a trusted advisor to our customers while leading hands-on delivery across multiple concurrent projects.
What Success Looks Like
You help customers clarify the outcomes they are pursuing, make better business decisions, improve their growth processes, and adopt connected Unanet solutions. You’ll keep multiple engagements moving, surface risks early, collaborate effectively, and leave customers with stronger processes and the confidence to sustain value.
But maybe we can merge into Responsibilities. However we have a separate "What You’ll Do" list. Could make Responsibilities section with that list. Let's decide: Use sections: About the role, Responsibilities, Requirements, Qualifications (maybe combine), Skills (differentiators), Benefits, Pay. But we need to avoid thin sections. Let's see content: Responsibilities: the "What You’ll Do" list (many items). Also "What Success Looks Like" could be part of responsibilities. Requirements: "Who You Are" list (5+ years experience, GovCon experience, understanding of GovCon growth processes, facilitating workshops, business process analysis, etc.) Qualifications: maybe overlapping; but we could treat "Who You Are" as Requirements, and "Your Differentiators" as Preferred Qualifications/Skills. Skills: maybe the differentiators list. Benefits: employee equity, discretionary bonus, eligibility to participate in Unanet’s employee benefits plans, link. Pay: salary range $98,600 - $118,735 per year. We should not include "Our Values" as it's not in the list but could be a section; but we can omit to keep fewer sections. We also need to remove boilerplate like EEO, etc. The posting includes EEO statement at end; we must remove. Also remove application instructions (none present). Remove cookie/navigation/legal etc. Now craft HTML. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep all details from the lists. Let's extract details. About the role paragraph: as above. What Success Looks Like paragraph: as above. What You’ll Do list items (each sentence). Let's list them: - Lead implementation and integrated solutions on time and within budget - Build trusted relationships with customers and stakeholders across business development, capture, proposals, operations, finance, delivery, and IT - Facilitate outcome- and capability-led discovery, workshops, and decisions that connect business goals to processes, roles, data, measures, and adoption needs - Assess current-state practices and guide customers toward a practical future state - Translate business needs into clear requirements, solution options, dependencies, risks, and delivery pathways - Achieve Professional Services targets (e.g., Budgeted Delivered Hours, Realization, Utilization) - Guide connected solution design across relevant Unanet products and capabilities, including GovCon CRM, GovIntel, OpportuneAI, ProposalAI, ERP connections, as well as reporting and analytics - Partner with Project Managers, Technical Consultants, Solution Architects, Customer Success, Sales, and Product to deliver a coherent customer experience - Own consultant-led engagement activities, including customer communication, meeting leadership, planning, follow-up, documentation, enablement, and adoption support - Manage scope, risks, priorities, and deadlines across several active projects while maintaining quality and responsiveness - Contribute customer insights and delivery feedback to improve Unanet’s methodology, playbooks, and delivery standards We need to keep each as - .
Who You Are list:
- 5+ years of experience in business consulting, professional services, software implementation, or a related field
- Experience supporting Government Contractors or working within the GovCon industry
- Strong understanding of GovCon growth processes, including pursuits, capture, proposals, contract vehicles, IDIQs, task orders, teaming, recompetes, and pipeline management
- Experience facilitating executive and cross-functional workshops
- Strong business process analysis, requirements definition, and future-state design skills
- Ability to connect business strategy to practical execution and communicate effectively
- Experience with CRM, ERP, proposal management, business development, or enterprise software implementations
- Strong project management, communication, organization, and follow-through skills
- Willingness and ability to travel
Your Differentiators (preferred, not required!):
- Experience with Unanet GovCon ERP, GovCon CRM, GovIntel, ProposalAI, OpportuneAI, or related GovCon technologies
- Familiarity with GovWin, SAM.gov, or comparable market-intelligence platforms
- Experience with change management, customer adoption, organizational readiness, or value realization
- PMP, Prosci, APMP, or comparable certifications desired
First 90 days: we could omit as not a standard section; but it contains substantive info about onboarding. Could be placed under Responsibilities? Might be better to include as a section "Onboarding and Ramp‑up". But not in allowed headings list; but we could still include if we think it's real content. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but not exclusive? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. Safer to stick to those. Thus we can incorporate First 90 days info into Responsibilities or About the role? Might be better to add a short paragraph under Responsibilities about ramp-up. But we must preserve all substantive information; we can't drop it. So we need to include it somewhere. Could add a section "Onboarding and Ramp‑up" but that's not in the list; risk of being considered not allowed. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not an exhaustive list. So we could add other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So maybe we can incorporate the First 90 days into Responsibilities as a subsection? But we cannot have subheadings unless we use
again; but we could just add a paragraph. Thus we can add a paragraph after the Responsibilities list about the first 90 days. Similarly, "Our Values" could be omitted or added as a section; but it's not required; we can drop as it's somewhat boilerplate but still substantive. However it's values statement; could be considered boilerplate but not exactly legal/EEO. Might be safe to omit. We must remove EEO statement. Now Benefits: "You will be eligible for employee equity as well as discretionary bonus compensation, subject to plans that may be in effect from time to time. You will further be eligible to participate in Unanet’s employee benefits plans and programs. For more details on Unanet’s benefits offerings, please visit https://unanet.com/employee-benefits." We need to keep that. Pay: "The salary range for this opportunity is $98,600 - $118,735 per year." Now we need to ensure we don't repeat job title as heading. Now produce HTML. Structure:
About the role
...
What Success Looks Like
...
Responsibilities
- Lead implementation and integrated solutions on time and within budget ...
In your first 90 days, you will complete onboarding and build relationships across our Professional Services and other cross-functional teams. You’ll learn Unanet’s GovCon solutions, customer journey, delivery standards, and business led consulting methodology. You’ll also shadow customer discovery sessions, workshops, and delivery reviews. By day 60, you’ll own defined portions of customer engagements, including preparation, facilitation, follow-up, and documentation. You’ll apply outcome-led discovery and help connect customer goals to processes, capabilities, data, and measures. You’ll have begun managing competing priorities across multiple active customer projects. By day 90, you’ll be independently leading assigned customer workstreams or consultant-led engagements. You’ll demonstrate effective risk management, customer communication, business-forward recommendations, and adoption support. You’ll provide actionable feedback to improve methodology, playbooks, and delivery practices.
Requirements
- 5+ years of experience in business consulting, professional services, software implementation, or a related field ...
Skills
- Experience with Unanet GovCon ERP, GovCon CRM, GovIntel, ProposalAI, OpportuneAI, or related GovCon technologies ...
Benefits
You will be eligible for employee equity as well as discretionary bonus compensation, subject to plans that may be in effect from time to time. You will further be eligible to participate in Unanet’s employee benefits plans and programs. For more details on Unanet’s benefits offerings, please visit https://unanet.com/employee-benefits.
Pay
The salary range for this opportunity is $98,600 - $118,735 per year.
Check we didn't miss any substantive info: The "What Success Looks Like" paragraph we kept. The "What You’ll Do" list we kept. The "