--- title: "AI Dashboard Builder for Team Dashboards | Briks" url: https://briks.dev/ai-dashboard-builder description: "Describe the numbers your team watches. Briks builds a dashboard with key figures, charts and searchable tables and publishes it to its own address. Start free." --- AI dashboard builder # An AI dashboard builder for the numbers your team watches Describe the figures, lists and screens your team needs. Briks plans the frame and every screen, builds them from a kit made for dashboards, and publishes the result to its own address. Try an example - A sidebar, an icon rail or top navigation - Key figures, charts and searchable tables - Its own database, with sample records to start **Fenwick** - Overview - Deals *12* - Accounts - Reports - Team - Settings **Fenwick** - Overview - Deals - Accounts - Reports Search`Ctrl K` **Overview** Pipeline and deals for the sales team Pipeline value **$412k** *8% on last month* Deals won **14** *of a target of 20* Win rate **31%** *3 points on last month* Example data Pipeline by stage 42 Lead 28 Qualified 17 Proposal 9 Negotiation 14 Won Example data Biggest open accounts | | Stage | | | --- | --- | --- | | Fieldway Logistics | Negotiation | $61,500 | | Linden Hotels | Negotiation | $54,100 | | Harbour Foods | Proposal | $48,200 | | Ostara Health | Proposal | $37,400 | Example data 4 of 6 A working demo with sample data. Try it. ## How the AI dashboard builder works A dashboard build goes straight from your description to a plan of every screen. The questions before building and the look boards are for websites and apps. 1. **Describe the numbers** Say who uses the dashboard and what they need to see: the figures, the lists and the screens. The products, prices and people you name become its sample records. 2. **Show it a dashboard you like** This step is optional. Add a dashboard whose layout you admire, and Briks follows its frame, density, panels and the arrangement of its blocks. Its words, logos and figures are never used. 3. **It plans every screen** The plan sets the frame, the navigation in groups, and every screen as blocks in reading order: key figures, charts, tables, activity and forms, each with its width on a twelve-column grid. 4. **It builds from a dashboard kit** Every table is a full data table and every chart a real chart, on quiet panels with figures in tabular numbers. There is no motion and no decoration. 5. **It publishes** The dashboard is published to its own briks.live address, kept out of search, with hosting included. Contrast is checked in the code before it goes out. 6. **You change it in words** Ask for a new column, another chart or a different period in the studio chat. Every change is saved as a version you can undo. ## Three choices every dashboard plan makes Before a single block is placed, the plan settles the frame, light or dark, and how tightly the rows sit. Try all three in the demo at the top of this page. - Frame **Sidebar, icon rail or top navigation** A sidebar suits a product with many areas, listed in labelled groups. An icon rail suits one with only a few. Top navigation suits a handful of screens that sit side by side. - Mode **Light or dark** Chosen from your description, or from a dashboard you showed it, and you can ask for either. Status colours keep their meaning in both. - Rows **Compact or comfortable** Compact rows suit long tables and operations work, where more on the screen means less scrolling. Comfortable rows suit a screen that is read at a glance. ## What every dashboard build includes Dashboards are built from their own kit, not from website sections. These are the parts the planner chooses from. - **A frame that stays put** A sidebar, an icon rail or top navigation around every screen, with the current area marked and counts shown as badges where you give them. - **A top bar** Search, notifications and a menu with the user's name and role from your description, plus a workspace switcher when the product has several. - **A command palette** Press Ctrl or Cmd and K to jump to any screen or action by typing its name. - **Key figures** The three to five numbers a screen answers first, each with its label, value, change and period, and a small trend line where it helps. - **Charts** Line, area, bar, stacked bar and donut charts, one question each, with units, labels and a legend. - **Data tables** Every table, even a short top-five list, is a full data table: search, filters, sorting, page size, row selection with bulk actions, and actions on each row. - **Empty states** Every list, table and feed says what it shows when there is nothing in it, and offers the action that fills it. - **Phones** On a phone the sidebar becomes a drawer behind a menu button, and tables scroll inside their panel or stack each row as a card. ## The screens a dashboard is planned from The home screen comes first. The planner adds every screen your description names, and at least two more that the busiest navigation items lead to, so the dashboard is never a single page. Each screen is planned from one of nine kinds: overview, list, detail, reports, form, settings, team, billing and inbox. The kind decides which blocks it holds and in what order, and each block takes its width on a twelve-column grid, so a chart and an activity feed can share a row. Every navigation item is planned to lead to one of those screens. Account pages, such as sign-in and forgot password, stand on their own without the frame, and they work: once the dashboard is in production, only signed-in Staff and Admin accounts see its data. Overview: 6 blocks on a twelve-column grid A working demo. Pick a screen to see its blocks. ## Its own records, with sample data to start A dashboard keeps its records in the project's own database, a table for each kind of record its screens show, such as orders, tickets or stock. The first version fills them with believable sample records that agree with each other, dated over the months before today. The products, prices and people you name become records; anyone else gets an invented name. Its tables, charts and key figures read those records through the dashboard's own routes, and every total and count is worked out from the rows, so a card's total matches its table. Forms that add or change a record save it. You see and edit the records in the project's Database tab, and the dashboard shows the change. Not yet ### Its own data only A dashboard reads its own database. It does not connect to your other databases, a spreadsheet or another tool yet. ## Built to be read every day A dashboard is a working tool, so it is built differently from a website. Dashboards are dense, quiet and exact. One page ground, every block on a panel, figures in tabular numbers so columns line up, and one accent colour for the current item, the main actions and the data. Status colours are kept for status. There is no hero, no animation as you scroll, no blur and no decoration behind the content. The type is a quiet face chosen for reading numbers, and corners, surfaces and spacing follow your description or the dashboard you showed it. ## Publish it, change it, keep it - **Its own address** Every dashboard is published to its own briks.live address, kept out of search, with hosting included. - **For your team only** Its preview opens for anyone with the address. Once it is published to production, only signed-in Staff and Admin accounts see its data, and you set each person's role in the Database tab. - **Changes in plain words** Ask for a new column, another chart or a different period in the studio chat. A change holds 5 credits and is charged for the work it took. - **Versions** Every build and change is a version. Anyone with edit rights can undo, redo or restore one. [Versions and undo](https://briks.dev/features/versions-and-undo) - **The code** Browse and edit the files written for your dashboard, and download them on a paid plan. [Your code](https://briks.dev/features/your-code) ## What dashboards cannot do yet - Not yet **Connect to other tools** A dashboard reads its own database. It does not read your other databases, a spreadsheet or another tool yet. ## What it costs to build a dashboard Dashboards use the same credits and plans as websites and apps. **50** credits held while a new dashboard builds **5** credits held for a change **5** credits held for a check A hold is set aside while the work runs. Each job is then charged for the work it took: what it does not use comes back, anything past the hold is drawn from your balance, and a request that fails is not charged. - **Free** **$0** to start - 50 credits once, at sign-up - 1 site - A briks.live address - 500 MB storage - **Starter** **$16** a month or $160 a year, 2 months free - 175 credits a month - 1 site - Your own domain - 5 GB storage - **Pro** **$29** a month or $290 a year, 2 months free - 400 credits a month - 3 sites - 3 of your own domains - 10 GB storage - **Studio** **$79** a month or $790 a year, 2 months free - 1,200 credits a month - 10 sites - 10 of your own domains - 25 GB storage - **Agency** **$199** a month or $1,990 a year, 2 months free - 3,000 credits a month - 30 sites - 30 of your own domains - 100 GB storage The Free plan's 50 credits are given once; there is no daily top-up. Paid plans are bought online at checkout, monthly or yearly. [Compare every plan](https://briks.dev/pricing) ## Questions about the AI dashboard builder ### What is an AI dashboard builder? It is a tool that turns a description of the numbers your team watches into working dashboard screens. With Briks you describe the figures, lists and screens, and it plans them, builds them and publishes the dashboard to its own address. ### Where do the numbers on my dashboard come from? From its own database. The first version fills it with believable sample records for your product, and every figure is worked out from those records. You change them in the project's Database tab, and the dashboard follows. ### Can the dashboard connect to my database or a spreadsheet? It has a database of its own: its records live in the project's database, where you edit them in the Database tab, and its forms save to it. It does not connect to another database or a spreadsheet yet. ### Can my team sign in to the dashboard? Yes. Its sign-up, sign-in and password reset pages work. While it is a preview, anyone with its address can open it; once you publish it to production, only signed-in Staff and Admin accounts see its data. Sign up with the email you use in the studio to become its Admin, then give your team their roles in the Database tab. ### Can I base it on a dashboard I like? Yes. Add a reference and Briks follows its frame, density, panels and the arrangement of its blocks. Its words, logos and figures are never used. ### Does Briks ask questions before building a dashboard? No. The questions before building and the look boards are for websites and apps. A dashboard goes straight from your description to a plan of every screen. ### Does the dashboard work on a phone? It is built for phones too. The sidebar becomes a drawer behind a menu button, and tables scroll inside their panel or stack each row as a card. ### Will my dashboard have animations? No. Dashboards are built without motion, decoration or blur, so the numbers are what you see first. ### Can I change it after it is built? Yes, in plain words in the studio chat, as often as you like. Every change is saved as a version you can undo, redo or restore. ### How much does it cost to build a dashboard? A new dashboard holds 50 credits while it builds and a change holds 5, and each is charged for the work it took. You start free with 50 credits once, and paid plans start at $16 a month, bought online at checkout. ## More ways to build with Briks - [**AI website builder** Describe your business in plain words.](https://briks.dev/ai-website-builder) - [**AI app builder** Describe what your app should keep and show.](https://briks.dev/ai-app-builder) - [**All features** Every feature, with what it needs: a plan, a switch or nothing at all.](https://briks.dev/features) - [**Templates** Start from a site that already works, rewritten for your business.](https://briks.dev/templates) ## Which numbers does your team need to see? Describe them in a sentence. Start with 50 free credits, no card needed. [Or start from a template](https://briks.dev/templates)