# How to hire: retainer, project or support | abuenoben

> Compare monthly retainer, fixed-scope project and technical support by scope, rate of change and delivery acceptance.

Canonical URL: https://abuenoben.com/en/collaboration
Language: en

Monthly retainer, fixed-scope project or ongoing support. The difference is how often priorities change and how outcomes are accepted.

[Tell me about your project](/en/contact#contact-form-shell)[Compare models](#model-comparison)

## Choose based on what you need

A retainer suits changing priorities. A fixed-scope project suits a defined outcome. For an application already in use, we can agree support and improvements.

### Monthly Retainer

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

[Assess monthly retainer](/en/contact?collaborationType=hours&projectType=other#contact-form-shell)

#### Best for

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

Limits and requirements to start

#### 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.

### Fixed-Scope Project

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

[Assess fixed project](/en/contact?collaborationType=project&projectType=other#contact-form-shell)

#### Best for

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

Limits and requirements to start

#### 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.

### Support and Evolutives

For a live product that needs continuity and clear priorities.

[Assess ongoing support](/en/contact?collaborationType=support&projectType=support#contact-form-shell)

#### Best for

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

Limits and requirements to start

#### 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.

## Ways to start

We can start with a technical review or a small assignment before committing to a longer phase.

### Express technical diagnostic

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

View scope and outcome

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](/en/contact?collaborationType=project&projectType=other#contact-form-shell)

### Unblocking sprint

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

View scope and outcome

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](/en/contact?collaborationType=project&projectType=support#contact-form-shell)

### Starter retainer for agencies

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

View scope and outcome

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](/en/contact?organizationType=agency&collaborationType=hours&projectType=support#contact-form-shell)

### Fixed-scope project

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

View scope and outcome

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](/en/contact?collaborationType=project&projectType=other#contact-form-shell)

## 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?

Tell me what you want to do and what you already have. I will suggest how to start before preparing an estimate.

[Tell me about your project](/en/contact#contact-form-shell)[Work with agencies](/en/agencies)