Founding client offer · 3 left
I design, build, test, and put one high-value AI workflow into use in your business, inside the tools and accounts you already own.
Founding build 01
A small company's accounting team took 10 days to close their books, and every time was different. I gathered the requirements, built the system inside their own accounting stack, tested it against real periods, and put four human approval gates where the owner signs off. It closes in 5.
Engaged by Jennifer Loo, CFO at Tala
What the system runs
Systems connected
The boundary
An AI Build is deliberately narrow. The goal is to put one useful system into real work, not produce a roadmap for everything AI could eventually do.
Good fit
Not a fit
Unsure on any of these? Bring it to the call.
Four-week build
Map the current workflow, establish the business result, and approve the trigger, inputs, actions, approvals, tests, and exclusions.
Create the smallest complete version inside your environment and connect it to the systems the workflow actually needs.
Run representative cases, add human checkpoints and exception paths, and correct failures before real work depends on it.
Use the workflow on representative or live work, complete the handoff, and make sure the process owner can operate it.
No black box
I build in client-owned accounts wherever practical. You keep the workflow, prompts, configuration, documentation, and operating knowledge after full payment.
The engagement includes a 30-day launch warranty for defects. It does not create a permanent support dependency or lock you into my tools.
Launch
Launch is a checklist, not an opinion. Every item is agreed in Week 1. The final 50% is due only when all of them are true, and if they aren't met you don't owe it.
The workflow is operational in your environment.
The agreed accounts and systems are connected.
The approved acceptance cases pass.
At least one representative or live run is complete.
No blocking defects remain.
Documentation and training are delivered.
Change control
Week 1 produces a written Build Plan. Anything that falls short of that plan is a defect, and I fix it at no cost. Anything new is a separate engagement, quoted and agreed on its own.
Each of these is new work, not part of this build:
Before you apply
Anything repeatable with a clear owner and a clear right answer. Recent shapes: a month-end close with reconciliations and approvals, inbound lead qualification and routing, proposals drafted from call notes, invoices and documents pulled into a system of record, a weekly reporting packet assembled from several sources. These are just examples. If your workflow isn't listed, send it anyway so we can chat about it at no cost to you.
We pick it together before anything starts. On the qualification call I'll tell you straight whether a workflow fits in four weeks and whether I think it gets you the result you're after. That is the point to decide. Once the build begins the workflow is fixed, and changes within it follow the scope rules above.
Yours. Your accounting system, CRM, email, storage, spreadsheets, and internal apps. If it has an API, or you can export from it, it is usually workable. The month-end close build connects eight systems including QuickBooks, Bill.com, Gusto, and Expensify. The systems themselves run on Claude.
No. I do the whole build: workflow design, context engineering, integrations, implementation, and testing. You bring the business expertise and the decisions. You don't need a technical team to hire me or to run what I hand over.
About two hours a week, with longer sessions at each end. Week 1 runs three to four hours: one live workshop to define the workflow, plus gathering documents and sample data. Weeks 2 and 3 are a sync and ad-hoc questions. Week 4 runs three to four hours again, because training and handoff need the process owner in the room.
You do not owe the second half. Launch is a checklist, not an opinion, and the criteria are listed above. I also screen feasibility during qualification, and I'll tell you if I don't think a workflow can be built in four weeks.
The warranty covers the acceptance criteria through 30 days of real production use, so the workflow proves itself under real conditions. It is not a window for new features. After it, ongoing support and new work are available separately.
You do, entirely. The workflow, the documentation, and the operating knowledge are yours, running in your own accounts. I retain no data, and I'm happy to sign an NDA before we start.
Your implementation partner
I'm Kenny Liao. I build and work with AI agents every day, teach tested systems on YouTube, have built and sold Claude plugins, and have trained finance and analytics leaders to use AI in real work.
You bring the business expertise. I bring the workflow design, context engineering, integrations, implementation, and testing needed to turn it into a system your team can operate.
Founding offer, 3 left. $5,000 fixed. The price goes to $7,500 after the third.
Send me the process you want to improve, how it works today, and what a useful four-week result would look like. I'll review fit before inviting you to a call.