Before committing budget to delivery, bring the business need, existing systems, and practical options into focus. We work with your team to recommend an approach and define a scope your stakeholders can review.
Already have an agreed scope? Talk to us about Design or Build.
We review the people, workflows, systems, data, and constraints involved to identify the gaps and dependencies that matter.
You get: A documented view of how the work operates today.
We assess practical approaches, explain the trade-offs, and recommend a direction that fits your priorities and constraints.
You get: A recommendation your stakeholders can review and act on.
We set out the proposed work, its boundaries, dependencies, and delivery priorities.
You get: A defined scope for the next stage.
Mapping shows how people, processes, and technology work together. Discovery reveals where work slows down, information is repeated, and dependencies affect what can change. These insights help prioritise improvements and define a practical scope for delivery.
Illustrative example. Findings and recommendations depend on the organisation and agreed scope.
ANZCA Music Examinations
K Stack mapped ANZCA’s examination workflows and supporting systems to identify where administrative effort was concentrated. The engagement established improvement priorities and a phased delivery roadmap, giving the team a clear basis for its next platform investment.
Discovery · Workflow mapping · Platform direction
Plugya
K Stack mapped how office teams and field technicians each work, so one product could serve both. That understanding shaped the design and delivery of Plugya’s desktop and mobile applications.
Discovery · Workflow mapping · Product direction
Every engagement is tailored to your organisation. These examples show the typical workshop involvement, estimated fee, and outcomes for different levels of Discovery.
Around AUD $6,000 + GST
A short, focused engagement for a workflow, feature, integration, or platform decision.
Typical outcomes
Around AUD $12,000 + GST
A broader engagement for work involving multiple workflows, stakeholders, or system dependencies.
Typical outcomes
Fee estimated after discussion
For teams that need Discovery alongside a prototype to explore an experience or test a technical assumption before a larger build.
Typical outcomes
Session counts, fees, and outcomes are indicative. We agree the scope, deliverables, schedule, and final fee with you before starting. A prototype can also be commissioned separately after Discovery.
The findings help you decide whether to test an idea, begin delivery, or improve what you already have.
Use a prototype or proof of concept to explore a user experience or technical assumption before committing to a larger build.
Turn the agreed scope into a focused first release, with clear priorities and boundaries.
Continue with application improvements, additional technical capacity, or fractional CTO guidance as your organisation needs it.
Existing requirements are a useful starting point. Discovery can help review assumptions, dependencies, and delivery options where these still need resolving. If the scope is already agreed and sufficiently defined, we can discuss moving directly into Design or Build.
Yes. Discovery can examine an existing application, integration, or workflow to establish what is getting in the way and assess whether to improve, extend, or replace parts of it.
The examples above are a starting point. Lite typically suits a focused question; Plus allows for broader workflows and dependencies. If a proposed experience or technical assumption needs testing, we can scope Discovery with a prototype. We'll discuss your priorities and tailor the engagement accordingly.
We agree the participants with you based on the scope. Typically, sessions involve the people responsible for the business outcome, those who use the workflow, and those who understand the existing systems. Different people may join different sessions.
Bring the requirements, process notes, system information, and known constraints you already have. We'll agree what else is needed when scoping the engagement. You do not need to arrive with every detail resolved.
Lite and Plus typically focus on understanding the work, assessing options, and defining a direction. A prototype or proof of concept can be scoped alongside Discovery or commissioned afterwards. Production development is agreed separately.
No. Discovery is a standalone engagement. You can take the findings and agreed deliverables to your internal team or another delivery partner. If you choose to continue with K Stack, we'll scope that work separately.
The session counts above indicate workshop involvement rather than the total duration. The schedule also allows for analysis, documentation, and review. We agree the timing with you based on the scope, access to information, and stakeholder availability.
Tell us about the project or decision you're considering. We'll discuss the scope and whether Discovery is the right starting point.