Engine Labs

Boundaries

What we don't do, and what we won't promise.

Most agencies hide this in the fine print. We put it on its own page. If your brief lands here, the Control Centre will say so and offer a referral.

Excluded scope

What we don't do.

We don't build systems that make legal, medical, financial, employment, credit, insurance, immigration, housing or safety decisions on behalf of humans.

Those decisions need a regulated professional, not an agent. Drawn from MSA §3 and Addendum §5 — the contracts disclaim automated regulated decisions, full stop.

What we can do instead

Build the admin layer around regulated work — intake forms for a law firm, supplier paperwork for a clinic, candidate screening drafts for a recruiter to review.

We don't take on production-grade cyber security, penetration testing, SOC2 / ISO certification or regulated compliance ownership.

MSA §3 explicitly excludes “senior software engineering consultancy, cyber security auditor, regulated engineering firm, enterprise architect, or compliance officer” from our role.

Where to go instead

Specialist firms (ASD-aligned consultancies, accredited SOC2 auditors). We can refer; we can't be them.

We don't build mission-critical infrastructure where a failure has material legal, financial or safety consequence.

Pricing §5 lists this as out-of-scope. A one-operator studio cannot meet the redundancy, monitoring and incident-response posture mission-critical work requires.

Where to go instead

A senior engineering firm with on-call rotation and an SRE practice. We're happy to recommend names.

We don't scrape restricted platforms, extract data from sources that breach platform terms, or build mass-cold-outreach systems on unconsented lists.

Addendum §5 and §7 plus ACMA spam rules. The Outreach Engine exists, but only on permissioned data — your CRM, your opted-in list, an existing business relationship.

What we can do instead

Build outreach Engines on top of consented contact lists, with throttling, unsubscribe handling and human review on the first batch.

We don't take on managed hosting, 24/7 monitoring, or enterprise DevOps.

MSA §3 and Pricing §5. We're not a managed services provider. Engines run on your accounts, in your tools, on third-party providers we don't control (MSA §11).

Where to go instead

Managed services providers, or an in-house platform team. The handover pack documents the dependencies so you can decide where to put that capability.

No promises

What we won't promise.

We won't promise a revenue lift, lead volume, conversion rate, response time or AI accuracy number.

MSA §16 disclaims outcome guarantees explicitly. Anyone who does promise these is making it up.

What we will commit to

We commit to: a fixed scope, a fixed price for in-scope work, a defect-fix period, and a documented handover. The outcome is yours to measure.

We won't promise uptime guarantees beyond what the underlying third-party tools offer.

MSA §11. Your Engines run on OpenAI / Anthropic / Zapier / Slack / Stripe and the rest. We don't control them.

What we will commit to

We document the dependencies on day one. If a provider drops a model or changes a price, we tell you and quote any rework.

We won't promise that an AI output will always be correct.

Addendum §4. The human-review step is non-negotiable for anything that touches a customer, contract, account or person's record.

What we will commit to

Drafts queued for one-click send. Confidence flags on extraction. Citations on knowledge answers. The human is in the loop where it matters.

We won't quote a fixed price for unclear scope.

Pricing §7. Larger or ambiguous projects begin with a paid scoping workshop credited against the final fee.

What we will commit to

Open the Control Centre, tell us what's slowing you down, and we'll either give you a band or recommend the workshop.

Why

Why we publish this.

Showing the boundaries closes faster than puffy claims. For a senior buyer making a A$3,500–A$8,500 decision, explicit exclusions are a trust accelerator, not a deterrent.

The language on this page is drawn directly from the contract pack — MSA §3, §16, Addendum §5, Pricing §5–§7. There is no version of these statements that sales-friendly copy can soften without breaking the contract underneath.

If your brief looks like one of these categories, we'll decline politely and tell you where to go. You'll get the explanation in plain English, not a vague “not a fit”.

Referrals

Where to go instead.

Generic recommendations only — we don't take kickbacks, and we don't have any formal referral arrangements.

  • SOC2 / regulated compliance

    an accredited auditor

  • Penetration testing

    a CREST-registered Australian firm

  • Lawyer

    your jurisdiction's law society referral service

  • Financial / tax adviser

    a CA-ANZ or CPA Australia-registered practitioner

  • Mission-critical SaaS engineering

    a senior product-engineering consultancy (we'll suggest one if you ask)

Get started

Use the Control Centre anyway — we might still be the right fit.

Most briefs we see have one regulated layer wrapped around a perfectly buildable admin layer. The Control Centre will tell you which is which.

Open the Control Centre