cadloft

AI for small business in New Zealand, set up inside your business by people who stay

An AI agent is only useful once it has your records, your systems and your way of working in front of it. We do that part on site, and we hand over when your team is running it.

Who it is for

For New Zealand small businesses with no one whose job is the AI. Manufacturers first, because that is where cadloft’s own tools are deepest, and other small businesses are welcome: the agent, the approval rule and the way we work are the same whether the back office makes kitchens or fixes boilers. You keep the systems you have.

What an engagement looks like

The order is fixed; the pace depends on the business. A typical run is a few months, with most of our time in the first weeks.

  1. Map the back office

    We sit with the owner or office manager and write down how work actually moves: enquiry to quote, quote to order, order to invoice, invoice to paid. Where it lives, who touches it, and what gets forgotten. This is a document you keep whatever happens next.

  2. Stand up the agent

    We set up an AI agent on that map, give it its own sign-in to the platform that belongs to your business alone, and switch on only the parts you need. From day one it drafts, prices, files and reminds, and it asks rather than guesses.

  3. Connect your tools and existing systems

    The agent is connected to cadloft’s tools for the common jobs and to what you already run: your Xero, your email, your spreadsheets. We do not replace systems that work; we put the agent in front of them.

  4. Stay until it sticks

    We stay on through the first months, tuning what the agent handles alone and what it brings to a person, and fixing what the map got wrong. Weekly at first, then as needed.

  5. Hand over the day to day, not the platform

    When your team is running the work, we step back from the work. You keep the agent, the records and the map. We keep running what is underneath it: your instance, the upgrades, the support and whatever gets built next. Handing over the typing is not the end of the engagement.

What we keep doing after that

This is a service, not a licence. The engagement does not end at go-live, because a business that stopped changing would be the only kind that could be finished with.

  • We stand your instance up and set it up

    When you ask for it we provision your own instance of the platform and the agents that run on it, configured against the map we made with you rather than handed over as an empty account for somebody there to fill in.

  • We support it, maintain it and upgrade it

    Keeping it running is ours, not yours. Improvements and new parts reach your instance without anyone at your end managing an upgrade, and when something is wrong you tell a person who knows your setup.

  • We build the automations that are only yours

    Some of what a business does is genuinely specific to it: the step nobody else runs, the way only your industry handles that one thing. We build for those, wired into the same records and the same approval rule as everything else rather than bolted on the side.

  • It keeps changing because you do

    A new product line, a second site, a supplier who changes how they invoice: those are changes to the workflow, and reshaping it is part of the arrangement rather than a new project with a new quote.

What the business needs to have

  • An owner with two hours a week

    Someone who can say how the business actually works and make a decision. Without that person the map is a guess and the agent learns the wrong habits.

  • A Xero login

    Or whichever accounting system you use, and the willingness to connect it. The agent needs to see invoices and payments to be useful about money.

  • Email

    A business mailbox the agent can read quotes, orders and supplier invoices from. A Google mailbox connects directly today.

What we never do alone

Nothing leaves the building without a person’s OK. That rule is built into the platform, not written into a prompt.

  • Sending anything to a customer or supplier

    A quote, an invoice or a purchase order is drafted by the agent and sent only when a signed-in person of your business approves it. The agent files a proposal showing exactly what would go out.

  • Approving or paying money

    Approving a supplier invoice or recording a payment is a person’s action. The sign-in the agent holds cannot approve, whatever it is asked.

  • Deleting a record

    There is no delete for anything a person can see. Records are cancelled or archived and the history stays, with who or what made every change.

How your team works with it

Your team asks for things in the channel it already talks in: Slack, Microsoft Teams or WeChat. Raise the quote, chase that invoice, tell me who is on site. A top-tier AI model does the work behind it.

  • Your records stay in your own system

    What the agent reads and writes belongs to your business and is kept in your own account on the platform, rather than scattered through a chat history or someone’s personal sign-in.

  • What was asked, and what was done, is written down

    Every request and every action the agent takes is recorded, so months later anyone can go back and read how something came to be.

  • What one person teaches it, everyone gets

    Correct your pricing or the way you word a quote once and it holds for the whole team, instead of living in one person’s private chat.

Assistants such as Claude Code or Codex are built for a different job, one developer working alone on code, and they are good at it. They are not built to hold a business: nothing that remembers how yours runs, no record the team can read, and no place your records actually live.

The AI behind it

  • OpenAI
  • Anthropic

Where your team talks to it

  • Slack
  • Microsoft Teams
  • WeChat

Systems it connects to

  • Xero
  • SmartPayroll

Questions we get asked

What does it cost?

Talk to us. There are no published subscription tiers; each engagement is scoped to the business and invoiced by us as agreed in writing. Tell us what your back office looks like and we will tell you what it would take.

Where is our data stored?

Information is stored on cloud infrastructure operated by Railway and Vercel, currently outside New Zealand. Under the Privacy Act 2020 we may disclose information to an overseas provider only where it will be subject to comparable safeguards; our agreements with these providers require that. The privacy policy has the full list of who handles what.

Who owns the data?

The business does. Data you enter remains yours, we use it only to provide the service, and you can export it on request while the account is active.

What happens if we stop?

You export your data, and we delete it on request. Financial records that New Zealand tax and employment law requires you to keep are retained for the period the law sets, and then deleted.

We set it up with you

This page is that offer in full. If you would rather see what the tools cover first, the home page lists every module the agent can reach.