All pricing examples on intunio.se are calculated at 995 SEK/h — our Team retainer rate.
Team retainer is our main model and the arrangement we recommend for most engagements. You reserve a fixed capacity per month — 1 FTE, 1.5 FTE, or 2 FTE — and pay the month's capacity in advance. In return you get our best hourly rate, 995 SEK/h, and a team for design and development working with your product over time. Team retainer is our take on what the industry usually calls a retainer.
At Intunio we believe in long, close collaborations. Our role is to be a long-term partner — open, transparent, and driven to deliver something that makes a real difference. Team retainer is built for that: predictable costs, a team that has time to understand your context, and a model that adapts as needs change.
All pricing examples on intunio.se are calculated at 995 SEK/h — the Team retainer rate.
With Team retainer, you buy capacity from a team rather than hours from an individual consultant. You decide the size — from a half-time resource up to several FTE — and the composition: designers, developers, or a mix, depending on the phase.
Predictable monthly cost. The month's FTE cost is invoiced at the start of the month. The cost is known in advance and easy to budget against.
995 SEK/h instead of 1,095 SEK/h. 1 FTE ≈ 160 hours per month ≈ 159,200 SEK/month.
Why is prepayment cheaper? Because you reserve capacity in advance, we can plan long-term, staff consistently, and spend less time on administration. We share that gain with you through the rate.
30 days mutual notice. No longer commitment. The model is built on the engagement feeling valuable month by month.
You buy capacity, not an estimate. The month's cost is known in advance, and unused hours roll over to the next month. Nothing expires, and we don't run over either.
Needs in projects always change over time. You can scale FTE capacity up and down between months, and adjust the mix of designers and developers in the core team without new negotiations.
No consultant stands alone. Behind the core team are colleagues and specialists who already know the context, and the option to bring in expertise via the Extended Team. The context lives in the team, not in one person.
Needs in product development always change. Team retainer is the arrangement for those who want to adjust along the way — this is where the model differs from a fixed-staffed project.
Composition that follows the need. You can scale capacity up and down between months, switch people, and adjust the mix of designers and developers without new negotiations. Engagements often start with a focus on design and shift toward development as the build picks up.
For concrete accessibility packages, see our WCAG audit and EAA assessment →.
The need to bring in specialist competence comes up in many engagements. With the Extended Team you do it within the same model, at the same hourly rate, for the time you need. No new negotiation, no fresh start.
3D design, motion design, illustration, product-related branding. "We need a marketing film. Bring in motion design and 3D for three weeks."
AI in the design and development workflow, design system governance, agile coaching. "We want our development team to use AI more effectively. Bring in 20 hours of process advisory."
Code review, architecture review and platform selection, security review, DevOps advisory. "We're about to build a new product and need an independent platform and architecture review before development starts. Bring in 40 hours."
WCAG audits, accessibility design integrated into design systems, EAA assessment. "We want to know where we stand for EAA. Bring in 30 hours of accessibility expertise, run an audit, deliver an action plan."
Nothing expires as long as the agreement is running. The balance lives throughout the engagement and can be used when it suits you — an intense week later on, a focused effort, or building up before a launch. You get maximum value out of every month, even when your own organisation is busy.
In a Team retainer engagement we work in three layers:
Project team. The core team that works on your product every day. Designers, developers, or a mix depending on the phase. They are responsible for client dialogue, the process, user research, UX and visual design, development and testing, and delivery.
Product Owner on your side. You drive the backlog and planning, and participate in sprint planning, sprint review, and daily collaboration with the team.
Back Office. Behind the core team sit our design and technology leadership. They come in for check-ins, design and tech reviews, and can be brought in via the Extended Team when specialist input is needed.
Team retainer: 995 SEK/h. Fixed monthly capacity paid in advance. Our best rate — and the base for all pricing examples on intunio.se.
Included at no extra cost. AI tools (Claude, Cursor, Codex), Linear, Figma, Slack, and GitHub.
Termination. 30 days mutual notice. No longer commitment.
If you'd rather work on an ongoing basis without prepayment, the standard rate of 1,095 SEK/h applies — see Expert consultants.
Team retainer fits when you want a partner rather than a supplier, when the product evolves over time and context is valuable to build up, when you want to be able to switch competences and scale without new negotiations, or when you already know the engagement will run for at least several months.
For other models:
Fixed price → for smaller, defined deliverables at a fixed price — demos, POCs, pre-studies, audits.
Expert consultants → for estimated projects without the prepayment model, or when your existing team needs strengthening with an expert.
In ambiguous cases we talk it through. The model should serve the collaboration.
995 SEK/h is Team retainer: you reserve a fixed monthly capacity and pay it in advance. 1,095 SEK/h is the standard rate for ongoing work invoiced in arrears, for example in Expert consultants. Prepayment gives us plannability — we share that gain with you through the rate.
They roll over to the next month. Nothing expires as long as the agreement is running. We stay within the monthly capacity and check in with you if anything looks like it needs to grow beyond it.
Yes. It's common for engagements to start at 1 FTE and grow to 1.5 or 2 FTE when the product calls for it. Equally common to scale down again when intensity drops. Adjustments are made month by month without new negotiations.
Yes — that's one of the model's strengths. The composition adapts to the need: swap a designer for a developer, bring in a specialist via the Extended Team, or rotate profiles when the project enters a new phase.
Typically two to four weeks from agreement to first sprint. Sometimes faster. It depends mostly on your side — when you have a Product Owner in place and a clear first goal.
30 days mutual notice. No longer commitment beyond that. The model is built on the engagement feeling valuable month by month.
The time our consultants work on your project, plus the tools we use to do the work better and faster: AI tools (Claude, Cursor, Codex), Linear, Figma, Slack, and GitHub. Travel is invoiced separately by agreement.
Yes. You decide the composition of the core team and can adjust between months. Engagements often start with a focus on design (pre-study, design system, UX) and shift more toward development as the build picks up.
A specialist pool that sits behind the core team, for niche needs you don't want in the core team full-time. Visual edge, process advisory, technical deep review, accessibility expertise. Same hourly rate, same invoicing model. You ask, and we bring them in.
Yes, AI tools are included in the rate. We use Claude, Cursor, and Codex where they make the work better: in analysis, design work, design system work, and code. It's our expertise working faster, with AI as a tool.
We're based in Gothenburg and work with clients in Sweden, Europe, North America, and Asia. Design work and development happen mostly remote, complemented by workshops and on-site visits when it's valuable. For clients in Gothenburg, proximity is part of the collaboration.
Tell us about your project and your needs, and we'll come back with a concrete recommendation.