Prairie Agentics

We build the small thing you actually need.

Prairie Agentics creates apps on demand, does the research behind them, and produces the content they need - directed by a human, built and checked by agents.

Start a brief

Three services

App creation on demand

What the visitor gets
A small, single-purpose app or tool built to their brief - for example a finder, a scanner, a tracker, a calculator, or an internal helper. Built, tested, and delivered as one complete package.
What we need from them
What it must do, who will use it, and on what device. Rough notes are fine - shaping the brief is part of the work.

Research

What the visitor gets
A grounded answer they can act on: options compared, sources checked, unknowns named as unknowns. A short verdict with the reasoning shown, not a pile of links.
What we need from them
The question, the decision it feeds, and any deadline. The sharper the question, the sharper the answer.

Content creation

What the visitor gets
Finished content made to order - explainers, product and help pages, summaries, scripts, and documents - written in their voice, checked before it ships.
What we need from them
The audience, the purpose, and any source material or examples of the voice they want.

How it works

  1. Brief. The visitor fills in the intake form below. Fifteen plain lines from them is enough to start.
  2. Build. The brief is expanded into a clear spec, then built in stages. Nothing outward-facing is sent without the director's go.
  3. Check. Work is tested against the brief by a checker who did not build it. A fail is a send-back, not a patch-over.
  4. Deliver. One complete package, ready to use - not pieces to assemble. Revisions come back through the same brief.

Human-directed. Agent-built. Checked before it ships.

Every job has a human director who approves each stage. Agents build, research, and write - a separate check stands between the work and the customer. If we cannot verify something, we say so on the page and in the work, rather than dressing a guess up as a fact.

Start a brief

3. Which service?

Watching whether anyone cares

Two signals. Visits show in the Cloudflare dashboard for the domain — no code on this page needed. Briefs are the real signal, and the collector answers your question directly: once it is live, it does both. Every brief will be stored first, then automatically forwarded to Gmail as it arrives. You will also be able to download the full set from the store any time. Storing happens first, so a brief is never lost if an email fails.

1. Stored — the record

Once live, each brief lands in a Cloudflare KV store the moment it is submitted. Count them any time, export the lot from the Cloudflare dashboard (Workers & Pages → KV) when you want them as files.

2. Emailed — the loop to Gmail

Once live, right after storing, the collector forwards the same brief to the owner’s Gmail inbox. One email per brief, as it arrives. The address itself stays off the public page — forwarding happens server-side, with the real address set only in the Worker’s own settings.

3. What is still needed

The collector is one small Cloudflare Worker file. Putting it live needs your Cloudflare account: create the KV store, verify a sending domain, deploy. Until then, this form says so honestly instead of pretending a brief was sent.

Get the collector file (collector-worker.js)

One file, no build step. Deploy it on the same domain as this page so the form posts to /api/brief. Full deploy steps are in the note saved with it (your_files/prairie-agentics/deploy-and-monitor.md).