Data engineering

Data your company can act on, which begins with agreeing what each number means and who answers for it.

What this practice covers

Each one stands on its own, and most engagements end up touching two or more.

Data governance: Agreeing who answers for the data your decisions depend on, written into a document short enough that busy people actually use it.
Cloud data platforms: Choosing the cloud platform suited to the queries you run most, then standing it up with cost limits in place from day one.
Data migration: Moving your records between systems so that what lands in the new one can be proven against what left the old.
Data warehousing: Gathering the numbers your teams report against into a single place, each given one agreed meaning and one system it is drawn from.

Where to begin

The order matters more than the technology. A platform chosen before anyone has agreed what the key figures mean often has to be rebuilt later, and a migration into a warehouse nobody trusts moves the problem without solving it. Most engagements therefore open with governance, even if only for the handful of numbers a board actually reads, and the engineering follows from those decisions.

Amos builds the pipelines himself, so the definitions agreed in a meeting are the ones that end up in code. The work is sized to the company: a small business with three systems needs far less than a group running a dozen, and the brief is where that gets settled.

Who does the work

Amos Weiskopf has spent more than twenty years writing software and the data pipelines that feed it.

Questions buyers ask

Which of these services do I need first?

If your teams argue over which figure is right, start with governance or the warehouse. If a system is being replaced, the migration comes first. The brief is where that order is settled.

Can you work with the platform we already have?

Usually, yes. A new platform is only worth recommending when the current one cannot carry the work or costs far more than it should.

Is this only for large companies?

No. The work is sized to the number of systems and figures involved, and smaller companies often need only one or two of these services.

What does data engineering cost?

The price depends on how many systems and figures are involved, and is quoted after the brief.

How do we begin?

With a written brief. Say which figures your teams argue over and which systems feed them today, and the scope is worked out from there.

Engagements by written brief.

Work begins from a documented problem statement, not a sales call.

Write a brief Or book a meeting