How to scope a website, app,
automation or AI project

1. Define the business outcome and the users

Describe the task people need to complete, who does it today and what makes the current process difficult. Choose a measurable acceptance condition. For example: an authorised operations user can find an order, update its status and see a recorded history of the change. This is an illustrative requirement, not a client result.

2. Choose the smallest useful first release

A business website needs agreed pages, content ownership and an enquiry route. A mobile app adds device support, account flows, backend APIs and release responsibilities. Custom business software needs user roles, key workflows and rules for accessing and changing records. Separate essential requirements from later improvements.

3. Map integrations and exception paths

For workflow automation, list the trigger, source fields, destination, validation rules and required permissions. Decide what happens when a record is incomplete, an API times out or a repeated event arrives. Name the person who receives failure alerts and the process for retrying or correcting a failed run.

4. Add evaluation and human review to AI work

For an AI assistant or integration, specify the approved information sources, who can access them and what the system should do when it cannot answer. Build representative evaluation examples before rollout. Include human handoff, source references where appropriate and rules for actions the assistant may take. Sensitive information should stay out of an initial public enquiry.

5. Make acceptance criteria testable

Write a short list of scenarios with an input, expected output and responsible reviewer. Include a normal path, a missing-input path, a permission check and a failure/recovery path. For a reporting pipeline, agree the source of truth and reconciliation checks rather than relying only on a visually correct dashboard.

6. Agree ownership, costs and handover

Confirm who provides hosting, domains, API subscriptions and content; how source code and documentation will be handed over; and who operates the system after launch. Ask the proposal to state scope, exclusions, milestones, review windows, quotation currency and third-party costs. Delivery dates and prices depend on the actual brief.

What should you send in a first enquiry?

• Your business goal and the people who will use the solution.
• The workflow or pages required in the first release.
• Existing systems and integrations, without passwords or private records.
• Target timeline, budget range, country and time zone.
• Who will review the work and maintain it after handover.

Working with an India-based delivery team

Cubitors is based in New Delhi, India, and focuses on international projects. Agree meeting windows, written updates, access arrangements and review responsibilities before starting. Location alone does not determine delivery fit; the scope and working arrangements need to match the project.