Customers ask this before they sign: what does it actually look like when Maya goes live? Here's the version we wish someone had given us, written from the side of the team running it.

Days 1–3: Connect and read

We connect to your ERP, your inbox, and your bank feed using credentials your team already provisioned. Maya doesn't act in week one. It reads. It builds a model of your vendor master, your PO patterns, your typical exceptions.

Most controllers spend this week wondering if anything is happening. It is.

Days 4–7: Shadow mode

Maya starts processing invoices without posting. For each one, it tells you what it would do, why, and what it's unsure about. Your AP team reviews the queue alongside their normal work — same screens, same workflow.

By Friday of week one, accuracy on the routine invoices is usually above 95%. The exceptions are the ones you'd already pull aside.

Days 8–10: Limited go-live

We pick one vendor cohort or one invoice type and let Maya post for real. Reversible by default — every action logged, every entry undoable. The AP team watches the queue but stops touching the routine work.

Days 11–14: Expand

By the end of week two, Maya is processing the bulk of inbound invoices. The team's role shifts from doing the work to reviewing exceptions. Customers describe this moment as weird in a good way — the queue clears without them.

What week three looks like

If week two went well, week three is when finance leads start asking what else they can put on Maya. Reconciliation usually goes next, then vendor onboarding. We say no to a few of those — not every workflow is ready, and we'd rather scope down than overpromise.

— Elin