What it costs

Work directly with the engineer responsible for delivery. We agree
the scope, price basis and documented handover before work begins.

Use the hourly rate and booking discounts below to plan a review, a
project or ongoing engineering work. Amounts exclude VAT and are
starting points for a quotation, not a fixed price for an
unspecified task.

Before work starts, we agree the scope, deliverables, responsible
people and billing basis in writing. Changes are priced before they
are made. The terms explain payment, ownership and liability; the
service levels cover defects, operating agreements and handover.

Price

From 1,400 DKK an hour, excluding VAT — and less per hour the longer
the booking.

  * the hour: from 1,400 DKK

  * the day: from 9,842 DKK (1,330 DKK an hour — 5 percent less)

  * the week: from 46,620 DKK (1,260 DKK an hour — 10 percent less)

  * the month: from 190,400 DKK (1,190 DKK an hour — 15 percent
less)

A Danish working week is 37 hours, so a day here is 7.4 of them and
a month about 160. The longer the booking, the lower the hourly rate
it is worked out from. Every figure on this page excludes VAT,
currently 25 percent.

Three ways to work with us

A second opinion

You have something running and you want to know whether it is built
well, what it will cost you later, and what to fix first.

What you get. A few days of our time, and a written answer you can
hand to somebody else: what is there, what will hurt, and the order
to deal with it in.

A piece of work with an end

You know what you need built. A pipeline, a database that stops
falling over, a platform, a system moved somewhere better.

What you get. A scope and a price agreed before we start, the thing
itself, and the documentation that lets your own people run it
without us.

A regular part of the week

You want the engineering there on a standing basis, without hiring
for it — a day a week, two days, whatever the work actually needs.

What you get. Agreed hours each week or month, the same people every
time, and 30 days' written notice by either side. No minimum term.

Plan a first engagement

These examples show a starting scope we can agree, rather than fixed
packages. Before work begins, we confirm deliverables,
responsibilities, handover and billing in writing. Describe the work
first; any access to systems or data is agreed separately.

A defined software change

What to bring: Describe a workflow, integration or part of an
application you want to change, the system it belongs to and the
constraints it must meet.

What we can agree: We can scope a small delivery with acceptance
checks, documented interfaces and a handover that explains the
delivered code and how to maintain it.

Scope and next decision: Agree which changes and acceptance checks
are included and who accepts the handover. Further features or
ongoing operation are scoped and priced before they start.

Review a database or data flow

What to bring: Describe one database or data flow, the questions it
must answer and the constraints the review needs to consider.

What we can agree: We can scope a review with a written diagnosis
and a prioritised implementation plan that you can hand to the
people doing the next work.

Scope and next decision: Decide whether the engagement ends with the
review or includes implementation. Agree the required information,
access and who will receive the handover before work starts.

Review or improve a deployment path

What to bring: Describe one deployment path or operational risk, the
systems involved and who currently operates them. Explain what a
useful change would address.

What we can agree: We can scope a review or implementation with a
documented rollout, rollback and ownership plan, with a handover
explaining how to operate the agreed system.

Scope and next decision: Agree whether operation is included. For
systems we run, incident response times, covered hours and
availability are set in the agreement for that system.

Work through a technical decision

What to bring: Describe one technical or delivery decision, the
options under consideration and the constraints around it. Explain
who needs to use the recommendation.

What we can agree: We can scope a review that hands your team a
written comparison of options, a recommendation and the next
actions, with the reasoning documented.

Scope and next decision: Agree the decision covered, who provides
information and who uses the handover. Implementation or an ongoing
leadership role needs its own agreed scope.

A defined set of design assets

What to bring: Describe your audience, the identity you already use
and the places it needs to appear. Identify the existing material
the agreed work will build on.

What we can agree: We can scope a defined set of design assets,
handed over with usage guidance and editable source files for the
agreed uses.

Scope and next decision: Agree which assets and uses are included
and who provides existing material. Further assets and changes are
agreed and priced before they are made.

Diagnose a device or network

What to bring: Describe the device or network, the symptoms and the
data that must be preserved. Explain the constraints the diagnosis
needs to consider.

What we can agree: We can scope diagnosis and a written
recommendation, handed over so you can decide whether to proceed
with a repair or recovery attempt.

Scope and next decision: Agree the risks, access and scope before
any repair or recovery attempt. The recommendation informs that
decision; the outcome of an attempt depends on the actual situation.

What your own work costs depends on what it is, and we would rather
look at it than guess. The figures above are where the conversation
starts.

hThis page on the web	URL:https://engineer.company/what-it-costs/	engineer.company	70
