One request.
Two actions.
An uncertain retry can cause a duplicate customer action. The team needs to know what occurred before trying again.
For founders and teams running consequential systems
Nilsoft reviews, repairs and builds workflows across people, software and AI — from the process your team keeps fixing by hand to the agent you need to trust in production.
One underlying discipline: establish the state, the decision, the action and its result.
Problems worth solving
Small inconsistencies become expensive when software takes action. Nilsoft follows the work across people and systems so the next decision rests on what can be established.
An uncertain retry can cause a duplicate customer action. The team needs to know what occurred before trying again.
Staff compare records, chase missing handoffs and keep conflicting systems aligned by hand.
A workflow might work in the demo, yet the team cannot establish what it permits or whether the intended effect occurred.
Six ways to start
Start with a clear question. Nilsoft can assess it, examine the full workflow, build a bounded correction, or review a system as it changes. Scope is agreed before an engagement.
You can see the friction, but need a first informed move.
One operating problem or proposed use case. A review of supplied material, a discussion of up to 90 minutes, and a short written assessment with three ranked next actions.
Scope boundary An initial assessment. A broader audit or implementation is scoped separately.
Discuss this workPeople and systems maintain conflicting versions of the same workflow.
Map one existing workflow, its sources and owners, then identify evidenced contradictions, duplicated handling and reconciliation work. Receive prioritised findings and a discussion.
Scope boundary A scoped operational review. Target architecture and implementation are quoted separately.
Discuss this workAn agent can act, but its permission and effects are hard to establish.
Review one agent and one consequential action path across tools, permissions, approvals and available execution evidence. Receive a boundary map, findings and control recommendations.
Scope boundary A focused review. The full seven-deliverable Continuity Diagnostic is a separate AUD $5,000 engagement.
Discuss this workA repeatable task is still being carried by hand.
Implement one agreed routine workflow with established tools and integrations, agreed acceptance checks and a handover.
Scope boundary Requires a clear outcome and straightforward approval rules. Licences, additional workflows and ongoing support are separate.
Discuss this workA consequential workflow needs explicit controls before it can carry more responsibility.
Design and implement one bounded intervention for state, authority or effect verification. Exercise agreed failure and recovery cases, then hand over the controls and evidence.
Scope boundary The entry price covers a scoped intervention. Deployment authority, milestones and support are agreed separately.
Discuss this workA working workflow changes, and somebody needs to keep examining the evidence.
Scheduled monthly review of one agreed workflow’s supplied evidence and changes, with written findings, priorities and a review discussion.
Scope boundary Review at the entry tier. Monitoring, incident response, repairs and support are separately scoped.
Discuss this workStarting prices are in AUD. The scope, inputs, timing, payment and acceptance criteria for each new service are agreed before work begins. Tax treatment follows the Nilsoft invoice and applicable requirements.
A deeper diagnostic
The accepted Continuity Diagnostic examines one bounded consequential workflow across state, tools, approvals and outcomes. It gives your team an evidence-linked diagnosis, proposed remediation architecture and three prioritised next moves.
Explore the full diagnosticContinuity Diagnostic / NIL-CD-001
$5,000 AUD · fixed fee
One bounded AI, automation or operational workflow. Seven deliverables and a 60-minute findings session.
Delivery within five business days after required access, evidence and discovery are complete.
Diagnosis and proposed corrections. Implementation is a separately agreed decision.
Explore a sample diagnosisInside a diagnosis / finding 01
Illustrative sample — synthetic data, not a customer result.
A changed fact. An unchanged permission.
The agent may act on permission that no longer covers the current order. A valid earlier approval is not enough to establish that this action is still permitted.
Proposed correctionBind approval to the relevant order state. Re-read and compare that state immediately before execution; route a mismatch back to the decision owner.
Inspect all three findingsBring the system in front of you
Tell us what happens today, what should happen instead, and where confidence breaks down. We’ll establish the right scope before an engagement.