We automate the paperwork your team still does by hand.

Your quotes take four days. Your follow-ups don’t happen. The same details get typed into three systems. Nullnil builds the automation that removes those steps — and the website behind it. Auckland.

The problem

Every business runs the same five stages

Whether anyone’s named them or not. And most businesses leak work and money at all five — quietly, every week, without anyone putting a number on it.

  1. 01

    Be findable

    You don't look like a real business

  2. 02

    The enquiry

    The reply lands two days later

  3. 03

    Win the work

    The quote takes four days

  4. 04

    Deliver & get paid

    The same details, typed in three times

  5. 05

    Keep them

    They never hear from you again

Find yourself on it. Most owners can point at the stage that's costing them the most within about four seconds.

Where does yours leak?

None of this is a technology problem. It’s work being done by hand that doesn’t need to be.

  • 01Be findable

    A site built years ago that loads slowly, no enquiry form worth the name, and a half-filled Google listing. When someone does look you up, nothing about it reassures them.

    Enquiries that never even start.

  • 02The enquiry

    Enquiries arrive in a shared inbox nobody owns, or a phone that rings out while everyone's on a job. Nothing happens automatically in the meantime.

    Someone else replied in twenty minutes and won it.

  • 03Win the work

    Quotes and proposals built by hand in the evening, one at a time. When they go quiet, nobody chases them.

    The biggest and most measurable loss in the business.

  • 04Deliver & get paid

    One job re-keyed between the system that scheduled it, the one that ordered the parts, and the one that invoices for it. Invoices raised late, debtors never chased.

    Your cash, sitting in someone else's bank account.

  • 05Keep them

    No reminder, no service recall, no reorder prompt, no reason for a past customer to think of you first.

    The cheapest work you'll ever win, left on the table.

What we do about it

Two jobs, one pipeline

The front of the pipeline is being findable and not dropping the enquiry. The back of it is quoting, delivering and getting paid. They meet at the point most businesses lose things — the ninety seconds after an enquiry lands, where the web side hands over to the systems side and nobody owns the gap.

Stages 02–05

Automation & AI

The manual work between an enquiry arriving and the money landing. This is the core of what we do.

  • Quotes generated from your own numbers instead of typed out
  • Follow-up that happens whether or not you remember
  • Supplier invoices and orders read and entered without anyone keying them
  • The same details moving between your systems once, not three times
  • Invoices raised on completion, and chased on schedule
  • Past customers brought back with reminders and recalls

Stages 01–02

Website development

The front door: existing properly, and not dropping the enquiry when it arrives.

  • A fast site that reads as a real business on a phone
  • Built search-ready — correct titles, structure and a complete Google listing
  • Enquiries routed somewhere accountable, with a reply that goes out straight away
  • Booking and quote-request forms that feed the automation behind them

On AI

Everyone’s telling you to use AI. Almost nobody’s telling you where.

Most of what gets sold as business AI is a chatbot that gets switched off within a month. We start with your actual process — the quotes, the orders, the invoices, the enquiries — and work out which parts of it AI genuinely handles well, which parts just need two systems joined up, and which parts shouldn’t be automated at all.

Where it earns its keep: reading supplier invoices and orders so nobody types them in. Sorting an enquiry and drafting the first reply. Turning a photo of a handwritten job sheet into a record. Answering “what did we quote them last time?” from your own files.

And the rule we build to: nothing an automation writes reaches your customer until one of your people has seen it. That’s thirty seconds of checking, and it’s the reason this is safe to run at all.

Where we’d tell you not to use it

  • Anything where a wrong answer reaches your customer, or a regulator, unchecked
  • Decisions about people — hiring, performance, who works which shift
  • Work that has to be right every single time rather than almost always
  • Anything two systems talking to each other would fix more cheaply and more reliably

How we work out which is which

  • We look at your process first, not at a demo of something we want to sell you
  • Every leak we find gets one of three verdicts: AI does this well, this just needs plumbing, or don’t automate this
  • You get that in writing, and you keep it whether or not you build anything with us

Being clear

What we don’t do

A short list, on purpose. We’d rather you found this out here than three weeks into a conversation.

  1. Marketing, ads, SEO or social

    We fix what happens after an enquiry arrives, not getting more of them. If more customers is the problem, we're the wrong people and we'll say so.

  2. IT support, email security or backups

    We'll set up the access our own work needs, properly. Anything broader is an IT company's job, not ours.

  3. Chatbots with nothing behind them

    A bot with no process behind it gets switched off within a month. We automate a named task or we don't touch it.

  4. Anything sent to your customers unchecked

    Nothing an automation writes reaches a customer without one of your people seeing it first. We build it that way on purpose.

How it works

How an engagement runs

Four steps, in order, and the first one is free. We won’t quote a big build off a single conversation — until we’ve looked properly at your systems, any number we gave you would be a guess, and a guess is no use to either of us.

01

A free call

30 minutes, no charge. You describe what's slow; we ask the questions we'd ask any new client. You'll leave knowing whether we can help and roughly what it would cost.

02

The audit

We map how your business actually runs, put a number on every place work and money leak out, and hand you a prioritised list — including which parts AI genuinely helps with and which it doesn't. Fixed price, one to two weeks.

03

The fix

We build whatever closes the biggest gap first — usually the quoting and follow-up, sometimes the data entry, sometimes the website. Fixed scope, agreed in writing before we start.

04

Keep it running

Your software changes without warning, and things that worked stop working. A monthly plan watches it, fixes it, and keeps improving it.

Straight up

Who this works for, and who it doesn’t

We’d rather tell you now than take your money and disappoint you in a month.

This is for you if

  • Six to fifty people on the tools or at the desks
  • You're turning work away, or you're visibly backed up
  • The owner still makes the call on something like this
  • Every job needs a quote, a booking and an invoice
  • There's a way you do things — even if nobody's written it down

Probably not, if

  • You need more customers — that's a marketing problem, and marketing isn't what we do
  • Under about six people — you'd be paying us to solve something you can still do yourself
  • Big enough to have your own IT person or agency on retainer
  • You want IT support, email security or backups — that's an IT company's job, not ours
  • You want a cheap website on its own, with nothing behind it

Where to start

Start with a conversation

No charge and no pitch. If we’re not the right people for the problem, we’ll tell you and point you somewhere better.

Free · no pitch

30 minuteson the phone or a video call, whichever suits

You tell us what’s slow or manual. We ask the questions we’d ask any new client. By the end you’ll know whether we can help, roughly what it would involve, and what it would cost.

We work evenings and weekends, so there are a limited number of slots each week. Trades tend to ring rather than book — info@nullnil.net works just as well.