Contract & Billing Operations Specialist

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: Recruitment Disclaimer etc. Also remove navigation/legal/EEO etc. The posting includes sections: About Teletask (company description), What You'll Actually Do (responsibilities), Required Qualifications, Preferred Qualifications, What Success Looks Like In The First 90 Days, Who You'll Work With, What We Offer (benefits). Also maybe "About Teletask" is company description; could be "About the role"? But we can use headings: About the role (maybe combine About Teletask and role description). However we must follow instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. We have: - About the role: could include About Teletask and description of role purpose. We'll put a paragraph summarizing. - Responsibilities: from "What You'll Actually Do" bullet points. - Requirements: maybe combine Required Qualifications and Preferred Qualifications? But we have separate headings: Requirements, Qualifications, Skills. Could split: Requirements = Required Qualifications; Qualifications = Preferred Qualifications; Skills = maybe list of skills like analytical, attention to detail, communication, Excel, etc. But we can also put skills under Qualifications. However we need to avoid thin sections. Let's think: we have Required Qualifications (list), Preferred Qualifications (list). Could combine into Qualifications section with subheadings? But we only allowed

headings, not nested. Could make two sections: Requirements (Required Qualifications) and Qualifications (Preferred Qualifications). Skills maybe not needed separately if covered. We also have "What Success Looks Like In The First 90 Days" could be a section maybe "Goals" but not in list; we could treat as part of Responsibilities or maybe a separate section like "Expectations". But instruction says prefer few substantive sections over many thin ones. Could incorporate that into Responsibilities or a separate "Performance Expectations". Might be okay to add a section "First 90 Days Goals". But not in the given list; but we can still use

for any section heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we should stick to those headings. So we can map "What Success Looks Like In The First 90 Days" to maybe "Responsibilities" or "Expectations". Could add a subsection under Responsibilities but we can't have nested headings. Could just include as part of Responsibilities paragraph. "Who You'll Work With" could be part of About the role or maybe omitted as thin. Could incorporate into About the role. "What We Offer" corresponds to Benefits. We have no explicit Pay or Schedule info, so we should not create those sections. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities, Requirements, Qualifications, Benefits we need lists. We must preserve all substantive information, not invent or summarize away detail. Must not omit details like specific tools (SAP Ariba, Proactis), SOC 2 reports, W-9s, etc. Must keep all. We need to avoid boilerplate: Recruitment Disclaimer, etc. Also remove duplicated lines. Let's extract content. About Teletask: "Teletask powers public sector communication. Government and public health agencies use our automated text, voice, and email outreach to reach the families they serve. Our largest footprint is WIC (Women, Infants & Children) nutrition programs, where Teletask messaging drives appointment attendance for over 6 million participants across 35+ US states. Teletask is at an inflection point, and we are building operational infrastructure to match the product." Role purpose: "Teletask is now looking for a Contract & Billing Operations Specialist to act as the operational engine for our revenue cycle. In this role, you will oversee the critical quote-to-cash process, ensure that deals are legally compliant, and successfully submitted through procurement portals." We can combine into About the role paragraph. Responsibilities (What You'll Actually Do): bullet points: - Manage Bids & Procurement Portals - Execute Bid Submissions: Submit proposals and bids via enterprise and government e-procurement portals (like SAP Ariba and Proactis). - Package Compliance Docs: Ensure every submission is accurate and complete by attaching all required vendor and compliance documentation, including SOC 2 reports, W-9s, and sole-source justifications. - Navigate Legal & Compliance - Broker Insurance & Terms: Coordinate with insurance brokers to secure Certificates of Insurance (COIs) and collaborate with internal stakeholders to review statutory-language edits during contract negotiations. - Maintain the System of Record: Keep our compliance repositories organized by accurately saving executed BAAs, HIPAA documents, and government addendums directly into our financial system. - Enable the Sales-to-Delivery Handoff - Validate the Deal: Serve as the vital bridge between a signed contract and client success. You will promptly reconcile inbound Purchase Orders (POs) against finalized agreements. - Give the Green Light: Act as the final gatekeeper for order fulfillment, providing the official authorization to the Sales team to initiate the customer onboarding ticket once all financial requirements are met. We need to preserve all details. Could break into list items each representing a duty. Could combine sub-bullets but we only have
  • . Could embed semicolons inside li. We'll create
    with each major duty as
    • . Inside each li we can have sentences. Responsibilities list: - Execute bid submissions via enterprise and government e-procurement portals (such as SAP Ariba and Proactis). - Package compliance documentation for submissions, ensuring accuracy and completeness by attaching required vendor and compliance documents including SOC 2 reports, W-9s, and sole-source justifications. - Coordinate with insurance brokers to secure Certificates of Insurance (COIs) and collaborate with internal stakeholders to review statutory-language edits during contract negotiations. - Maintain compliance repositories by accurately saving executed BAAs, HIPAA documents, and government addendums into the financial system. - Validate deals by reconciling inbound Purchase Orders (POs) against finalized agreements. - Provide final gatekeeper authorization for order fulfillment, enabling the Sales team to initiate customer onboarding tickets once all financial requirements are met. That covers. Requirements (Required Qualifications): list: - 3 - 5 years in Revenue Operations, Deal Desk, Sales Finance, or Contract Administration, ideally in a B2B SaaS or technology environment - Strong analytical skills: ability to audit platform utilization data, calculate billing overages, and reconcile an account without a template - Sharp attention to detail: catches missing signature page before it costs a bid - Comfortable operating as connective tissue between Sales, Finance, Legal, and Implementation - At least 1 year of experience directly handling government contracts - Deep understanding of government procurement processes, regulations, and compliance requirements - Experience navigating government contract management systems, portals, and reporting requirements - Excellent problem-solving skills to navigate unique challenges and requirements of government contracts - Strong verbal and written communication skills - Proficient in Microsoft Office Suite, particularly Excel (utilizing pivot tables and VLOOKUPs) We'll put each as
    • . Qualifications (Preferred Qualifications): list: - Experience with Zoho Books, Zoho CRM, or similar mid-market platforms preferred - Public sector or public health contracting exposure (cooperative purchasing vehicles, state term contracts, or WIC programs) is an asset - Experience building or documenting a quote-to-cash process - Hands-on experience executing formal vendor bids through enterprise or government e-procurement platforms (SAP Ariba, Proactis, or similar) - Working fluency with SOC 2, HIPAA, and BAAs, plus confidence to review statutory contract language We'll list. Benefits (What We Offer): list: - Ownership of the revenue cycle end to end: bids, compliance, contracts, and renewal billing in one seat rather than split across four - Chance to build process in a business where operational machinery, not product, is the growth constraint - Entrepreneurial, fully remote environment with high visibility and autonomy - Exposure to the Solen Software Group portfolio company network and operating model We should not include recruitment disclaimer. We also might include "Who You'll Work With" but could be omitted as thin. Could incorporate into About the role: "You will report to Teletask's executive leadership team and sit at the center of the revenue cycle. A given day might mean a submission in the morning, a statutory-language edit at noon, and a validate deal implementation in the afternoon. The team is small by design, so the process you build becomes the way Teletask operates." That's substantive; we can add to About the role paragraph. Thus About the role paragraph will include company description, role purpose, reporting line, day-to-day variety, team small. Now ensure we don't repeat job title as heading. We'll not. Now produce HTML fragment: start with maybe but not required. Just output headings and content. We'll output:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      ...

      Qualifications

      ...

      Benefits

      ...
      Make sure no extra text. Check for any boilerplate: we removed Recruitment Disclaimer, etc. Check for any duplicated lines: we haven't duplicated. Check for any placeholders like "commensurate with experience": none. Now craft the paragraphs precisely preserving details. About the role paragraph: "Teletask powers public sector communication; government and public health agencies use its automated text, voice, and email outreach to reach the families they serve, with its largest footprint in WIC (Women, Infants & Children) nutrition programs driving appointment attendance for over 6 million participants across 35+ US states. The company is at an inflection point, building operational infrastructure to match its product. Teletask is seeking a Contract & Billing Operations Specialist to act as the operational engine for its revenue cycle, overseeing the quote-to-cash process, ensuring deals are legally compliant, and submitting them through procurement portals. The role reports to Teletask's executive leadership team and sits at the center of the revenue cycle; a typical day might involve a morning bid submission, a noon statutory‑language edit, and an afternoon deal validation. The team is small by design, so the processes you build will become the way Teletask operates." That seems good. Now Responsibilities list items as above. Make sure to include all details: SAP Ariba, Proactis, SOC 2 reports, W-9s, sole-source justifications, Certificates of Insurance (COIs), BAAs, HIPAA documents, government addendums, financial system, Purchase Orders (POs), finalized agreements, Sales team, customer onboarding ticket, financial requirements. Let's craft each li: - Execute bid submissions via enterprise and government e‑procurement portals such as SAP Ariba and Proactis. - Package compliance documentation for submissions, ensuring accuracy and completeness by attaching required vendor and compliance documents including SOC 2 reports, W‑9s, and sole‑source justifications. - Coordinate with insurance brokers to secure Certificates of Insurance (COIs) and collaborate with internal stakeholders to review statutory‑language edits during contract negotiations