Turn strategy into measurable progress.
StratCo Flow connects assessment, planning, execution, measurement and reporting in one place, so leaders and teams set direction, organise delivery and understand what their efforts are achieving.
| Objective | Owner | Status | Trend | Current | Target |
|---|---|---|---|---|---|
| Increase cereal production | DPS, Agriculture | On track | 58,400 t | 62,000 t | |
| Reduce maternal mortality | DPS, Health | At risk | 112 per 100k | 95 per 100k | |
| Improve customs clearance time | Commissioner, BURS | Off track | 9.2 days | 4.0 days | |
| Digitise land records | Director, Lands | On track | 81% | 100% |
Most tools own one stage. This one closes the loop.
Assessment platforms stop at the diagnosis. Reporting tools stop at the report. Delivery tools never knew the strategy. StratCo Flow runs all five stages on one model, so the report you publish in March is the evidence you plan against in April.
Scroll sideways to see the whole diagram
Frameworks are configuration
Balanced Scorecard, KPI and RAG, OKR and digital maturity are settings over one model. Switch or blend them without a migration, and run a Balanced Scorecard ministry that holds an OKR technology team.
One cascade, top to district
National vision to national development plan to ministry to department to district, as nested workspaces. Every level owns its own scorecard and rolls up to the one above it.
History that cannot be edited
Check-ins are append-only, enforced in the database rather than by convention. A number that was reported in June still reads the same in December, and the audit trail says who wrote it.
Know where you actually stand.
Evaluate performance, capabilities, risks and opportunities, and establish the evidence needed to make informed strategic choices.
- Maturity and capability assessmentsExpert scores and staff sentiment blended per pillar and sub-pillar.
- Surveys with no loginTokenised links, rate limited, five minutes, works on a phone on district bandwidth.
- Compare any two assessmentsBaseline against today, pillar by pillar, with the movement shown.
- Publishing feeds the planA published assessment writes its scores into every measure it covers.
Write the plan people can be held to.
Translate insight into clear priorities, objectives and initiatives, with the responsibilities, timelines and measures that will show success.
- Four frameworks, one modelBalanced Scorecard, KPI and RAG, OKR and digital maturity as templates.
- Measures that mean somethingDirection, unit, baseline, target, thresholds and a named owner.
- Strategy mapObjectives laid out by perspective with the cause and effect links drawn between them.
- Alignment you can scoreContribution links between goals, an alignment score, and a list of orphans nothing supports.
The delivery layer scorecard tools never ship.
Put plans into motion. Coordinate work across teams, track commitments and address obstacles, while keeping delivery aligned to the objectives it is meant to move.
- Initiatives tied to objectivesEvery piece of work hangs off the goal it serves, with an owner and a horizon.
- Four views on the same workBoard, table, timeline and chart, with drag to move and drag to reorder.
- Milestones and dependenciesWhat has to finish before the next thing can start, and what slips when it does not.
- Sync with the delivery toolsTwo-way with Jira and Azure DevOps, so technical teams keep working where they already work.
Nothing drifts between the meetings.
A consistent rhythm of check-ins, health and adaptation. The system asks the owner for the number before the review, not the analyst on the night before it.
- Append-only check-insA value with a note and a date, enforced immutable by the database itself.
- Automatic RAG healthRed, amber and green from the thresholds you set, rolled up at every level of the cascade.
- A forecast, not just a statusWhere each measure lands at this rate, so a red surfaces weeks before the meeting.
- Reminders on your cadenceDriven by the template's review rhythm, once per person per period, never nagging.
The pack builds itself.
Communicate progress, explain performance and highlight what needs a decision. The board pack, the performance agreement and the public dashboard all come from the same numbers.
- Performance agreementsThe signed document a ministry runs on, print ready, always current, never retyped into Word.
- Board and council packsStyled PDF and PowerPoint, generated on the cadence, delivered to the distribution list.
- A public transparency pagePublish the scorecard citizens are entitled to see, without exposing the working papers.
- Drafts written for youAn executive summary and a performance narrative proposed from the data, confirmed by a person before it goes out.
One platform, and what holds it together.
Five work modules in the order you use them, over one set of shared services. Everyone who touches the plan works in the same system, under the same permissions, reminders and audit trail.
Scroll sideways to see the whole diagram
Separation that holds
Separation is enforced beneath the application, in the data layer itself, rather than by application code that has to remember. A defect in a feature cannot expose another organisation's plan.
Your identity provider
Single sign-on on every install, with no bypass. Bring Entra ID, Google Workspace or your own directory, map groups to roles, and provision people automatically.
An audit trail that holds
Every change recorded with who, what and when, available to administrators and paginated for the auditor who wants the whole year.
Roles that match the org chart
Administrator, owner, lead, contributor and viewer, scoped to a pillar or a workspace, so a district lead sees the district and the minister sees everything.
An API for the whole product
Every screen runs on a documented REST API. Issue your own keys, subscribe to webhooks, and build the integration we have not thought of.
White label, one build
Your name, your colours and your logo, applied at runtime. Consultancies run their practice on it, and every client sees their own brand.
Where you need it to live
Hosted on the continent by default. Or installed on your own infrastructure, because on-premises here is a deployment choice and not a premium tier.
English and Setswana
The whole interface in both, so the district officer filling in a check-in reads it in the language they think in.
Usable by everyone
Built on accessible primitives, keyboard complete and screen reader tested, because a public body cannot buy a system half its staff cannot operate.
The three gaps the category leaves open.
The global tools are good at one stage each. These are the three places every evaluation we have run finds them short, and the three things this platform was built to do.
Execution, not just reporting
Initiatives, tasks, boards, milestones and dependencies live in the same system as the scorecard, so progress rolls up from the checklist to the objective without anyone retyping it.
The reporting-first tools link out to a separate project tool and lose the thread.
A cadence that runs itself
Check-ins are requested, chased and collected before the review. The agenda is what is off track. The pack is built when you walk in, and the decisions are minuted against the objectives they belong to.
Most platforms leave the meeting, and the chasing that precedes it, to you.
Fitted to how this region works
The national plan cascade, the performance agreement, the review committee, low bandwidth, on-continent data and pricing per organisation in Pula.
The global tools price per user in dollars and have never seen a performance agreement.
| Capability | Reporting-first tools | Enterprise OKR tools | StratCo Flow |
|---|---|---|---|
| Balanced Scorecard and performance agreements | Deep | Shallow or absent | Deep, and the agreement prints |
| OKRs alongside a scorecard | Rare | Deep, but only OKRs | Both, as configuration |
| Execution down to tasks and dependencies | Links out to a project tool | Links out to a project tool | Built in, rolls up to the objective |
| Review cadence collected and chased for you | Manual | Partly automated | Requested, chased, then the pack builds |
| National plan cascade to district level | Not modelled | Not modelled | A first-class structure |
| Data kept in country | Rarely offered | Rarely offered | Hosted, your cloud or on premises |
| Priced for a public body here | Per user, in dollars | Per user, in dollars | Per organisation, in Pula |
Categories rather than named products, because the strongest tool in each column is strong at what its column is for. The comparison that matters is whether one system covers all seven rows.
Designed around how strategy is actually run here.
Not retrofitted from a Silicon Valley goal tracker. From the national plan to the district office, it fits the process you already run and the constraints you actually have.
The national cascade
National vision to development plan to ministry to department to district, as a first-class structure rather than a naming convention.
Works on district bandwidth
Usable on a modest connection and on a phone. Heavy artefacts generate as lightweight documents rather than streaming a dashboard nobody can load.
Data stays on the continent
Hosted in a regional data centre by default, with on-premises deployment where the data must remain in country.
The performance agreement
A hard requirement in public service here, and a first-class output rather than something you rebuild in a word processor each year.
Live on your own plan, not a demo dataset.
Most organisations already have the plan. It is in a spreadsheet, a strategy document and a set of quarterly slides. The work is not writing it again, it is getting it into one place and putting a rhythm around it.
Bring the scorecard in
Import objectives, measures, baselines and targets from the spreadsheet you report on today. Pick the template that matches how you already work, and rename the entities to your own vocabulary.
Name owners and set the rhythm
Every measure gets a person and a due date, and the workspace gets its review cadence. This is the step that decides whether the rest works, and it is the step most rollouts skip.
Run one review on it
Let the system collect the first round of check-ins, then hold your next review from the pack it builds. One cycle is enough to know whether the cadence holds.
Cascade and assess
Add the departments and districts beneath you, then run the first assessment so the next cycle plans against evidence rather than last year's assumptions.
Priced per organisation, in Pula.
Per-user pricing in dollars is how global tools lose public-sector deals here. A ministry cannot commit to a number that moves with the exchange rate and grows every time a district officer is added, so the price does neither. Three packages, each one annual figure, quoted for the organisation in front of us.
Starter
One team, running the loop end to end for the first time.
- Scope
- One workspace. A directorate, a department, or a single organisation.
- Capabilities
- Plan, execute and measure. Objectives, measures, owners, initiatives, tasks and the check-in cadence.
- Platform
- Hosted by us, in the region.
- Support
- Email support. Onboarding and training quoted separately.
Professional
The whole organisation on one plan, with the reporting that comes out of it.
- Scope
- Every department, region and district in one cascade.
- Capabilities
- Everything in Starter, plus assessments, staff surveys and the reporting layer: board packs, dashboards and the performance agreement.
- Platform
- Hosted by us, in the region, under your own branding.
- Support
- A named contact and a response commitment. Onboarding included.
Enterprise
A group or a national cascade, running where you need it to run.
- Scope
- A group, a ministry portfolio or a national cascade. Unlimited organisations under one roof.
- Capabilities
- Everything, including the API and white labelling for advisory firms running it for their clients.
- Platform
- Hosted, your own cloud account, or on premises. Your own identity provider, and data residency you choose.
- Support
- Implementation, migration and training scoped with you.
Never metered, on any package
People, workspaces, measures, check-ins, assessments, surveys, reports and packs. Adding a district office costs nothing, because the whole point is that everyone is on the plan.
Quoted separately
Migration of an existing plan, facilitation of the first assessment, and training for the strategy office. Nothing on that list is required to start.
The ones that come up in every evaluation.
Can we run it on our own infrastructure?
Yes, and it is the same product. The API, the database, the identity server and the app run as containers on one machine or in one cluster namespace. On premises is a deployment choice here, not a tier with a different price or a reduced feature set.
Where does our data actually sit?
In a regional data centre on the continent by default. If your rules require it to stay in country, it runs in your own cloud account or in your building, and nothing leaves it.
Will it use our existing sign-in?
Yes. Single sign-on is on every install with no bypass, including in development. It federates to Entra ID, Google Workspace or any other provider that speaks the standard protocols, maps your directory groups to roles, and provisions people automatically.
We run a Balanced Scorecard, but one division wants OKRs.
Both, on the same platform. Frameworks are configuration rather than code, so a workspace picks its own template, vocabulary and cadence. A ministry on a Balanced Scorecard can hold a technology team running OKRs without either side compromising.
Our plan lives in Excel today.
Import it. Objectives, measures, baselines and targets come in from a spreadsheet export, and so do bulk check-in values afterwards, matched by identifier or by name.
What happens to our data if we stop using it?
You take it. There is a complete export of everything your organisation holds, plus CSV and Excel for the working data. Nothing is held back to make leaving harder.
Does it work outside the capital?
It is built for that case. The interface stays usable on a modest district connection and on a phone, heavy artefacts generate as lightweight documents rather than dashboards that will not load, and a check-in written offline sends itself when the signal returns.
Start with the scorecard you already report on.
Import it from the spreadsheet, set the review rhythm, and run the first check-in this month. We will walk your team through it on your own plan, not a demo dataset.