Tell us what you’re building.

We read every message ourselves, and reply ourselves. Here is the fastest way to get a genuinely useful answer rather than an acknowledgement.

Send us a message.

Five fields and a description of the work. The budget and requirement questions are there to route your enquiry to the right person, not to qualify you out of a conversation.

Or email support@maku.au

Prefer email? That works too.

Write to support@maku.au and a real person reads your message, rather than an automated ticketing system that categorises it before anybody on the team has looked at it.

Send a few honest paragraphs rather than a single line. The more context we have at the beginning, the faster we can give you an accurate answer instead of a list of clarifying questions.

What to include.

Whether you use the form or email, these are the details that let us answer properly the first time.

  • What you’re building, described in your own words
  • Who it’s for, and what those people currently do instead
  • What success would look like six months after launch
  • Your timeline, including any deadline that genuinely cannot move
  • A rough budget range, even an uncertain one
  • Your current website address, if you already have one

None of it needs to be polished. An unfinished description of a real problem is considerably more useful to us than a tidy specification written to sound impressive.

What happens next.

We usually reply within one business day, with either a straight answer or a short list of follow-up questions about the parts of your brief that would change the estimate significantly.

If it looks like a good fit on both sides, we’ll arrange a 30-minute call to work through the details before anything is formally scoped or quoted.

Hacked site?

Put HACKED in the subject line and we’ll treat it as urgent, ahead of the general inbox. Read how we handle hacked WordPress sites while you are waiting to hear back from us.