Setting up your Lore
Business
Glossary
Playbook
Persona
Deploy
← Back to site
Step 1 of 5 · Your business
Let's build your Lore.

We'll pre-load the right vocabulary for your industry so you're not starting from scratch. Takes about 60 seconds to get the basics in place.

We'll reference this when generating your context — helpful but not required.
🏗️
Construction & Trades
Residential, commercial, civil, subcontractors, QS
⚖️
Legal & Law Firms
Solicitors, barristers, in-house legal teams
🏥
Healthcare & Allied Health
GPs, physios, dental, psychology practices
📊
Professional Services
Accounting, finance, insurance, consulting
🏠
Real Estate & Property
Agencies, property management, valuers
Other
We'll start from a blank slate
Step 2 of 5 · Glossary
Your business vocabulary.

We've pre-loaded NZ/AU construction terms. Accept the ones that apply to your firm, skip any that don't, and add your own. These are the words your AI will finally understand correctly.

Suggested terms — click to accept
Terms specific to your firm — client categories, internal codes, trade classifications.
Step 3 of 5 · Playbook
How you handle variations.

A Playbook is a process your AI can follow. We've started with your variation order process — the most common source of miscommunication between builders and clients. Adjust the steps to match how your firm actually works.

1
Variation identified on site
Site supervisor or project manager identifies work outside original BOQ scope and documents it with photos and notes.
2
VO drafted and costed
Office prepares written variation order with scope description, materials, labour, and total cost + GST.
3
Principal sign-off obtained
VO sent to client/principal for written approval before work proceeds. No work commences without signed approval.
4
Work completed and documented
Variation work is completed, photographed, and recorded in site diary with date and labour hours.
5
Invoice issued — 14-day terms
Tax invoice raised referencing VO number and approved amount. Payment due within 14 days of invoice date.
This will be encoded in your Lore so AI never quotes the wrong payment terms.
Step 4 of 5 · Persona
How your firm communicates.

Eight quick questions. Your answers create a voice profile so every AI output sounds like it came from your firm — not a generic chatbot.

Tone with clients
How you address clients
Email sign-off
Email length preference
Language style
When things go wrong with a client
Step 5 of 5 · Deploy
Push your Lore to your AI tools.

Select a tool to connect. Lore generates a system prompt you paste in — or connects directly via MCP if the tool supports it. Your AI immediately inherits everything you've just built.

🤖
ChatGPT
Custom GPT or system prompt
🟣
Claude
Claude Project instructions
💙
Microsoft Copilot
M365 Copilot system message
🟠
HubSpot AI
CRM AI assistant context
💬
Website Chatbot
Intercom, Drift, Tidio, etc.
MCP Server
Direct API / developer setup
🎉
Your Lore is live.

Your AI tools now know what your business means. Every response will reflect your vocabulary, your process, and your voice. Deploy more tools any time.

Open your Lore dashboard →
Step 1 of 5