How We Work
How an engagement runs from the first call to shipped work: the check-in cadence, what stays yours, and what happens when it is not working.
How an Engagement Runs
Every engagement runs to the same marks, from the first call through the check-ins after work starts.
The first call
Twenty minutes. You describe the situation and we say plainly whether we can help, and how.
Delivery plan
A delivery plan with the lead named on it. For an AI engagement, the AI Diagnostic workshop is booked.
Work starts
The build kicks off under the delivery lead, or the AI Diagnostic workshop runs with your department leads.
First check-in
The delivery lead checks that access, tooling and the first tickets are all working, before a day is lost to setup.
Week-one check-in
We check that the work landing matches what you expected, and change the setup if it does not.
Month-one review
A review of the engagement end to end: what has shipped, what has changed, and whether the setup still fits.
What You Own, What We Own
These are fixed on every engagement, not negotiated per client. The split differs by service.
Build Custom Software
Yours
- The scope and the priorities
- Sign-off on the design
- The definition of done
- Handover or run, decided before we start
Ours
- The architecture and the build
- The delivery lead and the project manager
- Staffing the build team
- The delivery flow and the check-in cadence
Develop AI Solutions
Yours
- The pace, and which processes come first
- The decisions the governance record holds
- Sign-off before an agent goes live
- Your enterprise licence and platform choice
Ours
- The training, the risk register and the builds
- Recommending the platform per use case
- Measuring agents against real work before launch
- The delivery lead and the engineers
Code, Data and Access
Your code stays in your repositories, under your access controls, unless we agree otherwise. Engineers work on managed devices with ISO 27001 practices embedded. Adaca is ISO 27001 certified, and we meet SOC 2 Type 2 requirements with the audit pending.
When It Goes Wrong
- The scope has changed.
- Tell the delivery lead. Changes are written into the plan and costed before they start, so what you approved stays what you pay for.
- The work needs to pause.
- A fixed-cost outcome runs to its milestone. A monthly engagement is revisited at renewal rather than partway through, so the commitment is set at the start.
- It has gone wrong with an offshore provider before.
- That is the most common history clients bring. Delivery is led from Australia, the engineering team is ours and has been since 2015, and the check-ins above are how you see the work landing.
Case Studies
Qantas
Collaboration portal for aerospace engineers during aircraft maintenance and repair
Read case study →
ANZ
Real-time CRO dashboard for enterprise risk during the Banking Royal Commission
Read case study →Swiss Agency for Development and Cooperation
Kulmis, a digital platform bringing programme evidence into one analytical environment for SDC's work in Somalia, Kenya, Ethiopia and Somaliland
Read case study →Childcare Centre Desktop
A custom AI assistant for childcare centre staff, built on Claude inside the product's own infrastructure
Read case study →
ShoreTrade
B2B seafood marketplace now powering the new Sydney Fish Market
Read case study →
Cora Group
Real-time supply chain visibility where there was none.
Read case study →
ClearView
Life insurance advisor portal serving thousands of advisors with 99.9% uptime
Read case study →
BikeExchange
Rebuilding a global cycling marketplace as a fully proprietary platform
Read case study →
EY
R&D claims collaboration portal adopted globally from Sydney to New York
Read case study →
Retail Insight
Vendor managed inventory platform for a major retail supply chain
Read case study →
IAG
Multi-brand data dashboard for a major insurer, consolidating over 30 databases
Read case study →
ABL Corp
Custom software engineering for a regulated financial services environment
Read case study →Common Questions
What happens on the first call?
Twenty minutes with a delivery lead. You describe the situation and we say plainly whether we can help, and how.
How long before work starts?
A delivery plan reaches you within 48 hours of the first call. A build typically starts in week two; an AI engagement starts with the AI Diagnostic workshop, booked at the first call.
What are the check-ins?
Three in the first month, at set points rather than on request. One day after work starts, the delivery lead checks that access, tooling and the first tickets are working. One week in, we check that the work landing matches what you expected and change the setup if it does not. One month in, a review of the engagement end to end.
Where does our code live?
In your repositories, under your access controls, unless we agree otherwise. Engineers work on managed devices with ISO 27001 practices embedded.
Do you hold ISO 27001 certification?
Yes. Adaca is ISO 27001 certified, and we meet SOC 2 Type 2 requirements with the audit pending.
Engineers work on managed devices with those practices embedded.
What do we control, and what do you?
The scope, the priorities and the definition of done stay with you, along with sign-off on the design and on anything that goes live. The architecture, the build, the delivery lead and the engineers are ours.
The exact split differs by engagement and is fixed at the start rather than negotiated per client.
What happens if it is not working?
Tell the delivery lead. The check-ins exist so that a problem is caught in the first month rather than the last, and the setup changes if the work landing does not match what you expected.
How long has Adaca been doing this?
Since 2015. Leadership is local, the engineering team is ours, and the model has run in that shape throughout.
Last updated