Zalos

What do they actually do

Zalos builds computer-use agents that log into a company’s existing finance systems (ERPs, portals, document stores) and carry out repetitive tasks like invoice handling and reconciliations. The agents operate through the UI like a human, can fetch and interpret documents, interact with web portals, reconcile records across sources, and keep screen captures and logs for audit trails Zalos homepage.

Today, Zalos is running demos and early-access pilots with finance teams rather than a self-serve product. The near-term focus is expanding agent coverage across finance workflows and hardening integrations, human-in-the-loop controls, and enterprise security to turn pilots into scalable deployments Zalos homepage, YC listing, Privacy policy.

Who are their target customer(s)

• Head of Finance / CFO (mid-market or enterprise): Needs accurate, timely closes without raising audit risk, but reconciliation and invoice work is still manual and slows reporting. Wants to keep the ERP and cut routine effort without a big systems change.
• Accounts Payable Manager: Overloaded with invoices from portals, email, and PDFs; many exceptions require manual lookup and vendor follow-up. Backlogs cause late payments, lost discounts, and firefighting.
• Reconciliation Specialist / Staff Accountant: Spends much of the day matching records across banks, payment platforms, and ledgers. Work is repetitive with edge cases that still need checks, making it hard to onboard/retain and leaving little time for analysis.
• ERP / Finance Systems Administrator: Accountable for ERP stability and security; reluctant to adopt tools needing deep integrations or change controls. Needs clear audit trails, access controls, and low-friction automation that won’t break workflows.
• Treasury / Payments Operations Lead: Chasing unapplied cash and failed payments across gateways and banks hurts cash visibility and forecasting. Manual investigations slow cash application and risk missed credits or duplicate payments.

How would they acquire their first 10, 50, and 100 customers

• First 10: Founder-led outreach to finance leaders via YC/network and targeted outbound to teams with heavy manual reconciliation. Run a scoped pilot that proves an agent in the customer’s ERP with audit logs and a short report on effort saved Zalos homepage, YC listing.
• First 50: Turn early wins into a repeatable pilot-to-contract playbook: standard connectors and onboarding checklists for common ERPs/portals, templated pilot agreements and success metrics, and dedicated sales/CS running concurrent pilots, using early customers as references.
• First 100: Scale via partners and productization: co-sell with ERP consultancies, accounting outsourcers, and payment-gateway vendors; ship hardened connectors, admin controls, and audit/HITL features to enable lower-touch sales and listings on marketplaces, backed by documented security posture Privacy policy.

What is the rough total addressable market

Top-down context:

Zalos sits at the intersection of finance operations automation, close/reconciliation software, and RPA-style UI automation inside existing ERPs. Buyers are finance and IT leaders allocating budgets to reduce manual close work, AP/AR exceptions, and portal-driven tasks without changing core systems.

Bottom-up calculation:

Illustrative: if targeting 25,000 mid-market/enterprise companies that have multi-system finance workflows and would buy at an average annual contract value (ACV) of $40k–$120k for one or more agents, the TAM would be roughly $1–$3B. Expanding to global enterprises and adjacent workflows could increase this materially.

Assumptions:

• Addressable segment focuses on firms with 200–5,000+ employees and fragmented finance portals/ERPs.
• Adoption starts with 1–3 agent workflows per customer with ACV scaling by volume and controls/compliance needs.
• Pricing reflects agent-driven automation value comparable to AP/AR automation or RPA-led deployments.

Who are some of their notable competitors

• UiPath: Enterprise RPA platform used to automate finance tasks by driving UIs and orchestrating bots, with HITL and broad ERP connectors. Overlaps on “act like a user” automation; Zalos positions packaged, finance-focused agents rather than a build-your-own platform UiPath.
• Microsoft Power Automate: Low-code workflow + RPA in the Microsoft stack that can run desktop/web UI flows against ERPs/portals. Often used as an internal automation platform; Zalos operates agents for customers as pilots and managed deployments Microsoft Power Automate docs.
• BlackLine: Controls-first close and account reconciliation software with templates, governance, and auditor workflows. Competes on reconciliation/control use cases; differs from UI agents that log into third-party portals to fetch documents and take actions BlackLine.
• HighRadius: AR and cash-application automation for remittance capture, payment matching, and ERP posting. Overlaps on unapplied cash and treasury pain points; Zalos emphasizes UI agents across fragmented portals and ad-hoc systems HighRadius.
• Stampli: AP automation with invoice capture and collaboration, keeping humans in the loop for exceptions. Targets AP backlogs; differs from agents that operate directly inside customer ERPs and external portals Stampli.