§00 · Workflow Lab · Founder Days

One repeated workflow.
One full day.
A reviewable AI work product you can sign your name to.

For tax, accounting, consulting, and professional-services operators who know AI should help — and are tired of prompt tips, vendor demos, and ad-hoc ChatGPT no one will defend on a real client file.

Book a free Workflow Diagnostic
FREE · SHORT CALL · KUAN READS YOUR INTAKE PERSONALLY AND EMAILS YOU A TIME WITHIN ONE WORKING DAY · NO PAYMENT YET · IF THERE'S NO VALUABLE WORKFLOW, THE ANSWER IS NO-BUILD.
FormatPrivate 1-on-1 Lab day · live online
InvestmentUS$500 founder day · 1-on-1 with Kuan
OutcomeMapped workflow + review gates + AI-assistance plan
MethodThe AI Workflow Map

Already decided? Book a US$500 founder day →

DRAFT · v3
AWM—01 WORK PRODUCT
CLIENT MEMO · TAX POSITION · FY26
Recommendation on the
incentive position for
[ client name ].
AI Background extracted from prior memos & source-of-truth file. S.01
AI Position drafted from precedent + technical references. S.02
AI Comparable cases assembled; cross-checked against schedule. S.03
HUM Judgment call on incentive applicability — owner: Director. REV.1
HUM Factual accuracy spot-check; provenance of every figure. REV.2
HUM Sign-off & client-facing tone pass — owner: Partner. REV.3
Reviewed by
Director · Tax
Approved
Partner
FIG. 01 · A SAMPLE WORK PRODUCT — REVIEW GATES MARKED
§01
The problem

You've seen the demos. You still don't know how to turn AI into actual work.

CONTEXT
PROFESSIONAL SERVICES
TAX · ACCOUNTING
CONSULTING · LEGAL

Real work depends on private documents, templates, precedents, judgment, source-of-truth materials, review standards, output formatting, and confidence that the AI result is not quietly wrong.

Generic AI training teaches features. It does not turn one messy workflow into a reviewable work product. What you keep running into instead:

  1. 01 Tool demos A vendor showed up. Everyone nodded. Nothing shipped.
  2. 02 Prompt tips A Slack channel of clever prompts no one trusts on a live client file.
  3. 03 Ad-hoc ChatGPT Quietly used. Not reviewed. Not auditable. Sometimes pasted into things it should not be.
The gap is not awareness. The gap is one real workflow you've actually mapped, reviewed, and trusted enough to keep using.

That is what we build in a day. One workflow. One artifact. One review gate you will actually defend in front of a client or the partner who signs.

§02
Who this is for

If you repeatedly produce a high-value work product, this is for you.

BEST-FIT BUYER
TAX · ACCOUNTING
CONSULTING · LEGAL
PROFESSIONAL SERVICES

COMMON THREAD
A REPEATED ARTIFACT WHERE ACCURACY, PRIVATE CONTEXT, AND REVIEW MATTER.
01
Proposal decks
Pitch and proposal documents you assemble repeatedly.
02
Client memos
Advisory, position, and recommendation memos.
03
Tax incentive assessments
Repeated incentive, credit, or position write-ups.
04
Due diligence notes
Standardised review notes and red-flag packs.
05
Research packs
Briefings, market summaries, technical synthesis.
06
Internal status updates
Weekly partner updates, project status notes.
07
Client reports
Monthly or quarterly recurring client deliverables.
08
Follow-up workflows
Repeated client outreach and documentation chains.
09
Workflow artifacts
Anything you produce again and again where judgment matters.
§03
The method

The AI Workflow Map.

DRAWING№
AWM—001

REV. B
2026-05

A schematic for turning a repeated workflow into something a professional can sign their name to. AI drafts, searches, extracts, compares, summarizes, or assembles. A human reviews, decides, approves, and owns the final work.

Drawing №
AWM—001
Title
AI Workflow Map — method overview
Rev.
B / 2026-05
Scale
1 : 1 (concept)
Required path
Conditional / feedback
⚑ Core rule
Read left-to-right. You start with a workflow you already do and end with a first real use you can measure. Every node is something you can point at on a whiteboard. Nothing is hidden inside a vendor's black box.
§04
What you walk out with

Seven artifacts. Zero black boxes.

D.01
Workflow selection
A 1-page brief naming exactly which workflow we are touching and what we are explicitly not changing.
BRIEF · PDF
D.02
Workflow map
A drawing of how the work actually moves today — people, files, hand-offs, bottlenecks.
DIAGRAM · PDF
D.03
Source-material checklist
The inputs the artifact depends on, with privacy class, owner, and whether AI may touch them.
CHECKLIST · MD
D.04
Review-gate checklist
The questions a human asks before the artifact leaves the office. Defensible to a partner or client.
CHECKLIST · MD
D.05
AI-assistance plan
Specifically where AI drafts, extracts, compares, or assembles — and where it does not.
PLAN · PDF
D.06
Synthetic / sanitized demo examples
Worked examples on safe stand-in data so the plan is concrete, not hypothetical.
EXAMPLES · DOCX
D.07
First-use next step
Which real piece of work it runs on next, who reviews it, and what "good" looks like.
PLAN · MD
§05
The lab day

What a full day looks like.

FORMAT
FULL-DAY LIVE
ONLINE LAB

FOUNDER PHASE
PRIVATE 1-ON-1
YOU + KUAN
(the practitioner,
not a vendor sales team)
IN 1 FULL DAY
↓
OUT 7 ARTIFACTS
ALL EDITABLE.
NOTHING HIDDEN IN A VENDOR BOX.
08:45 — 09:00
Coffee & re-grounding
Quick look at the workflow brief from the diagnostic. Agree what we are and aren't doing today.
09:00 — 10:30
Current-state mapping
We draw the workflow as it actually exists. Who does what, with which inputs, at which step. Where the time goes.
10:30 — 11:30
Sources & privacy class
List every input. Tag privacy class. Decide what AI may and may not touch.
11:30 — 12:30
AI-assistance plan
Identify the specific drafting, extraction, comparison, and assembly steps where AI earns its keep.
12:30 — 13:30
Working lunch
Off-record. We talk about the practice, not the workflow.
13:30 — 15:00
Review gates
Design the human-review checklist. The questions someone with your job title would actually ask before approving.
15:00 — 16:30
Synthetic demo examples
Build worked examples on sanitized stand-in data so the AI-assistance plan is concrete, not hypothetical.
16:30 — 17:30
First-use next step & sign-off
Pick the next real piece of work this runs on. Set the review owner. Agree what "good" looks like.
+ later
Optional 1:1 implementation
A separate engagement, only if the workflow, source boundary, and review owner are clear. From US$1,500.
Total elapsedOne full day, live online
Files you bringSanitized samples only
What you walk out withAll seven artifacts, editable copies
§06
Investment

Founder pricing. Limited seats.

⚑ Founder Day — limited 1-on-1 availability
Workflow Lab
Founder Day
US$500 Per founder day · 1-on-1 with Kuan · ~2–4 days/month
  • Workflow Diagnostic (lead-in conversation)
  • Full-day live online Lab · private 1-on-1 with Kuan
  • All seven artifacts, editable
  • Synthetic / sanitized demo examples
  • First-use next step
  • Money-back / free 1:1 risk reducer
Book a US$500 founder day Or start with the free Workflow Diagnostic
Optional · after the Lab
1 : 1 Implementation
or Workflow Factory sprint
from US$1,500 Quoted once workflow, source boundary, buyer, & review owner are clear
  • 1:1 paid workflow implementation
  • Or Private Workflow Factory sprint
  • Internal SOP + review-gate documentation
  • Scoped to one workflow at a time
  • No retainers, no platform lock-in
Discuss in the Diagnostic
FOUNDER 1-ON-1 PRICING. PRICE RISES AND FORMAT MAY SHIFT TO SMALL GROUP ONCE THE METHOD AND ARTIFACTS ARE LOCKED.
NO RETAINERS. NO SUBSCRIPTIONS. NO VENDOR TOOL SOLD ON THE WAY OUT.
NO PROMISE OF FULL AUTOMATION. HUMAN REVIEW STAYS IN CONTROL.
§07
The lead magnet

Start with a free Workflow Diagnostic.

A short diagnostic conversation. No obligation. No raw private client files needed — sanitized descriptions are fine. If there's no workflow worth pursuing, the recommendation is no-build.

For professional-services operators who know AI should help but do not know where to start. We pick one repeated workflow you bring, look at it together, and decide: Lab, 1:1 implementation, Private Workflow Factory sprint, nurture, or no-build.

Book a free Workflow Diagnostic
No raw files needed
WHAT YOU WALK AWAY WITH

One workflow, looked at honestly.

  1. One workflow selected — or rejected.
  2. The current workflow roughly mapped.
  3. The likely AI-assistance points identified.
  4. The privacy / review boundary clarified.
  5. A recommendation: Lab, implementation, sprint, nurture, or no-build.
Bring: one repeated proposal, memo, report, research, or client workflow.
Don't bring: confidential raw files. We work from your description.
§08
Proof

Where the pattern came from.

The strongest current proof: a Big Four tax director's proposal workflow, built in two passes with full human review at every gate. The same pattern follows in adjacent professional-services workflows — recurring reports, BD outreach, internal ops, member services, growth. Map the real artifact, sources, and review gates before touching tools. When the new AI leverage isn't clear, the honest call is no-build. Click any case to read the full story.

PROPOSAL · BIG FOUR TAX & ADVISORY

Proposal / professional artifact.

A director-level Big Four tax professional's repeated proposal workflow, built in two passes: first a web-form generator that auto-looks up the company's UEN, tax status, and GST then drafts the proposal; then a local/private assistant that assembles a near-sendable deck from the firm's master deck and credentials. Human review at every gate. Strongest current proof — a partner asked about rolling it out — still beta until run on a live proposal.

ROLE · DIRECTOR-LEVEL STATUS · BETA
Read the case →
REPORTING · WEB3 / CRYPTO · ADJACENT WORKFLOW

Recurring reporting.

A Web3 product manager turned scattered product material — meeting transcripts, Notion, Google Docs — into a decision-ready report. We set up Claude Code around his sources, mapped the report, and taught him to run it himself; he used it to produce the report behind his company's acquisition.

ROLE · PRODUCT MANAGER STATUS · DELIVERED
Read the case →
OUTREACH · WEB3 / CRYPTO · ADJACENT WORKFLOW

Sales outreach package.

A reusable outbound workflow for a Web3 BD rep, built in Claude Code across his real stack — Google Sheets → Apollo → drafts → Instantly → Asana. Find contacts, draft the sequence, export a ready-to-send CSV; the rep approves every message that goes out.

ROLE · BUSINESS DEV STATUS · DELIVERED
Read the case →
OPS AUTOMATION · MEMBER COMMUNITY · ADJACENT WORKFLOW

Inbound ops automation.

A recurring member service buried in near-identical signup messages each cycle. We engineered the full workflow — auto-reply → confirm → log to a shared sheet → day-of check-in — with the hard part designed for a personal account: protected contacts, strict rate caps, a kill switch, and a week-one dry run. Environment installed on the operator's machines; honest status — not switched on yet.

ROLE · OPERATOR STATUS · IN PROGRESS
Read the case →
DM SALES · CREATOR / COACHING · ADJACENT WORKFLOW

Inbound DM sales bot.

A sales creator's Instagram inbound was full of the same qualifying conversations. We built a DM conversation engine — an eight-stage playbook, tuned over five iterations and graded turn-by-turn against real chats — and deployed it as a live demo with full Instagram integration. Honest status: blocked on Meta's app review, never connected to the live account; inbound-only by platform rules.

ROLE · FOUNDER / CREATOR STATUS · BUILT, NOT LIVE
Read the case →
OUTBOUND GROWTH · COMMUNITY MEMBERSHIP · ADJACENT WORKFLOW

Outbound growth engine.

An affiliate promoting a membership community needed to reach thousands of prospects on X — personally — and post awareness content daily. We built a running system of three automated loops: one personalizes DMs from each prospect's profile, one sends them on an hourly cadence, and one drafts awareness tweets into a review queue. Live and running on schedule.

ROLE · GROWTH OPERATOR STATUS · RUNNING
Read the case →
Anonymized to industry and role. Raw customer material stays out of public materials. Specific examples shared on request, under NDA, after the Workflow Diagnostic — and nothing becomes a public case study without explicit permission.
§09
Risk reducer

You leave with the artifacts. Or you don't pay.

If you do not leave the full-day Lab with one mapped workflow and a concrete next step — you get a free 1:1 follow-up or your money back.

And on the diagnostic side: if the conversation does not reveal a workflow worth pursuing, the recommendation is no-build. No forced sale.

  • No promise of full automation.
  • No promise of AI correctness without human review.
  • Regulated, confidential, or client-sensitive work always keeps human review gates.
  • No raw private files required to start.
  • No platform you're forced to subscribe to afterwards. No retainer.
§10
The person doing the work

The person doing the work — not a vendor sales team.

AWS
Practice
Workflow Lab
1
Workflow per Lab.
One, mapped properly.
1
Full day on-site.
Live online.
7
Artifacts you walk
out with.
THE AI
WORKFLOW
MAP
method · rev. b
SectorsTax · Accounting · Consulting · Healthcare ops · Sales · Real estate
FormatFull-day live online Lab + Workflow Diagnostic
PrincipleAI drafts. The professional reviews, decides, owns the outcome.
Practitioner-led.
Workflow design for professional-services operators

Years sitting next to people doing the actual work — directors drafting tax memos, ops leads chasing purchase orders, founders writing proposals at midnight, agents matching leads to listings — and watching them try to bolt AI onto the side of it.

The pattern is almost always the same. The tool is fine. The prompt is fine. The workflow was never mapped. Nobody agreed on the artifact, the sources, or the review gate. So "AI adoption" became a synonym for "individuals paste things into ChatGPT and hope."

The Lab is the smallest unit of useful work designed around that. One day. One workflow. One reviewable artifact. If it's worth doing, you can feel it by lunch. If it isn't, we don't pretend.

ApproachOne workflow, mapped properly. AI drafts. Humans own the outcome.
BackgroundWorkflow design across tax, healthcare ops, sales, real estate, agency work, and SME operations.
§11
Frequently asked

The questions we get before booking.

Then the answer is no-build, and the Workflow Diagnostic will say so. We'd rather tell you not to do the Lab than take your money for one that produces a polished artifact nobody uses.

The Diagnostic exists for exactly this reason: it sorts "this is worth a Lab" from "1:1 implementation" from "Private Workflow Factory sprint" from "nurture" from "don't bother." All of those are legitimate outcomes.

No. The diagnostic works from your description of the workflow — the shape of the artifact, the sources it depends on, the people who touch it. Raw client files are never uploaded, transmitted, or required to begin. If we eventually look at samples (typically during the Lab itself), they're sanitized first, on your machines.

No. Prompts are downstream of the workflow. We design the workflow first — what the artifact is, what the sources are, where AI assists, where the human reviews. Prompts that survive contact with a real client artifact fall out of that design naturally. We do not sell prompt libraries.

Whichever ones fit the workflow and your existing licences. The Lab is tool-agnostic. We've worked with teams running everything from enterprise Microsoft 365 + Copilot to a single shared ChatGPT Team seat to fully local models on the firm's own hardware.

The AI-assistance plan you walk out with is portable: it documents what good looks like, not which vendor is meant to produce it.

A short, defensible human-review checklist your team can run before any AI-assisted artifact leaves the office. Typical items: source provenance, factual accuracy spot-check, judgment calls the human owns, sign-off owner, escalation path for exceptions. It looks like a real audit checklist, not a "is this output good?" thumbs-up.

Then we map the workflow anyway and design the review gate, and the Lab outcome includes a memo describing exactly what an AI-assisted version would look like and what data classes it would need to touch. That memo becomes the conversation you take to compliance. We've seen several "blocks" turn into "approved with conditions" once the workflow and review gate were drawn clearly.

Optionally, yes — the 1:1 paid implementation starts from US$1,500. There's also a Private Workflow Factory sprint for larger scopes, quoted once the workflow, source boundary, buyer, and review owner are clear. We will not sell implementation before the Diagnostic / Lab; we don't know enough to scope it honestly.

Yes, if you produce a repeated artifact where accuracy and judgment matter — proposals, client memos, position papers, research, recurring reports. The Lab is scoped per workflow, not per headcount — and during the founder phase, each Lab Day is private 1-on-1 with Kuan.

It means: a real version of the artifact you already produce — with the AI-assisted steps, sources, and human review gates drawn explicitly underneath it. A partner or client could trace any line back to its source, judgment call, and reviewer. That's the bar.

§12
The next step

Bring one
repeated workflow.
Leave with a map,
a review gate, and
a first real use.

The Workflow Diagnostic is free. Short. No raw client files. If there's no valuable workflow to map, the answer is no-build — and you've lost an hour, not a contract.

FormatVideo / live online
BringOne repeated workflow
LengthShort conversation
CostFree

Skip the diagnostic? Book a US$500 founder day directly →

FORM · 01 · WORKFLOW DIAGNOSTIC

One short conversation. You bring one repeated workflow — proposal, memo, report, research pack, or client process. No raw files. No obligation. We decide together whether a Lab is worth doing.

Book a free Workflow Diagnostic
No raw files. No obligation. No retainer pitch.