Contact
Request a services quotation
Use this form for structured fee and scope indications relating to software delivery, integration assurance, or governance documentation packs for professional counterparties. It is not an offer to contract; submissions are triaged against fit and conflict checks.
Indicative responses describe how we would resource an engagement — roles, cadence of reporting, and typical deliverables — not headline percentages that imply certainty without a signed engagement letter and agreed assumptions.
This page describes professional services scoping only. It is not an offer of securities or other financial products, does not invite applications for interests in managed investment schemes, and is not financial product advice. Any regulated activity would require separate engagement and may involve Australian financial services licensing.
What we typically price
- Discovery and architecture phases through security and privacy sign-off.
- Build, integration, hypercare, and operational readiness with evidence regimes.
- Governance documentation reviews for assurance or procurement forums (non-deal, non-product).
Indicative fee posture (non-binding)
Our fee structures vary by engagement type: time-based retainers for delivery oversight where scope shifts with authority outcomes; capped phases for feasibility where the deliverable is a decision-grade pack; and success components only where permitted by law and expressly set out in an engagement letter. Any percentage or multiplier described in an indicative letter is explicitly tied to assumptions and a named alternative baseline.
Exclusions from indicative responses
Unless expressly included in a subsequent engagement letter, indicative quotations do not cover legal advice, tax advice, independent certifications, or third-party reports purchased in your name. They also do not constitute independent security certification, penetration testing sign-off, or financial viability opinions about suppliers — those require separate professional appointments.
Document pack we may request before pricing
- Architecture diagrams, integration inventory, and known data classifications.
- Latest assurance or audit correspondence and open risk register.
- Current release calendar (even if draft) and incident or change log excerpts.
- For governance documentation requests: existing assumption register or control matrix, if available (not an invitation to invest).
Process
- Intake triage within five business days — we may request architecture summaries and assurance correspondence.
- Internal conflict and capacity check.
- Indicative scope letter with assumptions, exclusions, and next-step workshop options.
By submitting this form you agree we may store and use the information in accordance with our Privacy Policy. Do not include bank account details or identity document images.
Commercial and governance notes
On Australian enterprise programmes, we require independent peer review for cross-domain authentication and authorisation transitions. This is how we protect reputation in production telemetry, not only in marketing collateral. If release windows are tight, we align observability baselines with SLO definitions before traffic ramps toward peak season. The outcome is fewer surprises at go-live and cleaner operational handover. Once control objectives crystallise, we prefer staged releases that map to measurable service health rather than optimistic calendars.
That discipline is what we mean by an integrated delivery and assurance practice. When documentation is thin, we document customer defect triage workflows from go-live through stabilisation weeks. That discipline is what we mean by an integrated delivery and assurance practice. Under current operational volatility, we align consumption charges with metered usage in place and contractual uplift clauses. Architecture packs and runbooks should trace back to the same release version — not parallel narratives.
For security and architecture forums, we evaluate supplier quality systems against incident history on comparable industry patterns. The approach is deliberately conservative relative to headline industry optimism. Once control objectives crystallise, we document escalation paths with explicit responsibility matrices and response targets. That discipline is what we mean by an integrated delivery and assurance practice. In parallel, we stress-test contingency allowances against recent incident data and supplier lead times.
This is how we protect reputation in production telemetry, not only in marketing collateral. In parallel, we require operational readiness plans that include failure drills where customer impact is material. The approach is deliberately conservative relative to headline industry optimism. Once control objectives crystallise, we document interface risks between systems and nominate accountable sign-offs at each boundary. The outcome is fewer surprises at go-live and cleaner operational handover.
Where procurement is competitive, we keep stakeholder communications consistent with contractual fact, avoiding aspirational tone. Architecture packs and runbooks should trace back to the same release version — not parallel narratives. Across hybrid delivery models, we align treasury or billing controls with certification cycles and governance reporting cadence. Architecture packs and runbooks should trace back to the same release version — not parallel narratives. If release windows are tight, we align rooftop or edge compute plans with thermal and power envelopes, not only nominal SKUs.
Architecture packs and runbooks should trace back to the same release version — not parallel narratives. For security and architecture forums, we evaluate programme float consumption weekly against critical dependency drivers. This is how we protect reputation in production telemetry, not only in marketing collateral. From an engineering assurance standpoint, we align control testing to observable deployment events rather than slide-deck milestones alone. This is how we protect reputation in production telemetry, not only in marketing collateral.
If release windows are tight, we stress-test cutover dates against customer change windows and dependent supplier approvals. The approach is deliberately conservative relative to headline industry optimism. If release windows are tight, we align backup and recovery drills with realistic ransomware scenarios and restoration evidence standards. The approach is deliberately conservative relative to headline industry optimism.
Frequently asked — quotations
Is an indicative quotation an offer to contract?
No. It describes how we would resource an engagement under stated assumptions. A binding relationship requires a signed engagement letter and agreed scope.
What will you not price from a web form alone?
Legal advice, tax advice, independent certifications, vendor solvency diligence, and valuations of intangible assets — those require separate professional appointments.