Practice 1 · build

Workflow automation in three stages: Workshop, Build, Evolve.

Start with a free discovery hour. Then a paid Workshop that ends in a written proposal with a process map and a fixed price. The proposal is yours whether or not we build it. Aligned to NIST AI RMF and ISO/IEC 42001, the same governance discipline Cyber Node brings to cyber risk.

Workshop

The Workshop is two to four hours with the people who run the process today. We prepare in advance from the documents you send us, so the session starts at the real questions. It is paid in full at booking.

A$1,500 + GST

Two to four hours, prepared in advance. Paid in full at booking. The proposal is yours whether or not we build it.

Book a free discovery hour

What you get from the Workshop

  • A process map: where the time goes, where the errors come from, and which systems hold the data.
  • A written proposal: what the first version will do, how long it will take, and a fixed price for the Build.
  • A working session with the people who run the process, not a questionnaire.

Most engagements need one Workshop. Where a second is needed, we say so and price it separately. The proposal is yours whether or not we build it.

The journey

1

Workshop

We map the process with the people who run it. You receive a written proposal with a fixed price.

2

Build

Fixed price, scoped in the proposal. One complete first version, with review windows booked up front.

3

Launch

Live in your own accounts, with a handover runbook. Part of the Build.

4

Evolve

Optional and monthly. A standing review, an improvement backlog, monitoring and upkeep.

Build

The Build is a fixed price, scoped and priced in your Workshop proposal. It is delivered as one complete first version, not in pieces. Review sessions are scheduled up front, and your feedback is due inside each review window so nothing waits in an inbox. Extra requests are welcome and flow into Evolve.

What is inside every Build

Three things, every time. What gets built: the agent itself, configured against the workflow scoped in the proposal, with the connectors it needs (email, calendar, CRM, file system, accounting system, whatever the workflow requires), the prompts and tool definitions checked into version control, and the runbook section that documents how it operates and how to turn it off. The guardrails: scope boundaries enforced in the prompt and in code so the agent cannot drift into work it was not built for; rate limits and cost caps so a runaway loop cannot generate a four-figure cloud bill overnight; logging and tracing so every decision the agent makes is auditable. The eval: a small evaluation set of representative inputs with expected outputs, run against the agent before deployment and again after, with the results recorded so you can detect drift the next time you change the prompt or the model.

None of those three is optional. If the eval fails or a guardrail is missing, the workflow does not deploy. We do not ship on hope.

Launch

Launch is part of the Build. The system is deployed into your own cloud, AI and Microsoft 365 or Google accounts, connected to your live systems with a tested rollback path. We run an acceptance walk-through with you, and hand over a runbook: what runs, what to watch, who to call. Everything runs in accounts you own. We hold delegated access to operate, and nothing more.

Evolve

Evolve is optional and monthly. A standing review of what ran and what failed, an improvement backlog prioritised with you, monitoring and upkeep (failures caught, credentials renewed, models kept current, cloud spend reviewed), and a one-page report of what ran, what we fixed and what comes next. New scope lands here once the system has proven itself.

What happens after the Workshop

The proposal is yours whether or not we build it. If you want the Build, the fixed price is in the proposal. If you do not, you keep the process map and the proposal.

This service is not

  • An AI strategy deck.
  • Bespoke ML model development or training.
  • An open-ended retainer with no shipped artefact.

Frequently asked

The Workshop is A$1,500 + GST, paid in full at booking, and it is the only price we publish for this practice. The Build is a fixed price set in your proposal, because it depends on the process and not on the buyer. Evolve is optional and monthly.

Yes. The Workshop is separate, paid work, and the proposal is yours whether or not we build it.

Configurations are documented in the AI model register. The providers used during your engagement are named in the SOW and disclosed in the configuration disclosure standard delivered with the work. The marketing site does not name providers as a matter of voice policy.

No. Bespoke ML model development and training are out of scope. Core Nova works with deployed and pre-trained AI capabilities (LLMs, agent frameworks, AI features inside SaaS products) and helps clients integrate them safely.

Only if you choose Evolve, which is optional and monthly. Without it, the Build is launched into accounts you own with a runbook, and operation sits with your team.

Yes. AI incident response is in scope for engagements where it applies, and can be bought standalone. Scope and price are agreed before work starts. Same incident-response posture Cyber Node brings to cyber incidents.