Five steps, one working system.

Five stages. At every stage you know what you get, when you review it and what happens next.

Every engagement runs in five steps: discover what currently goes wrong, design what resolves it, build in short iterations, integrate with the systems you already use, and scale once it works. You see working software in weeks rather than waiting months for one large release.

The path

  1. Discover

    We walk the process with the people who carry it out, and measure where the hours go today.

  2. Design

    You see the screens and the structure before production code.

  3. Build

    Each iteration leaves a working version you can use yourself.

  4. Integrate

    Connected to your existing systems, tested on your own data.

  5. Scale

    Two weeks of rollout with your team, a follow-up measurement, and who maintains what.

Working session at the meeting table: three people with papers, the Elusive website on the screen
This is what a discovery session looks like: at the table, paper at hand, the screen on.

How long does an engagement take?

A clearly scoped integration usually takes a few weeks. A complete platform can take months. We divide the work so you can review working parts along the way. We discuss dependencies, new findings and extra requests before they change the schedule.

When is custom software not the right choice?

If an off-the-shelf package covers most of your process and what remains is a setting or a single integration, custom software is too heavy. We say so in the first conversation, and we name the package or integration we would pick ourselves. Custom work pays off where your process sets you apart, or where people work around their software every day.

What is expected from us?

One person who can make decisions and is reachable, plus access to the people who currently do the work. That second one matters more than it sounds: whoever runs the process knows the exceptions, and it is exactly those exceptions that decide whether the system works.

How do you make sure the team actually uses it?

By rolling it out together instead of only handing it over. We start with one process, not five at once. In the first two weeks after go-live, the people who work with it report what is wrong or could be better, and we adjust it. Only once that process is genuinely in use do we pick up the next one. Software the team helped shape gets used. Software that is imposed gets worked around.

What happens after delivery?

We agree that up front, not afterwards. Software that stands alone needs little maintenance. Software hanging off external systems has to change when those systems change. Either way, you know who to call when something stops and what that costs.

Clear ways to work together

Three shapes, depending on how large the question is. Every track ends with software running in production that belongs to you.

  • Sprint

    Fixed scope

    One defined deliverable: an integration between two systems, a recurring step that disappears, or an internal screen that does not exist yet. Scope and price are fixed upfront.

    • One clearly scoped outcome
    • Delivered production-ready
    • The code and documentation are yours

  • MVP

    Production-ready

    A first version of your product or platform that real users can use. How long it takes depends on the scope, usually a few weeks.

    • Complete application: screens, database and integrations
    • Set up to keep building on after v1
    • Code, infrastructure, and data are yours

  • Partnership

    Ongoing

    Fixed build capacity per period, for organisations that keep extending. New parts, integrations and automations delivered to a steady rhythm.

    • Fixed build capacity per period
    • You set the priorities together with us
    • The system stays yours

At a glance

SprintMVPPartnership
WhenOne clearly bounded needA first version for real usersKeep shipping, continuously
SizeOne outcomeA complete v1A roadmap at a fixed cadence
TimelineSet by the scopeUsually a few weeksOngoing
Your roleScope up front, then handoverReview each iterationSet priorities together
OwnershipFullFullFull

A Sprint starts at 999 euro. For an MVP or a Partnership it depends on scope; we share that figure during the intake.

Is this where your organization gets stuck?

Describe briefly where the work piles up. In a thirty-minute call we walk your process and decide whether custom software returns anything here.

Does one of these sound familiar?

Book an intro call