Every enquiry, handled the way you would.

01 Enquiry

Arrives by your web form or an email — and becomes a lead on the spot.

02 Qualify

The AI reads it, fills the gaps and lines up the right questions — in your words.

03 Quote

Your proposal, your number — prepped however you like, never sent without you.

04 Close

A patient follow-up in your voice that stops the moment they reply.

Context — what it knows & what steers it Action — a real thing that happens Code — a certainty, not a judgement

01 How it's built to behave Three layers of context stack up — and steer every decision in the flow below.

        
            LAYER 01
            The universal floor
            Every Leadflow build
          
            Reads and drafts — never sends on its own, never changes a status, never sets a price.
            This layer is what keeps behaviour consistent and bounded. The hard guarantees aren't the
            AI; they're the code underneath it. When the AI is unsure, it fails safe.
          
            “STOP” opts out — in code, before any AI reads it
            A reply instantly cancels every pending chase
            Opt-out re-checked on every single send
            Two gates never automate: the booking time + the price
            AI unsure or erroring → flagged for you, never lost
          
            LAYER 02
            Everything that makes it Aino's
            the layer you help us build
          
            Your business, your voice, and your read on a real project versus a tyre-kicker.
            The more of your operation we map, the sharper this gets.
          
            Transparent LED film · smart film · switchable glass · LED screens
            Your voice — design-led, warm, “let's bring it to light”
            A long spec sale — proposals, not quotes; web & email first
            Real signals — budget allocated? fitout date? which site?
            Your asks — job · site · timeline · budget · a visit that suits
            Your fulfilment — site measure · showroom demo · staged install
          
            LAYER 03
            What it sees in the moment
            this one enquiry, live
          
            For this specific enquiry, right now: the email or form in front of it, the whole thread
            so far, and everything already on this lead's record — what's known, and what's still missing.
          
            This message
            This thread's history
            This lead's record — fields known vs blank

Every layer compounds, then pours into each decision below ↓

02 What it does with an enquiry One enquiry's journey — start to close.

enquiry in

An enquiry lands

A web-form submission, or an email to your inbox — either becomes a lead in seconds.

option · your missed-call line

Your line — +61 2 8211 2705. A missed call fires an instant text-back — and it knows who's calling. A number the system doesn't recognise gets a warm catch-all (“Sorry we missed you — tell us about the project and we'll come straight back”); a client already on your books gets a more personal note, in your voice. Either way the enquiry's captured before the call ever feels missed.

CODE deterministic · certain

Have we met this sender?

An exact match on phone or email, straight against your database. A certainty — not a guess the AI makes.

known

Pick up their thread

Lands on their existing record & conversation.

new

Open a fresh lead

A new record, ready to fill in.

AI · reads & drafts

How real, and how complete, is it?

The AI reads what they wrote — pulling out the facts to fill the blanks, and reading how serious and specced it is. Steered by everything in Layer 02. Low confidence and it's flagged for you — never acted on blindly.

enough to run with

Move to qualifying ↓

It has what it needs to take the next step.

thin / vague

your call — to decide together

Two ways to draw it out

a.Send your hosted enquiry form — the fastest way to get the specs.

b.AI drafts a friendly clarifier → you send it.

An open seam — we'll pick the right default with you, not for you.

AI drafts → human sends

Fill the gaps

Missing the budget? the site? the timeline? The AI lines up the right ask from your question bank — in your words.

The AI writes. You send.

Pre-approve the bank and routine asks can send themselves — earned, and your choice. Anything the AI composes fresh always waits for your tap. The booking time and the price never automate, in any version.

a flexible seam — we'll map this to how you actually quote

The proposal

You quote the way you quote. Today the figure's yours to type — and as you trust it, the system can do more of the running: your rate card, the maths, even a draft for you to approve. However the number gets there, it's always yours, and it never sends until you send it. (You sell proposals, not quotes — the system speaks your language.)

You approve the figure. You send.

When the proposal goes out, the follow-up begins ↓

the chasing you stop doing

The chase that closes it

After the proposal, a patient follow-up on your cadence — Aino's default is day 3, 7, 14, then 30 — and only inside your sending hours. Every word is one you've already approved, and nobody on the team has to remember to chase.

option · set per client

A $3k fit-out and a $400k facade shouldn't be chased the same way. We can wire the rhythm to a deal's size and the timeline it implies — so the bigger, slower projects get the longer, patient cadence. Mapped with you, per client.

The moment they reply, every pending chase stops. Nothing nags a client who's already answered — and “STOP” opts them out for good, in code.

Locked — every version

The AI reads and drafts. Only a human sends.

Every message the AI writes waits for a person. Auto-send is earned, word by word — and it's you who grants it.

Locked — every version

The price is always yours.

Type it yourself, or let the system run your rate-card maths — even draft the figure, as you come to trust it. However it's reached, the number stays yours, and it never goes out until you send it.