Kemlat Header
Kemlat
  • Home
  • About
  • Services
    Business & TransformationA clear view of the problem and a plan you can deliver.8 Project & DeliveryGovernance that connects plans to results.3 ERP & CRMConnected processes and data in systems that fit your work.2 Digital ProductsWebsites, apps and platforms built around your needs.8 AI & AutomationPractical solutions for tasks that should take less time.8 Quality EngineeringMore confidence in every release.3 Cloud & SecurityA dependable foundation for your digital work.5 Managed ServicesStability, support and improvement after launch.3 Brand & CreativeAn identity and experience that tell your story clearly.4 Digital GrowthBetter visibility and decisions based on performance.5 Games & ImmersiveInteractive experiences for learning and for brands.4 Training & EnablementSkills your team can put to work.3
    All services56

    The KEMLAT Method

    KEMLAT
    Build your projectPick the services you need and get an approximate cost range in a minute.
  • Work
  • The Method
  • Insights
  • Contact
ARGet in touch
  • Home
  • About
  • Business & Transformation Project & Delivery ERP & CRM Digital Products AI & Automation Quality Engineering Cloud & Security Managed Services Brand & Creative Digital Growth Games & Immersive Training & EnablementAll services Build your project
  • Work
  • The Method
  • Insights
  • Contact
Get in touch
العربية [email protected] +962 79 122 3241
Check the Main Menu location in Apppearance->Menus->Display Location.
Business Intelligence for Owners: Ten Questions to Answer Every Week - Kemlat Insights
Kemlat2026-10-21T16:50:36+03:00
All insightsاقرأ بالعربية
Enterprise Systems

Business Intelligence for Owners: Ten Questions to Answer Every Week

Owners do not need forty dashboards. They need honest answers to about ten questions every week. What those questions are, and what has to be true in your systems to answer them.

20 November 20265 min read
Share
Business Intelligence for Owners: Ten Questions to Answer Every Week - Kemlat Insights

A familiar story: the owner of a mid-sized company has paid for a business intelligence project and still runs the business from phone calls. The dashboards exist, but they were designed by analysts for analysts: dozens of charts, filters and drill-downs that take time to learn. On the first morning of the week the owner calls the finance manager and asks, “How are we doing?”

Good business intelligence for owners starts from that phone call. It answers a short list of questions, every week, in the same place, from numbers everyone trusts.

Why owners stop opening dashboards

It is rarely a lack of interest. Owners stop using dashboards for three reasons. The numbers do not match what finance says, so they are not trusted. The dashboard answers questions the owner does not ask, such as sales by colour of product, while missing the ones they do ask, such as which customers are slow to pay. And it requires effort to find the answer, when the owner wants it on one screen.

All three are design problems, not technology problems. Power BI, Tableau, Looker Studio and the reporting built into most ERP (enterprise resource planning) systems can produce an excellent owner view. The work is in choosing the questions and making the data behind them reliable.

The ten weekly questions

Every business is different, but most owners of trading, manufacturing and service companies return to a similar set of questions. A useful owner view answers these, each with this week, the trend and the comparison that matters:

  1. How much cash do we have, and what do we expect in the next four to eight weeks? Bank balances, expected collections and committed payments. Cash surprises are the ones that keep owners awake.
  2. Are sales on track? Month to date against target and against the same period last year, split by the two or three dimensions that drive the business, such as branch, channel or salesperson.
  3. Are we making money on what we sell? Gross margin by product group or service line, with any significant drop highlighted.
  4. Who owes us money, and who is getting slower? Overdue receivables by customer and age, and customers whose payment days are lengthening.
  5. Which customers are growing or fading? Top customers’ purchases against their recent average. A large customer quietly buying less is often the most important signal on the page.
  6. Are we delivering what we promise? On-time delivery, service response times or project milestones, whichever reflects the promise to customers.
  7. Is stock healthy? Value of stock, slow-moving and expiring items, and stock-outs on key items.
  8. Are costs under control? Main expense lines against budget, especially those that move quickly, such as overtime, freight and fuel.
  9. What is unusual this week? A short list of exceptions: large credit notes, unusual discounts, sudden changes in a branch’s numbers.
  10. Where do I need to make a decision? Items waiting on the owner, such as large approvals, pricing exceptions or credit limit increases.

Ten questions, one page or two, refreshed automatically. Anything else belongs in departmental dashboards.

Practical tip: write each question in plain words at the top of its section of the dashboard. If a chart does not clearly answer the question above it, change the chart or remove it.

What has to be true underneath

A clean owner view sits on top of less visible work. Answering these questions reliably usually requires:

  • Agreed definitions. What counts as a sale (invoiced, delivered or ordered), how margin is calculated (with or without rebates and freight), when a receivable counts as overdue. Write them down and show them in the dashboard.
  • Data entered in the system, on time. If receipts are posted weekly, collections figures will always lag. If credit notes are raised at month end, margin will swing.
  • Connected sources. Sales and stock from the ERP, cash from bank statements, targets and budgets from finance, delivery data from logistics. Each needs an automated feed into the reporting model.
  • Clean master data. One record per customer and product, with groups and categories assigned consistently. Otherwise “top customers” splits one client across three names.
  • An owner for every number. When something looks wrong, someone specific checks and explains it.

An illustrative scenario: a family-owned trading company

Take a second-generation owner of a building materials trading company in Amman, with three branches and around 120 staff. A previous BI project produced a dashboard with 18 pages. He uses none of them and relies on a weekly call with the finance manager and each branch manager.

The redesign begins by listing what he asks on those calls. The list is short: cash, sales against target by branch, overdue customers, the top 20 customers’ buying, stock of slow items, and large discounts given. Two of those cannot be answered from the system at all, because discounts are recorded inconsistently and some customers exist under multiple names.

So the first month goes on data: a rule for recording discounts, a merge of duplicate customer records, and a daily feed of bank balances. The second month builds a two-page owner view answering the agreed questions, refreshed every morning, with a phone layout. The weekly calls continue, but they now start from the same numbers and spend their time on decisions.

Keeping the owner view honest over time

An owner view decays if nobody looks after it. Products are added, branches open, a new salesperson joins, and slowly the numbers stop covering the whole business. Give one person, usually in finance, responsibility for the owner view: checking at the start of each week that every feed refreshed, that totals agree with the accounting system, and that new branches or product groups appear where they should.

Review the questions themselves every six months. The business changes, and a question that mattered during a cash squeeze may matter less once the squeeze is over. Removing a page is as useful as adding one.

Weekly answers, not more charts

Business intelligence earns its cost when the owner opens it at the start of the week and finds answers they trust. To begin, write down every question you asked your managers by phone last week. That list, not the existing dashboard, is your specification. Building that foundation and the reporting on top of it, from data architecture to dashboards and data quality, is what our Enterprise Systems service is designed to deliver.

Found this useful?Share it with your team or someone who needs it.
  • WhatsApp
  • LinkedIn
  • X
  • Facebook
  • Telegram
  • Email
Related service

Enterprise Systems

We design and build systems, and migrate data into them, based on real operational needs, not generic templates.

Also related: Intelligent Automation

Explore our services

Related insights

Post-Go-Live: The First 90 Days After a System Launch - Kemlat Insights
Enterprise Systems

Post-Go-Live: The First 90 Days After a System Launch

Go-live is not the finish line. The first 90 days decide whether a new system becomes how the company works or a costly parallel to the…

19 Nov 2026 · 5 min read
Choosing the Right Database and Hosting for a Business Platform - Kemlat Insights
Enterprise Systems

Choosing the Right Database and Hosting for a Business Platform

The database and hosting decision is usually made in a five-minute developer conversation and lived with for ten years. What managers should ask before it is…

18 Nov 2026 · 5 min read
Single Sign-On and Identity: Keeping System Access Under Control - Kemlat Insights
Enterprise Systems

Single Sign-On and Identity: Keeping System Access Under Control

A sales manager leaves on Thursday and can still log in to the CRM five weeks later. Single sign-on and a clear identity process fix that,…

17 Nov 2026 · 6 min read

Kemlat Footer
Kemlat
Kemlat

We help organisations transform complex operations into clearer ways of working, practical solutions, and measurable outcomes.

Quick Links

  • Home
  • About Kemlat
  • Our Services
  • Selected Work
  • The Method
  • Contact Us

Services

  • Business & Transformation
  • ERP & CRM
  • Digital Products
  • AI & Automation
  • Cloud & Security
  • Digital Growth
  • All services
  • Build your project

Get in Touch

Email [email protected]
Location Almadina Almunawwara St., Amman, Jordan
WhatsApp & Phone +962 79 122 3241

© 2026 Kemlat. All rights reserved.

Privacy Policy Terms of Use
Kemlat Method

Request a Service

Tell us what you need and we will get back to you within one business day.

By sending this form you agree to our privacy policy.

Request received

Thank you. Our team will review your request and contact you within one business day.