You're pledging to donate if the project hits its minimum goal and gets approved. If not, your funds will be returned.
I am seeking $4,000 for an eight-week Axiom Evidence Toolkit pilot. I want to test whether a nontechnical report author can make a spreadsheet's sources, checks and limitations clear to someone else.
The intended result is a free practical guide, reusable source-register and evidence-packet templates, a worked example using public or synthetic data, and published findings from a small usability evaluation. A limited browser prototype would be built where it improves on an existing spreadsheet and checklist. The toolkit is at the planning stage, with no prototype, recruited participants or committed project funding.
My view is that important decisions should rest on verifiable evidence, with uncertainty stated clearly. The intended users are people at small mission-driven organizations who prepare reports from public spreadsheets. The project would help them preserve the connection between a figure and its source.
In weeks one and two, I would define the evidence packet, compare existing workflows and begin recruiting volunteers. Weeks three and four would implement only the useful missing functionality. The proposed browser workflow would preserve the input, record its source, run explicit user-selected checks and export a portable report. Local processing without uploading file contents is a design goal to verify before release.
In weeks five and six, I would aim to run up to five task-based sessions. The proposed success criterion is that four of five participants can complete the packet with no more than one facilitator prompt and identify a remaining limitation. I would report the actual participant count, assistance and failures. This is an exploratory pilot. Weeks seven and eight would address priority defects and publish the guide, example, method and aggregate findings.
The public benefit is practical education about evidence and uncertainty. Materials would be freely available without purchasing Axiom services. Any newly funded code would be kept separate from existing proprietary IP; a software release license remains to be selected before such a release.
The minimum and maximum request are both $4,000 for this defined pilot:
$600 for workflow and example design.
$1,800 for a limited browser prototype and report export.
$750 for correctness, accessibility and usability review support.
$450 for the guide and release documentation.
Up to $400 for project-specific development, testing and hosting tools.
These are proposed allowances, totaling $3,600 in scoped contractor services and $400 in tools. Actual quotes, platform charges and eligible costs would stay within those caps. I would contribute planning, coordination and review in kind.
This request excludes equipment, owner salary, unrelated company overhead and existing proprietary development. I seek a regular grant, with no equity or investment instrument. I would maintain a separate expense record and obtain any required approval for material scope changes or unused funds.
I am Ryan W Bates, founder and systems architect of Axiom Insights LLC, a Wyoming single-member company formed in October 2024. Axiom focuses on analytics, dashboards and software. I started the company to build the work I intend to do after military retirement.
I am the sole owner and current team member. Axiom is pre-revenue and has no employees or contractors currently engaged. I would engage specialists for defined deliverables after funding and quotes are in place. There are no prior results for this toolkit. My company website, https://www.axiominsights.org/, provides context for the business direction.
The eight-week schedule would begin with funded work and is subject to military duties and contractor availability. The project would use only public or synthetic examples.
Existing tools may already solve the task adequately, the prototype may add little value, volunteer recruitment may fall short, or the schedule may slip. I would compare the baseline before committing to custom functionality, limit the feature set and record errors and assistance needed.
If a simpler workflow proves more useful, the outcome would be that documented workflow and an explanation of the result. If too few volunteers participate, the published findings would identify that limitation and avoid broad conclusions. Material changes to the funded scope would be discussed with Manifund before implementation.
Axiom has received $0 in funding during the past 12 months, including owner contributions, loans, investments, donations and grants. The toolkit has no committed funding.
Before this Manifund proposal, Axiom submitted seven funding applications requesting $30,600 in total. These are pending requests, not funds raised. They include separate $4,000 applications to Emergent Ventures and FUTO for this same pilot. I would disclose overlapping offers and resolve the allocation before accepting funds or charging an expense to more than one award.
There are no bids on this project.