Engagements · INR

Start with clarity,then commit with confidence.

The figures below are honest starting points—not fixed packages. Final scope, delivery plan, and price depend on discovery, integrations, data readiness, risk, and what already exists.

Starting points

Choose the shape, not a rigid box.

Every engagement begins by confirming the problem, constraints, acceptance criteria, and the smallest useful release.

Focused MVP · From ₹49,999

Validate one valuable product slice

Suitable for a focused AI interface, retrieval experience, internal tool, or compact automation workflow.

  • One clearly bounded use case
  • Essential interface or workflow
  • Core integration or data path
  • Deployment and practical handoff
Product build · From ₹1,49,999

Engineer a production-oriented system

Suitable for an agent or retrieval system with an application, backend services, integrations, and operational controls.

  • Product and technical discovery
  • Web application and backend APIs
  • AI, retrieval, or workflow layer
  • Testing, deployment, and observability
Custom engagement · Scoped in INR

Build and evolve a larger capability

Suitable for multi-system products, private deployments, phased platforms, or an ongoing engineering partnership.

  • Phased roadmap and architecture
  • Complex or multiple integrations
  • Environment-specific controls
  • Support terms defined in the proposal
What shapes the proposal

Price follows the real engineering work.

Discovery exists to replace assumptions with a buildable plan.

01 · Product

Scope and experience

Number of workflows, user roles, interfaces, platforms, and release requirements.

02 · Systems

Data and integrations

Source quality, API availability, migration needs, permissions, and third-party dependencies.

03 · Intelligence

Model and quality requirements

Retrieval complexity, tools, evaluation, latency, review paths, and acceptable failure modes.

04 · Operation

Deployment and support

Hosting, environments, monitoring, documentation, maintenance, and response expectations.

A responsible start

From conversation to committed scope.

01

Share context

Explain the problem, users, current tools, and urgency.

02

Discover

Clarify constraints, dependencies, data, and decision points.

03

Prioritise

Define the smallest release that can create or test value.

04

Propose

Set out scope, assumptions, milestones, and commercial terms.

05

Build

Engineer in visible increments with regular review.

06

Evolve

Use operational evidence to guide what comes next.

Get a specific estimate

Tell us enough to price the real work.

Share your workflow, current systems, desired outcome, and timeline. We will use discovery to define a credible scope.