Ways to start

A bounded first engagement buys clarity or capacity without creating an oversized relationship.

01

Express technical diagnostic

Review of a blocked website, app, backend or integration to order risks, dependencies and the next step.

Useful when
When you still do not know whether you need a sprint, retainer or fixed project.
What is delivered
Technical reading, risk list, action priorities and model recommendation.
Request diagnostic

02

Unblocking sprint

Scoped intervention to close a concrete piece: integration, release, critical bug, frontend or backend.

Useful when
When there is a date, a clear blocker and little room to set up a long process.
What is delivered
Functional delivery, technical notes and next steps to continue without dependency.
Assess sprint

03

Starter retainer for agencies

Controlled monthly capacity for delivery peaks, technical presales, QA, integrations and evolutives.

Useful when
When there are several small pieces or variable workload during the month.
What is delivered
Priorities, response window, light follow-up and visible consumption.
Assess retainer

04

Fixed-scope project

Delivery with scope, milestones and acceptance criteria: landing, CRM integration, API, app or mobile stabilization.

Useful when
When the expected result is clear and it is better to close price, scope and calendar.
What is delivered
Plan, implementation, validation, close and documented handoff.
Assess project

Three frames, three rules

Choosing the right one reduces scope drift, idle time and incompatible expectations.

01

Monthly Retainer

For variable workload, several open fronts and recurring senior support.

Assess monthly retainer

Best for

  • Several small or medium deliveries.
  • Priorities that change during the month.
  • Senior capacity without expanding the permanent team.

Not a fit when

  • A single closed deliverable with scope and validation already defined.
  • Unlimited availability or permanent reaction without clear priorities.
  • On-call, 24/7 or structural emergencies outside a specific agreement.

To start

  • Priority owner.
  • Initial list of active fronts.
  • Agreed channel and response window.

02

Fixed-Scope Project

For a concrete piece with date, deliverable and acceptance criteria.

Assess fixed project

Best for

  • Deliverables with a clear expected outcome.
  • Teams that need plan and milestones.
  • Work with a fixed date.

Not a fit when

  • Open work that changes direction every few days.
  • A live priority list with decisions that are not mature yet.
  • Contexts without a clear owner to validate scope, milestones or decisions.

To start

  • Objective, date and main deliverable.
  • Validation owner.
  • Documentation or access to estimate.

03

Support and Evolutives

For a live product that needs continuity and clear priorities.

Assess ongoing support

Best for

  • Product with improvements and issues to order.
  • Continuity without opening a new project every time.
  • Balancing fixes, evolution and technical debt.

Not a fit when

  • 24/7 support, on-call or permanent incident response.
  • Environments without a priority owner or decision capacity.
  • Expecting immediate reaction to every request outside the agreed frame.

To start

  • Initial task list.
  • Criteria to separate urgent issues from improvements.
  • Review cadence and owner.

From brief to close

  1. 01

    Context

    You tell me objective, date and blocker. I tell you if it is worth continuing.

  2. 02

    Scope and model

    We define frame, base scope, milestones and limits.

  3. 03

    Execution and follow-up

    It is clear what enters, what changes and what is delivered.

  4. 04

    Close or continuity

    We close deliverables or move into continuity without artificial dependency.

Not sure which model you need?

Share the objective, timing and blocker. The first reply can recommend a working model before estimating.