The honest answers to the eight objections we hear most before a prospect signs with Aivid — cost, timeline, data, integrations, and what happens day one.
Aivid runs on three transparent monthly tiers — Starter at $2,500/mo (one audit agent, a single business process mapped end to end), Growth at $10,000/mo (up to three agents, daily digest, integration with two core systems), and Enterprise at $25,000+/mo (multi-agent fleet, custom integrations, dedicated ops lead).
The full breakdown lives on our pricing page. The free audit at /ai-audit is the on-ramp — it costs you nothing and tells you which tier fits before you sign anything.
Two to four weeks from the kickoff call to a live, deployed agent running daily.
Week one is kickoff and data access — we get read-only credentials to the source systems and confirm the first process to map. Week two is build — the agent goes live with its first process registered and a daily digest running. Weeks three and four are tuning: accuracy checks, edge cases, and the roadmap for the second agent.
The agent runs on Render with a Neon Postgres database, with infrastructure defined in render.yaml at the repo root. Every row is tenant-scoped by company_id — there is no shared pool between customers.
We never train on your data. Credentials are stored encrypted at the platform layer (managed secrets, not in source). All access is over TLS; access logs are auditable on request.
Yes. The integration layer speaks REST, SQL, and file drops (CSV/SFTP), which covers the vast majority of ERP/WMS/TMS stacks in use today — NetSuite, SAP, Oracle, Manhattan, Blue Yonder, and the long tail of mid-market systems.
On the audit call we confirm your specific stack. If a connector is missing, we build it as part of onboarding — engineering time is included in the Growth and Enterprise tiers.
The agent runs a digest job on a cron schedule (declared in polsia.toml), watches every process registered in the processes table, and writes a scored audit_results row for each one — on a 0–100 automation opportunity score.
It also writes a digest_reports row per cycle, which surfaces on the /app dashboard so you see what changed since yesterday. There's no console to babysit — the dashboard is the front end.
Two people, part-time.
One executive sponsor (you, or a head of ops) for the kickoff call and weekly check-ins. One ops lead for process Q&A — the person who actually knows how the work gets done today. Engineering only gets pulled in if we need custom integrations beyond REST/SQL/file drops.
A 30-minute walkthrough. We start from your intake form submission — company, ops stack, top pain point — and confirm the scope live.
Then we flag the top three automations on the spot, ranked by ROI. It's a working session, not a sales pitch; you'll leave the call with a written shortlist even if you never sign.
Week one is kickoff and credentials — we get read-only access to the systems that hold your ops data. Week two is first agent live, with the daily digest already running and visible on the dashboard.
Weeks three and four are tuning and roadmap review: accuracy checks, edge cases, and a written plan for the second agent — what it would do, what data it would need, and what the monthly cost would step up to.
Three fields, one business day, no discovery call. Submit the intake form and we'll send your 1-page automation audit.