Standard Ledger × simplefy.ai

Fractional Chief AI Officer

Momentum towards an AI-native practice

Evidence of how today's work is compounding into an AI-native accounting practice—from live client experiences to connected data, an AI-capable team and a governed operating model.

May–July 2026Prepared 4 August 2026

July snapshot · July 2026

July: live onboarding and the next operating layer

jAIn moved into production and began handling real onboarding. In parallel, Xero access, R&D tooling, platform architecture and organisation-wide skills shifted from separate initiatives into the foundations of Standard Ledger's AI-native practice.

Evidence confirmed in July

  • jAIn launched in production on 22 July with both onboarding paths verified end to end.
  • The existing client base was loaded: 424 clients with their entities, services and folder links.
  • The first real client onboarding reached 90% automatic completion, with the remaining fields routed for staff judgement.

Momentum through the months

Starting with July, each snapshot shows where attention was directed across the four capabilities—not effort totals. The 5% squares make the changing shape of the engagement easy to compare.

Production value and the next operating layer

July

Directional view

jAIn launched without rollback

The onboarding platform went live after controlled end-to-end verification, and the first real client moved through the production flow on launch day.

  • Production launch completed on 22 July after both onboarding paths passed controlled tests.
  • New accepted proposals now enter the live onboarding workflow.
  • The full existing client base was available in the production data model.

The next automation portfolio took shape

Xero access, R&D tooling, platform architecture, team training and the wider AI direction were translated from separate conversations into connected workstreams.

  • A general-ledger-first Xero access path was defined as a shared dependency for R&D and future CFO work.
  • The R&D automation repository moved into the Standard Ledger organisation and its three workstreams were mapped.
  • The SL skills marketplace was connected at organisation level on 23 July.
What this enabled
  • jAIn beta stabilisation and expansion into additional service lines.
  • R&D expense automation, CFO workflow discovery and a governed AI ideas pipeline.

Practice-building mix

Primary emphasis 60%

AI-enabled client experience

↑ 20 points from June
AI-enabled client experience jAIn and onboarding
60%
Connected data and automation R&D, Xero and finance automation
20%
Team capability and adoption Skills, training and AI Ops
10%
Strategy and operating model Architecture and future direction
10%

Each square represents 5% of the month's focus.

Capability shipped and transferred

June

Directional view

Seven SL-specific skills moved into a maintained product

The first skills tranche expanded from three ideas to seven working skills, supported by contribution guidance and an organisation-level distribution path.

  • Seven skills shipped in the SL plugin release on 10–11 June.
  • Team setup guides and the marketplace distribution path were completed for broader adoption.
  • Remco completed an authoring and usage session on 12 June.

jAIn kept advancing toward production

Delivery continued alongside the skills launch, preserving momentum toward the July production cutover rather than treating capability work as a separate initiative.

  • The client, entity and service model became the stable foundation for onboarding across service lines.
What this enabled
  • The SL-wide skills marketplace connection completed in July.
  • A practical team-training program that can build on real SL workflows.

Practice-building mix

Primary emphasis 45%

Team capability and adoption

↑ 15 points from May
AI-enabled client experience jAIn and onboarding
40%
Connected data and automation R&D, Xero and finance automation
10%
Team capability and adoption Skills, training and AI Ops
45%
Strategy and operating model Architecture and future direction
5%

Each square represents 5% of the month's focus.

Discovery into reusable foundations

May

Directional view

AI work became a repeatable capability

The shared SL skills repository was established under Standard Ledger's ownership, creating a maintained home for the skills direction that shipped in June.

  • The SL skills repository went live in the Standard Ledger GitHub organisation on 6 May.
  • The AI Ops workstream was shaped around a repeatable set of skills and routines for the SL team.

The engagement gained an operating rhythm

A fortnightly cadence separated jAIn delivery from AI capability work, creating a clearer route for decisions and follow-through.

  • The fortnightly engagement sync was established on 6 May with two parallel agendas.
What this enabled
  • The seven-skill release and organisation-wide distribution work completed in June.
  • A reporting model based on shared workstreams rather than isolated tasks.

Practice-building mix

Primary emphasis 55%

AI-enabled client experience

May baseline
AI-enabled client experience jAIn and onboarding
55%
Connected data and automation R&D, Xero and finance automation
5%
Team capability and adoption Skills, training and AI Ops
30%
Strategy and operating model Architecture and future direction
10%

Each square represents 5% of the month's focus.

Roadmap · April–September 2026

How the work compounds

Live foundations are opening the next layer of the AI-native practice. Every stop retains a clear state so active work, upcoming opportunities and long-term direction stay distinct.

Connections show compounding capability, not a strict delivery sequence.

  1. 01 Delivered Live 22 July; expansion through August

    jAIn launch and expansion

    Stabilise live onboarding, learn from real client journeys and extend the service model beyond R&D and Tax.

    Built from May, June, July

  2. 02 Active First tranche shipped; adoption now

    AI Ops Kit

    Validate the first skills in real use, move them toward default installation and keep improving them through a governed contribution loop.

    Built from May, June, July

  3. 03 Upcoming Four sessions across August–September

    Team training

    Build practical Claude literacy across the Australia, UK and Philippines teams using SL's own tools and workflows.

    Built from June, July

  4. 04 Active Architecture and proof of concept from late July

    Xero access and ecosystem

    Prove a reusable general-ledger access pattern that can support R&D tooling, CFO workflows and later finance agents.

    Built from July

  5. 05 Active Architecture steer from late July

    Platform architecture

    Give SL one governed way to build and operate automations across Google, Zapier, Claude and the SL codebase.

    Built from May, July

  6. 06 Active Discovery complete; detailed work next

    R&D tooling

    Harden the existing notification tools and move the highest-value expense-classification workflow toward a scalable build.

    Built from July

  7. 07 Upcoming Discovery after jAIn stabilisation

    CFO toolkit

    Map the advisory cycle and select the strongest opportunity for AI to improve the quality of analysis and client advice.

    Built from July

  8. 08 Vision Direction being shaped now

    AI vision and ideas pipeline

    Shape a business-level direction for where agents, human judgement and client-facing experiences should reinforce each other.

    Built from May, June, July

The north star · strategic direction, not a delivery commitment

An AI-native operating model for Standard Ledger

The longer-term opportunity is not a collection of disconnected automations. It is a governed operating layer where agents support sales, finance, operations and delivery; staff retain the judgement points; and clients can see progress without relying on email status checks.

  • A governed agent portfolio that creates and completes follow-on work across core functions.
  • A client-facing status and next-action layer built from data that jAIn already captures.
  • A structured ideas pipeline and one sanctioned build path so useful experiments can become shared capability.