Every engagement is scoped and quoted to your work, then set out in a written proposal and Statement of Work under our Master Services Agreement, in Australian dollars. You're buying a system and the outcomes it produces — not time on a meter.
The choice is ownership: own the system we build, or subscribe to the capability. Same platform underneath — and we operate it in production either way. We don't do one‑off builds and walk away.
We assemble your system through the Assembly Engine and hand it over. You own it outright and receive a working copy you can take with you.
Skip owning the build. Subscribe to the outcome instead, delivered on the platform we own and operate for you.
Agentic Operations runs your system in production. It's part of both models above — not a separate option, and not optional.
Two parts under one agreement: we build or configure the system around your expertise, then keep it running. Each engagement applies the Assembly Engine's proven patterns, reusable modules and platform methods to your domain — scoped to fit, not restarted as a blank-slate software project.
We design, build or configure the system around your expertise. In the asset model, you receive a working copy you own. In the subscription model, LlamaPath retains ownership and grants access to the capability under the SOW. Either way, the work is scoped and accepted against agreed milestones.
We host and operate it on the platform — kept reliable, secure and current — for a consolidated monthly fee. Asset ownership, subscription access, the operating term and what happens at the end are set out in your agreement.
There's no fixed menu — every engagement is scoped and quoted to your work, built on patterns the Assembly Engine already supports. What moves the figure:
Most client relationships start from $3,000–$5,000 per month, depending on scope and operational requirements. Any one‑time build, onboarding or implementation fee is quoted separately where it applies. We set the full figure out in a written proposal and Statement of Work under our Master Services Agreement before any work begins — a fixed, agreed figure, not an open‑ended meter. Prices are in AUD. LlamaPath is not currently GST-registered, so GST is not charged unless this changes and is stated in your proposal.
Each engagement is quoted in a proposal and Statement of Work under our Master Services Agreement and invoiced in Australian dollars, with payment terms stated on each invoice (typically 30 days). After an accepted proposal and SOW, we invoice you or send a secure payment link through our payment provider. This website does not collect card details.
See our Terms of Use and Billing, Refunds & Cancellations.
Most client relationships start from $3,000–$5,000 per month, depending on scope and operational requirements. Any one‑time build, onboarding or implementation fee is quoted separately where it applies. The figure depends on how closely your work fits patterns the Assembly Engine already supports, plus scope, complexity, hosting and usage, and operating level. We set it out in full in a written proposal and Statement of Work under our Master Services Agreement, in Australian dollars, before work begins. No open‑ended meter. Prices are in AUD. LlamaPath is not currently GST-registered, so GST is not charged unless this changes and is stated in your proposal.
Two parts under one agreement: we build your system, then we operate it. In the asset model, you own the working system; in the subscription model, you buy the capability and results while we own and operate the platform underneath. Either way, you're buying operational capability, not a one‑off deliverable.
You're usually ready when the workflow has already been proven manually, tested with AI tools or automation, and still needs a more reliable operating shape. Strong-fit signals include known bottlenecks, a need for scale, data or capability ownership, custom integrations, monitoring, governance and operational support.
Because a system that's left alone quietly breaks as the services it relies on change. The subscription keeps yours monitored, maintained, secure and current, with known fixes applied where possible and the rest escalated before they sit unnoticed. You're paying for it to keep working.
In the asset model, you own your code and business logic throughout, delivered as a working copy you can run elsewhere. In the subscription model, the end-state is set out in the proposal and Statement of Work. The operating term, and what happens when it ends, are agreed up front. See our Billing, Refunds & Cancellations page for how pre‑paid and completed work is handled.
Tell us about the work you'd like to turn into a system. A short capability assessment is a quick way to see what the platform could run.