Jimenez Julien, the person who builds and answers for GrantClock

Why a grant calendar, and why this one

GrantClock started with a phone call from a food pantry director in Ohio who had just discovered, on a Friday afternoon, that a $45,000 renewal had closed eleven days earlier. Nothing had gone wrong in her program. The reports were written, the outcomes were good, the relationship with the program officer was warm. The window had simply opened in a newsletter she read on a busy week, and the note she made about it lived on a legal pad that went home in a tote bag.

I had been building small operational software for owner operated businesses for years, and I recognized the shape of the problem immediately. It was not a knowledge gap. It was a calendar that existed in four places and belonged to nobody. What I did not understand yet was how specific nonprofit deadline work is, so I spent the following months doing the only thing that helps: sitting with people who do it.

I interviewed 214 development leads and executive directors at organizations with two to nine employees. I asked to see their actual spreadsheets, not a cleaned up version. Almost every one had a tab structure invented by whoever last held the job, a color code that only made sense to that person, and at least one date copied wrong. I learned that a grant is never a single deadline. A modest $15,000 award from a community foundation can carry a letter of inquiry, a full proposal, an acknowledgment, an interim narrative, a financial report, a final report and a renewal window, each on its own cycle, some of them driven by the funder's board meeting schedule rather than by any calendar you control.

I also learned what the trade actually fears. It is not a bad proposal, because a bad proposal gets a polite no and you try again. It is the silent lapse: the report that was drafted but never submitted, the extension that had to be requested before the period ended, the restricted award spent slightly outside its window. Those failures are administrative, they are entirely preventable, and they damage relationships that took years to build. That is the narrow problem GrantClock exists to solve, and I have deliberately kept it narrow. It is not a donor CRM, it does not write narratives, and it will not tell you which funders to approach.

I work with operators the same way now that the product is in daily use. Every quarter I run calls with a rotating group of subscribers, mostly development directors and grants managers, and I ask what broke. The 48 hour escalation to the executive director came out of those calls. So did the distinction between a report being drafted and a report being confirmed received, which sounds like a detail until you have watched a team argue about it in front of an auditor. When a funder changes its reporting pattern, I update the template myself and note the date it changed.

What I am accountable for is straightforward. The dates in the product have to be right, the alerts have to arrive, the export has to open in the tools your treasurer already uses, and the words on this website have to describe what the software actually does today. If any of those fail, the email address below reaches me and not a queue.

Experience and expertise

• Twelve years building and shipping operational software for small organizations, with the last four focused on nonprofit administration.
• 214 structured interviews with executive directors, development directors and grants managers at US nonprofits under ten employees.
• Hands on review of 90 US funder reporting patterns, covering family foundations, community foundations, corporate giving programs and state pass through awards.
• Publication director at MLJ, SASU, the company that publishes GrantClock and answers for its content under French law.
• Working knowledge of the documents a small nonprofit finance function lives with: the audit grant schedule, restricted fund tracking, match commitments and no cost extension requests.

How this product is built and maintained

GrantClock ships small changes often rather than large releases rarely. Every deadline template is checked against the funder's own published guidelines before it goes in, and each one carries the date it was last verified so nobody trusts a stale pattern. When a template changes, subscribers with that funder in their portfolio are told in the Monday digest, not silently updated.

The editorial rule for this website is equally simple. Every number on these pages comes from our own account data or from the interview set described above, and it is restated when the underlying figure moves. Testimonials are published with the name, role, organization and city of a real subscriber who read and approved the quote. There are no stock quotes, no invented logos and no metrics I cannot trace to a source. If a claim on this site cannot survive a direct question from a board treasurer, it does not belong here.

Support is answered by me and by the small team at MLJ. There is no tiered support desk, and the reply target is one business day. Feature requests that come from three or more organizations doing the same work get scheduled openly, and the ones that would turn GrantClock into a donor database get declined just as openly.

Published articles

Everything below was researched, written and signed by me for The Grant Cycle, the GrantClock magazine on grant calendars, funder deadlines and the reporting year of a small development office.

Contact the author

Write to jimenezjulien42@gmail.com with a question about grant tracking, a correction to something published here, or a request for a walkthrough with your own portfolio on the screen. If you would rather see the product before you write, the four step setup and the pricing table are both on the home page.