Start with the workflow
Map who does the work, which information they need and where handoffs fail. This establishes whether to build a new application, extend an existing tool or connect systems.
Business tools and web applications
Potential scopes include internal portals, approval workflows, reporting interfaces and customer applications. Roles, permissions and audit requirements belong in the requirements, not a late add-on.
SaaS and product foundations
For a new product, define the smallest useful release: core user journey, account model and essential operations. Billing, tenant separation and administration require explicit design decisions.
APIs and third-party integrations
Document data ownership, authentication, rate limits and recovery from failed requests. A useful integration handles duplicates and missing data as well as the happy path.
Security and scalability
Access control, validation, backups and monitoring should match the system’s risk. Capacity planning starts with expected users and workloads; scale claims need measured evidence.
Delivery and ownership
Agree milestones, acceptance criteria, repository access and handover materials in the proposal. Maintenance and future development should have a defined owner.
AI where it supports the task
An AI feature needs a specific purpose, permitted data and a way to evaluate incorrect output. Start with a bounded experiment before making it part of a critical workflow.