About StoneCore

Origin

StoneCore began as a response to a familiar Melbourne pattern: product teams inheriting large automated suites that nobody trusted, while planning still treated “more tests” as the default answer. The practice formed to give those teams a place to buy judgement—strategy, review, and readiness—without hiring a permanent headcount for every decision.

Mission

Help Australian product and engineering organisations decide what QA automation should protect, how deep to go, and which release risks deserve explicit acceptance. We measure success by clearer planning conversations and fewer surprises after go-live—not by the number of scripts produced under our name.

Working approach

Engagements stay small on purpose. One lead consultant owns the relationship, facilitates workshops, and writes the artefacts. We prefer short feedback loops over multi-month programmes that outlive the original question. When implementation work is needed, we recommend partners or your internal squads rather than quietly expanding scope.

Values in practice

• Specificity over slogans — recommendations name suites, environments, and owners.
• Honest exclusions — if a request is really staff augmentation, we say so early.
• Respect for local context — Australian privacy expectations, timezone realities for distributed squads, and the pressure of retail and banking release windows show up in how we schedule work.

People

StoneCore is a boutique practice. Client-facing work is delivered by consultants who have led QA automation programmes and written test strategies inside product organisations—not by generic project managers reading from a framework binder. When an engagement needs a second pair of eyes, we bring a peer reviewer under the same brief.

Community

We contribute field notes publicly when a lesson can be shared without exposing client detail, and we keep office hours in Melbourne for conversations that are better face-to-face than over a ticket.