Can the first AI project cover every department?

The usual start is one workflow, with acceptance examples agreed first. Wider use is a later scope, not an assumption of the pilot.

Is ongoing support included?

Only if the written scope says so. Otherwise support after handover is quoted separately.

ENQUIRY NOTE · 2026-09-24

What is agreed before a Quguo software project starts

Describe one workflow, who does it today, which systems already exist, and the timing. Quguo writes the scope, milestones and acceptance examples before development starts. Work after handover is not included unless the scope says so.

One workflow

An AI enquiry is about one job: search over material you already hold, help with a repeated task where a person still checks the result, or moving information between systems you already use. A custom software enquiry is a business application, an internal tool, or an integration. A smart-hardware enquiry adds the device, its connection, and what the user does with the data.

These are separate briefs. They are not one packaged product.

Written before development

The written scope names the features, the milestones, who owns the result, and which examples count as acceptable. For a device, it also names who provides the hardware and who is responsible for hardware versus software. Hardware manufacture, certification and supply stay outside the software work unless the scope includes them.

After handover

Development covers build, test, deploy and handover of the agreed scope. Later support is a separate agreement. A conversation about a possible feature is not part of the project until it is added to that scope.