How PieBox Works

PieBox works as a task flow from idea to delivery. You do not need to master every feature before you start, but it helps to understand the main objects: projects, conversations, materials, agents, deliverables, previews, and publishing.

Together, these objects explain how PieBox can take a rough idea and move it toward something you can view, revise, share, or launch.

Projects

A project is the main unit for organizing work in PieBox. A project usually maps to a clear goal, such as a product website, a campaign page, a research report, a slide deck, or a small app that will keep evolving.

Keep the boundary clear. "Build the first version of a product website" is a better first project than "build the whole brand system."

Conversations

The conversation is where you collaborate with PieBox. You describe the goal, add constraints, review output, and request changes. PieBox keeps working from the same context, so you do not need to explain the background again every time.

A good conversation does more than ask questions. It keeps clarifying delivery standards: who the result is for, what problem it should solve, what must stay, and what should be avoided.

Materials

Materials give PieBox useful context. They can include notes, screenshots, tables, reports, reference sites, existing code, brand guidelines, or business data.

The more specific the material, the closer the first version can be to the real need. You can start without materials, but for business work it is usually better to add them early.

Agents

Agents are the execution capabilities PieBox uses for different parts of a task. A task may need product thinking, content structure, visual judgment, implementation, data analysis, debugging, or publishing checks.

You do not need to manually manage every agent. Describe the final deliverable and provide the available materials. PieBox will organize the work around the task.

Deliverables

A deliverable is the result PieBox produces. It is not just a chat reply. Depending on the task, it can be:

• a previewable website or page
• a product prototype, landing page, or small app
• a slide outline, report, or proposal document
• a market research or data analysis report
• copy, positioning, chart suggestions, or an action list

A useful deliverable should be able to move into the next step: review, revision, sharing, publishing, or decision-making.

Preview

Pages and apps usually need a preview. A preview link lets you check layout, interaction, content, and mobile behavior in a realistic environment. It also lets teammates or clients give feedback on the same version.

Preview before publishing. It is the right stage for finding issues, rewriting copy, adjusting structure, and confirming the experience.

Publishing

When a page or app is confirmed, it can be published to a real URL. Publishing should not be treated as a black box; it is the step that makes an approved version accessible.

Before publishing public-facing work, check:

• whether the core information is accurate
• whether desktop and mobile layouts are usable
• whether links, buttons, and forms work
• whether sensitive information is included
• whether the team or owner has approved the version

Continuous Iteration

The first delivery is not the end. You can keep modifying the same project based on feedback: update pages, add content, extend features, refresh data, or republish.

PieBox is useful because it makes that loop lighter. You can get an initial version earlier and move faster from feedback to the next version.

Recommended Mental Model

If you are new to PieBox, understand it in this order:

1. Use a project to hold a clear goal.
2. Use conversation to express requirements and changes.
3. Use materials to add context.
4. Let agents execute the work.
5. Review, preview, and publish the deliverable.

Once this flow is clear, the feature and deployment docs become easier to evaluate.