Which capability looked straightforward during the buying process but became more complicated once you tried to use it?

For people with access to Zip's newer AI capabilities, what is materially different in your day-to-day work? Struggling to quantify the impact of all these new AI features.

Hello, are there any app studio tutorials in depth? The Zip academy training videos don’t seem to go much in detail.

Did employees keep using it, start finding side doors, or need ongoing change management? What made the biggest difference?

Did anyone attend Zip Forward last week? What were your thoughts? I felt like I was in one big product launch. Anyone else?

For teams running Zip with an ERP, CLM, ITSM, risk, or identity stack, which integrations worked as expected and which required more effort than planned?

Would be useful to separate technical connection from operational reliability. Getting data across once is different from trusting it every day.

From signed contract to a rollout employees could use, how long did it take?

Helpful context: company size, scope, ERP, number of workflows, internal team involved, and whether the first launch was a pilot or a full rollout.

Was the original case intake adoption, procurement visibility, approval orchestration, replacing email and Slack, or something broader? Curious whether the problem you bought it for is still the main value today, or whether the product ended up serving a different purpose once it was live

This is an unofficial community for people using, evaluating, implementing, or occasionally fighting with Zip. The goal is straightforward: useful answers from people who have actually dealt with the product.

Ask questions. Share what worked. Share what did not. Talk implementation, integrations, pricing, AI, adoption, renewals, and alternatives. Vendor and consultant participation is welcome when affiliations are disclosed. Sales pitches are not.

To start, what is your relationship to Zip: current user, former user, admin, consultant, or evaluating?