Skip to main content
Demystify OS

Services

Demystify OS for IT services

IT services: Software studios, IT consultancies, support and AMC providers, SaaS resellers and firms that bill overseas clients, from small teams to mid-sized firms.

Demystify OS lists 6 workflows for this industry, each step with the proof you check, and 5 of them are available today.

Every status on this page is shown as recorded: available, in beta, early access, on the roadmap, or on request.

Demystify OS Cloud Starter, 25 people: from ₹14,999 a month plus GST.

Demystify OS Cloud is an invite-only beta from 1 November 2026, public from 1 January 2027.

The moment that matters

Month end arrives, and someone has to turn a month of logged hours, retainers and export work into correct invoices before the owner chases the last one.

What Demystify OS runs for IT services

Counted on 2 November 2026. A job we have not built is shown as on the roadmap, never as live.

Workflows

  • Export invoice draft

    Available

    Bill an overseas client. Raise an invoice in the client's currency with the rupee rate noted. When you bill an export, the invoice prints your LUT declaration. A reminder tells you when your LUT is due for renewal.

    Proof: Currency, rate and declaration text come from the system on an export invoice. Whether a sale counts as an export stays your CA's call.

    Done by: Finocket

  • Month-end invoice lines from hours

    Available

    Turn logged hours into invoice lines. Developers log time against a client and project on the timer. At month end, unbilled hours become invoice lines at your rate cards.

    Proof: Logged hours become invoice lines.

    Done by: Finocket

  • Milestone invoice schedule

    Available

    Bill a fixed-price project in tranches. Split a project contract into milestone invoices. The tranches cannot add up to more than the contract.

    Proof: Billed milestones are checked against the contract limit.

    Done by: Finocket

  • Retainer and AMC invoice run

    Available

    Send retainer and AMC invoices on a rule. Set a recurring rule for each retainer or support contract. The invoice goes out on schedule.

    Proof: The monthly retainer invoice is raised from a rule.

    Done by: Finocket

  • Prepaid contract release schedule

    Available

    Spread a prepaid annual contract across months. Record a prepaid annual support or SaaS contract and see the deferred revenue schedule month by month.

    Proof: The monthly release schedule is built from the prepaid contract. The accounting treatment stays your CA's judgement.

    Done by: Finocket

  • TDS list for your CA

    Early access

    Record TDS your client kept. Record the TDS a client deducted and read it in the TDS summary. You and your CA match it against 26AS at year end.

    Proof: TDS entries are kept in one list. Matching to 26AS is still done by a person.

    Done by: Finocket

Routines

  • Four-week baseline, then a monthly read

    Early access

    Cadence: Four weeks first, then every month

    You receive: Each metric below names where its number comes from; where it says a manual count, keep that count in a sheet.

Skills

  • Export invoice draftOn the roadmap
  • Month-end invoice lines from hoursOn the roadmap
  • Milestone invoice scheduleOn the roadmap
  • Retainer and AMC invoice runOn the roadmap
  • Prepaid contract release scheduleOn the roadmap
  • TDS list for your CAOn the roadmap

Integrations and distribution channels

  • CRM

    Early access

    Keep client and project contacts next to their invoices and hours, so the founder sees who is open and who is due.

    Through: Finocket

  • Web

    On the roadmap

    A client page for open invoices and statements. Estimates, open invoices and statements are on the client link today; a fuller project status page is planned.

    Through: Industry pack

  • Email

    On the roadmap

    Through: Connector Hub

You approve

Approvals themselves are in beta, invite-only. Each card approves the work of an agent that is on the roadmap for this industry, so each is shown as planned.

  • On the roadmap

    Approve or send back the month-end invoice batch

  • On the roadmap

    Approve or reject an export invoice before it goes to the client

Memory and governance

One memory for every agent, and the controls around it.

Each agent would need to remember once your client list with currency, your rate cards, your LUT details, your retainer and milestone terms, and your TDS sections, so no job asks for them again.

  • Memory fabric

    Built, not launched to customers

    One memory shared by every agent: your parties, items, price lists and decisions are held once, with where each came from, so an agent does not ask you the same thing again.

  • Approvals

    In beta, invite-only

    Anything with a consequence waits for you. You tap approve or reject on your phone, and Mysty acts only after you do.

  • Evidence ledger

    Built, not launched to customers

    Every action leaves a receipt, and the receipts are kept in one ledger you can check later, for your own auditor.

  • Guardrails

    Built, not launched to customers

    Each agent has one role, a limit on what it may do and a named checker. Nobody marks their own work done. Money, publishing and outreach stay a person's decision.

Time and errors back: how you will see it

Measure first, then compare. Your own four weeks are the only baseline that counts. We print no promised saving.

  • Time

    Hours, rate cards and recurring rules sit in one place.

  • Errors

    Export declaration text, currency and milestone limits come from the system.

  • Cash

    Retainer and milestone invoices follow recurring rules.

  • Control

    Project, client and TDS reports read from the same books.

Before you start
For four weeks before you switch on, count in a sheet: invoices raised in the month and how many are still unpaid, export invoices with a credit note for an error, and timesheet entries returned at approval.
Every month after
Each month, read the same counts again and compare them to your four-week baseline.
Who reads it
Founder or finance lead
Where it shows
Each metric below names where its number comes from; where it says a manual count, keep that count in a sheet.

Metrics to adopt: how the business runs

  • Open invoices share

    What it is
    Share of the invoices raised in the period that are still unpaid.
    Formula
    invoices still unpaid / invoices raised in the period x 100
    Where the number comes from
    Finocket client report (/reports/clients)
    How often
    monthly
    Better is
    lower

Errors: count them as errors over transactions

  • Export invoices corrected

    What it is
    Share of the export invoices raised in the period that carry a credit note tagged as a wrong currency, rate, tax line or declaration.
    Formula
    export invoices with a credit note for an error / export invoices raised x 100
    Where the number comes from
    Finocket invoices and credit notes; counted by hand from the list
    How often
    monthly
    Better is
    lower
    One error is
    One export invoice with a credit note raised to correct a wrong currency, rate, tax line or declaration counts as one error, however many credit notes touch it. Count only invoices raised in the period you are measuring.
  • Timesheet entries sent back

    What it is
    Share of the timesheet entries submitted that a manager returned at approval.
    Formula
    entries returned at approval / entries submitted x 100
    Where the number comes from
    Timesheet approval card (built, behind a switch); until on, a manual count in a sheet
    How often
    weekly
    Better is
    lower
    One error is
    One timesheet entry returned by a manager at approval counts as one error, a human rejection.

Start with a four-week baseline

  1. Step 1. For four weeks, count open invoices, export invoices with a credit note and returned timesheet entries in a simple sheet.
  2. Step 2. Ask your people to log every hour on the timer against a client and project, and set a recurring rule for each retainer or AMC contract.
  3. Step 3. Raise your next export invoice and your next milestone invoice in Finocket, and read the project and TDS reports at month end against your baseline.

What OS does not do for you yet

OS does not yet track export realisation deadlines, EDF or e-BRC status, or MSME payment ageing for this industry, so keep those on your own calendar.

Source is a code and document read dated late October, not a walked product. Timesheet approval, project profit and retainer cap cards are built but behind a switch, so the jobs shown are timer, export invoice, milestone, recurring, deferral and TDS jobs are shown. Claims for this vertical are not approved yet, so no rate or deadline is stated. Readiness table row: READY.

Sources: art:finocket-usecase-map-it-services-1028, art:vertical-readiness-live.

The mix for your business

Pick what fits. Each product keeps its own site, and each link below says where it goes.

  • Demystify OS

    In beta, invite-only

    The platform: the workflows, routines and channels above, with approvals and a receipt for every action. Editions: Community, Cloud, Private.

  • Mysty and Mysty Workers

    Available

    Mysty is the AI. Mysty Workers is the AI workforce that does the jobs. Mysty on the company site (opens a different site)

  • Finocket for IT services

    Available

    GST bills, stock and books for this kind of business. See it on finocket.com (opens a different site)

  • ASHR.work

    Available

    People operations for your team, including Employee Directory, Leave Management, Holiday Calendar, Documents & Templates. ashr.work (opens a different site)

  • Demystify Assure

    On the roadmap

    Compliance for firms and their clients. Planned, ready 31 December 2026.

Start with the Diagnostic

Start with the Diagnostic: ₹1 L plus GST, ten working days, read-only connectors. The fee is credited to your plan.

Demystify OS Cloud is from ₹14,999 a month for 25 people. Invite-only beta; public from 1 January 2027.

Ask what Demystify OS runs for IT services

Questions

What does Demystify OS do for IT services?
It lists 6 workflows, such as Bill an overseas client and Turn logged hours into invoice lines, and shows each one's status, so you can see which are available and which are on the roadmap.
What is available today and what is not?
Each workflow, routine and integration carries a status chip: available, in beta, early access, on the roadmap or on request. A job we have not built is never shown as live.
What does it cost?
Demystify OS Cloud Starter, 25 people: from ₹14,999 a month plus GST. Start with the Diagnostic: ₹1 L plus GST, ten working days, read-only connectors. The fee is credited to your plan.
When can I start?
Demystify OS Cloud is an invite-only beta from 1 November 2026, public from 1 January 2027.
How does this connect to Finocket?
Finocket has a vertical kit for this industry on finocket.com, linked from this page. Demystify OS works alongside it: Finocket keeps the books and stock, OS runs the routines around them.
Who sees my data?
Connectors start read only, anything with a consequence waits for your approval, and every action leaves a receipt in a ledger you can check. Demystify is DPDP-aligned and has SOC 2 on the roadmap.