Who this is for

Built for teams running grant-funded programs

Federal grant recipients, fiscal sponsors passing money through, foundation grantees and research centres. The common thread is not sector or size: it is that somebody else — an agency, a foundation, an auditor, a board — will eventually ask what you did, when you decided it, and what evidence you had.

Primary

Federal grant recipients

Nonprofits, tribal organizations and higher-education departments running several concurrent awards.

The pattern is familiar: three to fifteen awards, each with its own reporting cadence, its own agency portal, and its own set of people who know what happened. Performance narratives are written in Word from memory a week before they are due. The monitoring file is a folder. When the Single Audit arrives, somebody spends a week rebuilding a year.

In Kharazm each award carries its reporting obligations as dated milestones, and the report that satisfies an obligation is linked to it — so the deadline and the artifact that closed it are one record. Decisions land in the register as they happen, with owners and written resolutions. At year end the audit pack is generated rather than assembled.

Typical access: grants administrator as admin, program director as manager, programme staff as members, finance and the awarding agency as scoped viewers.

The change that matters

Not that reporting becomes faster — though it does. That the report stops being a document somebody wrote and becomes a record the organization can stand behind three years later.

Relevant: 2 CFR 200.329, 200.303, 200.334.

Secondary — the sharpest fit

Fiscal sponsors and pass-through entities

Organizations that move money onward, and therefore carry monitoring duties for everyone they move it to.

A fiscal sponsor is a pass-through entity by definition. Every sponsored project is a subrecipient relationship that has to be risk-assessed in writing, monitored proportionately, and followed up when findings appear — under 2 CFR 200.332, for each one, every year. Most sponsors run this in a spreadsheet that lives with one person.

Kharazm gives each subrecipient a risk determination with a written basis, a monitoring plan that follows from it, and a dated log of what was actually done. Sponsored project leads can be given scoped access to their own project and nothing else. The monitoring file for forty projects becomes one view instead of forty tabs.

Typical access: sponsor operations as admin, project leads as scoped viewers or members on their own project only.

Why this is the sharpest fit

One account, many awards, an obligation that repeats per project, and a team small enough to decide in a fortnight. Everything Kharazm is good at compounds here.

Relevant: 2 CFR 200.331, 200.332, 200.337.

Tertiary

Foundation grantees

Teams reporting to program officers who increasingly want federal-grade evidence without federal paperwork.

Foundation reporting has quietly tightened. Program officers ask for outcome narratives tied to what was actually delivered, and multi-year grants come with interim reports that are compared against each other. There is no Uniform Guidance obligation here, but there is a relationship that depends on the last report being consistent with this one.

Foundation grantees use the same published-report model without the federal fields. The practical benefit is different: a program officer can be given scoped access to their own grant and see progress between reports, which is the single most effective thing a grantee can do for renewal.

Funding cycles here are uncorrelated with federal ones, which makes this a deliberate hedge rather than an afterthought.

No federal fields required

Assistance Listing numbers, pass-through flags and Single Audit framing are optional. A foundation grant is an award with a funder, a period and a reporting cadence.

A distinct product, not a plan

Single Audit in a Box

For the organization whose audit is four to eight weeks away and whose documentation is scattered.

This is not the platform with fewer features. It is a narrow tool with one job: assemble the monitoring file, evidence index, decision record and report register into a printable audit pack, in about thirty minutes, for a flat $199. Everything that would slow down a team under time pressure has been removed.

When to use which

  • Audit in weeks — Single Audit in a Box, flat fee, one call.
  • Audit next year — the platform, so the record builds itself and next year is not an event.
  • Both — start with the audit product; converting carries your data over at half price for year one.

Adjacent

Research centres and multi-institution consortia

Why the usual tools fail here

A five-university consortium cannot run inside any one institution's research administration system, so it runs on a shared drive and a monthly call. The subaward monitoring obligations are identical to any other pass-through — an NIH RPPR is a performance narrative and a consortium partner is a subrecipient — but there is nowhere neutral to keep the record.

What we are honest about

Kharazm has no single sign-on, so an institution-wide purchase through central procurement is not realistic today. Where this works is at the level of a centre, core facility or consortium with its own budget and its own decision. If you need Shibboleth or a completed HECVAT, we do not have them yet and will tell you so on the first call.

Who this is not for

If you are choosing a tool on board views, automations, time tracking or client invoicing, Kharazm will disappoint you and there are better products for that work. Agencies, CPA practices, law firms and solo consultants are welcome to sign up, and we will support you, but we are not building for those needs and will not pretend otherwise on a roadmap call.

If you need clinical trial management under 21 CFR Part 11, Kharazm is not a validated system and should not be used for trial conduct data.

Try it on the award that worries you most

Fourteen days, no card. If a reporting cycle needs longer, ask and we will extend it.