Masarkum has no separate “AI section”. Assistance appears inside the screen you are actually working in — the project page, the risk register, the policy document — and always ends in a human decision.
Built and running inside the existing modules.
A full charter from data you already entered
Reads the project overview, its strategy linkage, team, key results, milestones and challenges, then drafts a one-page charter in six sections: vision, outcomes, scope, team, milestones, risks.
Any single section can be regenerated without touching the rest, a full revision history is kept, and the approved charter exports to Word and PDF.
From a forty-page document to what it obliges you to do
An executive summary of each policy, a version comparison that shows what actually changed, and extraction of the obligations it creates so they become trackable controls.
From a table cell to a paragraph fit for the board
Drafts the risk description, its likely impact and its treatment plan in executive-report language, drawing on the probability, impact and linked controls already in the register.
Gather the evidence once, satisfy several frameworks
Suggests where one control satisfies more than one standard — NCA, ECC, ISO 27001 and 22301, NIST CSF, PDPL — cutting duplicated evidence gathering between audit cycles.
A starting point instead of a blank page
Builds a first-pass BIA for any asset from its metadata and comparable prior analyses, for the continuity team to review and adjust rather than write from scratch.
Turns the dashboard into a written briefing
Reads the KPI dashboards and writes a briefing explaining what changed, why, and what is needed — ready for leadership without rewriting.
In a government and enterprise context, AI is judged less by what it can do than by what it is not allowed to do. These are our four limits.
Every generated output arrives as a draft carrying an AI-generated marker, and is adopted only after review by a person with approval authority. No path in the platform bypasses that cycle.
Where the source data is insufficient for a section, the system marks it “needs input” and lists what is missing, instead of inventing plausible-looking content.
Model version, prompt version, token count, latency and outcome are recorded for every call in an auditable log. Access keys are never logged.
Subscriber data is not used to train general-purpose models and stays isolated from every other organisation’s data, as the privacy policy and subscription agreement set out.
Designed and specified in our build documents, not yet released. We list it because an organisation choosing a strategy platform is choosing a direction for the next five years, not one — and not as a commitment to a release date.
From one objective to a complete plan
Turns a broad objective into sub-objectives, KPIs, initiatives, risks and a proposed timeline, learning from prior years’ data and established sector practice.
Catches the decline before it becomes a crisis
Watches KPIs continuously and, when one slips, proposes specific actions: reallocating resources, adjusting the timeline, changing the initiative owner, or creating a supporting initiative.
Data that arrives without anyone entering it
Integrates with the organisation’s systems — ERP, HRMS, CRM, email, calendar, document libraries, spreadsheets — to update KPIs automatically instead of by periodic manual entry.
Test the decision before you take it
A “what if” scenario environment that projects the effect of a change on KPIs, risks, schedule and budget, so the decision rests on a data-based estimate rather than instinct.
Finds the gap in the strategy map
Links KPIs to objectives and initiatives to sub-objectives automatically, and surfaces objectives no KPI measures and initiatives that serve no objective.
The monthly report writes itself
Produces periodic reports as slides and PDF, explaining KPI movements, analysing root causes and recommending action — at a depth matched to the reader: a one-pager for a minister or a detailed deck for the PMO.
Ask the strategy directly
Query and update through conversation: “show me the late initiatives in customer experience” returns the list, the reasons for delay, and suggested remedies.
These are targets from our product design document, not measured results from live operations. We show them as what we are building toward.
40–60%
target reduction in the time to build a strategic plan
70%
target reduction in periodic report preparation time
6
sections generated by the automatic project charter
100%
of generated outputs pass through human approval
We will walk through the charter generator, policy summarisation and performance narrative on data close to your own reality — not a canned example.
