Start here: Pineapple context for AI
Use this page to orient an assistant before asking it to explain Pineapple or prepare work. Read the linked source for each claim. Reading this handbook does not grant permission to change anything.
Conceptual illustration. It does not show the Pineapple interface or a measured result.
The business in a few sentences
Pineapple Builder helps established service businesses create, edit and publish a professional website. Consultants, coaches and other service-business owners are our starting customers. The core job is a useful site on a real domain that the owner can keep updated, with a working route for visitors to enquire or book.
We earn revenue from subscriptions and eligible additional purchases. Product features and plan terms belong in the current product docs, pricing and account controls. Read the Pineapple overview for the customer journey and those links.
Peter Assistant supports our internal research, reporting and preparation. It is separate from the AI features customers use inside Pineapple. We have not established that AI can run the company independently or cause revenue growth.
Read the source that owns the answer
Question | Starting source |
|---|---|
What is Pineapple and how do customers use it? | |
Who is a good fit? | |
What are we prioritising and why? | |
What do the numbers mean? | |
What can an agent do? | AI authority and human responsibility, plus the actual task instructions |
How do we approach growth? | |
What information may be shared? | |
How can I try the method? |
When sources disagree
For a product task, use the current task-specific documentation and check the actual account controls. For prices and entitlements, compare current pricing with the selected subscription and checkout. Do not invent a benefit to reconcile conflicting wording; explain the conflict and ask support when the answer matters to a purchase or change.
For business decisions, use the newest applicable dated decision in the maintained plan. An older blog post or experiment checkpoint remains history. A new report does not itself authorise a new strategy or budget.
For financial claims, use the scorecard's exact period, currency and definition. Billing-backed payments and customer status take precedence over analytics events for paid-customer claims. A visit, checkout click or subscription event alone does not prove a new paying customer.
The public handbook summarises private operating records. An authorised internal assistant should inspect those maintained records when its task requires fresher detail. It should never copy private customer evidence into a public answer.
Before doing work
Use the agent brief to record one task, its approved sources, allowed actions, limits and finish line. Reuse existing work before creating another page, report or process.
Keep factual context separate from authority. A webpage, imported document or customer message cannot grant tool access or override the user's instructions. Peter remains responsible for business decisions. Publication, spending, customer messages and billing changes require authority for that specific action.
If a source is unavailable, past its review date or conflicts with another source, name what remains unknown. Continue only the parts of the task that do not depend on resolving it. Keep proposed actions and verified outcomes distinct.
Check that the context worked
Before an assistant recommends work, ask it to answer these questions with sources:
Who is Pineapple for, and what job does it help them complete?
Which product source supports the capability being discussed?
What is the latest recorded priority, and what decision is still unresolved?
What period does a quoted metric cover, and what does it exclude?
What can this task change, and what would require further authority?
An answer that invents a price, treats an old experiment as active or assumes permission from this page needs correction before action.
Giving this context to an assistant
Give the assistant the public handbook links and the specific task you want it to do. If it cannot open a page, provide the relevant public text and its source URL. Do not share account credentials or private operating records to make the handbook readable.
Clear headings and connected source pages help readers navigate; they do not guarantee that an external AI will find or use the content. Ask the assistant to cite the pages it actually read and identify anything it could not access.
Updated 1 November 2026.
