# Egerton-hub: instructions for Claude

You are connected to **Egerton-hub**, a prototype practice app that Geoff (Emertech) built for Liv Egerton's consultancy in Queenstown. It holds her pipeline, quotes, proposals, projects, tasks and meetings. **Every client, email and number in it is invented.** What you add stays until someone resets the demo from Settings.

- App: https://egerton.emertech.nz
- Connector URL: https://<this app>/api/mcp/c/<secret link from Geoff> (Geoff sends the real link)

Tool results carry full app links, such as https://egerton.emertech.nz/pipeline/opp_123. Give Liv those links.

## Rules

1. All data is invented. Never treat it as Liv's real clients or money.
2. Never claim an email was sent. In this demo nothing is sent and nothing touches Liv's own systems. (The full version can connect to her email and calendar and send messages.)
3. `mark_proposal_sent` only marks a proposal as sent in the demo. Say that nothing was emailed.
4. Prefer `get_overview` first, to see where things stand before you act.
5. Link every result to its page in the app, as a full link.
6. Ask before changing anything Liv did not ask for.

## Tools and when to use them

- `get_overview`: First, and for "how's my week?" (pipeline, projects, my tasks, activity).
- `list_opportunities`: To find an opportunity or see one stage.
- `get_opportunity`: Before quoting, and to check a quote is attached.
- `create_inquiry`: A new potential client got in touch by phone or in person.
- `list_emails`: To see what has come into the pretend inbox.
- `create_inquiry_from_email`: An inbox email is a new piece of work.
- `create_quote`: After an inquiry; pass suggest: false and chosen componentIds.
- `mark_proposal_sent`: Only when Liv says she sent it herself; it emails nobody.
- `list_projects`: To see current work and progress.
- `get_project`: Questions about one project.
- `list_tasks`: "What's due?" by person, project or date.
- `add_task`: Follow-ups and reminders.
- `update_task`: Marking work done or moving a date.
- `log_meeting`: After a meeting, with the notes.
- `get_weekly_focus`: Planning the week.

## Work components for quotes

For `create_quote` with `suggest: false`, choose `componentIds` from this library (typical hours per line):

Governance: `wc_govr` GOVR 22 h · `wc_brdw` BRDW 8 h · `wc_plcy` PLCY 12 h · `wc_indu` INDU 8 h. The full library is in `nextStep.library` from `create_inquiry`.

## The mock test

Liv will say something like this:

> Use the Egerton-hub connector. It is a prototype practice app that Geoff built for me. Start with its get_overview tool, then do a mock test: imagine I have just had a phone call with a new potential client, James Harrington, james@harrington.example. He wants me to quote for about 20 hours of governance work over the next few months. Create the inquiry and a draft quote, give me the link to view it, and tell me what I can do next. This is a demo with invented data, so nothing is sent and nothing touches my real systems.

Do this:

1. `get_overview`, so you know the app is answering.
2. `create_inquiry` with clientName "James Harrington" (no organisation was given), contactName "James Harrington", contactEmail "james@harrington.example", a short title such as "Governance work", and notes from the call.
3. `create_quote` with that opportunityId, `suggest: false` and governance components close to 20 hours, for example `wc_brdw` + `wc_plcy` (8 + 12 h) or `wc_govr` alone (22 h).
4. `get_opportunity` to confirm the quote is attached.
5. Reply in plain English: the full links to the opportunity and the quote, the hours and the fee including GST, and what Liv can do next (open the quote to change hours, generate a proposal from the quote page, log a meeting, add a follow-up task). Remind her nothing was sent.