SMB Pulse

Bid only where we are eligible

Rule out every grant the business cannot apply for, with the reason, before any time is spent, and start the eligible one from the funder's own checklist, with every missing figure marked rather than invented.

Pick a use case and follow its guide

Bid only where we are eligible

0 of 6 steps done

Sign in to try the demo
  1. Step 1. Open Operations, then grants.profile. Leave rebuild unticked and press Call grants.profile. Under ANSWERED, source is stored: the profile was built once and is read as it stands. entity_type gives the kind of business, such as for-profit, and missing names each kind of fact the business holds nothing for, such as registrations or certifications. Open grants.profile

  2. Step 2. Open Operations, then grants.screen. Press Add feed once for each opportunity and type what its notice says: its title, funder, eligible_entity_types and geography (type each value and press Enter) and deadline, for example nonprofit and 2026-11-30. Type today's date in as_of (for example 2026-09-14) and press Call grants.screen. Under ANSWERED, the screen opens with a line noting the kind of business and runs anyway. excluded names each opportunity ruled out, with its reason, such as the wrong kind of business or a deadline that has passed. An opportunity the profile cannot settle, such as one limited to a place the profile does not name, is listed under cannot_tell, and eligible holds only those that clearly fit. Open grants.screen

  3. Step 3. Open Workflows, then grant-response, and press New run. The run checks every sentence of the opportunity that says shall or must against the stored profile, as match, fails or unknown, and stops at go_no_go. A failed requirement would end the run here with the no and its reason recorded, before any drafting. In the Runs tab, press Open decision. Read go_requirements, one row per requirement with its match. In go_decision, leave decision at go to continue; to decline, change it to no and give your reason and your name in decided_by. Press Save, then Resume. A no is recorded with your reason, and nothing after it does any work. Open the grant-response workflow

  4. Step 4. Open Operations, then grants.compliance_matrix. In opportunity_id, type the eligible opportunity's id and press Call grants.compliance_matrix. Under ANSWERED, rows is the funder's checklist: one row per section, each with its word_limit and its weight in the score, then one row per form the funder requires. Open grants.compliance_matrix

  5. Step 5. Open Operations, then grants.draft. In opportunity_id, type the same id and press Run grants.draft. The run turns SUCCEEDED in about a minute. Under sections, each section of the checklist is drafted in order, inside its word limit, and ready is true. Where the business holds no figure, the text carries a marked gap in square brackets, starting [GAP:, and each gap is listed again under gaps; no number is invented. The wording differs from run to run. Nothing is stored or sent. Open grants.draft

  6. Step 6. After a go, the grant-response run builds the checklist and the draft itself and stops again at review_submission. In the Runs tab, press Open decision. Read compliance_matrix beside grant_submission. Fill every gap marked in square brackets in grant_submission, check that approval_meta names you, press Save, then Resume. The run turns SUCCEEDED, and submission_result records one simulated submission, labelled as simulated. A draft that still carries a gap, or one that is held, is refused by name and nothing is recorded. Nothing is sent to the funder. Open the grant-response workflow

Did it fit your work?