---
title: "How the Fluff product team subscription works | Queue, tracks and reviews"
description: "How our flat-fee development subscription works: unlimited requests in a queue, one task at a time per track, senior review on every release."
url: https://www.fluff.software/how-it-works/
updated: 2026-10-23
publisher: Fluff Software
---

# How it works

Unlimited requests, worked one at a time per track, with senior review on every release and CTO-level judgment built in.

[Book a 20-minute call](https://www.fluff.software/contact/) [See pricing](https://www.fluff.software/pricing/)

_Image: A team working through ideas on sticky notes_

## Everything runs through one queue.

You add requests. We work through them in the order you set. Each track works on one task at a time, so you get a steady flow of finished work instead of ten things half done.

That one-at-a-time rule is also how “unlimited” stays fair. There’s no cap on what you can ask for, and no hours to count. Delivery is paced by the number of tracks you have. Want more moving at once? Add a track.

Example queue Track 1, active

1. Fix VAT rounding on credit notes Shipped
2. Learner progress export for funders Shipped
3. New booking confirmation emails Building
4. Reorder dashboard widgets by role Up next
5. Integrate the new payment provider Queued
6. Accessibility pass on sign-up Queued

+ Add a request

## Four steps, repeated every week.

1.

### Fill your queue

Features, fixes, design tweaks, integrations, written in plain English. Reorder whenever priorities change.

2.

### We build, one at a time

Each track works on one task until it’s properly done. Most tasks land within a few working days.

3.

### You review and sign off

Every release gets a senior review before it reaches you. You test it, give feedback, and we tighten it up.

4.

### Next one starts

There’s no new quote or contract. The next request starts as soon as the last one is signed off.

## Requests, tracks and turnaround.

### What counts as one request

Anything we can ship as a self-contained piece: a new feature, a fix, a design change, an integration. Bigger pieces get broken down with you into smaller ones that ship one after another.

- “Add a CSV export to the reports page” is one request.
- “Rebuild the reporting module” becomes five or six, each shipped and reviewed in turn.
- “Tweak the copy and colours on the pricing page” is one request.

[How to write a request that ships quickly](https://www.fluff.software/guides/how-to-write-a-good-request/)

### What a track is

A track is one stream of work. Embedded has one, Embedded Plus has two running in parallel, Partner has three or more. If you need things moving faster, adding a track is the lever.

### Turnaround

Most tasks land within a few working days. We commit to a rhythm instead of a number of tasks, because a two-line fix and a payments integration aren’t the same size.

## What keeps the quality up.

### Senior review on every release

Nothing reaches you until a senior developer has reviewed it. That includes code written with AI tools: we design it, review it and test it before it ships.

### Urgent bugs jump the queue

If something’s broken in production, it goes to the front on every plan. Embedded Plus and Partner also get priority on time-sensitive fixes that aren’t emergencies.

### Revisions go in the queue

If something isn’t right, tell us. The change goes into the queue like any other request, at no extra charge.

## Working together.

### Day to day

A shared board showing your queue, what’s being built and what’s shipped, plus a direct line to the team with no account managers in between.

### Onboarding

Usually within a week or two of signing. A short session to sort access, understand how your product is built and agree what goes first. We review your codebase early so we understand it before we change anything.

### What we need from you

Someone on your side who can make decisions and review work as it lands. Quick feedback is what keeps the queue moving, so the model works best when that person isn’t a bottleneck.

[How to review work quickly without it taking over your week](https://www.fluff.software/guides/uat-without-the-bottleneck/)

### What isn’t included

Third-party costs such as hosting, app store fees and licences. You pay those directly, so you own the accounts. Extra CTO days beyond your plan are £1,000 a day.

## When it isn’t the right fit.

It’s built for teams that already have a live product and a backlog. It’s the wrong fit if:

- **You don’t have a product yet.** Start with a [Discovery Sprint](https://www.fluff.software/ways-to-work/discovery-sprint/) to work out what’s worth building.
- **Nobody can make decisions or test.** The queue stalls without quick sign-off. We’d rather tell you that now.
- **You want the cheapest hours you can find.** You’re paying for judgment and finished work, so there are cheaper ways to buy raw hours.

## Questions about how it works.

Is it really unlimited?

Unlimited requests, yes. Add as much to your queue as you like. We work through it one task at a time per track, so you get a steady flow of finished work rather than ten things half done. Want things moving faster? Add a second track.

Why not just hire a developer?

You could. It will probably take months to find the right person, you carry the cost if it doesn’t work out, and you get one person’s skills. With us you get senior developers, product thinking and CTO-level judgment, usually starting within a week or two of signing.

Why a 12-month term?

Good product work compounds. The longer we work with you, the better we know your codebase, your users and your business, and that’s where the real value shows up. The term lets us invest in understanding you properly instead of treating you like a ticket.

What counts as one request?

Anything we can ship as a self-contained piece: a new feature, a fix, a design change, an integration. Bigger pieces get broken down with you into smaller ones that ship one after another.

What do you need from us?

Someone on your side who can make decisions and review work as it lands. Quick feedback is what keeps the queue moving.

[All questions](https://www.fluff.software/faq/)

---

Fluff Software, a senior product team embedded in your business. Book a call: https://www.fluff.software/contact/ or email contact@fluff.software. Agents: see https://www.fluff.software/llms.txt and https://www.fluff.software/AGENTS.md.
