Web, mobile & AI
development agency

Both offers rely on the same delivery foundation (steering, Jira, iterative releases, included maintenance).

The difference mainly concerns:

• the number of active requests in parallel (1 in Launch, 2 in Partner)
• the delivery cadence (lighter monthly cycle vs alternating weekly cycle)
• the indicative response time (12h vs 2 business hours)
• the level of reactivity and parallel execution

The foundation includes:

• continuous scoping
• backlog structuring in Jira
• technical decisions
• development
• stabilization
• beta then production releases
• minimal documentation
• business-hours support

This is an obligation of means, with no fixed delivery deadline or business-outcome guarantee.

A request is a functional or technical topic handled continuously until delivery or closure.

The number of active requests depends on the selected offer.

Non-active requests remain in the shared backlog.

Capacity does not roll over from one month to the next.

Yes.

Urgencies submitted via Jira are handled with priority during defined hours (business days, 10:00-20:00).

No default 24/7 on-call coverage is included.

The framework can be extended with monthly options that can be enabled or disabled without changing the core subscription.

Examples:

• UI / UX design
• Enhanced QA and testing
• Framed on-call support
• Security / compliance
• Reinforced governance

Each option has a clear scope and is billed monthly.

Yes.

Additional quotes can be proposed for needs outside the recurring framework: audit, targeted migration, partial redesign, exceptional feature, or specific project.

They are independent from the subscription.

The custom offer applies when:

• the project durably exceeds standard capacity
• a closed or structured scope is required
• specific commitments are required (deadlines, SLA, compliance)
• dedicated capacity is needed

It is based on a fixed package defined by scope, deliverables, and planning.

Launch and Partner are commitment-free with monthly tacit renewal.

Cancellation is possible at any time, effective at the end of the current month.

Any started month is fully due.

This version strictly follows your contractual shared foundation, formal offer differences, and the options / escalation logic defined in your documents.

Inprogress Agency supports web and mobile products with a continuity mindset: execution, technical steering, and structural trade-offs, without requiring the client to build a dedicated internal team.

Collaboration relies on a shared Jira backlog, centralized written exchanges, a weekly sync point, and minimal documentation maintained in Notion.

The organization follows a pragmatic Agile approach (SCRUM/KANBAN) oriented around backlog execution: needs are clarified, split into actionable items, prioritized, then carried to delivery or closure.

Releases are iterative (beta -> production), with structured feedback cycles and technical arbitration capacity to preserve product coherence and avoid uncontrolled technical debt.