Custom builds · Business & technology consulting

Before you buy software, know what you need.

We map how your company really works, find where time and margin leak, and tell you what to fix with a setting, what to automate and what to leave alone. You get a plan you can execute, with us or with anyone else.

  • Process mapping with the people who do the work
  • A shortlist of what to automate, ranked by what it returns
  • An independent view on buying, building or keeping what you have
Danube screen: Custom builds · Business & technology consulting

Why companies ask for advice

Software projects fail on the brief, long before the code.

Today

Nobody has the whole picture.

Each department knows its own steps. Where the hand-offs break is known only by the clients who feel it.

Today

Vendors answer a different question.

You ask what you need; they answer what they sell.

Today

“We need AI” is not a brief.

Without a concrete task and a way to measure it, an AI project is a demo that never reaches the daily work.

What we do

Three kinds of work, each ending in something you can act on.

Numbers first

We start from what your data already says.

Revenue, margin and workload per client, per colleague and per stage show where the effort goes and what it brings back. Decisions follow the numbers, not the loudest opinion in the room.

  • Which clients, lanes or products make the margin, and which consume it
  • Where requests wait, and for how long
  • A baseline to measure any change against
Danube screen: We start from what your data already says.
Cost analysis

What each unit of work really costs you.

For a fleet, that is the cost of a kilometre; for a service team, the cost of a ticket; for sales, the cost of a won deal. We build the calculation with your finance team and leave it running.

  • Direct costs, fixed costs and overhead allocated by agreed rules
  • Break-even per vehicle, team or product
  • A report you keep using after we leave
Danube screen: What each unit of work really costs you.
Process design

The process drawn as it should run, step by step.

We put the target process on a canvas: who does what, what triggers the next step, what is automated and what stays with a person. The same drawing becomes the specification for whoever builds it.

  • Hand-offs, approvals and exceptions made explicit
  • What to automate now, later, or never
  • A specification a developer or a vendor can price
Danube screen: The process drawn as it should run, step by step.

Screens are from the platform, with sample data. Some show the Romanian interface; the app also runs in English.

Typical engagements

Six questions we are asked to answer.

Each has a fixed scope and ends with a written result.

  • Buy, build or keep?

    Whether to replace a system, extend it or leave it, with the cost of each road.

  • What should we automate first?

    A ranked list of tasks, with the hours each one returns.

  • Are we ready for AI?

    Which tasks suit AI today, which data they need and what must stay with people.

  • Why is the margin falling?

    A cost and pricing analysis on your own records.

  • How do we scale the team?

    Roles, targets, rotation and the reports that make them fair.

  • How do we switch without stopping?

    A migration plan: data, parallel run, training and the day of the switch.

How an engagement runs

Short, concrete and with a written result.

  1. 1

    Kick-off

    The question, the people involved and the data we may look at.

  2. 2

    On the ground

    Interviews with those who do the work, and a look at the real records.

  3. 3

    Findings

    What we saw, with numbers, presented to the people who decide.

  4. 4

    Plan

    Steps, owners, order and estimated cost, yours to execute.

Questions

What people ask about consulting.

Will you just recommend your own product?

No. If a setting in the software you already own solves it, that is the recommendation. The plan is written so that any competent team can execute it.

How long does an engagement take?

A focused question usually takes one to three weeks. The scope and the duration are fixed before we start.

Where does your experience come from?

From ten years inside freight, technology and logistics, building and running the systems we now sell. The method applies to any business that runs on requests, orders and deadlines.

What do we need to prepare?

Access to the people who do the work and, where possible, to exports of the real data. We sign a confidentiality agreement before we look at anything.

Ask the question you would ask a colleague you trust.

A first conversation costs nothing. You leave it knowing whether an engagement is worth it.