Skip to content

Case studies.

Real Bedstone-delivered work that operates in production. We are deliberate about which engagements we publish, and we ask client consent before naming names. The work below is what we are allowed to show. More case studies are landing through 2026 as engagements mature and consent lands.

Thirteen entities, five systems, one place to work.

An Australian group running more than a dozen entities coded every supplier invoice by hand against spreadsheets and memory. We left the existing systems alone and built the context layer above them: every invoice resolved to the right entity and job, verified against the supplier's own history, routed for approval, and recovered where the cost belonged to someone else.

Read

Australian construction SaaS. Standards, operated as software.

Multi-tenant SaaS we built and operate for the Australian construction sector. Manages standards compliance, project documentation, and team workflows for AU builders. Live in production with active customer use, with a v2 rebuild on AWS shipping through 2026. Client name withheld at their request.

Read

Operational AI for industrial engineering

Active build with an Australian industrial engineering operator on operational AI for plant and field operations. Case study landing once the engagement reaches a publishable milestone and consent is confirmed.

Further case studies through 2026

Additional Bedstone engagements across financial services, mining, and government will be published as they reach a state we and the client are comfortable making public. Engagement-letter-stage case studies are not published. Live, operating systems with measurable outcomes are.

Why we publish so selectively

Most agency case studies are aspirational. The build is described in past tense, the metrics are loosely sourced, and the client is anonymised behind a stock-photo executive. We don't run that pattern. Case studies on this page are:

  • Delivered. The system is built and operating in production. Not a slide deck, not a phase-one demo.
  • Operated. We are still on the bridge. The case study reflects what we are responsible for today, not what we shipped and walked away from.
  • Consented. The client agreed to the framing. Where the client has not agreed to specifics, we leave those specifics out rather than approximating them.
  • Honest about scope. If we delivered one piece of a larger system, we say so. If the metrics moved partly because of work outside our scope, we say so.

The result is fewer case studies, published more slowly than the market average. The trade-off is that everything on this page is defensible under direct questioning.

Want a reference call instead of a written case study?

For prospects evaluating us on a real engagement, we can arrange a direct reference call with a current or past client where consent allows. Reach out and we will scope the right reference for your situation.

Start a brief · What to bring to the first call · Pricing and engagement structures

Start a brief