NLEN
Book a coffee

How we work

We build along with your process.

No thick functional design delivered after six months. Instead, a team that gets to know your process and delivers something every sprint that you use the week after.

Principles

Six agreements that come back in every project.

  1. 01

    Understand first

    We start with the work, not with the technology. Who does what, where does someone wait, what is in Excel and why. We ask the questions you have been putting off.

  2. 02

    Challenge assumptions

    We do not follow a specification blindly. If a step is unnecessary or can be done smarter, we say so.

  3. 03

    Working software, early

    The first module runs after the first sprint. Users test it in their real work and their feedback steers the next sprint.

  4. 04

    One dedicated team

    The same business engineers do the analysis, the building and the implementation. You never have to explain anything twice.

  5. 05

    Next to your ERP

    We always build next to your ERP or another system of record. That is where the administration stays. Our software reads the data, adds what the package cannot do and writes everything back cleanly.

  6. 06

    For the long term

    Software should still fit in five years. We build in modules, so the system can grow.

How we work

From the process as it runs today to software people keep using.

The timeline plays by itself. Click a step or drag the slider. The example follows how we built Clarity for REV’IT!.

Example screen based on the Clarity case. No real client data.

01 Intake

We look at the work as it is done today

Prices in separate Excel files, feedback on samples in emails and photos, specifications in folders. We want to see the process as it really runs.

At ClarityAt REV’IT! the pricing and delivery model lived in separate, home-made Excel files.

02 Analysis

The process on one map

Designers, engineers and product managers tell us what they need. We draw the flow and point out where it gets stuck.

At ClarityNo existing PDM package supported the collaboration between design, engineering and product management.

03 Sprint 1

The first module is running

Product data and specifications in one place, with the safety requirements of materials built in. People use it straight away.

At ClarityClarity was delivered step by step and tested and used in daily practice straight away.

04 Sprint 2+

Sprint by sprint, one step ahead

Feedback on samples goes through an app: take a photo, draw on it, add a comment. Every version is tracked.

At ClaritySolvos built along with the development of the new collection, always one step ahead.

05 Live

Connected and in use

The system runs next to the existing systems and talks to them. Nobody has to retype data any more.

At ClarityClarity was developed, tested, debugged and connected in real time.

06 Afterwards

Software people keep using

Designers have time left for the real work. The process grows, and the software grows with it.

At ClarityClarity saves REV’IT!’s designers 20% of their time. Atlas and the Middleware followed.

Questions

What we often hear.

Why Mendix?

We have built in Mendix since 2013. We model software instead of programming everything. That makes building and changing it faster, and the result runs in the cloud.

Do we have to replace our ERP?

No. We always build next to your ERP or another system of record and connect to it fully. At North Actionsports Group the portal uses the ERP data and writes new data back for administration.

What does it cost?

We work on an hourly basis and discuss up front roughly what a first release takes. Call or email us for a conversation.

A coffee first, then a plan.

A first conversation comes with no obligation. In Uden, at your place or online.

Book a coffee →