AI support-intake pilot.
Your team stays in control.

The written scope defines the inputs, expected outputs, reviewer and acceptance criteria before implementation. The pilot includes:

• 20 agreed tests using no more than 200 records. These cover the agreed categories, reply guidance, uncertain or malformed inputs, and human review.
• One revision within the agreed scope. Additional workflows, apps or requirements are quoted separately.
• A documented handover. Review the workflow, its limitations, test results and the steps your team will use to operate it.
• Seven calendar days of defect correction. The written scope defines the coverage and start date. This does not include new features or ongoing operations.

AI output needs review. The pilot does not promise a particular accuracy rate, time saving or business result. Acceptance depends on the criteria we agree and the test results.

Arjit Srivastava leads delivery with AI-assistant support for implementation. Before committing to a delivery date, we check the chosen apps and model provider, approved samples, data-handling permissions, access, costs and Arjit’s availability.

You provide a workflow owner, an authorised reviewer, approved sample requests and response guidance. We demonstrate the proposed path with those samples before confirming implementation. There is no fixed delivery timeline until these prerequisites and the written scope are agreed.

Our homepage workflow demonstration uses sample data and simulated actions. It is not a customer deployment, does not connect to business systems and does not send requests to an AI model. It illustrates the approach; live compatibility must be validated for your pilot.

Ongoing management, additional integrations, autonomous sending and broader business-process outsourcing are outside this pilot. Any later work requires a separate scope.