How we get started — Run, Learn, Compress
Allari onboards customers under a single operating model: Run, Learn, Compress. We take operational custody of the ERP support layer (Run), record every ticket, hour, and decision in OpenBook® (Learn), and engineer the recurring failures out of the queue so the support run-rate trends down each month (Compress). This page mirrors the printable Customer Onboarding Guide and describes the engagement model, the budget guardrail, and the kickoff checklist a new customer works through with us.
Download the printable Customer Onboarding Guide (PDF).
Three phases, one controlled path
- 01 Ready — sponsor, scope, named owners, and a not-to-exceed budget guardrail confirmed in writing. Nothing technical begins until alignment is documented.
- 02 Align — security, Teams/O365, ticketing, and remote access coordinated with your security owner. Roles, MFA, and minimum access provisioned together.
- 03 Run — work begins inside the shared workspace, against the approved guardrail, with visible work notes and the agreed governance cadence.
Four decisions to confirm before kickoff
- Customer sponsor — named sponsor, day-to-day operational owner, and access owner.
- First outcomes — backlog reduction, ERP support coverage, stabilization, reporting, integrations, automation, project capacity, or adjacent-stack support.
- Budget guardrail — not-to-exceed amount, written approval owner, and review cadence.
- Access path — Teams and O365 workspace, remote access method, ERP systems, adjacent-stack documentation, and security owner.
Permission before overrun — the budget guardrail
Allari operates against a customer-approved, not-to-exceed amount. If projected work approaches the limit, we surface status and request written permission from the named approver before continuing. Spend, remaining budget, and forecast are reviewed on the agreed cadence in OpenBook®. No quiet drift, no surprise overrun — the customer sees current spend, projected work, and the decision required.
Collaboration and access
We work inside Microsoft Teams and Office 365 with a security owner you nominate. The customer confirms the remote connection method (VPN, VDI, PAM, or another approved tool); Allari uses named accounts and the minimum access needed to begin safely.
How work moves and stays visible
Every request follows the same path — Request → Triage → Execute → Close — with the customer-visible state and the recorded operating knowledge at each stage. Living documentation accrues in the dynamic runbook; OpenBook® governance reviews run on a regular rhythm.
Ready to start — kickoff checklist
Business and governance: sponsor, day-to-day contact, security/access approver, meeting cadence and escalation path, not-to-exceed budget and approval owner. Access and systems: Teams/O365 owner, approved remote access method, named accounts with MFA and ERP roles, ticketing and documentation access, restricted/regulated data rules.
Engagement structure
Most ERP contracts protect the vendor. Ours is structured so the math has to work for you first. Three-year term, annual recalibration against actual workload, ninety-day exit clause with no penalty, renewal earned not assumed. The standard ERP support contract — fixed-fee, five-year auto-renew, decoupled from the customer’s actual workload — is structured to protect the vendor. Year four isn’t guaranteed. It’s earned by the prior three.
Book a working session — getstarted@allari.com · 866.937.2224. Or use the contact form at /contact.