how we work

Talk, build, deliver.

“We get on with it instead of sitting through endless meetings. We deliver value — straight away, no compromises.”

Digitalbucht is the sister company of Holzbucht: same attitude, different material. Over there, one-of-a-kind pieces are made from wood; here, from code and data.

We work in short cycles, directly with the people who will use the result. Status reports get replaced by something you can click through.

DAY 1 First conversation, 30 minutes. Goal, data situation, deadline.
DAY 2 Fixed-price quote with scope, dates and acceptance criteria.
WEEK 1 Access, data connections, first working piece by Friday.
WEEK 2 First version in use with real users, corrections applied directly.
AFTER THAT Further build-out in two-week steps, or a clean handover to your team.

fixed-price package

A clearly defined result: an app, a dashboard, an automation, a website. The price is agreed up front.

from 2 weeks

sprint subscription

A fixed capacity every month for ongoing work. You set the priorities, we do the building.

cancel monthly
interim & advisory

We take on IT responsibility for a period, or review a quote before you sign it. For a single project with an end date: external IT project manager.

by the day or week

Power BI, metrics and dashboards

Numbers rarely live in one place: an ERP system, a DATEV interface, and a handful of spreadsheets kept current by hand every week. The first step is always connecting these sources properly, instead of gathering them again each time.

DATEV data is the most common special case — it has its own page: DATEV in Power BI, in detail.

A Power BI dashboard then shows what already holds true in the morning, instead of being pieced together afterwards. What it does not do: make decisions for you, or fix data that was wrong at the source. A dashboard makes what's there visible — it doesn't invent better numbers.

A first usable report rarely takes months: once the data connection is in place, the dashboard follows the same rhythm as any other project here — usable after the first two-week stretch, then extended step by step. A sample dashboard shows what that looks like.

tools

Power BI · Azure · SQL · Python · React · React Native · Microsoft 365 · DATEV interfaces · ERP integration

what we don't do

Weeks of workshops before the first line of code · licence sales and commission models · reports nobody reads · projects without a named user