Engagements & commercials

AI Discovery & Strategy

Two weeks, fixed fee. A team of three on site and remote. Output: discovery pack and fixed-price build proposal. The discovery fee is credited against the build if you proceed within 60 days.

Build increments

After discovery, work is structured as fixed-scope, fixed-price, fixed-date increments. The first increment targets a production release by week 12 — the scope defined and agreed in discovery.

• Weekly demos; nothing invisible
• Evaluation harnesses and security review from the first sprint
• Change managed through documented scope revisions, not silent drift

Managed run

Optional ongoing operations at a monthly fee tied to systems under management. Includes evaluation against drift, cost control, agent supervision, model upgrades and a quarterly roadmap.

You can take the system in-house at any time. Handover is a success case.

Data & AI Foundations

Time-boxed foundation build, then optional managed data operations. Priced after discovery when the platform scope is understood.

Application & Cloud Modernisation

Fixed-price per application or per wave. Scoped when legacy constraints are mapped — often in discovery or a focused assessment.

What is not included unless scoped

• ERP or core system licence fees
• Third-party model API costs (passed through or billed to your cloud account, agreed in discovery)
• Travel beyond what is agreed in the statement of work
• Work outside the defined increment without a change order

Payment and contracting

Terms are set in master service agreement and statement of work. Invoicing follows milestones: discovery on start, build on increment milestones, managed run monthly in arrears.

For vendor onboarding, our legal entity is IQLEXA Technologies Private Limited. Write to hello@incubics.com for company information and questionnaires.

Choosing the right entry point

1. Most engagements start with AI Discovery & Strategy
2. If the use case is clear and data is ready, discovery still validates architecture, governance and cost before build
3. If the blocker is legacy APIs, modernisation may run in parallel or as a preceding wave — scoped separately