New features — continuous, not one-off.

Good ideas often die in the backlog because every feature needs a new quote. In the retainer we just build them — month after month, prioritised by what brings you the most. From 600 €/month on the retainer.

01 · Why continuous

Every good idea just gets built.

Instead of writing a quote for every small task, we draw features straight from your hour quota. You say what matters — we deliver in a fixed rhythm.

  • From a small improvement to a complete module
  • Prioritised by impact, together on a monthly rhythm
  • Delivered on staging, with tests for critical paths
  • No fresh brief, no quote ping-pong per idea
  • Larger features spread predictably across months
Continuous feature development in the retainer at Forge12
03 · Sizing

How we size features.

Size
Effort
Example
In the retainer
Quick win
< 1 day
Button, text, small flow
On the side each month
Feature
1–5 days
Form, filter, export, mail flow
Within the monthly quota
Module
1–4 weeks
A whole functional area
Across months / a sprint

Prioritised by impact versus effort — the biggest lever first, together at the start of each month.

02 · Examples

What we often build continuously.

AutomationOut with the manual work.Automate recurring processes, win back time.
ExperimentsTest measurably.Small A/B tests and prototypes before investing big.
04 · From wish to live feature

Visible, tested, handed over.

01

Idea & prioritisation

Quickly estimated by impact and effort. You decide the order — the biggest lever first.

02

Build on staging

Built on a test environment, with four-eyes code review.

03

Tests & approval

Tests for critical paths; you see the state before go-live and approve it.

04

Live + docs

Deploy, short docs, done — and traceable in the monthly report.

FAQ

Common questions about features.

01How are features prioritised?

By impact versus effort: at the start of the month we roughly estimate both and you decide the order. So the biggest lever for your goal always lands on top — not "whoever shouts loudest".

02What if a feature needs more hours than my monthly quota?

We break it into deliverable stages across months or use the fair hour rollover. For very large work we may suggest a separate sprint instead — transparently estimated up front.

03Do I get to see every feature before go-live?

Yes. It's built on a staging environment, you review and approve. Only then does it go live — no surprises in production.

04Do you write tests for new features?

For critical paths, yes. That keeps the solution stable through later changes and catches regressions early instead of at the customer. Tests are part of the quota, not extra.

05Do I own the code of the features?

Yes, entirely. The repository, source code and docs are yours — any other developer could take over. No lock-in.

Straight talk

What might still hold you back.

01How do we know the right features get worked on?

You prioritise — we build in the order that brings you the most, transparently each month. No feature enters the quota without your sign-off.

02Does quality suffer when new things keep coming in?

No — every feature is tested and cleanly integrated, not bolted on. Precisely because the same developer knows the system, there are fewer breakages than with rotating contractors.

03You're a single founder — what if you're unavailable?

Standard stack, tested code, documented deployment, repository with you — any competent developer can carry on seamlessly. Your roadmap doesn't hang on one person.

04Am I tied to the retainer?

No. Cancellable monthly, no commitment beyond the current month. You stay because the features keep coming — not because of a contract.

An objection we didn't cover?Write to the founder directly
PART OF YOUR RETAINER

Got a feature idea? We'll build it in the retainer.

Build features continuously (retainer) · Forge12