Everything the center is doing, where everyone can see it.

A center runs a dozen things at once. The seminar series, the REU digest, the advisory board recommendation somebody has to follow up, the roster that changes every term, the publications that arrive without anyone telling you. Each has its own schedule and its own list of people. SimplyScholar keeps them running and keeps the record as it goes.

Thirty minutes, with your center's actual data. No pitch deck.

Your center · Tuesday

7:02 am

Overnight

  • 6 new publications from CrossRef. Four acknowledge the award. Two do not, and are flagged.

  • Thursday seminar, 31 of 44 replied. Agenda goes out tomorrow morning.

  • Annual report due in 88 days. 79 requests sent, 21 back.

  • S. Bergström, no response in 14 days. Third reminder queued for Friday.

This week’s digest is drafted and goes out at nine.

Ready to review

Two acknowledgement queries and one advisory board follow-up.

Researchers from these institutions are in SimplyScholar today

  • MIT
  • Dartmouth
  • UC Santa Barbara
  • Penn State
  • University of Illinois
  • University of Colorado
  • North Carolina A&T

01

The problem

Your current tools wait for you.

Cayuse, InfoEd, Interfolio, and the spreadsheet they sit next to have one thing in common. You log in, you enter data, you pull a report. Between those moments the center is still running, and every hour of keeping it running is yours.

Nobody knows what is going on
You send the update. Half of them read it. The new postdoc has not heard of the seminar series, two thrusts are duplicating a measurement, and the recommendation the advisory board made in May is still sitting with somebody who has forgotten.
After One place people go to see what the center is doing this week.
Scheduling anything takes a fortnight
Forty people, three departments, two institutions. The poll, the reminder about the poll, the room, the follow-up because six people never answered, and the six who turn up not having read the agenda.
After Invitations, reminders and agendas go out on their own schedule.
Nobody responds to your emails
You send data requests to fifty researchers. Three reply. You send reminders. Two more. You end up entering eighty percent of it yourself, out of email threads and hallway conversations.
After Researchers submit their own, and you can see at a glance who has not.

02

How it works

Three things that run themselves.

Each one has its own schedule and reports what it did. The writing and the judgment calls stay with your coordinator and PI.

It keeps everyone posted

The seminar on Thursday, the REU deadline in two days, the paper that came out this morning, the postdoc who started last week. Your people get one place to look and a digest they did not have to be added to. Invitations, reminders and agendas go out on a schedule you set once.

You stop being the only route between any two people in the center.

It collects and chases

Publications arrive from CrossRef, profiles fill in from ORCID, award data comes from the NSF API, all without anyone asking. When something is due, structured requests go out pre-filled with what is already known. Non-responders get reminded on a schedule you set once. Gaps get flagged early, and the people who will never reply get entered on their behalf for you to approve.

Ten minutes of their time instead of an hour of yours, repeated fifty times.

It drafts

Because the year was recorded as it happened, the annual report is a review. Personnel counts, bibliography, outreach metrics, partnership tables, advisory board recommendations and what was done about each one, and the narrative around them. You edit, approve, export.

Weeks of assembly become a couple of days of editing.

03

What it tracks

What a center actually has to keep track of.

People and teams
Every PI, postdoc, graduate student, and technician, with thrust assignments and mentorship chains. Demographics collected once and reported every year after.
Publications
DOI import from CrossRef, award acknowledgement verification, and bibliography generation in whatever format the agency asks for this year.
Outreach and broader impacts
REU and RET tracking with demographics, K-12 activity, workshop participation, and templates for the activity types NSF asks about.
Events and meetings
Seminars, workshops, retreats and industry days, with who came and what came of it. Advisory board recommendations tracked from the meeting they were made in to whatever was done about them.
Partnerships
Industry, academic, and government partners, with contribution tracking and agreement status, so the collaboration table writes itself.
Compliance
Deadline tracking, training status, disclosures, and subaward monitoring, with push to the agency portals so a publication is entered once rather than five times.
The public website
Researcher directory, publication listings, event calendar, all generated from the same records. The public site is current because everything behind it already is.

04

Who builds it

We build the sites NSF programs run on.

SimplyScholar is built by KZN Consulting. We have run NSF program and center websites for close to a decade, across three directorates, and several of them belong to the program itself: the site for every MRSEC, or every PREM, one level above any single center. Publishing there means we have seen what a MRSEC, a PREM and a MIP each have to show, across every center in the program.

For a few individual centers we have also done the collection itself: the roster, the publications, the outreach numbers, gathered and kept current between reports. That is where the rest of the product comes from.

Since 2015
building and running NSF program and center websites, without a gap.
5 program sites
the program's own site, covering every center it funds. Go and look at any of them.
3 directorates
MPS/DMR, TIP/ITE and BIO/IOS. Three separate reporting cultures.
6 programs
MRSEC, PREM, DMREF, EPIIC, MIP and NeuroNex, plus DOE EFRC.

The five program sites: mrsec.org, prem-dmr.org, dmref.org, nsf-epiic.org, neuronex.org.

AWS hosting, encryption in transit and at rest, tenant isolation, US data residency. KZN has built and operated systems under HIPAA and FERPA obligations for state government.

05

Who it is for

Center directors and PIs
See the whole operational picture. Know who is producing, who needs support, and how the annual report is shaping up, without adding another thing to your coordinator's week to find out.
Program coordinators
You are almost certainly doing two people's jobs. This one takes the chasing, the transcribing, and the version control, and leaves you the parts that need a person: the writing, the researchers, and the judgment calls.
Researchers and students
One link, ten minutes. Confirm the publications already found for you, add your outreach, done. No login, no account, no password to reset.

06

Pricing

Under two percent of a typical center budget.

Budgeted into the award as center infrastructure, alongside the other things the center runs on. Priced by how many people you are keeping track of, not by how much money you were given.

Starter

Single-PI grants, seed funding, solo labs.

$99/mo

Under 20 researchers

  • Data collection campaigns
  • Annual report generation
  • Public website
  • DOI auto-import

Enterprise

Large MRSECs, MIPs, multi-agency compliance.

$2,499/mo

100+ researchers

  • Everything in Center
  • Cross-project analytics
  • Multi-agency compliance
  • Priority support

Network

Multi-center and consortium deployments.

Custom

Multiple centers

  • Everything in Enterprise
  • Cross-center dashboards
  • Researcher matchmaker
  • Shared resources directory

All plans include unlimited collection campaigns, report generation, and the public website. Billed annually, and academic institutions can pay by purchase order. Founding-customer pricing is available for the first ten deployments.

07

Common questions

How is this different from a research center website?

A website is one thing SimplyScholar produces, not what it is. The product is the operational layer underneath: structured collection from researchers, a live view of who still owes what, and reports generated from records you already hold. The public site comes out of the same data, which is the only reason it stays current.

How long until it is running?

Your first collection campaign goes out in week one. Publications import automatically, so the roster and bibliography are largely populated before you ask anyone for anything.

Do researchers need accounts?

No. They get a link, pre-filled with what we already know about them. They confirm, add what is missing, submit. No login, no password, nothing to forget between reporting cycles.

Can we pay from the grant?

Yes. It is a budgetable line inside the award, not an institutional software purchase, which is what keeps it clear of central procurement. Purchase orders are fine and billing is annual.

What happens to our data if we leave?

You export it. Personnel, publications, outreach, partnerships, all in open formats. Your data was never meant to be the lock-in.

Tell us what you chased last week.

Thirty minutes, with your center's own data, and no pitch deck. You will see your own people and your own week in it.

Request a demo