Neto

Neto runs the store. AI keeps it moving.

We run Neto for our own online store, with tens of thousands of products, and we've joined it to the CRM, the workshop and the phones. We do the same for yours, then train your team.

Built and running

What we wire around Neto.

All of it runs at Tune Cycles today.

Orders into the CRM

Every order lands as an opportunity that moves through picked, packed and shipped as Neto fulfils it.

Customers, consent included

Customers and prospects kept in step with the CRM, with their newsletter and SMS opt-ins carried across.

Accounts without retyping

A Neto customer account created from the CRM in one step, and workshop customers given an account automatically.

"Have you got one?"

Chat and an after-hours voice agent that answer product and price questions from your own catalogue, refreshed daily, and text a link to the product.

Supplier stock kept current

Supplier stock and cost feeds written into Neto, so the store shows what you can actually get.

Product pages, checked

Product descriptions drafted with AI from the brand's own specs, and checked by a person before they publish.

CRM pipelines including an online order pipeline
Orders as a pipeline
Email campaign reporting: opens, clicks and deliveries
Campaign reporting · sample figures
Safe by design

You approve. AI earns its way in.

Every build starts small and read-only, and gets write access one step at a time.

Dry run first

Every tool shows what it would change, and changes nothing until a person says yes.

You approve what matters

Quotes, refunds, anything sent under your name: a person signs off before it goes.

Customers know it's AI

Chat and voice agents say they are AI, offer a person, and announce recording before a call is recorded.

Your data stays yours

It lives in your own Simpro, ServiceM8, CRM and AI accounts. Nothing is copied into a system we own.

Built to local rules

Call-recording consent, the Spam Act for texts and email, the Do Not Call Register for AI voices, and no AI-written reviews.

Handed over properly

Every build ends with an AI policy and a register of the AI tools you use, with one named owner.

General information, not legal advice.

How it starts

One job first. Measured.

We don't start with a platform. We start with the task that eats the most hours, and prove it.

  1. 01

    A fifteen-minute call

    Which job eats your week? Which system holds it? We tell you straight if AI is the wrong tool.

  2. 02

    We time it

    Minutes per task, on your own jobs, before anything changes. That number is what we have to beat.

  3. 03

    We build one thing

    It runs as a dry run first. You see every change it would make, and you approve it.

  4. 04

    We train the people who use it

    Role by role, on your own system, with your own jobs. The go-to person in the office first.

  5. 05

    A month later, we check

    Is the task faster? Who still uses it? What needs changing? Then we pick the next job.

Every build is quoted before it starts. No platform plans, no lock-in.

Questions

Neto questions.

Is Neto the same as Maropost?

Neto is now part of Maropost, sold as Maropost Commerce Cloud. Most stores still call it Neto, and so do we.

Do you build Neto stores?

We work on the store you have: product data, feeds, content and the connections around it. Ask us about a theme or a rebuild and we will tell you straight whether we are the right people.

Can the AI see our orders?

Only what it needs, read-only first. A customer asking where their order is can get an answer without anyone digging through Neto.

Systems

The systems around Neto.

We don't replace what you run. We wire AI into it, connect it to what sits beside it, and train the people who use it.

Book a call

Find the hours first.

Fifteen minutes, no pitch deck. Tell us which job eats your week and we'll tell you whether AI is the answer yet.

Hayden Nosatti · Leadout · Sydney