Skip to content
Konsul
Menu
All examples

Example: Proposals and grants

Stop rebuilding the same document by hand.

Proposals, grant drafts, donor updates and client reports: each one is built in your own template from your records. Anything it cannot fill is marked missing, and every document waits in a folder for you to read and send. The example here is a nonprofit's donor updates.

By hand

Writing proposals and grants. About 25 minutes each time, every time it comes up.

With a build

Handled for you, and nothing reaches a customer in words you have not approved.

What a diagnostic would check first

The diagnostic decides what gets built, or whether anything should. What follows is one way it could look.

  1. Where the facts come from and who signs off
  2. Hours per document today

One way it could look

Open the working example

Quick look. The full example has every screen. Made-up nonprofit, donors and numbers. The AI paragraphs are pre-written for this demo. Nothing is sent from this page.

Want one shaped around your business?Tell us what's breaking

How it would work

  1. Step 1

    It reads your records

    A donor list, a gifts list and a short table of what each program did, exported into one Google Sheet you own.

  2. Step 2

    It fills your template

    Your own Google Doc, with fields like {{first_name}} and {{total_given}}. Every name, amount, date and program comes from the sheet.

  3. Step 3

    It marks what to check

    A field with no data says Missing. The optional AI paragraph is marked for review, and any number in it that is not in your data is flagged.

  4. Step 4

    You send it

    Each update lands in a Drive folder with a short checklist at the end. You read it, edit it and send it yourself.

Waits for your OK

  • Every update. Each one lands in a Drive folder as a doc. Nothing is emailed, printed or posted.
  • The AI paragraph, if you switch it on. It is off by default, and AI text stays marked until a person reads it.
  • Any field it could not fill. It says Missing in the doc and in the sheet, so no update goes out with a blank or a guess.
Watched by Kustos

Konsul builds it. Kustos keeps it running and right.

Once it is live, Kustos checks it on a schedule and drafts a fix when something breaks. A person approves every change.

What could go wrong

The AI paragraph states a number that is wrong.

Any number in AI text that is not in the donor's gifts or your impact table gets a "check this number" flag in the doc and in the sheet. The AI paragraph is off unless you switch it on.

An empty field leaves a hole in the letter.

Empty fields are written as Missing, listed at the end of the doc and in the Donors tab, and the update is marked needs review.

Your donor system's API key can change records.

A Bloomerang API key gives full read and write access and there is no sandbox. The build reads a sheet export instead, so it never holds that key.

Next step

Start with the process that costs you the most.

Rough numbers are fine. Describing it takes about three minutes.

Tell us what's breaking