Services

10-Day Pilot

See your workflow run as software first. Then decide.

In ten working days we build your workflow as a first version, with your real or realistic data. Your team tests it, and you get a decision paper with effort and possible savings. Flat fee, no slide deck.

Book a callStart a project

A pilot is worth it when the workflow in question ties up at least half a position today, or an investment depends on it.

For whom
For managing directors and teams with a workflow or idea that still needs to prove itself.
Duration
Ten working days
Outcome
Your workflow as software, team test run, documentation, decision paper with savings calculation

Others would have written us a concept. Kevin had something we could try out after three days. So we knew quickly whether it worked before we put serious money on the table.

Matthias MonshausenMatthias MonshausenManaging Director, Powerconcept Monshausen GmbHProject: app for construction plans on site. Client since 2021

What you get at the end.

The pilot isn't the finished product yet. It answers one question: is the build worth it? Everything is documented and reproducible. What's missing for day-to-day operation comes in the build.

  • Your workflow as software

    Does only what's needed, but does it for real. You can run it yourself and you get the code.

  • Test run with your team

    First the demo with your data, then two or three people from your team work with it. Questions, open points and next steps are put in writing.

  • Documentation for your team

    How the parts fit together, which interfaces exist and why we decided what we did. Written so your team, or any other, can carry on with it.

  • Decision paper with savings calculation

    What the build needs (timeline, effort, integrations, risks) and what it could save, calculated with your numbers. The basis for the build offer.

Ten working days, one decision.

This is how a 10-day pilot typically runs. For smaller workflows we combine steps, and the order stays the same.

  1. Day 1

    Sharpen the question

    Kickoff with the person who decides. Afterwards the question and success criterion are written down.

  2. Day 2

    Connect the data

    Access to real or realistic data, a first sample, first surprises.

  3. Day 3

    First end-to-end run

    One case runs through completely once. Not pretty yet, but real.

  4. Days 4 to 6

    Build what matters

    Exactly what answers the question. Nothing that only looks good.

  5. Day 7

    Checkpoint

    Demo with your team. Corrections happen now, not at the end.

  6. Days 8 and 9

    Test with real cases

    Edge cases, error rates, effort. What doesn't hold up gets written down.

  7. Day 10

    Present the result

    Live demo, documentation, decision paper with savings calculation and a clear recommendation.

Typical flow. In the first call we tailor each pilot to your question.

Days you see the current state

A clear workflow, access to data and someone who decides.

We clarify the workflow in the call, or it comes out of an audit. We work best with real data. If that isn't possible, we build with test data in the same structure.

What we need

  • One workflow or question it should be about
  • Access to real or realistic data
  • One contact who makes the subject-matter decisions
  • A test environment on your side, or ours, hosted in the EU

What you can rely on.

  • Day-7 commitment

    If the version on day 7 doesn't meet one of the checkpoints agreed in writing, we show you a new version within five working days until all are met, provided access and data are available as agreed.

  • Fixed amount

    Before the start you get a fixed amount for the scope agreed in writing. We only charge more if you commission additional work. Third-party costs, such as hosting or AI, are listed separately in the offer.

For businesses only. The written offer sets out the details, and your statutory rights remain in place.

If the build isn't worth it, we say so.

A pilot can also show that the data isn't good enough, the effort outweighs the benefit, or off-the-shelf software fits better. Then that's exactly what the decision paper says. You know where you stand, and we don't get a follow-up project. We're fine with that.

Common questions

How is it billed?

Flat fee, not by the hour. Before the start you get a written offer with scope and a fixed amount. How much it is depends on the scope and is clear after the first call.

How fast can we start?

Usually one to two weeks after the call. A first running version is often there after a few days.

Do we need an audit first?

No, you can start right away. If the question is still fuzzy, we take half a day at the start to sharpen it.

Do we get the code?

Yes. Usage rights pass to you on payment. You can develop the pilot further yourself, continue with another team or use it as the basis for a tender.

What happens after the pilot?

That's your call: build with us, continue in-house, or stop. The documentation is written so any team can work with it.

Which workflows suit a pilot with AI?

Processes where one step has to read free text, PDFs, scans or emails, or classify something: orders by email, tenders or product copy, for example. If a fixed rule is enough, you don't need a pilot, just an interface. Examples by area are in our article. AI process optimization

From pilot to product.

After the pilot your workflow runs as a first version, your team has tested it, and you have a decision paper with effort and possible savings. If you like, we turn that into an offer for the build.

If the pilot shows the build isn't worth it, the decision paper says so. You're under no obligation to order anything after that.

More on specific topics

Which workflow should run first?

In 30 minutes on video we find the workflow where a pilot pays off most. Or write it to us and we'll come back with a proposal.

Book a callStart a project

On working days we usually reply within 24 hours.