Maxima lists four ERPs on its integrations page (NetSuite, Microsoft Dynamics 365, SAP and Sage Intacct), and its new demand generation lead must build the engine "for an enterprise buyer rather than tuned for a mid-market one". Yet all 11 ERP-specific URLs in the sitemap are about NetSuite, the integrations FAQ only answers the NetSuite question, and nothing on the site speaks to a controller running SAP, the ERP most large enterprises use. An SAP controller searching "SAP account reconciliation automation" finds no Maxima page; a NetSuite controller finds eleven.
First action
List the SAP and Dynamics 365 customers or pilots that can be cited, even anonymously.
How to measure it
Share of demo requests from SAP, Dynamics and Intacct users
- Now
- –
- Target
- 25%
- By
- 2 quarters
Steps
Confirm coverage
Exactly what Maxima reads from and posts to each ERP today, signed off by engineering.
Forward Deployment Strategist 3 days
Write the SAP page
Workflows, approvals, audit trail and deployment timeline, in SAP terms.
Product Marketing 1 week
Add FAQ answers
One answer per ERP on /integrations.
Product Marketing 1 day
Extend the Answers Hub
Three questions per ERP, same format as the NetSuite pages.
Content Marketing 2 weeks
Add an ERP field
On the demo form, routed to a strategist who knows that ERP.
Enterprise Demand Generation Lead 2 days
Point ABM at it
Use each page as the landing page for accounts on that ERP.
Enterprise Demand Generation Lead 2 weeks
Measure
Demos and pipeline by ERP every month.
Enterprise Demand Generation Lead monthly
Why it works
Build one page per supported ERP beyond NetSuite (SAP first, then Dynamics 365 and Sage Intacct): what Maxima reads and posts back, which workflows run on day one, the approval and audit-trail story in that ERP's terms, and a deployment timeline. Add the matching FAQ entries to /integrations, three Answers Hub questions per ERP in the same format that already works for NetSuite, and an ERP field on the demo form so SAP leads reach a strategist who knows SAP. Use the pages as the landing pages for the first enterprise ABM list.
Enterprise buyers qualify vendors by their ERP first. A page that names their system, in their vocabulary, tells them Maxima has done this before, and it gives the ABM program a page that matches the account.
Ready to use
ChecklistERP page outline
[ ] What Maxima reads from <ERP> (GL, subledgers, reports) [ ] What it posts back, and who approves [ ] Five workflows that run on day one [ ] Audit trail in <ERP> terms [ ] Deployment timeline in weeks [ ] Customer proof (named or anonymous) [ ] FAQ entry on /integrations [ ] Three Answers Hub questions [ ] Demo form ERP field and routing
Risks and how to handle them
Overstating SAP depth
Describe only what is live; mark anything else as roadmap.
Thin pages
Each page needs a workflow walk-through and a deployment timeline, not just a logo.
Evidence
- Your websiteIntegrations page: the ERPs listed are NetSuite, Microsoft Dynamics 365 ("while Business Central remains your system of record"), SAP ("Access ERP transactions to prepare journal entries, reconciliations, and close workflows") and Sage Intacct; Workday appears only as Workday Payroll and Oracle is not listed. The page FAQ answers "Does Maxima integrate natively with NetSuite?" and no other ERP question.Source
- Your websiteSitemap (196 URLs, checked October 23, 2026): 79 Answers Hub pages and 71 articles. 11 URLs name NetSuite (for example "netsuite-close-automation-a-complete-guide-2026", "netsuite-account-reconciliation", "how-do-you-replace-netsuite-allocation-scripts-with-ai"); none name SAP, Dynamics, Intacct, Oracle or Workday. Comparison content already covers FloQast, BlackLine, Numeric and Ledge (for example /maxima-vs-floqast, "blackline-vs-maxima-ai-native-vs-bolted-on", "numeric-alternatives"). There is no pricing page, calculator, or page by role or industry. Articles include "Why the Best AI Model Still Scores 56 on Accounting" and "AI and SOX Compliance: The Hidden Risk of Shadow Preparation".Source
- HiringEnterprise Demand Generation Lead (San Mateo, posted September 25, 2026): "build the system that turns demand into repeatable pipeline"; "Capture the demand that already exists for financial close and accounting automation" and "create demand for a category they don't yet have a name for: agentic accounting"; "As our deals move toward six-figure contracts, the engine has to be built for an enterprise buyer rather than tuned for a mid-market one." The audience is "controllers and senior accounting leaders at mid-market and enterprise companies. They're pressed for time, allergic to hype". The role owns ABM for "the full buying group", integrated campaigns, lifecycle and nurture, and a marketing-sourced pipeline target, measured on "best-fit customer profile impressions, best-fit customer profile visitors, and best-fit customer profile pipeline", working with Product Marketing, Brand, Content, Corporate Marketing and Customer Marketing; HubSpot and Clay are named.Source
- HiringForward Deployment Strategists in San Mateo, Toronto and Bangalore (the India post is dated September 27, 2026): "Deployment is where Maxima proves itself"; they "Support pre-sales scoping and discovery", "Create standardized frameworks, tools, and templates for deploying Maxima across customers and industries", and need "Strong understanding of financial systems such as NetSuite, SAP, Oracle, or Workday". Success "looks like faster deployments, stronger adoption, and field insight turned into repeatable playbooks."Source
- HiringMaxima's description in every job post: it has "raised $41M from Redpoint Ventures, Kleiner Perkins and Audacious Ventures, joined by former BlackLine executives and the CFOs of Rubrik and Vanta", and "processed more than $400B across 350M transactions at 100.00% accuracy, for customers including Scale AI, Rippling, Glean, Zendesk, Handshake, Zip, and Decagon." Of 17 open roles, 14 are in engineering and product.Source