abuenoben
Contact

Three ways to work together.

A defined project, monthly development hours or application maintenance. We choose based on the work you have and how you need to organise it.

Tell me about your projectCompare models

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 development hours

Reserve development time for a changing backlog or several projects.

Discuss development hours

Best for

  • Priorities that change during the month.
  • Several tasks managed by one person on your team.
Limits and requirements to start

Not intended for

  • A fixed deliverable with a confirmed scope and deadline.
  • Unlimited availability or 24/7 incident response.

To start

  • A prioritised task list and someone who can approve the work.
  • An agreed block of hours, response window and usage record.

Fixed-scope project

Agree a deliverable, price, deadline and acceptance criteria before work starts.

Discuss a project

Best for

  • A website, integration or feature with a defined outcome.
  • A release with a clear approval process.
Limits and requirements to start

Not intended for

  • Requirements that change every few days.
  • A codebase that needs assessment before it can be estimated.

To start

  • The design, code or documentation needed to estimate the work.
  • The scope, milestones and person responsible for approval.

Support and ongoing improvements

Maintain a live application and plan its next updates. We agree the hours or scope separately.

Discuss ongoing support

Best for

  • Bug fixes, dependency updates and planned releases.
  • A product that needs someone to maintain its technical context.
Limits and requirements to start

Not intended for

  • 24/7 support or on-call cover without a separate agreement.
  • Immediate responses to every request regardless of priority.

To start

  • Repository access, a working build and the current issue list.
  • Response windows and a way to separate urgent fixes from planned work.

Start with a small assignment

An assessment or a first implementation can be a fixed-scope project or use hours from a retainer. The estimate sets out what that first assignment includes.

A technical assessment

For a project whose current state or risks are still unclear.

View scope and outcome
Useful when
Start with an agreed review before estimating the implementation.
What is delivered
A record of what was checked, prioritised findings and a recommendation for the next stage.
Request an assessment

A small implementation

For one defined blocker: a faulty integration, a critical bug or a release that needs preparation.

View scope and outcome
Useful when
Agree one outcome and how to check it. Expand the scope only after reviewing the result.
What is delivered
The agreed change, checks performed, handover notes and any remaining issues.
Discuss the first task

For +DERA, the first assignment was to reproduce the app, backend and website, investigate reported issues and recommend the next steps. See what the assessment covered.

From brief to handover

  1. 01

    Your project

    You share the goal, deadline and current state. I confirm whether I can help.

  2. 02

    The agreement

    We agree the work, price or hours, acceptance criteria and access needed.

  3. 03

    Development

    I deliver the agreed changes and flag any risks or requests that affect the plan.

  4. 04

    Handover

    You review the work and receive the code, documentation and agreed support details.

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 projectWork with agencies