Website to Qlik app
2:45 built from nothing
- 9 sheets
- 1,950 calls to Qlik
- Zero clicks
Every chart proven identical.
Every change is signed off before it goes in.


After main picture Before inset
No rebuild. No changes to your script, data model or master items. Nothing to install.
20 minutes · screen share · no prep · no access to your tenant
Founded by Brian Booden, 9x Qlik Luminary and Partner Ambassador, 2016 to 2025. 36 reviews from past Qlik work.

Sample Executive Dashboard app, sample data in US dollars. Not a client's app.
Sample Executive Dashboard app, 2 Oct 2026.
A website, an existing Qlik Sense app or a QlikView app. Same process, every app, whoever runs it.
2:45 built from nothing

39/39 charts identical

460/460 checks identical
Sample and demo apps, not clients' apps. One working day is what the HighCloud demo app took, not a promise for yours.
Qlik's MCP server creates sheets and charts, but it has no tools for themes, layout or styling. And Qlik says checking AI output is your job.
"It is the user's responsibility to review and verify any GenAI output before using or sharing it."Qlik help: Qlik MCP server
Qlik is changing how custom theme CSS works: Qlik Cloud from 18 August 2026, client-managed Qlik Sense in the November 2026 release. Looks built on CSS tricks are the ones at risk.
"Document Object Model (DOM) selectors in custom CSS are not a supported pattern."Qlik Community support update, 30 Mar 2026
Moving to another BI tool for a modern look means new models, new measures and every figure tested again. A Glow Up keeps the model your business already trusts.
It plays on its own; drag the handle to take over. Same app, same selections, same numbers. Only the presentation moved.

Sample Executive Dashboard app, sample data in US dollars. Not a client's app.
Was: KPI Dashboard
What changed
What didn't
20 minutes on a screen share. No prep, no access to your tenant.
Nothing reaches your app until the values gate says every chart matches.
"name": "Your brand",
"palettes": { ... },
"fontFamily": "Your font"Colours, type and chart palette from your own brand, built as an installable JSON theme: the route Qlik supports.


AI restyles a copy of the app the board opens. Every sheet is scored against one written design standard before anyone signs it off.
Every chart, under every agreed bookmark, before and after. One difference and nothing ships: it rolls back.
The same look on the apps you choose, each with its own values report. Same app IDs, links and bookmarks.
Sample Executive Dashboard app, 2 Oct 2026
Anyone can restyle a Qlik app, and anyone can run Qlik's QlikView converter. The difference is how it's done: one process, the same on every app, with the paperwork to prove it.
Both are sample apps, not clients' apps. One working day is what the demo app took, not a promise for yours.
Reviews its own work. Scores it. Fixes it. Scores it again.
Proven 4 Oct 2026 on a test copy of the Executive Dashboard: 11 fixes, 1 undo, every values gate passed, the original app untouched.
Round 1 done on the staging copy. Values gate: PASS.
Reviewed my own work and fixed what I found. Values gate: PASS. Scored again.
3: call it Sales by region
Done on the staging copy. Values gate: PASS.
approve
From a real Glow Bot run on 5 Oct 2026, on a test copy of a sample Accounts Receivable app. Values gate: PASS, 112 objects identical.
Every change stays on the staging copy until a named approver says approve.
Original objects unchanged after the full redesign of the sample Executive Dashboard, then replayed onto the live app with 0 differences.
How we measured itEach chart's values are fingerprinted before and after, under agreed bookmarks. One mismatch rolls the change back.
Values gate, sample app, 2 Oct 2026Filters, navigation and drill-downs all still working after the redesign: 294 checks in all.
How we measured itFilters, navigation buttons and drill-downs checked against the engine after the change.
Functionality audit, sample appBB Data Services' website rebuilt as a live Qlik Cloud app from nothing: 9 sheets, zero clicks.
How we measured it1,950 calls to Qlik in one run, with nobody at the keyboard.
Film 01: website to Qlik app, Oct 2026Every figure on this page comes from a real build or a real review.
How we measured itFirst client case study follows the founding pilots. Until then, the sample app does the talking.
Our rulePick a sector. Hover a card for the work.
He has helped us with the concepts, application and PoC evaluation of transitioning of our existing Qlik Sense estate to their cloud product.
Brian played a key role in supporting the stabilisation of our Qlik applications and the successful running of the SDR Qlik application.
Brian's deep and practical knowledge of Qlik has helped us to significantly improve the speed and accuracy of the computational engine.
From past Qlik work, not Glow Up projects.

Since 2012 I've been in the room with Qlik teams. The data models are usually excellent. The front ends often aren't, and people judge the numbers by how the app looks.
In February 2026 Qlik's MCP server arrived. It can build apps and charts, but it has no design layer, and nothing checks the numbers afterwards. So I built both, as one process that doesn't depend on who runs it.
GBP, ex VAT. No day rates, no surprises.
The full Hero App Glow Up at half price, for a named case study.
The app the board opens, made to look like your product.
The same look across the apps you choose.
No prep · no access to your tenant · no hard sell
Your demo is with Brian Booden, founder of BB Data Services and 9x Qlik Luminary and Partner Ambassador, 2016 to 2025. Not a sales rep.
Pick a topic or search. If yours isn't here, ask it on the demo.
No. Script, data model, expressions, master items, variables, bookmarks and section access are never touched. Only presentation changes: theme, layout, chart styling, titles. Every chart is checked before and after.
The values gate. Before anything changes, every chart's values are recorded under the bookmarks we agree with you, with a test user for each section access profile. After the change, the same check runs again. One difference anywhere and the change rolls back. You get the report: on the sample app, 39 of 39 charts identical.
Designed sheets can calculate differently from the originals, so we don't guess. Calc time for every sheet is measured before and after and reported, and you see the numbers before anything goes live. Measured and reported, never promised.
One command takes the whole glow-up off. Your original sheets stay in the app as Classic sheets throughout, so nobody loses the view they know.
Yes. We rehearse on a copy, then replay the same change log on your app after you sign off, so the app ID stays the same and everything pointing at it keeps working.
A named user in your tenant (for example glowup@yourcompany) with edit rights in one space that holds the apps in scope. It only sees the spaces you add it to. Your admin does two one-off jobs: create that user, and install the theme.
Not for the work itself. Themes are tenant-wide, so installing one is usually your Qlik admin's job: they upload it once, or let us do it while they watch.
No. If your admin has enabled it, it's used for read-only steps such as reading the data model; the restyle and the checks don't need it. Qlik MCP is available on all Qlik Cloud subscriptions once a tenant admin activates it and gives users the Qlik MCP permission.
Only what the job needs, and we agree it up front. The AI sees app structure: object definitions (titles, chart types, dimension and measure names, expressions), sheet layouts, the punch list and your replies to the bot, and sheet pictures, which can show numbers. It does not read data rows or the load script, and the values gate compares fingerprints of each chart's values, not the values themselves. Under the AI provider's commercial terms, this traffic is not used to train models. Prefer no AI at all? The bot can run on offered options only.
Yes. The Glow Bot runs on its own, as a dedicated user whose only access is the Glow Up staging space. It posts each result and a numbered punch list to your Slack channel; you reply in plain words ("3: call it Sales by region", "undo 2", "approve") and it makes the change on the staging copy, re-runs the values gate and replies with the proof. Nothing reaches your original app until a named approver says approve.
Slack, in a channel of your own: pictures, buttons and replies all work there. Microsoft Teams works in part today (text replies, no pictures or buttons), and email is available too. We set it up with your IT during onboarding, and it only acts on replies from the people you name.
Only Qlik MCP tool calls count: Qlik counts every five billable MCP tool calls as one question, from the same monthly allowance as Qlik Answers. Glow Up's heavy work (audits, restyle, values gates) doesn't use MCP tool calls. If you'd rather use no questions at all, we leave MCP off.
No. By default we run the Glow Bot for you and the AI usage is part of our price. If your IT policy wants it inside your own cloud, it can run there on your own AI provider account, directly or through your AWS, Google Cloud or Azure contract. Or it can run with no AI at all, on offered options only.
No. Qlik sets a limit on calls a minute for each user, and a Glow Up stays well inside it: building BB Data Services' whole website as a Qlik app from nothing took 2:45. We can also run the checks out of hours if you prefer.
No extensions. Your colours, fonts and chart palettes go into a JSON theme, the route Qlik supports after its 2026 CSS changes. Anything that still needs a style setting is listed in the change log, so nothing is hidden.
Glow Up is built and proven on Qlik Cloud. Qlik MCP is Qlik Cloud only. Running client-managed Qlik Sense? Ask on the demo and we'll scope it.
It depends on the app, so we agree a timeline at kick-off once we've seen it, including your review and sign-off. We don't promise a duration up front.
AI does the heavy lifting: it builds, records values and runs the checks. Every sheet is scored against one written design standard, and a named approver signs off the gate report. Nothing goes in without that sign-off.
Reply to the bot in your channel. Every run ends with a punch list: what is left, a picture of each item and one or two proposed fixes. Reply with the item number and what you want; the bot applies it to the staging copy, proves no number moved and replies in the same thread. Anything it cannot do is flagged for a person to do by hand, and it is still re-checked before it ships.
Your app restyled, your theme, the values gate report, the functionality checks, calc times for every sheet, a change log and the one-command undo.
Yes. Send your brand guidelines, or point us at your website. Colours, fonts and chart palettes become your Qlik theme. On its own that's the Brand Kit.
Moving a QlikView estate to Qlik Cloud? Qlik's converter keeps the QlikView look. We add a value check against the original, a register of every QlikView item, and a modern Glow Up on top. We've taken a QlikView demo app (HighCloud Airlines) through it end to end: 460 of 460 chart checks identical against QlikView, converted, redesigned and proved in one working day. That's what the demo app took, not a promise for yours. Ask on the demo call.
People decide whether to trust a number by how it looks. A clear, consistent app gets opened, read and believed. The data was already right; a Glow Up lets people see it.
A rebuild means new models, new measures and every number tested again, plus retraining everyone. A Glow Up keeps the model your business already trusts and proves nothing moved.
The full Hero App Glow Up at half price, £3,250 ex VAT, for a named case study. There are three places.
Yes. Founding partner pilots are open for co-delivery or white-label work with your clients. Apply for a demo and say you're a partner.
No questions match. Ask it on the demo.
Same process, every app, whoever runs it. Three founding pilot places at half price, for a named case study.