What's new.
New features and improvements in Brieful, newest first.
- Improved
🔍 Readiness Review: 'not reviewed' is now visible
A bid whose scope was never put through Readiness Review used to look identical to one reviewed and clean. Now the bid Overview shows an amber 'Readiness review not run' criterion, the Phases card shows coverage per phase, the BuildAI page warns above the kit download, and the kit's CLARIFICATIONS.md opens with a coverage notice. It is a warning, not a gate — nothing new is blocked.
Learn more → - New
🏗️ BidWin Architecture: decision register + deeper synthesis
The synthesis overview now comes in three depths — Executive, Standard, or Detailed with headed subsections tied to the named decisions — and a collapsible Decision Register under it lists every accepted decision exactly as recorded (why, alternatives set aside, impact, client's option and date). Both are in the Solution Architecture Word export, the register right after the overview. The 3-year TCO figure on option cards is gone; pricing lives in the Price tab.
Learn more → - Improved
📋 Dashboard: projects linked to a bid stay visible
Linking a project to a BidWin Project-mode bid used to remove it from the workspace dashboard, so a workspace owner lost sight of a project they could still open. The dashboard now lists these under 'Linked to a Build' with an Open button (and Open build for BidWin users). RFP bids stay inside BidWin.
Learn more → - Improved
🧭 Shell panel: a guided, step-by-step mode
The Shell panel now opens in a guided mode: five steps — Propose, Check the menu, Who sees what, First page per role, Preview & approve — each showing only what it needs, with a one-sentence explanation, a 'What's left' list with one-click fixes, and a tick when done. The landing step is simpler: choose Dashboard or Marketing from two pictures, keep the cards you want, and one 'Build all landing pages' button generates every role's page (and picks a featured list where there is none); the finer settings sit under 'Customize this page'. Nothing was removed — click Advanced for the full editor, and the panel remembers your choice.
Learn more → - New
🏠 Landing pages are now generated, not templated
The page every role sees first used to be a fixed template that ignored your Design Library. Now each role's landing page is built through the same pipeline as every other screen: pick Marketing (a public front page) or Dashboard (a signed-in work surface), choose the sections, set a headline and tagline, embed a featured list from one of the role's screens, add a hero image the client supplies, and click Build. It follows your Design Library — including a new 'Landing / Home page' pattern you can teach from a screenshot — passes the fidelity scan, and takes one-line refinements. Links can only go where that role's menu goes. A stale badge tells you when to rebuild, the build kit describes each landing page for the developer, and projects that never build one keep the simple template.
Learn more → - New
🌙 Dark mode in the Design Library
A new Mode switch (Light / Dark) on the workspace library, on project and portal design forks, and on admin templates. Dark gives a near-black page with the brand color as a glowing accent, and everything else is derived from that one switch: raised surfaces for cards, inputs and menus, reversed color ramps, dark status colors, flat elevation, and text on the action color chosen to pass contrast (a neon accent gets dark text). Contrast stays WCAG AA by construction. Prototypes, the navigation shell and landing page, the live preview, the fidelity scanner and the build kit all follow the mode, so a built system can be restyled dark through a change kit. A dark reference screenshot sets the mode for you, and 'Dark — Consumer app' is a one-click template. Existing designs are unchanged: no mode means light, exactly as before.
Learn more → - Fixed
🏛️ Design templates no longer wipe your screen patterns
Clicking Use on a Design Library template used to replace the whole library — even the template already in use — so List, Form and other screen patterns you had built from screenshots disappeared. Use now asks how to apply it: 'Apply look' takes the template's colours, fonts, corners and type scale and keeps your screen patterns, screenshots, navigation choices and logo; 'Replace everything' starts over. The template you applied last is marked In use, and the page warns before you leave or apply a template with unsaved changes.
Learn more → - Fixed
🎨 Project design forks no longer vanish after saving
A per-project design fork saved from the 🎨 Design panel (for example, starting from the Modern citizen app template) could disappear the next time the project page autosaved, because the page wrote the project back without it. Design forks, portal design forks and the portal configuration are now owned by the server and can never be overwritten by a page save. If you lost a fork, apply it again once and it will stay.
Learn more → - Improved
🧭 Shell: any workspace member can approve
The navigation & shell is the analysts' working artefact, so approving it no longer needs a workspace owner or admin — any member of the workspace (or the creator of a personal project) can approve. Phases keep their stricter owner/admin gate.
Learn more → - Improved
🧭 Shell: 'off-menu on purpose', and why approval is disabled
Sign-in, reset password, own profile and actions opened from a button on another screen have no menu item by design — until now the Shell panel warned about each one forever. You can now mark a use case 'off-menu on purpose' (one click per warning, or all at once): the warning and the readiness finding go away, the document lists it under 'Reached without a menu item', and NAVIGATION.md tells the builder not to invent navigation for it. ⇪ Import as-built marks them automatically, since a built system is the truth, and drops any landing card a role could not see instead of leaving a blocking error. Blocking issues now sort first in red with a count, and the disabled Approve button says exactly what blocks it. Roles are reconciled too: after an import the notice names roles the built app uses that the project does not know, and project roles the built app gives no menu; each is a warning with a one-click fix (rename to a project role, remove the role, or copy another role's menu).
Learn more → - Improved
🧭 Project header: outputs on top, tools below
The project header's top row now carries the outputs — Training, Draft doc (or Document), History — and the second row keeps the working tools: Phases, Process, Screens, Prototype, Tests, Meeting, Import requirements, Readiness, Portals, Shell and the requirements count. Buttons are a little tighter so every tool fits on one row. 'Review readiness' is now simply 'Readiness'.
Learn more → - New
🧭 Navigation & application shell — approve the menu before the build
Until now every use case was approved on its own and the global menu, the landing page for each role and who sees what were decided at build time. The new 🧭 Shell panel derives all of that from your processes, use cases, screen maps and portals, lets you rename, regroup, reorder and set a landing dashboard per role, shows a live preview per role, and records an approval as a gate. Once approved, the shell is everywhere the client sees the system: every prototype renders inside it (in the app, in Present mode, in shared links and in the offline file) and its menu opens other use cases; each role gets a landing page; the shell follows the Design Library — its Navigation pattern's house choices (layout, accordion or open groups, a rail that collapses to icons, a “More” menu for long bars, icon modes) come first, its colours, font, logo and icon set paint the bar, and every choice shows where it came from and can be changed per project; 'Play all' opens on the landing page before the first use case; the requirements document gains a 'Navigation and application shell' section; the Readiness Review gains a Navigation lens; and the build kit ships NAVIGATION.md, design/navigation.json, design/shell.html and a gated shell step that generates the navigation allowlist test, with change kits and the reconcile pass tracking navigation drift. Nothing changes for projects without an approved shell.
Learn more → - Fixed
💾 Saves on large projects, and a warning when a save fails
On the biggest projects, changes made on the project page could stop reaching the server without any warning: the page sent the entire project on every save, and past about 4.5 MB the save was rejected silently. Readiness clarifications, screen maps and test cases now stay on the server instead of travelling with every save, which cuts the save to a fraction of its size. If a save does fail you now see a red message telling you the change was not saved. Phases can only be changed from the Scope Plan, so an out-of-date tab can no longer undo a phase change.
Learn more → - Fixed
🔒 Completed phases are locked
Nothing can enter a phase you have marked completed — not a new use case, not a new requirement, and not an item whose phase was changed. Anything that would land there goes back where it was, or into your working phase if it is new. This also fixes a bug where answering interview questions could silently move Phase-2 use cases into a completed Phase 1.
Learn more → - Improved
💳 Build kits are paid by card at purchase
Build-kit licences are now paid by card at the point of purchase, and the kit unlocks as soon as payment is confirmed — replacing the earlier invoice-with-terms arrangement announced in June. Pricing is unchanged: once per bid, by the number of approved requirements, with a top-up for the difference if scope grows later. Purchase orders and invoicing remain available for larger engagements, arranged as part of the engagement.
Learn more → - New
🖼️ Design templates grounded in open design systems
The template gallery gains Federal (exact U.S. Web Design System values) and Modern citizen app (Material 3 values), and the Enterprise / Data-dense and Clean SaaS templates have been re-authored on exact IBM Carbon and Radix values — all openly licensed, all deriving a full accessibility-safe design system. Pick one for your workspace, or use them as seeds for per-project and per-portal design forks.
Learn more → - New
🎨 Design Library v3 — professional screens from the same two colors
Prototypes now look designed, not generated. Your brand colors expand automatically into a complete design system — real typographic hierarchy, consistent spacing, status colors that pass accessibility contrast by construction, a proper icon set instead of emoji, and page layouts that follow per-screen-type structure. Nothing changes in how you author: pick a template, set two colors, done. Existing projects pick the new look up on their next prototype build. Bonus: import an agency's brand file directly (Figma variables, W3C design tokens, or Tokens Studio JSON) and the whole system derives from it.
Learn more → - New
🌐 Dual portals — public and agency staff, from one spec
Agencies that need a separate public portal and a staff portal (signed in with their Active Directory) can now capture that in one click: assign every role a portal, and screens, field exposure, validation and the build kit all follow. A 16-question agency questionnaire lands in Clarifications with recommended defaults, screens get portal badges with in-place fixes for any that span both, and build kits ship portal-aware prompts — enterprise SSO, deployment topology, and generated isolation tests included.
Learn more → - New
🔎 Readiness review — find the gaps before the build
One button reviews each finished use case the way a builder would read it — flow, screens, fields & data, business rules — and returns numbered clarifications: the question to ask your client plus the default we'd otherwise assume. Record decisions (or turn them straight into requirements), export the open questions as a client-ready Word document, and see "N clarifications block build" on the phase gate before a build kit ever ships a guess.
Learn more → - New
🔍 Guided search (add-on module)
Give the system you deliver a search box that answers from the client's own data — never from a model. The searchable catalogue derives from your approved screens, sensitive fields stay out by default, every query is permission-scoped and cost-bounded, and the generated SRCH requirements import into your project so search is tested and traceable like everything else.
Learn more → - New
🏗️ Ask us to build it for you
BidWin (bids & proposals) and BuildAI (the built system) are now service engagements rather than plans you buy yourself — our team does the work and you review it at every gate. Tell us what you need from the Contact page and we'll come back with how we'd approach it. Brieful itself is unchanged: still $49 per seat, still yours to run.
Learn more → - Improved
👥 A seat added mid-month is credited for what it paid
Adding a member part-way through a billing period is charged pro rata for the days remaining, and their AI-usage allowance is now prorated to match — so the credits track the money, the same way a mid-cycle plan upgrade already did. Their full monthly allowance starts at your next renewal. Members who joined before the period began are unaffected.
Learn more → - Improved
🔁 Change plan from Billing, with the price shown before you pay
Switching between Brieful and Brieful + BidWin now happens in Billing rather than the Stripe portal, and always shows the exact amount first. Moving up takes effect immediately, charges the prorated difference, and adds credits in the same proportion — so upgrading late in a cycle costs less and adds proportionally fewer credits, with the full allowance arriving at your next renewal. Moving down takes effect at your next renewal instead: you keep the higher plan and its full allowance for the period you have already paid for, and nothing is charged or refunded. Cancelled a subscription and changed your mind? A “Keep my plan” button brings it back without starting a second one. Any billing credit on your account is now shown on the page too.
Learn more → - Improved
💳 Billing now leads with what you have left
The Billing page has been rebuilt around the question people actually arrive with. It opens with your remaining credits rather than your spend, and one bar shows what you've used, what's left in this month's allowance, and any purchased credits held in reserve behind it. Credit packs now say what they buy before you click, and a new Credit activity list shows exactly where purchased credits went.
Learn more → - New
⚡ Buy extra credits when you run out mid-month
Hit your monthly AI budget in the middle of a deadline? Owners and admins can now buy a credit pack ($25 / $50 / $100 / $200) from Billing — charged once to your card and usable immediately. Purchased credits never expire and are used only after your monthly allowance, so nothing you pay for disappears at the end of a cycle. The usage meter shows your reserve alongside the monthly budget.
Learn more → - New
💳 Plans, billing and BuildAI kit licensing
Paid plans can now be started and managed from Billing in your workspace — monthly per seat, cancel anytime, with your AI-usage budget following your billing cycle. BuildAI build kits are licensed per bid and priced by the number of approved requirements they contain, fixed when the kit is first generated; if scope grows later, only the difference is invoiced. Kit licences are invoiced with payment terms rather than charged to a card, so agency buyers can pay by PO or transfer.
Learn more → - New
📐 Build kits now ship the technical documentation package
Every BuildAI kit now includes delivery-grade technical documentation, assembled from work you already did: a Solution Architecture Document with C4 diagrams, an Architecture Decision Record per workshop decision (options-not-taken included), interface control sheets, a mandated-vs-designed service-level document, and the intended data model. Two new build-session prompts complete it against the real code: as-built API/schema/operations docs, and a nine-area, review-gated security assessment with a government-readiness summary.
Learn more → - New
🔄 Living delivery — change kits, reconcile & drift
Delivered systems now stay synchronized with your specification instead of drifting from it. Every build kit carries a version manifest; when requirements change after delivery, download a Δ change kit containing only what moved — with CHANGES.md, plain-English release notes for end users, and a regression gate. A reconcile prompt in every kit makes the delivered code report its own drift back for your review, and a drift card on the BuildAI page (plus stale flags on training tasks) tells you at a glance whether what you shipped still matches what you specified.
Learn more → - New
📕 Role guides & quick-reference cards
Approved training tasks now assemble into deliverables: a per-role Word guide (getting-started with your site facts, every procedure with its traceability line, the status glossary) and a 1–2 page quick-reference card. The build kit also ships the approved tasks with instructions for expanding them into full guides against the real code — so delivered training can honestly claim to reflect the deployed system.
Learn more → - New
🎓 Training view — the task library
A new Training view turns each use case’s positive test cases into user procedures — plain-language steps bound to real screens, traceable to requirements and test cases. Every screen and button a task names is automatically verified against the screen map before you review it, and only tasks you approve feed the role guides and quick-reference cards coming next.
Learn more → - New
🎓 Training deliverables — SCORM modules, printable walkthroughs, roles & statuses
Your published narrated walkthrough is now three deliverables from one approved source: play it, package it as a SCORM 1.2 module for the agency’s LMS, or export it as a Word step-by-step procedure with a field reference. Plus a roles & statuses glossary generated from your domain pack — with anything used-but-undefined flagged instead of invented.
Learn more → - Improved
🏛️ Design Library v2 — enforced brand fidelity, per-project design & government templates
Prototypes now carry your design system as real CSS baked into every build, and each build is verified — off-brand colors and fonts are detected and auto-corrected. Upload one screenshot and Brieful reads your whole theme from the pixels (including the neutrals humans get wrong). New: logo/seal upload with a consistent branded header on every screen, per-project design forks for client work, WCAG AA contrast warnings, and built-in Government templates with the official-banner and accessibility conventions ready to go.
Learn more → - New
🎬 Movie mode — narrated, self-running prototype demos
Every prototype can now play like a product film: generate a screen-by-screen storyboard (review and edit every line, then publish), and ▶ Play walks the prototype by itself — screens advance, a voice narrates, a spotlight highlights what's being discussed, captions always on. 🎬 Play all chains every use case into one continuous demo, published movies play on share links, and ⬇ Demo HTML exports a standalone self-narrating file that works offline.
Learn more → - Improved
Generate all test cases in one click
The Test Cases view now has a “🧪 Generate all” button that covers every use case whose interview is finished — no more generating them one at a time. They run in the background and appear as each finishes, and the run stops cleanly if you hit your usage limit.
Learn more → - New
Phases — trim a big spec into a buildable Phase 1, grow with Phase 2+
The new 🧩 Phases panel organizes any project into phases: ✂️ AI trim proposes the minimum coherent Phase 1 and moves the rest to Phase 2 (nothing deleted — later phases show greyed as “Next phase”). Prototypes, screens, tests, and the document are phase-aware: build lazily per phase, later-phase prototypes EXTEND the approved earlier ones instead of rebuilding, and the document presents Phase 1 as the spec with later phases clearly marked. Completed phases lock; deleting a phase asks merge-vs-remove.
Learn more → - Improved
Map all screens & flows now runs in the background
“Map screens for all” and “Map all flows” no longer need the page kept open — they run in the background, so you can leave and come back. Progress shows on the button, finished maps appear as they land, and if anything is interrupted your completed maps are saved (just click again to finish the rest).
Learn more → - New
Step-by-step “Run a project” guide
A new 10-stage walkthrough (Guide in the top nav) takes you from a document or an idea to a build-ready spec, prototypes, tests, and an exported document — each stage shows what you do, what Brieful does, and how you know you’re ready for the next. The feature-by-feature reference is still there as “Help”.
Learn more → - New
Confirm scope, then choose: interview or auto-generate
After your processes and use cases are extracted, you now review and confirm them first — then choose your path: dive into the guided interview, or (for projects with a source document) auto-generate requirements for every confirmed use case in one step. The same unified scope engine powers core projects and BidWin bids.
Learn more → - New
Delivery use cases — work products, priced but not prototyped
Use cases now carry a kind: Feature (software behavior) or Delivery (work products and services like project plans, design documentation, training, or migration). Delivery use cases are tagged automatically when scope is generated from documents — flip any with the 📦/🖥 chip. They keep their requirements and count in estimates, but prototype building skips them: no more prototyping a project plan.
Learn more → - New
Watch your prototypes build live
Click Build all and a full-screen live view opens: every use case's screens appear on the canvas as the AI builds them, with a running screen count and timer, finishing with a build summary. You can close it anytime and reopen with the 🎬 Watch button.
Learn more → - New
Napkin mode — sketch to prototype
Snap a photo of a whiteboard, napkin sketch, or hand-drawn wireframe and upload it when starting a project. Brieful now reads the design — boxes become screens, arrows become flows, margin notes become rules — and turns your sketch into structured requirements and a clickable prototype.
Learn more → - New
Share prototypes with a link
Send anyone a clickable prototype — no login needed. Click 🔗 Share in the prototype view to create a time-limited public link (24 hours, 7 or 30 days), see how many times it was viewed, and turn it off anytime. The shared page carries your copyright and a confidentiality notice.
Learn more → - Improved
Edit screens without starting over
The Screens & Flows view now lets you make a targeted change — add a field, change a screen, adjust a rule — with a plain-English instruction, keeping the rest of the spec intact. Each use case expands/collapses, shows its requirement coverage, and screen mapping is available once a use case's interview is finished.
Learn more → - Improved
Much better prototypes
Prototype screens are now generated by our most capable AI model, with an automatic quality check that catches and repairs broken screens before you see them. Informational pages (FAQ, landing, dashboards) render as real content instead of forms, each screen shows which requirements it covers, and key actions in a prototype now actually work in demos — submit a form and watch the list update.
Learn more → - Improved
Better Word document exports
Your requirements document now exports to Word with process and screen-flow diagrams embedded as clean images (they used to sometimes appear as code). Large documents — hundreds of pages with lots of diagrams — export much faster now, with a live progress indicator so you can see it working.
Learn more → - New
Two-factor authentication (2FA)
Protect your account with an authenticator app: set up 2FA from Account → Two-factor authentication (QR enrollment + one-time recovery codes). Workspace owners can require 2FA for all members, and platform admins are always required to use it.
Learn more → - New
Build all prototypes in one click
In the Prototype view, use '🎨 Build all' to generate prototypes for every use case that doesn't have one yet — instead of building them one at a time. They build in the background and fill in as they finish.
Learn more → - New
Bring your existing requirements into Brieful
Joining a project midway? Use '⬆ Import requirements' to paste or upload requirements you already have (Word, PDF, Excel, CSV, or Markdown) — Brieful maps them into processes and use cases (preserving your IDs and priorities), you confirm where each lands or merge duplicates, and it then only interviews the gaps.
Learn more → - New
Draft requirements for a use case in one click
Any use case that has no requirements yet now shows a '✨ Draft requirements' button — Brieful drafts its core requirements from your uploaded document or notes so you don't start that use case from scratch, then you refine them in the interview. The use-case list also collapses/expands per use case to stay scannable.
Learn more → - New
Browse the domain pack library
A new Domains page lists every available domain knowledge pack, grouped by industry with search and filtering — so you can see which fields Brieful already covers as a built-in subject-matter expert. The library is growing across industries.
Learn more → - New
Domain packs: expert-verified vs AI-generated
Every domain pack now shows a trust level — '✅ Expert-verified' (reviewed by a person) or '🤖 AI-generated · beta' (a fast AI-built kickstart, not yet expert-validated). You see it when picking a pack, with a reminder to confirm AI-generated suggestions.
Learn more → - Improved
Domain packs: seeded requirements + per-pack release
Starting a project from a domain pack now offers the pack's default requirements and domain assumptions as one-click confirm items (the '💡 Domain' button). And each pack can be released to users individually — kept Internal for testing, then made Public when ready.
Learn more → - New
Domain knowledge packs
Start a project from a curated domain pack (e.g. Professional & Occupational Licensing) and Brieful asks expert questions and proposes the typical processes and use cases for that field — you confirm everything. Packs are authored and approved in the new Knowledge Studio.
Learn more → - Improved
Zoom and pan process diagrams
Process and flow diagrams now have an Expand button that opens a full-screen view at readable size — scroll or drag to move around, Ctrl/⌘+scroll to zoom — so large swimlanes are easy to follow instead of being squeezed to fit.
Learn more → - New
Project history & baselines
Every project now has a History panel: an activity timeline of who did what, and Baselines — named snapshots of your requirements you can compare against the live project and restore at any time. Great for client sign-off and tracking change.
Learn more → - New
See your AI usage as you work
A live usage meter now sits in your dashboard and project headers, showing how much of your monthly budget you've used. It warns you as you approach the limit, and each project shows its own approximate credit cost.
Learn more → - New
Choose how much detail you need
Start a project in Presales demo, MVP, or Full spec mode — the interview adapts its depth so a quick demo isn't buried in the same questions as a full build-ready spec. Change the scope anytime from the project header.
Learn more → - Improved
Discard & rebuild a prototype
Regenerate a prototype from scratch in one click when you'd rather start over than refine — your requirements stay untouched.
Learn more → - New
See how to navigate a prototype
Presentation mode now shows what's clickable: toggle highlighted hotspots on every screen, follow a Next steps bar to jump between screens, and hover a step to flash the link that takes you there.
Learn more → - New
Sync requirements from a meeting
Paste or upload a Teams/Zoom transcript and Brieful reconciles it against your requirements — proposing confirmations, edits, additions, and removals for you to review, each backed by a quote from the discussion.
Learn more → - Improved
Large projects build reliably
Prototypes, test cases, and the requirements document now build in the background section-by-section, so even very large use cases finish without timing out — however many requirements you add.
Learn more → - New
Start from a design template
Apply a ready-made design template — colors, fonts, and layouts — in one click, then customize. New workspaces start from a default template automatically.
Learn more → - New
Generate QA test cases
Turn each use case into traceable test cases (happy path, negative, edge, and permission), in step-based or Gherkin format, with requirement coverage and CSV export for Jira/Xray, TestRail, or Azure DevOps.
Learn more → - New
Team workspaces
Invite teammates into a shared workspace, collaborate on the same projects with roles and live presence, and share one design library across the team.
Learn more → - New
Clickable prototypes & flow canvas
Generate a working, clickable HTML prototype per use case, view it as screens or a Figma-style flow canvas, refine it by chatting, and export it as a standalone file.
Learn more →