Questions, answered.

Aurgus is calculation-native infrastructure for enterprise channel rebate programs. We model the math under your rebate program — every accrual, adjustment, supersession, and settlement — on an append-only event log that is audit-defensible by construction. Your ERP posts the journal entries per its own configuration.

Channel-finance and operations leaders — CFOs, Controllers, SVPs of Sales Operations, Channel Finance Heads — at $1B+ B2B technology companies running channel rebate programs on Vistex, Model N, SAP IRM, IBM CDM, or other incumbent platforms. In-scope verticals: enterprise software, semiconductor, networking, storage, electronic components, manufacturing.

Sub-$500M revenue businesses; pharmaceutical rebate programs (Medicaid Drug Rebate regime); retail trade-spend; food and beverage CPG; consumer-goods promotional. Different operational shapes; specialized vendors serve those better.

Monosij Bagchi — Founder and Subject Matter Expert. Twenty-plus years across SAP, Vistex, and rebate operations at Fortune 500 distributors and manufacturers. See /about for the practitioner-corpus articulation.

Platform fee keyed to your annual rebate volume managed. Five-tier structure. No per-seat, FUE, per-agreement, per-module, perpetual-license, or per-row pricing. See /pricing for the full methodology and tier breakdown.

The methodology is open; the specific engagement number is established in conversation. The same rebate program at $50M annual volume vs $500M annual volume is a different engagement. Posting a single price would over-charge the smaller customer and under-deliver to the larger.

Not in the traditional sense. You can try the product using sample data or your own POS CSV — that's the no-friction exploration path. Enterprise engagement begins with a discovery conversation, not a self-serve signup.

Annual contract structured around engagement scope. Onboarding, parallel-run against incumbent, cutover, ongoing operational support — all in scope. We don't sell services attached to the platform fee.

Yes. Currently engaging the design-partner cohort — Tier 5 equivalent with reference rights, co-roadmap input, and parallel-run guarantee. Speak with an Expert to learn whether the cohort is still open.

Every accrual, adjustment, reversal, and settlement is an immutable event with full calculation lineage. Corrections happen by supersession — a new event replaces the old — never overwrite. Quarter-end reproducibility is a property of the data model, not of process discipline.

Aurgus computes rebate math. Your ERP (SAP, Oracle, NetSuite, Microsoft Dynamics) posts journal entries per its own configuration. We push shell settlement documents — customer, material, condition type, amount, period — and your ERP determines the GL posting. No double-modeling of journal entries, no integration gymnastics.

Six canonical bucket patterns in v1: volume flat, volume tiered (linear and retroactive), growth incentive, SPIF per unit, MDF (Market Development Funds), cooperative marketing. Pattern coverage expands based on design-partner requirements.

CSV import/export universally. Direct integration with SAP S/4HANA, SAP ECC, Oracle Fusion, NetSuite, Microsoft Dynamics 365 — delivered as part of the engagement scope. We don't ask you to migrate ERPs.

Yes — REST API available within the engagement scope. SDK and webhook patterns for high-volume integration patterns. Documentation is engagement-gated, not public.

No. Aurgus's revenue is the platform fee. We never train models on customer data, never resell anonymized aggregates, never build benchmarking products downstream. The trust commitment is structural to how the company is funded.

Yes. Per-tenant database isolation. Enterprise tier adds per-tenant data planes with customer-managed encryption keys. See the Privacy Policy for the full data-handling commitments.

US-region cloud infrastructure (Fly.io and select partner regions). Enterprise tier supports specific geographic restrictions as part of engagement scope.

SOC 2 Type 2 attestation is in progress, available at Enterprise tier and above. ASC 606 variable-consideration alignment is a design property of the platform, not a compliance checkbox.

Engagement includes parallel-run against your incumbent through the full cutover period. We model your existing condition records and pricing procedures into Aurgus primitives, run both systems in parallel, validate output for parity, then cutover when calculation accuracy is verified.

Typically 90 days for the parallel-run + cutover cycle. Specific timeline depends on program complexity and integration scope, established at engagement.

Founder-led discovery. Named onboarding lead. Technical account manager at Tier 4 and above. Customer-direct support — we don't sell through resellers or services partners.

Yes — at design-partner phase, every engagement has founder involvement in discovery and architecture-fit assessment. As the company scales, the founder remains involved in Tier 4 and Tier 5 (Strategic) engagements.