Skip to content

    One definition for every number

    Every number is traced to the system it comes from and given one agreed definition. The monthly pack is built on top, and its assembly is automated only once those definitions hold.

    You can’t skip a rung, because each one rests on the one below. (read where we wrote it)

    Which three streams should the monthly report draw on?

    Sales, operations and people. Most companies measure the first closely and the other two hardly at all, so the report shows a third of the business.

    1. Sales data

      Revenue and the CRM: what was sold, at what price, to whom, and what is still in the funnel.

      • Revenue by customer, product and sales channel
      • Leads and how many become sales, shared with the Revenue Operating System
      • Orders signed, invoices sent and cash collected, and the three match

    2. Operations data

      SLAs, quality, onboarding, project closures and billing: the stream most companies have never instrumented.

      • Each client tracked from first day to last
      • Service and quality numbers reviewed monthly, not pinned up
      • Invoices raised when work is delivered, not when someone remembers

    3. People data

      Headcount, cost and capacity, read from whatever HRMS or master the company keeps, and forecast forward.

      • One staff list every report reads from, never retyped
      • Staff cost forecast by client and for planned hires
      • Team capacity checked against the plan, so hiring follows the numbers

    How does a number get from its source to the board pack?

    Agreeing the definitions takes longest, because that is where teams find they disagree.

    1. Find where the numbers actually live

      Sales in a CRM, operations in a spreadsheet, people in a payroll tool, cash in the bank. The first job is establishing which source is authoritative for each number.

    2. Agree the definitions

      Most reporting disagreements are definition disagreements. What counts as a closed deal, when revenue is recognised, which headcount is billable. Written down once, used everywhere.

    3. Build the monthly pack

      One document that tells the story of the month: what happened, why it differed from plan, and what it means for the next quarter. Built to be read by a board, not assembled to satisfy one.

    4. Move it from manual to automatic

      Once the definitions are stable the assembly can be automated. Doing it in that order is why our packs survive the month someone is on leave.

    What do founders ask about MIS?

    What does MIS stand for?

    Management information systems. In Indian practice it usually means the monthly reporting pack a management team and a board use to run the business, covering financial and operational numbers together.

    How is MIS different from financial statements?

    Financial statements are backward-looking and built for statutory compliance. An MIS is built for decisions: it carries operational drivers, comparisons to plan, and the leading indicators that say what is about to happen rather than what already did.

    What should an MIS pack contain?

    At minimum the profit and loss against plan, cash and runway, the revenue pipeline, unit economics for the core product, and headcount. Beyond that it depends on what the business actually runs on, which is the part worth spending time deciding.

    How long does it take to set up?

    The reporting itself can be built in weeks. The part that takes longer is agreeing definitions across teams, because that is where the real disagreements surface, and skipping it produces a pack nobody trusts.