A new version of your platform every two weeks.

Software is never finished. A fixed team works on your platform every month: new features, improvements and updates. In a fixed rhythm, with a fixed release day.

  • Fixed team that knows your platform
  • A release every two weeks
  • Always a view of hours and progress

This is what a two-week sprint looks like.

A fixed rhythm brings calm. You know when your requests are planned, when you can test and when it goes live.

2weeks per sprint
PlanMonday, week 1

Together we choose what delivers the most in the next two weeks.

BuildWeek 1 and 2

Your fixed developers build. You can follow the progress every day.

TestThursday and Friday, week 2

Everything goes past a second developer and the automated tests. You test along on the test environment.

ReleaseTuesday after the sprint

The new version goes live on a fixed day. With release notes, so that everyone knows what has changed.

A fixed number of hours per month.

You choose how much room your platform needs. That way you know exactly what it costs, and we can plan ahead.

16 hoursper month€150 per hour
€ 2.400excl. VAT per month

For small requests and maintenance alongside a stable platform.

  • Fixed developer
  • Release every four weeks
  • Updates and small improvements
Discuss this package
Most chosen32 hoursper month€140 per hour
€ 4.480excl. VAT per month

For a platform that has to move forward every month.

  • Fixed developer
  • Release every two weeks
  • Sprint planning and demo
  • Quarterly roadmap meeting
Discuss this package
64 hoursper month€130 per hour
€ 8.320excl. VAT per month

For a product you are growing fast with.

  • Two fixed developers
  • Release every two weeks
  • Sprint planning and demo
  • Monthly roadmap meeting
Discuss this package

The larger the package, the lower the hourly rate. Need more or less? Then we tailor the package to your platform.

You follow the work in the CodeIQ Console.

Every client has its own environment in the CodeIQ Console. It holds your requests, the sprint, what is ready for your approval and what is live.

CodeIQ ConsoleCustomer portal · Sprint 47
Hours this month21 of 32

Requests 3

KP-151Customer portal in EnglishRequest
KP-149Integration with new carrierRequest
KP-147Dashboard for managementRequest

This sprint 2

KP-146Customer moves an appointmentIn progress
KP-144Export to ExcelReview

For approval 1

KP-142Faster searching in filesYour approval

Live 2

KP-139VAT on credit notes10 Nov
KP-137New house style in emails27 Oct
All requests in one place

You put new requests in the console yourself. We estimate them and plan them with you.

You approve

A task is only finished when you have approved it on the test environment.

Hours always in view

Per task you see how much time has gone into it and how many hours are left.

Every change goes live in five steps.

Developing fast must not come at the expense of your platform. That is why every change follows the same route to live.

Build

On its own branch, never directly in production.

Review

A second developer reads every change.

Tests

Automated tests run with every change.

Test environment

You look at it and approve it.

Live

On the fixed release day, with a way back.

Frequently asked questions about ongoing development.

Is your question not listed? Call +31 10 318 0515.

What is the difference with separate assignments?

With separate assignments every project starts again: reading in, planning, quote. With ongoing development a fixed team that already knows your platform works on it. That is faster and cheaper.

Can we change the package?

Yes. If you have a busy period or fewer requests, we scale up or down. We agree that with you per quarter.

What if something urgent comes up in between?

Then we shift within the sprint. If it is an outage, it falls under support and always goes first.

Do we always have the same developer?

Yes, you have a fixed developer who knows your platform. During holidays or illness a colleague from the same team takes over.

Can you develop further on software that someone else built?

Yes. We then start with a code audit or a takeover, so that we know what is there. After that it moves into ongoing development.

The coffee is already on.

Bring your question, your process or an idea that is not finished yet. In a first conversation we map out your situation and you get honest advice on the next step.

Freshly made

How do you take it?