Questions and answers

A dashboard that builds itself from your own numbers. You describe what you want to see in plain words - sales by shop, pallets by loader, cash against plan - and a Guru builds it on your own site. From then on it updates as your data does.

Any business that has numbers it wants to see clearly: shops, warehouses, accountants, clinics, restaurants, trades, finance teams, boards. If the numbers exist somewhere - a till, a spreadsheet, a system, a sheet on a clipboard - a dash can be built from them.

No. If you can describe what you want to see, it can be built. There is nothing to install and nothing to configure - you ask, a Guru builds.

Exactly that. You ask for a dash or a change on your Requests page and press Send. A Guru builds it. There is no form to fill in and no menu of fixed charts to pick from.

Sign in with the login you were given. Your company has its own address - yourcompany.askadash.com - and you land on your dashboard. If you do not have a login yet, ask whoever looks after askadash at your company, or ask us.

There is a pricing guide with plans by company size and how many builds a month they include. The figures on it are placeholders for now - every plan is agreed with you, and there is no automatic charge for anything you do on the site.

One of askadash's own people. Gurus read what companies send, build it, answer questions and keep the sites running. Everything that gets built passes through a Guru first.

Open the Requests page. Write what you are after in plain words - or turn on the AI and talk it through - drop any files onto it, then press Save. It sits below as Pending until you press Send.

Your request appears on the Guru screen. A Guru reads it and can build it, tidy it up first, ask you a question, or turn it down with a note. Each step shows on your card, so you always know where it is.

Saved but not sent yet. You can still edit it, add files or take them off. Nothing happens to a pending request until you press Send.

A Guru has a question before they build. Their note is on the card. Edit your request with the extra detail and press Send again.

Yes, always with a note saying why. The usual reasons: it needs something outside your own data, it is not yet clear enough to build, or it would do something the site should not do - such as sending anything to a customer or supplier.

Small changes are often done in minutes once a Guru has picked them up. Bigger builds take longer and the Guru will say so on the card. You can carry on using the site while it happens.

New KPI tiles, charts, tables, comparisons (this week against last, this month against plan), pages for entering data, alerts when something goes out of range, a whole new dash for a colleague, a board pack - anything you would otherwise build in a spreadsheet or a slide deck.

It cannot reach data you have not given it, send anything to third parties, touch another company's site, or make figures up. If a request needs any of those, a Guru will say so.

Yes. Drop spreadsheets, PDFs, screenshots or photos onto a request. They stay with the request so the Guru can see exactly what you mean.

It helps you turn an idea into a request that can be built - it asks the short questions a Guru would ask (what is measured, over what period, from which file, who looks at it). It cannot build anything itself and it cannot see inside your files; it works from what you type.

Yes. If it has not been built yet, raise a new request saying so - or, if the Guru has asked a question, edit the original and send it again. Once something is built you can ask for it to be changed like anything else.

A quicker way to raise a request about the page you are looking at. It sits at the foot of every page. Save it as pending, or Send it straight to the Gurus - it is tagged with the page name so nobody has to guess which one you meant.

Your own data. That can be pages on the site where your people enter figures, files you send with a request, or systems we connect to for you. A dash never shows anyone else's data.

As soon as the data behind it changes - a row entered on a page shows on the dash straight away. Sources that arrive on a schedule (a nightly file, say) update when they arrive.

Yes. Entry pages can be built for anything you currently keep in a sheet - a row per day, per job, per person. They have add, edit and delete, and a one-off import that brings your existing spreadsheet rows across.

Yes. Each person can have their own dashes as well as the company ones, and a Guru can build a new dash for a colleague on request.

Personal look - light or dark, background motion, density, text size, accent colour - is under Settings by your name. Company-wide look and formats are in Company settings for admins.

A gentle set of curves that drift behind the page. The button in the header cycles Gentle, Brisk and Still, and the site respects a reduced-motion setting on your computer.

Yes. Pages lay themselves out for the screen they are on, so the dash you check at your desk is the one you check on the way in.

Staff see the pages they are given. Users can also raise requests. Admins look after their company's people, page access and company settings. Gurus are askadash's own people and build what is sent.

Page access is set per person by an admin, so a loader sees the loading page and the dash, and the finance lead sees the figures they need. Nobody sees another company's site.

Admins: Users & access in the Pages menu. Add their name, login, email and role, tick the pages they should see, and they are in.

Sharing a dash with a colleague - view only, or let them build on it - is being built now. Until it lands, an admin can give them access to the same pages.

Coming soon: channels for each team, direct messages and @mentions, right next to the numbers. It is on the front page so you can see the shape of it, but it is not live yet.

An admin at your company or a Guru can set you a new one. Once you are in, you can change it yourself under Settings, Account.

Every company has its own address, such as yourcompany.askadash.com. Signing in at askadash.com sends you to yours. Bookmark it.

No. Each company's data is kept separately and people only ever see their own company's site. Gurus can see every company's requests, because they build them, and nothing else crosses over.

No. The AI helpers work from what you type to them. Files you attach to a request are for the Guru, not the AI, and the figures on your dash are never sent to an AI model.

On askadash's own server, in askadash's own software. It is not put into any shared or public AI service.

The most recent build can be put back by a Guru if something is not right - it restores the site's pages, never your data, so nothing anyone has entered is lost. If an earlier change has broken something, raise a request with BUG at the top rather than undoing.

People at your company who have the Requests page, and askadash's Gurus. Nobody else.

No. askadash shows your numbers to your people. It does not send anything to anyone outside your company.

Ask a dash. It has two tabs: Ask a dash is a helper that answers questions about the page you are on and how askadash works - what a pill means, where a setting lives, how to raise a request. Ask a dev goes to a real person.

Got a problem, or trying to build something and struggling? The Ask a dev tab sends what you write to a real person at askadash. If you are signed in it becomes a request card on your Requests page, so you see the reply there; from the front page, leave your email and a dev replies to that.

No. It explains. Anything you want built or changed goes through the Requests page and Send, so a Guru always sees it first.

Now and then the assistant steps aside for a while rather than guess. It comes back on its own, everything else keeps working, and Ask a dev is always there.

Only in the browser tab you are in, while it is open. Nothing you type to it is kept against your login.

No - it knows how the site works, not what is on your dash. Ask a Guru, or look at the page, for the numbers.

Type the dash you have in mind and it sketches one in about twenty seconds - tiles, charts and pages - so you can see the shape of the idea. It is a sketch with made-up figures: nothing is built and nothing is stored. Sign in to have it built for real.

A worked example that plays on its own: a request is typed and sent, a Guru builds it, and the dash appears. Six examples from different industries, all with sample figures. Pick one from the tabs or just watch.

Because we are British, and your dash should read the way you do. Colour, centre, organisation - on purpose.

Nice-to-haves: things on your dash that would make the day easier but are not worth spending a build request on - a tile you would like moved, a column that would be handy, a page that could do with a better name, a colour that is hard to read, an idea, a grumble. Good or bad, it is all welcome. Wishes go on the devs' not-a-priority list; when one is simple and there is time it gets built for free, the wish is marked Built, and the company's admins are told.

Press Report a bug at the foot of any page. Say what happened, what you expected and which page you were on. A screenshot helps enormously.

The team reads it and marks it Actioned, Completed or Rejected with a reply. If you have asked for emails in Settings, you get one when it changes.

The Settings link by your name is yours alone - look, motion, text size, notifications, your password. Settings in the Pages menu are site-wide: company settings for admins, platform settings for Gurus.

Settings by your name, then Account. You need your current password to set a new one.

When a request you raised is built or replied to, when a bug you reported changes, and a daily summary at a time you choose. Tick the ones you want in Settings, Notifications.

Log out in the header. It signs you out everywhere on askadash and takes you back to the start page.

Yes - every company gets yourcompany.askadash.com, and your people are sent there when they sign in.

Company settings let an admin set the company name, accent colour, date and number formats, the day the week starts, and which features are switched on.

No. A login belongs to one person at one company. That is what keeps everyone's data apart.

Yes. It is your data. Ask a Guru through the Requests page and it will be handed back to you in a usable form.

Often, yes. Say what the system is in a request and a Guru will tell you what is possible and what it involves.

Press Ask a dash in the bottom corner: the first tab answers questions about the site, the Ask a dev tab reaches a real person. For a change or a new dash, use the Requests page. For something broken, use Report a bug. A Guru sees all of it.

Raise it as a bug with the page name and what you expected to see. If the figure comes from an entry page, check the row there first - the dash shows what has been entered.

Yes. Every request and bug report is read by a Guru, who replies on the card. If you would rather talk, say so in the request and someone will get in touch.