AI Email for Adelaide Businesses

No. Yes AI is a Melbourne business, Australian owned and operated, and we deliver to Adelaide clients remotely. There is no Adelaide team and no local presence. On the timezone: Adelaide runs on ACST and ACDT, which puts you thirty minutes behind us. That is a trivial difference and we are not going to inflate it into a selling point — it means a 9am meeting for you is a 9.30am meeting for us, and that is the entire story. The only practical consequence worth knowing is that we are awake and working the whole of your business day, which is more than can be said for a supplier in a genuinely different timezone.

No, on both counts, and this is the most important thing on this page. Yes AI is not a member of the Defence Industry Security Program. We hold no security clearances. We have no facility accreditation. That means we cannot handle classified material at any level, we cannot touch anything under the Defence Trade Controls Act 2012 or ITAR-adjacent export controls, and we cannot be part of a workflow where controlled technical data might reasonably end up in the mailbox we are reading. If your correspondence carries any of that, we are the wrong supplier and no amount of configuration fixes it. What we can work on is the large, boring, entirely unclassified administrative load that surrounds a defence supply chain — and there is a great deal of it.

More than you might think, because the unglamorous majority of a supply-chain contractor's inbox is not sensitive at all. Tender and RFQ queries about closing dates, formats and clarifications. Chasing suppliers for parts, dates and paperwork that has not arrived. Quality-record follow-ups — the endless loop of requesting a certificate, being sent the wrong one, and requesting it again. Purchase-order acknowledgements. Onboarding correspondence with new subcontractors. Invoice and payment queries. None of this is classified, none of it is export-controlled, and all of it eats the day of someone whose job was supposed to be something else. That is the honest opportunity, and it is a real one.

Design, not a promise. The workable approach is a mailbox boundary rather than a filter: the AI reads a specific, separately-addressed mailbox that only ever receives the correspondence classes agreed at setup, and it has no access to your main mail store, your engineering systems or your document repositories. Anything that must not be read simply never arrives where the system can see it. We will also configure hard exclusions on senders, domains and keywords as a second layer. What we will not do is claim that a keyword filter makes an uncleared system safe for controlled material — it does not, and any vendor telling you otherwise is selling you a compliance problem with a nice interface. The boundary has to be structural, and your security officer should be in the room when it is drawn.

It makes it less visible, which is not the same as easier. South Australia is one of the jurisdictions without state privacy legislation. The SA public sector runs on an administrative instrument — Premier and Cabinet Circular PC012, which sets out Information Privacy Principles for agencies — rather than a statute with the enforcement machinery that implies. The practical consequence for a business is that your obligations sit in two less obvious places: the federal Privacy Act 1988 and the Australian Privacy Principles where they apply to you, and your contracts. If you supply an SA government agency or a prime contractor, the privacy terms you are bound by are the ones in the agreement you signed, and they are frequently stricter than anything a state Act would have imposed. So the question is not "what does SA law require" but "what did we promise in the contract" — and that is a question worth answering before an AI reads the mailbox, not after.

To a model provider, which is the part worth understanding. For the AI to draft a reply it must first read the email, so the contents are sent to whichever provider runs the model. If that provider is overseas, that is a cross-border disclosure under Australian Privacy Principle 8 of the Privacy Act 1988, and you remain accountable for what the recipient does with it. We will tell you, per component, exactly which provider processes what and where it runs. What we will not do is give you a blanket assurance that your data never leaves Australia, because for anything involving a large language model that claim needs to be examined rather than asserted — and in a supply chain where you may have to answer for it in an assurance questionnaire, you want the examined version.

It can be configured to, and for anything that makes a claim we will argue against it. Australian Consumer Law applies to what your business says regardless of whether a person or a model typed it — an automated misrepresentation is still a misrepresentation, and the liability is yours. A model will confidently agree to a delivery date you cannot meet or quote a price you did not authorise, in your house style, which is what makes it hard to spot. Where auto-send is genuinely fine is acknowledgement traffic that asserts nothing: "we have received your RFQ, your reference is X, we will respond by Thursday". Everything that commits you to something waits for a person.

The correspondence pattern is similar to the supply-chain one, which is why it works. A winery distributing across multiple markets runs a permanent background hum of distributor enquiries, freight and logistics chasing, cellar door booking requests, wine club member questions, and the documentation trail that export requires. Most of it is repetitive, most of it is time-sensitive, and almost none of it needs judgement — it needs someone to actually do it, promptly, which during vintage is exactly who you do not have spare. The AI drafts, your person approves. Where it earns its keep is the chasing: the follow-up that everyone intends to send and nobody does.

Plans start at $149 per month, and the pricing page lists all three tiers with what is in each. Whether it pays for itself is arithmetic you can do without us: count how many emails a week are genuinely routine, and work out what the person currently handling them costs per hour. If your inbox is mostly novel, judgement-heavy correspondence, the drafting will not save you much because you will rewrite the drafts. If it is mostly the same forty questions, chasing and acknowledgements, that is where the time comes back. We would rather say that on a free call than have you discover it in month two.