Skip to content
Atlas
GET IN TOUCH

D://LEAD39Projects & Consulting

Someone to actually
finish it.

Scoped, managed delivery of technology projects, whether a migration, a rollout, an office move, or a system replacement, with one accountable owner from start to close. It is for organisations with a project that keeps slipping because nobody owns it end to end.

Projects stall for organisational reasons rather than technical ones. They belong to everybody, which means they belong to nobody.

The cost of leaving this alone is rarely one visible failure. It is the slow accumulation: the workaround that became the process, the thing only one person knows, the renewal nobody questioned.

Our starting point is always the same: establish what is actually true today, then decide what to change. Work scoped against an assumption tends to solve a problem you do not have.

  • 01Nobody owns itIt sits with whoever touched it last, which is not the same as being managed.
  • 02No current pictureWhat you have, what it costs, and who has access are all slightly out of date.
  • 03Only handled when it breaksAttention arrives after the disruption rather than before it.

What the engagement covers

Scoped before it starts, so you know what is included and what is not.

  • 01

    Scope and plan

    What is in, what is out, and what finished looks like, agreed in writing before any work starts.

  • 02

    One owner

    A named lead accountable for delivery, rather than a rotating cast of engineers each holding one part of it.

  • 03

    Delivery

    Executed to plan, with changes controlled and priced rather than quietly absorbed until the deadline moves.

  • 04

    Handover

    Documentation and training, so the project ends properly instead of trailing off into support tickets.

Discover, design, deliver, embed

Four stages with a written output at each one. You always know which stage you are in and what comes next.

  1. 01Weeks 1 – 2

    Discover

    We map how the work happens now, including the workarounds people are slightly embarrassed to mention.

  2. 02Weeks 3 – 4

    Design

    Options costed against benefit, so the choice is a decision rather than a preference.

  3. 03Per stage

    Deliver

    Built in slices that reach production and get used, each with a success measure agreed before it starts.

  4. 04Post-delivery

    Embed

    Training, documentation, and a check-in once the novelty has worn off. Adoption is the only measure that counts.

What you should expect

  • Someone other than you owns it, with that written down.
  • The current state is documented and stays documented.
  • Cost is planned ahead rather than discovered at renewal.
  • Decisions are made against evidence rather than assumption.

Questions we get asked

01What is projects & consulting?

Scoped, managed delivery of technology projects, whether a migration, a rollout, an office move, or a system replacement, with one accountable owner from start to close. It is for organisations with a project that keeps slipping because nobody owns it end to end.

02Why do IT projects run over time and budget so often?

In our experience, three reasons account for most of it. The scope was never written down precisely enough to tell when it had changed. Nobody was accountable for the whole thing, so each part was somebody’s second priority. And the work that decides success, which is data and adoption, was scheduled last and estimated optimistically. All three are avoidable, and none of them are technical problems.

03How do you charge for project work, fixed price or time and materials?

Both, depending on how well the work can be defined. Where the scope is genuinely clear, a fixed price is fairer to you because we carry the estimation risk. Where it is exploratory, a fixed price simply means we pad it, so time and materials against a capped estimate is the honest structure. We will tell you which one we think applies and why.

04Can you take over a project that has already stalled?

Yes, and it is a common request. We start with an honest assessment of where it actually is rather than where the plan says it is, which is usually the uncomfortable part. Sometimes the recommendation is to restart a portion of it. We would rather tell you that in week one than discover it in month four.

05Will you work with our existing IT provider on the project?

Yes. We are often brought in for project capacity alongside an incumbent who handles day-to-day support, and it works well when responsibilities are written down at the start. We will be explicit about where the seams are so nothing falls between us.

06What size projects do you take on?

From a single office relocation or a mail migration through to multi-site consolidations and system replacements. If a piece of work is too small to need project management we will say so and quote it as a job, because wrapping governance around a two-day task benefits nobody.

07How much does projects & consulting cost in New Zealand?

We quote after scoping rather than before. Anyone pricing this work without looking at your environment is guessing, and the guess is rarely in your favour. Scoping itself is quick, and we tell you what it costs before we start it.

08How long does it take to get started with projects & consulting?

A first conversation takes about half an hour and costs nothing. Scoping is usually a week or two of our time depending on the size of the environment, and we agree the delivery dates with you before anything is booked in.

09Can you deliver projects & consulting alongside our existing IT team or provider?

Yes, and it is common. We are happy to work as an extra pair of hands under your internal team, or alongside an incumbent provider on a defined piece of work. We will set out in writing where the responsibilities split, so nothing falls between us.

10Do we have to be an existing Atlas client to start a project?

No. This can be delivered as a standalone piece of work for an organisation we have never worked with before, or folded into a managed agreement if you already have one with us. Plenty of clients use us for one thing and keep everything else where it is.

11Do you deliver projects outside Auckland?

Our team is based in Auckland and we attend sites across the wider region. Most of this work is delivered remotely, so we support organisations throughout New Zealand, and we will say up front where being on site genuinely matters.

12Who from Atlas will be on the engagement?

Named people, not a queue. You get a lead who knows your environment and stays with it, which is the difference between explaining your business once and explaining it every time you make contact.

13What happens when the engagement ends?

You keep the documentation regardless, and anything registered in your name stays in your name. Whether we stay involved is your call. Some clients take it in house from there, others move it onto an ongoing agreement with us. We would rather you left cleanly than stayed because leaving was difficult.

Start with a conversation.

Tell us what you are dealing with and we will tell you whether this is the right service for it, and what it would take.

← All services