A dashboard review is best sold as a priced custom request: the follower sends a link, screenshots, or export of their Tableau, Power BI, Looker, or Google Sheets dashboard, and the analyst returns written or recorded feedback on layout, chart choice, and clarity within a set turnaround — no live call, portfolio marketplace, or booking calendar required. Custom Work lets you offer clearly scoped commissions and services: you set the price, the scope and the delivery time, and followers submit a brief and pay before you start.
How do you sell dashboard reviews from your bio?
Use Custom Work to sell a fixed-price dashboard review linked from your bio. The follower pays upfront, attaches a Tableau, Power BI, Looker Studio, or Google Sheets link or export, and you return written notes, an annotated screenshot, or a recorded walkthrough inside the delivery time you set. No live call, no scheduling.
The asynchronous format is a product fact rather than a preference: Brillay states that "Brillay is asynchronous — you answer questions by text and deliver Personalized Videos or services as recordings or files on your own time, within the delivery time you set. There are no live video calls or appointments to schedule" (how it works, FAQ "Are Brillay interactions live calls?"). Because a follower submitting a dashboard has already built the artifact, the reviewable material arrives with the order and the reviewer works from it directly.
The file exchange is what makes the format work. A Brillay Custom Work lets the follower attach their own files when they order, and lets the creator deliver "a written note plus up to 5 files (video, audio, images, PDF, Word, Excel, or PowerPoint)" — video or audio up to 20 minutes — "and/or a private link (Google Drive, Loom, Dropbox…) for anything larger". A dashboard link in, annotated notes or a screen recording out, fits that envelope without a scheduling step. The follower's dashboard is not an attachment to a generic product; it defines the work, so each order returns feedback on that specific file rather than the same review sold to everyone.
What counts as a dashboard review versus a tool-choice question?
A dashboard review is feedback on an already-built dashboard that the creator opens, inspects, and comments on. A tool-choice question is a text decision about which platform to adopt before anything is built. The distinction matters because only one of the two needs a file exchange, and that determines which Brillay offer fits.
“Should I build this in Tableau, Power BI, or Looker?” or “Is Power BI worth learning over Excel for my role?” are decision questions a follower can ask by typing the full context in one message.
A dashboard review is different, because an existing artifact — a live link, a screenshot set, or an export — has to be opened, inspected, and commented on. That requires the file-attachment capability Custom Work supports. A related but distinct request — a follower asking for a dashboard to be built from scratch rather than critiqued — calls for a separate build offer with its own scope and pricing.
| Request | Best-fit offer | Why |
|---|---|---|
| “Which BI tool should I learn first?” | Paid Questions | Text-based decision question |
| "Here's my Tableau dashboard link — what's wrong with it?" | custom request | Requires opening and evaluating a built artifact |
| "Build me a dashboard in Sheets from this data" | custom request (build, not review) | A different deliverable — a new build, not feedback on an existing one |
| "Quick encouragement before my portfolio review" | Personalized Video | A message, not technical feedback |
What should a dashboard-review listing include?
A dashboard-review listing should state five things: what the follower submits, which formats are accepted, how many pages or tabs are covered, what feedback format comes back, and the delivery time. Vague scope is the main reason an asynchronous review runs long, because an unspecified "dashboard" can be one page or twenty.
At minimum, a listing should state:
- Input: A shareable link (Tableau Public, Power BI published report, Looker Studio, or Google Sheets) or a set of screenshots/exported PDF if the dashboard is private.
- Scope: Number of dashboard pages or tabs covered — for example, "one dashboard, up to 3 tabs/pages."
- Feedback format: Written notes, an annotated screenshot, or a short recorded video walkthrough.
- Focus areas: Layout and hierarchy, chart-type choice, color use, filter/interaction design, and whether the dashboard answers its stated question at a glance.
- Delivery time: A delivery time you can reliably meet. You choose a delivery time from 1 hour to 5 days based on how much of the dashboard you agreed to review.
- Exclusions: Whether the review covers underlying data quality or SQL/DAX, or is purely visual/UX feedback on the finished dashboard.
Related reading: How to Write a Custom Request Offer covers scoping a listing so incoming requests match what was actually priced.
What should the review itself cover?
A useful dashboard review checks whether the visual design lets a viewer read the data quickly, not only whether the numbers are correct. The standard review areas are stated purpose, chart-type choice, visual hierarchy, color use, and interaction design — the same attributes emphasized by published dashboard guidance from Nielsen Norman Group, Tableau, and Microsoft.
Nielsen Norman Group, which studies how people read data visualizations, frames a dashboard's job directly:
"Dashboards are collections of data visualizations, presented in a single-page view that imparts at-a-glance information on which users can act quickly." — Nielsen Norman Group, "Dashboards: Making Charts and Graphs Easier to Understand" (source)
Nielsen Norman Group also recommends encoding the most important numbers using length and 2D position — the visual attributes people judge fastest and most accurately, such as bar and line charts — and reserving color for categorical grouping rather than magnitude, because viewers do not perceive color as an ordered quantity.
Density is the second thing worth checking, and two vendors publish specific numbers for it. Tableau's own data-visualization guidance tells authors to "limit the number of views in your visualization to three or four," warning that "if you add too many, the big picture is lost in the details" (Tableau, "Data Visualization Tips and Best Practices"). Microsoft's Power BI documentation recommends limiting a visual to 10–20 total fields for readability and performance, and states that the upper limit for a visual is 100 fields (Microsoft Learn, "Customize the Visualizations Pane in Power BI Desktop").
Microsoft states the page-level version of the same rule in its optimization guide:
"It's highly recommended you limit the number of visuals on a particular report page to only what is necessary." — Microsoft Learn, "Optimization guide for Power BI"
A structured dashboard review walks the file against a fixed checklist: what question does this page answer, does the most important chart carry the most visual weight, how many views compete for attention, and does color carry meaning or decoration.
| Review area | What to check | Common issue found |
|---|---|---|
| Purpose | Does the dashboard state what question it answers? | No title or context; viewer has to guess |
| Chart choice | Are bars/lines used for comparisons, not pie/donut charts? | Pie charts used for values that are hard to compare by angle |
| Hierarchy | Does the most important number get the most visual weight? | Every chart sized the same regardless of importance |
| Density | Are there few enough views and fields to read at a glance? | A dozen views on one page, well past Tableau's three-or-four guidance |
| Color | Is color reserved for grouping, not implying rank or value? | A default rainbow palette applied to sequential data |
Who is the buyer for a paid dashboard review?
The buyer is usually someone who built a dashboard for a job application, a bootcamp capstone, a client project, or a work deliverable and wants a second opinion before it reaches a decision-maker. That is a narrower and more motivated audience than the general population of people learning BI tools.
Career switchers into data roles are a large, documented segment. The U.S. Bureau of Labor Statistics projects that "employment of data scientists is projected to grow 35 percent from 2025 to 2035, much faster than the average for all occupations" (BLS Occupational Outlook Handbook, Data Scientists). BLS also projects about 24,800 openings for data scientists each year, on average, over the decade; those figures come from the Employment Projections program, whose 2025–2035 round was released on August 27, 2026 and which BLS updates annually. A steady stream of people entering the field through bootcamps and self-study creates recurring demand for a second, experienced set of eyes on a portfolio piece.
The buyer's earning power is documented too. The median annual wage for data scientists was $120,230 in May 2025 (BLS Occupational Outlook Handbook). For operations research analysts — another role that regularly builds and presents dashboards — the median annual wage was $88,940 in May 2025, with employment projected to grow 12 percent from 2025 to 2035 (BLS Occupational Outlook Handbook, Operations Research Analysts). Across computer and information technology occupations the median annual wage was $109,470 in May 2025, against $50,980 for all occupations. BLS wage figures describe who is buying, not what a dashboard review should cost, and no figure on this page projects what a Brillay offer will earn.
How should a dashboard review be priced?
Price a dashboard review on three inputs: pages or tabs covered, depth of feedback, and response format. A one-page written critique and a multi-tab recorded walkthrough are different amounts of work. Set each tier so the price clears a target hourly rate after the platform fee and payment processing are deducted.
The tiers and dollar figures below are illustrative examples, not Brillay data and not a pricing recommendation. Assumptions: a US creator, prices in USD, Brillay's 8% platform fee when a follower pays for work, and Stripe's published US rate of 2.9% + 30¢ per successful transaction for domestic cards (Stripe Pricing). Processing rates outside the US differ, so the net column applies to US card payments only.
| Tier | Scope and format | Illustrative price | Illustrative working time | Illustrative net at midpoint |
|---|---|---|---|---|
| Quick Read | One dashboard, one page, top 3 issues, short written notes | $25–$50 | 20–30 minutes | $37.50 → $33.11 |
| Full Review | One dashboard, up to 3 tabs/pages, written notes + annotated screenshot | $60–$120 | 45–75 minutes | $90 → $79.89 |
| Walkthrough | One dashboard within scope, recorded voice/video walkthrough | $120–$200 | 60–90 minutes | $160 → $142.26 |
The margin logic is arithmetic on Brillay's 8% platform fee when a follower pays for work (tips and goals carry 5%) and Stripe's published US card rate. A $90 Full Review clears $79.89: $90 minus a $7.20 platform fee minus $2.91 in processing ($90 × 2.9% + $0.30). At 60 minutes of working time, $79.89 is roughly $80 an hour. Working backward, a creator who wants a given hourly rate should divide it by about 0.89 to cover both fees, then add a margin for the reading and setup time a dashboard needs before feedback starts.
For a sanity check against employed rates: the BLS median annual wage of $120,230 for data scientists works out to about $58 an hour on a 2,080-hour year, which is this page's own arithmetic on the BLS figure rather than a BLS-published hourly wage (BLS Occupational Outlook Handbook). A review tier priced below that effective rate is being sold under what the same skill earns salaried.
What if the dashboard is bigger than what was purchased?
Decline an out-of-scope request rather than absorbing the extra work — a 12-tab enterprise reporting suite submitted to a one-page "Quick Read" tier is not the job that was paid for. Brillay publishes that option directly, so the scope boundary is enforceable rather than a negotiation the creator has to win.
A request that falls outside what you listed can be declined: Brillay's Custom Work page explains that a creator can decline any Custom Work order from their dashboard, including one that falls outside the scope they listed, and the request closes with the follower keeping their money. You're always in control of what you take on. Restating the page/tab limit at the point of decline, and pointing the follower to a larger tier, keeps the boundary clear.
Setting the page or tab limit before a request comes in covers those limits up front, which is easier than renegotiating scope after a follower has already paid.
What else can a BI-focused creator sell alongside dashboard reviews?
A dashboard review works best as one offer among several, because incoming requests arrive in different shapes: text decisions, file reviews, encouragement, and open-ended support. Put Custom Work, Paid Questions, Personalized Videos, Tips, and Goals behind one Brillay link so each follower can choose the paid option that fits what they need.
- Personalized Video: Encouragement before a portfolio review, interview, or capstone presentation.
- Goals: Cash toward a stated goal, such as funding an open dataset or a template library, with a visible progress bar rather than a per-item purchase.
- Tips: A way for someone who found a free tutorial or template helpful to contribute without buying a specific deliverable.
Developers and data practitioners weighing where else to route paid requests can see the fuller pattern on how developers get paid for review DMs.
What are the most common questions about selling dashboard reviews?
The recurring questions are whether a review needs a live call, whether to use a Paid Question or a custom request, how long a delivery time can be, what Brillay charges, and whether an oversized request can be refused. Each short answer below cites Brillay's published pages or the payment processor's published rate.
Does a dashboard review need a live screen-share call?
No. On Brillay, you deliver a dashboard review on your own time, with "no live video calls or appointments to schedule". The follower shares a link, screenshots, or an export, and the creator returns written notes, an annotated file, or a recorded walkthrough within the delivery time set on the service.
Should a dashboard question be a Paid Question or a custom request?
Use Custom Work when the follower needs to share a dashboard link, screenshots, or an export for the creator to open and evaluate, because Custom Work accepts attached files from the follower.
How long can a dashboard-review delivery time be?
For Custom Work, you set a delivery time in whole hours (1–24) or days (1–5), up to 5 days. Set a short window for a single-page "Quick Read" tier and the longer end for a full multi-tab walkthrough.
What does Brillay charge to sell dashboard reviews?
No monthly fee, you only pay a small platform fee when you get paid. 8% platform fee when a follower pays for work, 5% platform fee on tips and goals. Card processing is separate. There is no follower minimum. Stripe's published US rate is 2.9% + 30¢ per successful transaction for domestic cards; rates outside the US differ.
Can I decline a review request that's too big for the tier the follower bought?
Yes. A request that falls outside what you listed can be declined: Brillay's Custom Work page explains that a creator can decline any Custom Work order from their dashboard, including one that falls outside the scope they listed, and the request closes with the follower keeping their money. Decline rather than completing an oversized review for free, and point the follower to a tier that matches the dashboard's actual size.
Create your free Brillay page and turn the next "can you check my dashboard?" DM into a clearly scoped, paid review.
Keep reading
New in the library
Ready to get paid for the interactions you already get?
Create your free Brillay link