Skip to content

From first message to handover.

What happens from your first message to the day we hand over, and what we need from you along the way.

Step by step.

Most work follows these six steps. A Review moves through them quickly; a project takes longer.

Step 1

You tell us what’s going on.

A few lines on WhatsApp or the form is enough: the system, what’s wrong and what it’s costing you. We reply with where we would start, or the one or two questions we need answered first.

  • What the system does and who uses it
  • What is going wrong, with a real example
  • What you need first, and by when
  • Roughly what you can spend
Step 2

We pick the right starting point.

Usually over a short call. We work out which service fits, and say so plainly if none of ours do.

  • Review for one decision, or when nobody knows what is wrong
  • Fix Sprint for one clear problem
  • Managed Delivery or a Custom Project when the need is bigger
Step 3

We look before we promise.

Before we commit to a price or a date, we check how the system is built, where it runs and who controls it. If we can’t see enough, we tell you what is missing.

  • Code, hosting, database and domains
  • Who holds which accounts and passwords
  • How changes are released, and how to undo one
  • How staff actually use the system day to day
Step 4

We agree it in writing.

You get the price, what is included, what isn’t and how the result will be checked. Work starts once the agreement is signed and the first payment is in.

  • The price and when it is paid
  • What done means for the first piece of work
  • Who on your side decides and approves
  • What we need access to
Step 5

We build, test and release.

Work goes out in small pieces your staff can check with real cases before anyone relies on it. Nothing goes live without your approval.

  • A test system wherever the setup allows one
  • Checked with real orders, invoices or records
  • Your approval before release
  • A way back if a release goes wrong
Step 6

We hand over cleanly.

When the work ends, your team or the next vendor gets what they need to carry on, and access we no longer need is removed.

  • Code and documentation in your accounts
  • Notes on how the system is set up, released and run
  • Open issues and risks, written down
  • Our access removed or handed on

Progress, written down.

On Managed Delivery, you get an email every Monday: what we did, what is confirmed and what we need from your team.

It is short enough to forward to your boss or your CFO, and nobody on your side has to chase us for a status.

Antdragon

to me

Mon, 9:04 AM

Order system update

Hi all, here is our update for last week.

Progress

  • Branch sales report released. Totals now match accounting
  • Purchase order approvals are on the test system

Confirmed

  • Orders above RM10,000 need a second approval

Action needed from your team

  • The approver list by Wednesday, so we can release

We will continue with the non-blocked work in the meantime.

Technical Lead, Antdragon

Tell us what isn’t working.

A few lines is enough: the system, what’s going wrong and what it’s costing you. We’ll reply with where we would start.