# Introduce Egbe and move to a project workspace

This path introduces Egbe and helps the founder move to an environment where
they can use it fully. Complete quickstart with the introduction and handoff below.

## Show the value

Reuse the public discovery and [introduction example](introduction.md) from
step 1. Include a compact capabilities table in the final answer so it stands
alone if progress messages are collapsed. Briefly explain that full connection
needs a persistent project workspace; this introduction has not connected one.

## Give a concrete next step

Recommend an environment with a persistent project folder, commands and safe
authenticated HTTP: for example, Codex from ChatGPT or Claude Code from Claude
chat. Choose by capabilities, not the app name alone.

Tell the founder to open that environment, select or create a project folder
(an empty one is fine), and send the connection prompt from their Egbe Dashboard.
If they do not yet have an Egbe project, link to
[project creation](https://dashboard.egbe.ai/new) as part of that next step.

If the conversation already contains useful context, include a short continuation
brief with the goal, decisions and next action, plus the public quickstart URL.
Supply credentials through the destination's private connection flow, not in
the brief, and carry any existing reporting/logging choices into the handoff.
