Project APEX

Project APEX is an autonomous sales-agent prototype. It is built around a simple idea: a sales system should collect the right business context first, then use that context to support outreach, qualification, and follow-up work.

The project started with a strong visual baseline. The design work created a black-and-white shadcn-style system, a fullscreen product feel, and a clear onboarding direction. After that, the app moved from a static design into a working intake flow that can collect a business brief and prepare it for backend use.

What it does

• Presents a focused onboarding flow for a sales-agent product.
• Collects live intake information instead of only showing a static landing page.
• Uses a clean visual system so the product feels direct and serious.
• Persists onboarding data so the next agent step can use it.
• Keeps the runtime in the main app instead of leaving the useful parts inside a design-only workspace.
• Adds an intro flow that makes the product easier to understand before the user starts.

Recent work

The June work built the foundation in layers. First came the style guide and component baseline. Then the fullscreen UI system was expanded. The design workspace was moved into the project so the visual system could be reused instead of treated as a throwaway mockup.

After the visual foundation, the product gained an onboarding backend. The intake flow can now persist a brief at the end of the flow, and later commits made the onboarding input faster and simpler. The app runtime moved to the root so the project is easier to run and deploy. The most recent work added an Elson-style orb intro, which gives the onboarding flow a clearer first moment.

Value for users

The value is a better start for a sales agent. Most sales tools ask for too much setup or too little context. APEX tries to ask for the right context in a clean flow, then turn that into something an agent can use. That helps users move from a rough idea to a prepared sales workflow faster.

Current direction

The next step is turning intake into action. The product should take the brief, understand the offer, identify the target customer, and support the first practical sales steps. The interface should stay simple while the backend gets more useful.

Public boundary

This page describes the public product shape and build direction. It does not include private lead lists, customer data, prompt internals, or provider credentials.

Voice onboarding update

The latest APEX work turned the intake into a more natural guided conversation. A user can speak through the business context while the product keeps the brief updated in the background, asks the next useful question, and gives the user a live review before the onboarding is completed.

The flow was also grounded more carefully. Source collection, answer extraction, and the final handoff were separated so the agent does not keep asking the same question or lose the information that has already been captured. The landing surface was brought into the root app as part of the same pass, so the public story and the working onboarding flow now live together.

The value is a calmer start. Instead of filling out a long static form or trusting an opaque conversation, a user can talk through the context, watch the brief take shape, correct it, and approve the next step.