1. They understand your process first

First: they should understand your process before they sell you a tool. If the conversation jumps straight to a platform or a price list, you risk paying for software that does not match how your team actually works.

2. Clarity on ownership

Second: clarity on ownership. You should know what you own (accounts, data, workflows) and what happens if you part ways. Avoid "black box" setups where only the vendor can change anything.

3. Documentation and handoff

Third: documentation and handoff. Deliverables should include enough explanation that a future developer—or your internal team—can maintain the system. Automation that only lives in one person's head is fragile.

4. Support after launch

Fourth: support after launch. Real usage always surfaces edge cases. Ask how bugs, small changes, and new requirements are handled once the project is live. LCL Automation is built around shipped systems people rely on daily—not one-off installs that are abandoned after delivery.