--- title: "For the platform that runs your business | Fluff Software" description: "Ongoing development for the internal platforms and portals that run your operations. Flat monthly fee, urgent fixes first." url: https://www.fluff.software/for/platforms-that-run-the-business/ updated: 2026-10-23 publisher: Fluff Software --- # For the platform that runs the business. Learners, customers or inspectors judge you partly on your platform, and every change to it costs a quote, a wait and an argument. One flat fee ends that. [Book a 20-minute call](https://www.fluff.software/contact/) [See pricing](https://www.fluff.software/pricing/) _Image: Someone working on a laptop_ ## What we hear. - **“Every change is a quote, and every quote takes three weeks.”** Small fixes wait behind paperwork. - **“When the rules change, the deadline isn’t ours.”** Funding rules, inspection frameworks and seasons all come with dates set by someone else. - **“Users say the portal is clunky, and they’re right.”** Poor experience costs renewals and makes your team look amateur. - **“I’m the product owner, the tester and the help desk.”** Your week goes on checking work that should have been right first time. - **“I’ll never get a developer hire past the board.”** Headcount is hard to approve. A known monthly line is easier. ## How a fractional team helps. ### No quotes Add the change to the queue and it gets worked on. Reorder the day a rule changes, and the deadline item goes first. ### Experience design included UX and polish are what we sell: designing what your users need, from years of watching real people use real software. ### Right first time, more often Senior review before anything reaches you, so your testing becomes a quick sign-off. ### A line the board understands One monthly cost on a 12-month term, instead of a headcount request. We’d usually recommend [Embedded](https://www.fluff.software/pricing/), moving to [Embedded Plus](https://www.fluff.software/pricing/) when you want a shared roadmap and a planning session to take to your board. What you asked for “The funding rules change in April. Update the evidence form.” What we shipped New form ready before April, with learners already on programme kept on the rules they started under. *Started before April* Started after April Employer sign-off - **Asked why.** Learners who started before April stay on the old rules, so both versions have to run side by side. - **Spotted.** Employer dashboards would have mixed the two. Reports now split them. - **Designed for employers.** Sign-off is one screen instead of three, which is what they’d been complaining about. An example of how one request changes once a senior team has reviewed it. ## Relevant work. - [ _Image: EAL_ EAL ### A grading engine an awarding body can stake its reputation on EAL needed final grades for a brand-new qualification calculated correctly, for every candidate, every time. We designed it so the engine stays right even when everything around it changes. Grading thousands of candidates](https://www.fluff.software/work/grading-engine/) - [ _Image: TG Consulting_ TG Consulting ### EVOLUTION: one platform that works for students, assessors and organisers TG Consulting was stuck on off-the-shelf assessment platforms that fitted nobody. We designed for each group separately, then brought them together in one platform. Built for three very different users](https://www.fluff.software/work/evolution-assessment-centres/) - [ _Image: Enginuity_ Enginuity ### Enspire City: making engineering careers playable for children Enginuity wanted children excited about engineering and manufacturing. We built an animated, gamified city with accessibility designed in from the start, shaped by feedback sprint after sprint. Accessible by design](https://www.fluff.software/work/enspire-city/) ## Questions we hear. Who owns the code? You do. Everything we build lives in your repositories and belongs to you. What about urgent bugs? If something’s broken in production, it jumps to the front of the queue on every plan. Embedded Plus and Partner also get priority on time-sensitive fixes. 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. ## Worth reading. [Subscription vs retainer vs fixed price Which commercial model suits ongoing platform work.](https://www.fluff.software/guides/subscription-vs-retainer-vs-fixed-price/) [UAT without the bottleneck Reviewing work quickly without losing your week.](https://www.fluff.software/guides/uat-without-the-bottleneck/) [What is a development subscription? A plain-English guide for UK teams.](https://www.fluff.software/guides/what-is-a-development-subscription/) --- 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.