Skip to main content
In short: All requests go through the same dialog. You have three options: a new dashboard, a change to a live dashboard, or a copy. Before sending, you see a cost estimate. Alex builds a preview first. Nothing goes live until you approve it.

​
A new dashboard

1

Open the dialog

In the Console, go to Builds and click Ask for a live app.
2

Fill in the fields

  • Starting point (Start from an existing dashboard, optional, beta): Keep the default No — a new dashboard to create a dashboard from scratch. Alternatively, select a live dashboard from your workspace. It then serves as the template for the new dashboard (see “A copy”).
  • Name (What should it be called?): The name becomes part of the fixed link. That is why it cannot be changed later.
  • Purpose (What is it for?): Describe which figures matter, who uses the dashboard and which decision it supports. If you already have the data, say where it lives. The more specific you are, the closer the first preview will be to what you need.
  • Data source (Do you already know where the data comes from?, optional): for example a website, a spreadsheet you keep, an API or a colleague who has the data. This is a starting point for sourcing the data. It is not a promise about the final result.
  • Project (Project, optional): If a coworker has already researched this topic in a project, select it here. The coworkers can then build on that research. If you keep the default No project — set it later on the app’s page, you can assign a project later on the dashboard’s page.
  • Existing data (Do you have data already?, optional): Use Add files to upload Excel, CSV, PDF, HTML, JSON, text or Markdown files. Each attached file appears individually in a list. You can remove it again before you send the request.
  • Design reference (Design reference, optional): Attach a file, such as an earlier dashboard, a brand manual or a screenshot. Alternatively, provide a website (Design reference: web address). The dashboard adopts its look. Without one, Alex uses the default style.
  • Effort (How much work is this?): Standard uses existing or easy-to-find data. Deep work starts with research and can include paid data sources. The cost estimate adjusts accordingly.
3

Check the estimate and start

The dialog shows a cost estimate in credits. It is an estimate, not a fixed price. Click Start the build.
Alex then defines the data areas, their cadence and the delivering coworker. You don’t have to decide any of this yourself. You can adjust all of it later on the dashboard’s page. See Data areas and refreshes.
Screenshot needed: the “Ask for a live app” dialog with the choice between Standard and Deep work and the cost estimate.
Describe what you want to know and who looks at it. You don’t need terms like “feed” or “schedule”. You can also simply ask Alex in a normal conversation. The usual plan checkpoint then shows you the plan and a cost range before work begins.

​
A change to a live dashboard

Want a new chart, a corrected figure or an additional source? Request a change.
1

Open the dashboard's page

Go to Builds and click the dashboard.
2

Click Ask for a change

Under What should change?, describe what should change. You can attach files and a website as a design reference.
3

Check the estimate and send

Before sending, you see a cost estimate. Then click Ask Alex for this change.
Your readers continue to see the current version until you approve the change. After that, the same link shows the new version, without interruption.

​
A copy

A typical case: you want to use a proven dashboard for a different market, region or organization. On the dashboard’s page, open the … menu and choose Copy dashboard. Alternatively, in the dialog for a new dashboard, select a template under Start from an existing dashboard. You can copy any live dashboard in your own workspace. Then describe the new context (New context): market, region or organization. If needed, attach lists of people, media or regions under Your material. Finally, click Start the copy.
  • A copy takes over the look, the sections, the data areas with their cadence, the structure of the lists, and the rules and method. The rules and method serve as a starting point. They are adapted to the new context.
  • A copy does not take over the list entries, the data, the link, the password or the refreshes. The original remains unchanged.
Hannah researches the data the new context requires. Until the first real refresh, areas without supplied material show sample figures. Lists without material receive clearly marked sample entries (“Sample person 1”), never invented names. Attached files may be up to 25 MB each and up to 30 MB in total.

​
What happens next

Your request appears on the Builds page while Alex works. Once the preview is ready, it shows Ready for you. If something went wrong, it shows Didn’t finish. Use Ask again to start the request again. A build that did not finish leaves no half-built preview behind. Continue with Preview and going live.

​
One job at a time

Currently, each workspace can only process one build or one change at a time. If you start a second job, the Console rejects it. It shows you which dashboard is currently being built.
Who pays the credits and when they are charged is explained under Costs.

​
What you can do next

Preview and going live

Review what Alex built and approve it.

Costs

What a live app costs and when the Console warns you.