projectsmanager.ai
Product tour

Every screen, drawn with fictional data

Twenty-eight screens across the whole life of a donor-funded project. Each is marked so you know what exists today and what is still being built. Nothing here is a real programme.

For ministry and project-unit staff, and the donors who fund them. Start with the live demo, then ask us to walk you through it.

  • In the product a person can reach this screen today
  • Partly built the engine or a simpler screen exists; this is the design it is being built to
  • Preview · not built yet designed, not built

Design and planning

Start from the appraisal, cost the design, and turn it into an annual plan, each step traced to the one before.

  • In the product

    Appraisal

    Upload an appraisal document and see which of its assumptions the engine could verify against a cited page, and which it refused.

  • In the product

    Cost table

    Cost lines, the financing plan they must reconcile to, and an Excel upload that previews before it writes anything.

  • Partly built

    Annual work plan

    A plan an agent drafted from the cost table, inert until a person confirms it.

Placement and procurement

Put a project in its place in the hierarchy, then run procurement from plan line to signed contract.

  • Partly built

    New project and placement

    Create a project under a country, ministry and agency, or create it unplaced and say so.

  • Partly built

    Procurement chain

    From plan line through bids, evaluation and award to a contract, with every step recorded.

  • Partly built

    Contract

    Milestones that sum to the contract value, what the contract draws on, and the money linked to it.

Finance

Advances, withdrawal applications, invoices and the interim financial report, with what is not recorded named, never zero.

  • Partly built

    Advances and withdrawal applications

    Advances, what came back, and a designed thirteen-step approval tracker for withdrawal applications.

  • In the product

    Invoices and the interim financial report

    Invoices linked to contracts, and an interim financial report that says what it does not know.

Monitoring

Indicators, the risk and decision log, and the dependencies between activities.

  • Partly built

    Indicators and readings

    Each indicator against its baseline and target, with the readings behind it.

  • In the product

    Risk, issue and decision log

    Risks, issues and decisions in one log, with agent proposals held apart until a person confirms them.

  • Partly built

    Dependencies and procurable activities

    Which activities depend on which, and which of them need procurement, a judgement a person records.

Fixed assets

Everything the project buys that lasts: tagged, held by a named person, traced to the contract that paid for it, and handed over at closing.

  • Preview · not built yet

    Fixed asset register

    Every asset the project bought, with a tag, a custodian, a place and the contract that paid for it.

  • Preview · not built yet

    Asset detail and trace

    One asset, and the chain of records from the cost line to the tag that explains why it exists.

  • Preview · not built yet

    Asset handover at closing

    What has been signed over to the receiving unit, what is waiting for a receiver, and what closing is refused over.

Closing and reporting

Close the loop from design to next design, and assemble the Project Book and reports only from records that exist.

  • In the product

    Lifecycle: design to next design

    The loop that matters: what was assumed, what happened, and what a person wrote down that it implies.

  • In the product

    The Project Book

    One document per project, assembled only from records that exist, with a page for what it could not say.

  • Preview · not built yet

    Reports

    Monthly, quarterly, interim financial, mid-term and completion reports, all assembled the same way.

Organization and operations

What a minister sees across many projects, how disbursements move, and how a spreadsheet sync reports itself.

  • Preview · not built yet

    Country and ministry rollup

    What a minister sees across every project beneath them: counts by state, never a score.

  • In the product

    Disbursement pipeline

    Every activity's position in the thirteen-step disbursement workflow, with stalls named.

  • Partly built

    Spreadsheet sync status

    A sync that reports two separate signals, so a real refusal cannot hide behind a benign count.

Administration and states

Who can see what, what was done, and the named states every screen shares.

  • Partly built

    Users and grants

    A role is what you may do. A grant is which rows. No role bypasses the boundary.

  • In the product

    Audit log

    Who did what, to which record, with the outcome, including the things people were refused.

  • Partly built

    Named states and refusals

    The twelve states every screen shares: absence, refusal, proposal, loading, failed and empty, each distinct.

Assistant, sign-in and phone

Ask in words, sign in to your own place in the hierarchy, and work from a phone in the field.

  • Partly built

    Assistant

    Ask in words. It is designed to act as you, with your grant, and to refuse by name when it cannot.

  • In the product

    Sign in

    Sign in to your own place in the hierarchy. What you cannot see, the platform says by name.

  • Preview · not built yet

    Field officer on a phone

    My activities, record a reading, raise a risk: three screens for someone with a phone and sometimes no signal.

On the roadmap

Designed, not built yet.

  • Preview · not built yet

    Supervision and missions

    Mission reports and findings, with findings proposed as risks for a person to confirm.

  • Preview · not built yet

    Closure and completion report

    What stands between a project and closing, and a completion report assembled from the records.

How to read these screens

Dashed means unconfirmed

A dashed border marks something an agent proposed. It is not counted until a person confirms it.

Named, never zero

A figure nobody recorded says so. "Not recorded" and "not tracked" are different from zero, and every screen uses the same names.

Refusals say why

When the platform refuses, it names the extent and the kind. It never refuses a person because of what they are, only where they stand.

All figures, names and places on these screens are fictional. The tour uses the site's own fonts and loads nothing from third parties.