// Feature sprint

Your next feature
Ready within two weeks

Your software works, but something has been on your list for ages. We build it. In your existing software, with your existing data. Live after your approval.

What fits in
Illustration: Tulipsoft building a new feature for a client in two weeks

// What it is

One feature, two weeks, one agreement

What does it cost you that this feature still does not exist? As long as it waits, your team does it by hand. That time does not go to anything else.

A feature sprint is one feature in your existing software. Up front we agree together on what it needs to do. So we both know when it is done. We take ownership of the result. You approve before it goes live.

// What fits in

What you can have built in two weeks

One feature in your existing software, with your existing data and integrations. A few examples.

  • A new screen or overview

    An overview you now keep in Excel, or a screen your team is missing. Built on the data that is already there.

  • An export or report

    The figures you gather by hand every week are ready with one click.

  • A step that is now done by hand

    An approval, a calculation or a notification someone now has to do themselves. From now on your software does it.

  • Improve an existing feature

    It works, but not nicely. A form with too many steps or a search that does not find what you are looking for.

  • Checked before it goes live

    We build with our AI pipeline. A senior developer checks tests, security and quality. It only goes live once you approve.

  • Does not fit in
    • A new external integration
    • A data migration
    • Changes to login and permissions
    • Software we do not manage yet

    Then we start with a prototype, or plan two sprints. We only run a Feature sprint on applications we manage. Not a customer yet? Then a prototype is the starting point.

// How it works

How the two weeks go

  1. You point out what needs to improve

    In a 30-minute intake we agree together on what the feature needs to do. So we both know when it is done. After that you receive a no-obligation quote with a fixed price.

  2. Week 1, we build

    We do the development in one week. If something goes differently than expected, you hear it from us before you need to ask.

  3. Week 2, fine-tune and go live

    We align and fine-tune. If it does not match the agreement yet, we keep working until it does. At no extra cost. Live after your approval.

// Price

After a 30-minute intake you get a no-obligation quote with a fixed price

The price depends on the feature. That is why we first agree on what it needs to do. Then you know what it costs and when it is ready. No surprises afterwards.

Feature sprintNo-obligation quoteReady within two weeks. Live after your approval.
  • One feature in your existing software
  • If it is not right, we keep working at no extra cost
  • Checked by a senior developer

// FAQ

Frequently asked questions

What does a feature sprint cost?

That depends on the feature. After a 30-minute intake you get a no-obligation quote with a fixed price. If the result does not match what we agreed, we keep working at no extra cost.

What fits in a feature sprint?

One feature in your existing software, with your existing data and integrations. A new external integration, a data migration or a change to login and permissions does not fit. Then we start with a prototype, or plan two sprints. We only run a Feature sprint on applications we manage. Not a customer yet? Then a prototype is the starting point.

What if it takes longer?

Then we keep working until it matches what we agreed. At no extra cost.

Is AI code secure?

That is a fair question. That is why a senior developer checks everything before it goes live. Tests, security and quality.

Pascal Rieder on the phone at his desk

Fancy a coffee?

Which feature has been on your list for a while? In a 30-minute intake we agree on what it needs to do. Then you know when it is ready.

Contact