Skip to content
ASKIQ

Ask your business.
Get an answer.

The answer is already in your systems. It is just split across the accounting package, the CRM, the operational tool and a folder nobody has opened since March. ASKIQ connects to all of them and answers in plain English, in seconds, showing exactly which system every figure came from.

No signup. Read-only connections. Your data is never used to train a model.

An illustration of the product answering a question. A finance director asks why net profit fell when revenue rose. The assistant reads four systems in turn, naming each one with the number of records and the time taken, then answers that costs rose faster than revenue, with the figures behind it. All companies and figures shown are fictional.

Nobody is short of data. They are short of answers.

  • The answer exists. It is in four systems.

    The ledger knows the revenue, the CRM knows the customer, the field app knows the hours. Nobody has joined them since the last time somebody spent a weekend on a spreadsheet.

  • Every question becomes somebody’s afternoon

    A simple question turns into a request, a queue, an export, a pivot table and a version that is already out of date by the time it lands.

  • So people stop asking

    The real cost is not the waiting. It is the questions nobody bothers to raise, because the answer would arrive too late to act on.

One question. What it turned up.

Six questions from the live demo, each answered in seconds. The companies and figures are fictional; the findings are not. Every business has a version of these, sitting across systems nobody has joined.

  • Money you are owed

    £412,000of approved variations, done and never claimed

    Asked: Where did our margin go against tender?

    Nearly half the margin lost against tender was not cost at all. Calderwood alone holds £238k of it.

    The decisionRaise the claims this week

    Ask it in the Build IQ demo (opens in a new tab)
  • Work done at a loss

    £128,400a year, lost across seven fixed-fee contracts

    Asked: Which contracts are losing us money?

    The worst pays £2,400 a month for 41 hours of effort, most of it spent on one legacy application.

    The decisionReprice seven contracts at renewal

    Ask it in the IT IQ demo (opens in a new tab)
  • Money you are owed

    £386,000of unbilled work over ninety days old

    Asked: What is sitting in WIP right now?

    Twenty-two matters have had no time recorded for six months and no bill raised. The work finished; nobody closed the matter.

    The decisionBill twenty-two matters

    Ask it in the Legal IQ demo (opens in a new tab)
  • Capacity you already pay for

    £51,280of revenue lost to no-shows in one month

    Asked: What is our no-show rate?

    One clinic runs at 11.4% against 7% for the group, because it sends reminders 24 hours ahead instead of 48.

    The decisionChange one reminder setting

    Ask it in the Health IQ demo (opens in a new tab)
  • The wrong fix, avoided

    49%of late drops were late before the truck left

    Asked: What is actually causing our late deliveries?

    Traffic, the usual explanation, accounts for 16%. Most late dispatches come from one depot, where picking runs 41 minutes past cut-off.

    The decisionFix picking at one depot, not the routes

    Ask it in the Route IQ demo (opens in a new tab)
  • A leak, caught in the month

    £48,000of a £92k cost rise, traced to one staffing decision

    Asked: Why did net profit fall when revenue rose?

    Four contractors joined mid-month at agency rates, and the work is still being billed at the original tender price.

    The decisionReprice before the next invoice run

    Ask it in the Finance IQ demo (opens in a new tab)

None of these needed a new system, a data project or an analyst. The data was already there. What was missing was someone asking.


What changes at the top table

For the people running the business, the difference is not faster reports. It is meetings that end in a decision.

  • One number in the meeting

    Today

    Finance brings one figure, sales another, operations a third. Each is right about its own system on the day it was pulled, and the first half hour goes on reconciling them.

    With ASKIQ

    Everyone asks the same connected systems and gets the same answer, with the source attached. The meeting argues about what to do, not whose spreadsheet is right.

  • The board pack stops being a project

    Today

    A week of exports, cross-checks and chasing before anyone writes a word, and the figures are a fortnight old by the time the board reads them.

    With ASKIQ

    The figures are asked for the week of the meeting, against current data, each traceable to its source. The pack still gets written. Assembling the numbers stops taking a week.

  • The follow-up gets asked in the room

    Today

    "Why is that?" is met with "we will come back to you", and by the next meeting the moment to act has passed.

    With ASKIQ

    The second question is asked while everyone who can act on it is still sitting there.

  • The business stops depending on one person

    Today

    One person knows how to build the report. When they are on leave, or leave, the business goes without.

    With ASKIQ

    The knowledge of where each number lives is in the connectors and the vocabulary, not in one head.


Connect, ask, watch it work

Four steps, and only the first one involves anybody from IT.

  1. 01

    Connect what you already run

    Accounting, CRM, PSA, practice management, telematics, file storage, databases, your own internal apps. Read-only credentials, connected once. Nothing is migrated and nothing moves.

    • Read-only by default
    • Connected once, not per question
    • Your systems stay where they are
  2. 02

    Ask in your own words

    No query language, no report builder, no waiting for someone in finance to have a free afternoon. A question typed the way you would say it out loud.

    • Plain English, not SQL
    • Follow-up questions keep the context
    • Ask across systems in one question
  3. 03

    Watch it do the work

    Every lookup is named as it runs: which system, how many rows, how long it took. The working log is not decoration, it is how you know the answer came from your data rather than from a guess.

    • Each source named as it is read
    • Row counts and timings shown
    • The query itself, where it applies
  4. 04

    Get an answer, not a dashboard

    Figures, a table, a chart or a written recommendation, whichever the question actually deserves. Then the follow-ups it thinks you will ask next.

    • Seconds, not next Tuesday
    • The shape suits the question
    • Suggested follow-ups, already loaded

Six examples. The mechanism is not one of six.

These are demonstrations built on fictional companies, each connected to the systems that sector actually runs. Nothing about them is hardcoded. Pick one to see the systems it reads and the questions it answers.

Finance IQ

Finance director, controller or CFO

Your ledgers, asked in plain English.

Revenue, margin, cash and debtors across accounting, payments and CRM, compared, charted and written up without opening a spreadsheet.

Demo company
Northgate Group
Multi-entity services group
Connected systems
XeroAccountingSage 50AccountingStripePaymentsHubSpotCRMEmployment HeroPayroll
Questions it answers
  • Why did net profit fall when revenue rose?
  • Which customers are slowest to pay?
  • Which division is actually most profitable?
  • What does our cash position look like?
and 46 more in the demo

Every company, figure and system pairing above is fictional, built to show the shape of a real answer. The connectors are not: those are the systems these sectors run.


Three things, done properly

Everything else in the product supports one of these.

Connects to everything, moves nothing

Your accounting package, your CRM, your practice management system, your file storage, your own database. Read in place, with read-only credentials, on the day you connect them.

  • No migration project
  • No data warehouse first
  • Read-only by default

Answers in seconds, with the working shown

Each lookup is named as it runs, with the system, the row count and the time it took. You see where the number came from before you see the number.

  • Named sources, live
  • Row counts and timings
  • Traceable figures

Speaks your business, not your schema

Taught your vocabulary, your entities and your reporting rules, so an answer arrives in the language the business already uses.

  • Your terms, your entities
  • Your financial calendar
  • Curated questions on day one

What it actually does

Connects to what you already have

No migration, no data warehouse project.

The systems your company runs on stay exactly where they are. ASKIQ reads them in place, which is why connecting one takes an afternoon rather than a quarter.

Details

Asks across systems, not one at a time

The question nobody can answer today.

Most questions worth asking span two or three systems, which is exactly why they go unanswered. One question here reaches all of them.

Details

Shows its working

An answer you can defend in a meeting.

An assistant that cannot show where a number came from is a liability in any conversation that matters. Every answer here carries its provenance.

Details

Answers in seconds

Fast enough to ask the second question.

Speed is not a vanity metric here. A report that takes three days is a report you only request when you are already sure; an answer in seconds is one you can be curious with.

Details

Stays inside your walls

Your data does not become somebody else’s training set.

An internal assistant only earns the "internal" part if the data it reads stays under your control. This is the part IT asks about first.

Details

Fits the business it is put in

It should know what a "matter" is.

A generic assistant makes the reader translate. This one is taught your vocabulary, your entities and the shape of your own reporting.

Details

What waiting for answers costs you now

Put in your own numbers. Nothing here is our estimate of your business, and the working is printed underneath, the same as every answer the product gives.

Your business, today

Starting figures only. Move them until they describe you.

12

Directors, managers, team leads

3

Anything that means a report, an export or asking someone

2 h

Finding it, exporting it, joining it, checking it

3 d

The queue, not the effort

Loaded cost: salary plus on-costs

Every year, answering those questions costs

£149,040

£149,040 a year, 3,312 hours

Hours a year
3,312
Full-time people
1.9
Answers a year
1,656
Each one arrives
3 days late

The working

12 people × 3 questions × 46 weeks = 1,656 answers

1,656 × 2 h = 3,312 hours

3,312 h ÷ 1,725 h a year = 1.9 people

3,312 h × £45 = £149,040

That is the price of the current way, not a promise about ours. Someone still reads the answer and decides. What goes is the export, the join, the pivot table and the wait. It also leaves out the most expensive line: the questions nobody asks, because the answer would arrive too late to act on.


The questions IT asks first

Where does our data actually go?

Sources are read in place with read-only credentials and nothing is migrated. It can be hosted for you, run inside your own cloud tenancy, or self-hosted entirely. Your data is never used to train a model.

Can it see things people should not see?

No. It reads through your existing permissions, so a person sees only what they could already open in the underlying system. It does not widen access, and every question is logged.

What if it makes something up?

Every answer names the systems it read, the row counts and the timings, and shows the query where one was run. An answer you cannot trace is one you should not trust, so tracing is built in rather than offered.

How long before it is useful?

Connectors go in first and the first questions are answered the same week. A curated question set for your business means day one is useful rather than a blank prompt.

Our industry is not one of the six.

The six in the demo are illustrations, not a product list. The connectors are generic and the questions come from your own data, so the sector only decides which systems get plugged in.

Do people need training?

They need to be able to type a question. That is the whole interface, which is the point of building it as a chat rather than another dashboard nobody opens.

Pick your industry and ask it something hard.

Six sectors, fifty real questions each, answered in seconds with the working shown. It takes about two minutes to tell whether this solves a problem you actually have.