Jobs · Business Development · Arizona

Strategic Partnerships Manager: Digital Marketing Agency/Influencer Partners

Intuit · Tucson, AZ · 1 mo ago
On-siteBusiness Development$190k–$256k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes Overview, Responsibilities, Qualifications, maybe Benefits/Pay/Schedule. The instructions: 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. 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. We have content: Overview (maybe "About the role") includes description of role. Then Responsibilities (with sub-bullets). Then Qualifications (Required and Preferred). Then Pay info: "Intuit provides a competitive compensation package with a strong pay for performance rewards approach. This position may be eligible for a cash bonus, equity rewards and benefits, in accordance with our applicable plans and programs (see more about our compensation and benefits at Intuit®: Careers | Benefits). Pay offered is based on factors such as job-related knowledge, skills, experience, and work location. To drive ongoing fair pay for employees, Intuit conducts regular comparisons across categories of ethnicity and gender. The Expected Base Pay Range For This Position Is New York $189,500 - $256,000 Mountain View, CA $186,500- $252,500" Thus we have Pay info. Benefits? Not explicit beyond generic mention of benefits. Could include Benefits section? The posting mentions "benefits" generically but not specifics. The instruction: never create Benefits sections unless posting actually states them. It says "Intuit provides a competitive compensation package with a strong pay for performance rewards approach. This position may be eligible for a cash bonus, equity rewards and benefits, in accordance with our applicable plans and programs". That's a mention of benefits but not specifics. Might be considered filler? It says "benefits" but not specific. I'd treat that as not enough to create a Benefits section; we can include Pay section (since we have specific ranges). Schedule not mentioned, so omit. We need sections: About the role (Overview), Responsibilities, Qualifications, Pay. Possibly also Skills? Not separate; qualifications cover skills. Could combine Required and Preferred under Qualifications with subheadings? But we only allowed

    for section headings; we could have

    Qualifications

    and then inside we can have

    for prose and

    • for lists. We could separate Required and Preferred as
        with maybe headings inside? Not allowed to create extra headings? Could use inside
      • . Probably fine. We need to preserve all substantive information. Let's extract Overview text: "Overview As Strategic Partnerships Manager: Analyst and Agency Partners, you own Intuit's commercial relationships with two distinct partner segments that sit at the edges of the mid-market ERP ecosystem: independent ERP analysts, and digital marketing agencies whose client base includes mid-market businesses evaluating ERP solutions. ERP analysts in the mid-market are not the large research firms — they are independent voices: channel consultants, software selection advisors, and influential commentators who cover mid-market ERP platforms, shape buyer decisions, and maintain active networks of prospects and VARs. They generate a steady flow of referral introductions to buyers who trust their judgment. Building relationships with the right analysts and turning those relationships into a consistent pipeline of qualified warm introductions is the core of this motion. Digital marketing agencies represent a different but equally valuable opportunity. Many agencies serve mid-market clients who need ERP solutions as part of broader digital transformation work — and those agencies need somewhere to route those leads. This role builds the program and relationships that make Intuit the natural destination for those introductions. Both motions share the same KPI: qualified warm introductions attributable to a specific analyst or agency partner. You are not accountable for closed-won revenue — you are accountable for the quality and volume of the pipeline you generate through these relationships. PRIMARY KPI: Qualified warm introductions attributable to a specific analyst or agency partner — defined as a mid-market prospect introduction where an IES, QuickBooks Advanced, or Intuit Services opportunity has been identified. Measured separately for analyst and agency segments." We need to keep all that. We'll put in

        maybe multiple paragraphs. Responsibilities: There are bullet-like paragraphs under "ERP analyst relationships", "Digital marketing agency relationships", "Portfolio management & reporting", "Cross-functional collaboration". Each has multiple sentences. We'll convert each bullet to

      • maybe grouping under
          . Could also keep as paragraphs but instruction: Use
          • for any list of duties/requirements/benefits. So we should treat each duty as list item. Thus under Responsibilities

            Responsibilities

            then
              with
            • for each major duty. We need to capture all details inside each duty. Let's list duties: ERP analyst relationships: - Identify and map the independent ERP analyst community relevant to Intuit's mid-market segment: channel consultants, software selection advisors, VAR-channel commentators, and influential voices whose audiences include mid-market ERP buyers and channel partners. - Build and maintain active relationships with target analysts, positioning Intuit Enterprise Suite and QuickBooks Advanced as platforms worth recommending — keeping analysts current on product direction, competitive positioning, and the partner program. - Drive a consistent cadence of introductions from analyst relationships: warm referrals from analysts to mid-market prospects actively evaluating or replacing ERP platforms. - Provide analysts with the product knowledge, competitive context, and reference materials they need to credibly recommend Intuit's mid-market platform to their audiences and clients. - Track analyst-sourced introductions through the attribution model, ensuring each qualified referral is tagged to the originating analyst and reflected in pipeline reporting. Digital marketing agency relationships: - Identify and recruit digital marketing agencies whose client base includes mid-market businesses with ERP needs — prioritizing agencies with active practices in verticals where IES has strong product-market fit. - Build the agency partner engagement model: define the value proposition for agency partners, develop the referral process and attribution mechanism, and create the co-marketing and lead-routing infrastructure that makes it easy for agencies to send leads to Intuit. - Enable agency partners on Intuit's mid-market product lineup and lead qualification criteria — ensuring that introductions from agencies meet the quality threshold for IES sales engagement. - Drive ongoing engagement with active agency partners: regular pipeline reviews, co-marketing activity, and program performance conversations. - Track agency-sourced introductions through the same attribution model as the analyst segment. Portfolio management & reporting: - Maintain an active and prioritized portfolio of analyst and agency partners, with clear visibility into relationship health, referral activity, and pipeline contribution per partner. - Identify underperforming relationships and develop targeted activation plans — additional enablement, co-marketing investment, or relationship reset as appropriate. - Report regularly on analyst and agency pipeline contribution to Felicia Wilson and the broader Commercial Partnerships leadership. - Surface market intelligence from analyst and agency conversations — buyer sentiment, competitive dynamics, and segment trends — to the IES product and go-to-market teams. Cross-functional collaboration: - Collaborate with the ISV Partner Manager and other Commercial BD colleagues to identify where analyst or agency relationships intersect with or amplify other partner motions. - Work with marketing to develop analyst-specific content programs, agency co-marketing campaigns, and thought leadership materials that strengthen Intuit's position in the mid-market ERP ecosystem. - Engage with the IES product team to keep analyst partners current on roadmap direction and ensure that Intuit's product story is compelling and accurate in analyst-generated content and recommendations. Qualifications Required: - 10+ years of experience in channel partnerships, business development, or partner management within a SaaS or enterprise software company. - Familiarity with the mid-market ERP analyst and channel consultant community — you know who the influential voices are, how they operate, and what motivates them to refer business. - Demonstrated experience building commercial partner relationships and driving referral pipeline through those relationships. - Strong communication and relationship-building skills: able to engage credibly with independent analysts and digital agency principals, and to maintain productive long-term relationships with minimal formal program infrastructure. - Experience managing a partner portfolio with clear pipeline tracking and attribution discipline. - Proficiency with CRM tools (Salesforce preferred) and standard sales and partnership productivity platforms. Preferred: - Direct experience working with mid-market ERP channel analysts, software selection consultants, or VAR-channel commentators — you have existing relationships in this community. - Experience building agency partner programs, including referral process design, lead qualification frameworks, and co-marketing infrastructure. - Familiarity with Intuit Enterprise Suite, QuickBooks Advanced, or competing mid-market ERP platforms (Sage Intacct, Acumatica, NetSuite, Microsoft Dynamics). Pay: - Intuit provides a competitive compensation package with a strong pay for performance rewards approach. This position may be eligible for a cash bonus, equity rewards and benefits, in accordance with our applicable plans and programs (see more about our compensation and benefits at Intuit®: Careers | Benefits). - Pay offered is based on factors such as job-related knowledge, skills, experience, and work location. - To drive ongoing fair pay for employees, Intuit conducts regular comparisons across categories of ethnicity and gender. - The Expected Base Pay Range For This Position Is New York $189,500 - $256,000 Mountain View, CA $186,500- $252,500 We need to output HTML fragment only. We'll structure:

              About the role

              Overview text...

              Responsibilities

              • ...
              • ...

              Qualifications

              • Required:
              • maybe we need to separate? Could have nested list? Simpler: we can have two
                  inside? But instruction: Use
                  • for any list of duties/requirements/benefits. So we can have separate lists for Required and Preferred. Could do

                    Required

                    but that's not allowed? Only

                    for section headings. Could use inside
                  • to denote Required and Preferred. Or we could have two sections: Qualifications (Required) and Preferred Qualifications? But they said prefer few substantive sections over many thin ones. So maybe combine Required and Preferred into one list with markers. But we need to preserve all info; we can include headings inside
                  • using . That should be fine. Thus:

                    Qualifications

                    • Required:
                    • 10+ years of experience in channel partnerships, business development, or partner management within a SaaS or enterprise software company.
                    • ...
                    • Preferred:
                    • Direct experience working with mid-market ERP channel analysts, software selection consultants, or VAR-channel commentators — you have existing relationships in this community.
                    • ...
                    But having a
                  • with just a strong heading might be odd but acceptable. Alternatively we could make two separate
                      each preceded by a

                      Required:

                      but that adds extra tags. Probably okay. Simplify: Use

                      Qualifications

                      then

                      Required:

                      then
                        list required items, then

                        Preferred:

                        then
                          list preferred items. That uses

                          for prose (the headings) and

Similar jobs