AI Solution Implementation

Who it is for

For a company that knows what it wants to automate: there is a specification, a requirements document or a clear task. Integrations of CRM, email, messengers and internal systems, workflows, chains with AI. AI isn't required here: sometimes it's enough to connect existing tools correctly.

How the work goes

1. Free call. The task, the systems, the scope.
2. Specification. If there isn't one, it is written to the ANSS standard. A client's existing requirements document is checked by the same rules: acceptance criteria, boundaries, rollback. Small gaps are closed within the project, large ones with a separate specification.
3. Build and configuration. Strictly to the specification. A change of scope is agreed separately before work on it starts.
4. Acceptance. The solution is checked against the criteria from the specification on the client's data.
5. Launch and handover. The solution runs in the client's processes, documentation is handed over.
6. Support. At the client's choice, monthly.

What remains

A working solution accepted against the acceptance criteria. The specification it was built to, and documentation: how it works, how to make changes, what to do if it fails. The contractor is responsible for the result against the acceptance criteria.

Formats

Support after launch: monthly, scope and price are set at handover.

Prices are net, excluding VAT. The final price is set after the specification.

Format boundaries

A simple task can be built in-house during AI training on your tasks: the client builds the solution, the consultant guides. If it is unclear which solution is needed, solution design comes first. A document for a contractor without the build is the specification.