Brieflo is currently available by invitation only.

Frequently asked questions

What is the difference between Brieflo and a coding agent?

Brieflo does not execute code and does not build your project on its own. It gathers and structures the customer's request and delivers a handoff package that a coding agent or developer works from. The agent builds; Brieflo delivers the brief and the context.

How does resuming work?

Your customer signs in with a four-digit email code and continues exactly where they stopped: current question, answers, uploads, decisions, transcript, selected logo, themes, screens and open actions. No new paid action starts when the previous one is still running or already finished.

What about privacy?

Brieflo stores project memory to enable resuming, version history and handoffs. No blanket zero-data-retention is promised. Only necessary content goes to the chosen AI provider, and transcript or attachment content does not appear in ordinary logs.

Which languages does Brieflo support?

Dutch and English are both fully available from the first release, across every role, workflow, communication and output. Further languages are extensible without rewriting business logic.

How does a quote work?

You can produce a quote or explicitly skip it. If you produce one, you set the price. Brieflo supports multiple packages with their own scope and exclusions, VAT, instalments and validity. Acceptance requires the current offered version and recent authentication.

What is in a ZIP?

An agent ZIP contains the technical scope and assets: requirements, architecture, design, branding, agreements, metadata, README and manifest, and optionally the agent prompt. Commercial prices are excluded by default. A full project archive is a separate export profile.

Can I still submit changes after delivery?

Yes. Feedback and change requests remain possible in the same portal, without a new project activation. AI usage runs through the wallet within the configured limits.

{# The consent choice is reported to the server, so the CSRF cookie must be present on every public page. Without it the report is refused and the decision stays local-only. #}