Workshop Dispatch

Local AI tools, built in public and shared freely.

Jester Studio Works is a local AI workshop focused on practical examples over hype. It builds local-first hubs, automations, workflows, prompts, guides, templates, and notes in public so small businesses, churches, nonprofits, community groups, and everyday builders can learn from real working examples.

Most work is educational, openly shared, and designed to be understandable. Public demos use dummy data when possible, local AI when possible, and human review before publishing.

Core Lanes

Open work that people can actually use

The site is structured like a build library and field lab, not a funnel.

Public Builds

Local AI hubs, corkboards, trackers, portals, automations, and JSE/JSC build lessons that show the moving parts clearly.

Workflows Approvals Build notes

AI Field Notes

AI best practices, workflow design, privacy habits, dummy data examples, approval gates, and lessons learned from building.

Privacy habits human review Local-first

Prompt Library

Practical prompt examples for planning, operations, churches, nonprofits, small businesses, and workflow review.

Planning Operations Content

Tools Tested

Honest reviews of what a tool claimed, what it did, cost, privacy concern, and whether a local-first alternative makes more sense.

Bench tests Cost notes Verdicts

Support the Workshop

donations and optional support can help sustain open work. Support does not create a service contract or support obligation.

Optional support Open work Boundaries

About the Shop

Plain-language background on Jason, the workshop approach, and why local control and practical proof matter more than hype.

Veteran-owned Florida LLC Public learning
Why this exists

Educational work, shared openly

Practical examples over hype

The workshop publishes working examples that show where AI helps, where it fails, and where ordinary process design matters more than model size.

Local-first when possible

Private work should stay close to the people who own it. That means testing local models, controlled workflows, and smaller systems before defaulting to cloud sprawl.

Clear review boundaries

Public outputs are demonstrative only. They are meant to teach patterns, not replace judgment, supervision, or professional review.