One day workshop, Central Coast

Build your biz brain.

An AI assistant is only as useful as what it knows about your business. In one day, in person, you build what it should always know, the rules it follows and the files it can use, then test it on a real job of your own.

Your biz brainExample
1
Business context
Who you are, your customers, services, voice and numbers
Built
2
Rules
What it does, what it never does, what needs your sign off
Built
3
Your files
Price lists, past proposals and procedures it can draw on
Built
4
Lessons
Every fix becomes a line, so it gets better with use
Lessons fileWe say scope, not quote.
Never offer a discount without sign off.
Weekly
First workshop
Where
Time
Room
Small group, 2 of us on the floor
Price

The problem

Most people start every chat from a blank page.

You explain yourself every time.

Who you serve, how you talk, what you charge. Each new chat starts with none of it, so the answers come back generic.

What you know is scattered.

Price lists, past proposals and procedures sit in folders and in people's heads, where an assistant cannot use them.

Nobody has set the rules.

What can staff put in? What must be checked before it goes out? Without a rule, every person decides alone.

How it works

From a blank chat to an assistant that knows your business.

01 · Context

Write down what it should always know.

A plain document on your business: customers, services, voice, numbers and the words you use. You own it, and it works in any tool.

02 · Rules

Set how it behaves.

What it does, what it never does, what needs your sign off and what data stays out. You finish with a one page use rule for your team.

03 · Files

Give it your material.

A controlled folder of price lists, proposals and procedures. Then you test it on a real job from your own business.

The day

Mostly building, with help at your elbow.

Pick the part of the business where your time goes, such as reporting, marketing, finance, sales, operations or people. The method is the same for everyone. You work on your own function, at a table with others working on theirs.

  • A working assistant loaded with your context and rules
  • Your context and rules as a document you own
  • A folder of files it can draw on
  • A lessons file and a 15 minute weekly habit
  • A one page AI use rule for your team
  • Your next three things to hand over, in order
9:00
ArriveAccounts already set up from the pre-work email
9:30
What a business brain isAnd why a blank chat wastes your time
10:00
Build 1: contextYour business, in your words
11:00
Break
11:15
Build 2: rules and guardrailsWhat it does, never does, and who checks
12:00
Lunch
12:45
Build 3: your filesA controlled folder it can use
1:45
Test it on a real jobYour function, your material
2:45
Break
3:00
Lessons fileHow it gets better, and what comes next
3:45
Your next three stepsThen close at 4:00

Getting better with use

It improves because you teach it.

An assistant does not learn by itself. It gets better because you keep what it knows up to date. When it gets something wrong, or you fix a draft, you add one line to the lessons file: how you say it, what you never offer, which figure to use.

Fifteen minutes a week keeps it current. That habit is what you take home.

We show email and calendar access and automatic routines live on the day, with the risks. We do not build them on day one.

Who it is for

Decision makers who want it to fit their business.

This is for you if

  • You own or run a Central Coast business with a team
  • You already use a chat tool a little and want more from it
  • You want to work on your own business with someone beside you
  • You are happy to use sample or de-identified data on the day

This is probably not for you if

  • You want a lecture or a certificate
  • You want a ready made tool built for you in a day
  • You are happy with how you already use AI
  • You are a one person business with little admin load

The free government courses are a good place to start. This day is for when you want it built around your own business.

Your hosts

Two people who build software for a living.

[Host bio: name, background, years building software, why you run this on the Central Coast.]

[Second host bio.]

Register interest

Tell us you want in.

The first date is not set. Register and we will email you when it is confirmed, before it is announced anywhere else.

We use your details only to reply to you. See our privacy policy.

What happens next

We email you the date, venue and price once they are set. Registering is not a booking and you pay nothing.

If you want more afterwards

Nothing, unless you ask. Some owners want us to look at their business and build the next piece. That starts with a written audit and a fixed price, and the workshop is not a sales pitch for it.

Questions

The short version.

Which AI tool do you use?

We teach the method on one tool, chosen from what attendees already use, and show the same job in a second tool. Your context and rules are plain documents, so they move with you if the tool changes.

Is my business data safe?

On the day we use sample or de-identified material. We teach what to keep out of public tools and set the rule for your team. For anything built afterwards, privacy and where data is held go in the contract.

Do I need to be technical?

No. If you can write an email and keep a folder, you can do the day. There are two of us on the floor so nobody is stuck on setup.

What do I need to bring?

A laptop, an account on the tool we confirm in the pre-work email, and three de-identified documents, such as a price list, a past proposal and one procedure.

Can I send my team instead?

Yes, but the day works best for the person who makes the decisions. If you would like to bring a colleague, ask us about the room.

What do you promise I will get?

A working first version of an assistant that knows your business, and the habit to improve it. We do not promise savings or results, because they depend on how you use it.