IT, Security, & Integrations FAQ

Spiro is a subscription SaaS product licensed per user per year. The base license includes ERP synchronization, AI insights, reporting, mobile access, and core platform functionality. Optional modules such as calling and texting, Notetaker, quoting, support tickets, marketing insights, and territory management are licensed separately. Implementation and setup services are scoped independently based on complexity.

‍

Yes. Spiro supports multiple license types, including Full, Read Only, and Email Sync only. Email Sync licenses are commonly used to capture emails and related activity from users who do not need full CRM access but whose interactions should be reflected in customer records.

‍

Spiro provides standard connectors for common manufacturing and distribution ERPs, including Epicor Eclipse, SAP, NetSuite, Infor, Microsoft Dynamics, and Profit21. The ERP remains the system of record at all times. Spiro aligns to the customer’s ERP data model and business rules, ingests and normalizes that data, and controls what information is exposed to end users.

Real-time synchronization is used when ERP APIs or triggers are available. When they are not, Spiro uses scheduled batch synchronization, typically nightly. In both cases, the ERP remains authoritative and Spiro reflects the current operational state.

API-based integration is the default approach when supported by the ERP. When APIs or triggers are unavailable, Spiro uses automated, programmatic exports. Both methods are fully automated and require no manual intervention.

For changes such as salesperson reassignment or address updates, Spiro updates master records on each sync to match the current ERP state. Historical versions are not retained, but all changes are recorded in an audit trail.

For open orders, invoices, or other records that may change mid-period, Spiro refreshes the current state on each synchronization. Data is not treated as final until finalized in the ERP. Changes are tracked via audit history rather than versioned records.

Spiro can ingest kits exactly as modeled in the ERP, including parent and component structures. Optionally, Spiro can present a flattened view to users while preserving the ERP structure as the system of record.

Work orders are typically not synchronized, as sales teams usually rely on sales order status rather than internal fulfillment detail. If required, Spiro can integrate work order data when it is available through ERP tables, APIs, or exports.

Migration is delivered as a fixed-price engagement using a jointly defined project plan. Detailed scope, timelines, and responsibilities are finalized during evaluation or onboarding once requirements and data sources are fully understood.

Spiro provides a two-way integration with HubSpot, Mailchimp and Constant Contact to sync contacts and marketing activities into Spiro. This integration is available with the Marketing Insights module.

Spiro has a native integration with Microsoft 365. Users can authorize access individually via OAuth, or administrators can grant organization-wide permission. Email and calendar activity capture is included at no additional cost.

‍

Customer Success is included with the subscription. Each customer is assigned a named, US-based Customer Success Manager following Full Service Setup. Engagement cadence typically starts with biweekly meetings during early adoption, moves to monthly check-ins during the first year, and transitions to quarterly strategic reviews once established. Technical support is available via email. Customers also have access to a self-service Help Center, live training sessions, and monthly product update webinars.

Spiro follows an agile development process with releases every six to eight weeks. Releases are automatic, non-breaking, and require no customer action. Each release typically includes approximately one hundred enhancements and fixes, many driven directly by customer feedback. All changes undergo QA and regression testing prior to release. Customers are notified through release notes and release webinars.

Yes. Spiro is SOC 2 Type II compliant.

Yes. Spiro maintains documented disaster recovery and business continuity plans, available upon request. The platform runs on Heroku and AWS with built-in redundancy, continuous monitoring, and automated recovery. Databases support point-in-time recovery, and daily backups are performed. These controls are reviewed as part of SOC 2 Type II audits.

Data and configuration backups are included as part of Spiro’s disaster recovery and business continuity practices. Databases are continuously protected with daily backups, and application configuration and system images can be redeployed automatically.

Yes. Spiro supports Microsoft single sign-on using OAuth-based authentication, allowing customers to enforce their existing MFA and identity policies.

The Spiro mobile app is distributed through the Apple App Store and Google Play Store and supports enterprise deployment and control through standard mobile device management tools.

Spiro tracks business activity such as emails, meetings, calls, notes, and record updates. It does not track low-level UI telemetry like page views. Platform performance and availability are monitored at both the infrastructure and application layers.

‍