Skip to content

Software that knows your steps, for work that got stuck in Excel.

For companies and small product teams whose work is split across spreadsheets, mail and three tools. We build one app that knows the steps you already take, with the records that must stay closed.

Custom software

When Excel became the source of truth, or three systems spell the same customer three ways, we build one place. An app with sign-in, roles, and the flow you walk us through. No platform deck, no twelve weeks of discovery. The StepQuests admin, Weekboodschappen's internal ops, the Bar Boef CMS: that kind of tool, then for your company.

Who the users are, the steps they take today, and which records must stay closed.

What you get

Sign-in, roles, the screens of the real work, and data in Postgres or a similar store. Migrations in files, not loose SQL on production. Errors a colleague can read. Source after payment, with an agreement on what we reuse internally.

How we start

We start with who the users are and the steps they take today, including the ugly exceptions. Then a thin slice that already clicks: one task that hurts now. A price estimate for that slice, then more in sprints. Scope that shows up later gets named immediately.

When this fits

This fits when the work is yours and a shelf product misses the steps. A public marketing site belongs with web. A product with accounts for customers who pay belongs with SaaS. The software-fit quiz suggests a shape if you are still deciding.

Ready to tell us what you need?

Sketch the steps that now live in Excel or mail. We come back with a shape and a price estimate. The quiz is five questions if the shape is still open.

Questions about this work

Could we just buy a shelf product?
Sometimes. If a shelf product covers the steps, we say so in the reply. Custom work is for when three tools spell the same customer three ways, or Excel became the truth.
Who owns the code?
Custom work moves to you after payment. Shared internal libraries we agree separately. That sits in the terms, named before we start.
Do I need developers on my side?
No. We design, build and ship. If you do have someone, we work with that person, on the same repo.
How do you protect sensitive records?
Say in the form what must stay closed. We put rights per role, secrets outside git, and logs where you can find a failure. A pentest is in the delivery only if it is in the job.