Focused Build
A tightly scoped engagement centred on one primary workflow or validation goal.
Often suitable for
- A single automation workflow
- A small internal tool
- A clearly scoped prototype
- A focused knowledge assistant
Pricing
Clear scope before commitment.
Pricing follows the actual system and delivery requirements rather than a generic feature package.
Project minimum
US$5,000
One starting signal. A scope built around the real work.
Most projects are scoped around system complexity, number of workflows, integrations, data requirements, user roles, delivery timeline and post-launch support.
Engagement models
Different scopes, not fixed packages.
These are useful ways to frame an engagement. The proposal defines the actual deliverables, milestones and commercial terms.
Custom System
A connected application with several user, data or administration requirements.
Often suitable for
- A multi-page AI application
- A complete administration interface
- User roles and permissions
- Multiple data sources or model providers
- Several connected business workflows
Product Partnership
A multi-stage engagement for a product that needs continued definition and iteration.
Often suitable for
- An AI SaaS MVP
- A product delivered in phases
- Continued feature iteration
- A longer-term technical collaboration
Scope variables
What affects pricing
A useful estimate depends on what the system needs to do, the condition of its inputs and how it will be operated after launch.
- 01The number and complexity of workflows
- 02Data condition, migration and processing requirements
- 03External systems and integration constraints
- 04User roles, permissions and administration
- 05Security and compliance requirements
- 06Delivery timeline and review availability
- 07Infrastructure and post-launch support
Scope boundaries
What the proposal makes explicit.
Every engagement is different. These lists explain the usual direction without turning it into an implied commitment.
What is normally included
The proposal states the exact inclusions. Depending on scope, these commonly include:
- Discovery and solution definition
- Product and interface design where applicable
- Engineering for the agreed workflows
- Testing and milestone reviews
- Agreed deployment support
- Documentation and structured handover
What is normally not included
These items require explicit scope and are not assumed to be included:
- Third-party subscriptions, usage fees and infrastructure charges
- Paid licences, fonts, media or other external assets
- Data cleaning or migration beyond the agreed scope
- Integrations not listed in the proposal
- Ongoing support after the agreed delivery period
- New workflows or features added after scope approval
CHANGE CONTROL
How scope changes are handled
Any requested change is documented with its effect on cost and timing, then agreed before work begins.
A considered first step
A useful estimate starts with a useful brief.
Share the workflow, users, integrations, timing and budget range so the first review can focus on fit.