Library — Modules — WildBreeze

001 — How it works

Three steps. No glue code on your side.

Every module is a fixed shape. We deploy it into your cloud, hand over the keys, and step out of the room.

// 01

STEP 01 — BROWSE

A catalog organized by job, not technology

Templates are listed by the operational job they solve — "weekly KPI report", "BBD watcher", "ad-spend reconciliation" — not by which framework they use. The technology serves the job, not the other way around.

// 02

STEP 02 — DOWNLOAD

One file, no dependencies you don't want

Each template is a single file or a small folder. No installer, no SaaS account, no telemetry. The README is honest about which parts you'll need to wire.

// 03

STEP 03 — ADAPT

Drop into your stack, change what's yours

Templates assume nothing about your warehouse, your auth, or your conventions. Substitute placeholders, tweak the SQL, adjust the prompt — the template is scaffolding, not a finished product.

library / weekly-overview / template.sql

-- library: weekly_overview / template.sql
-- replace ${WAREHOUSE}, ${ORDERS_TABLE}, ${TZ} for your stack
SELECT
  DATE_TRUNC(order_date, WEEK(MONDAY)) AS iso_week,
  SUM(revenue) AS revenue,
  COUNT(DISTINCT order_id) AS orders
FROM ${WAREHOUSE}.${ORDERS_TABLE}
WHERE order_date >= DATE_SUB(CURRENT_DATE(), INTERVAL 13 WEEK)
GROUP BY 1
ORDER BY 1 DESC;

002 — Inside the module

What's actually in Library.

The capabilities that make this module the right shape, not just the right name.

// 01

HTML report shells

The visual shape of an Almanac-style report — without the BigQuery glue. Wire your own data.

// 02

SQL query templates

Real, opinionated SQL for ISO-week, MTD, YTD, YoY. Tested in production.

// 03

Agent recipes

YAML recipes you can drop into a scheduled-agent runner — yours or Field Office, when it ships.

// 04

Prompt patterns

The prompt fragments we've found actually work for ops reporting. Cited, dated, versioned.

// 05

Per-template license

Most templates are free for any operator's own use. Some (the heavier ones) are paid one-time.

// 06

No telemetry

Templates don't phone home. We won't know you used one unless you tell us.

003 — Built for

The operators we built this with, not just for.

A module joins the catalog only after the same shape has been built three times for three different operators. Here's who those were.

Technical operators

Comfortable with SQL, comfortable with YAML, want the shape rather than the consultancy.

Teams with dev capacity

You don't need us to write the glue — you need us to have already thought about the shape.

Hobbyists and side-projects

Personal warehouses, indie SaaS dashboards, small ops tools — Library is for those too.

004 — Operating notes

The honest answers we get asked first.

If you have a question that isn't here, that's also fine — bring it to the call.

When does this ship?

Planned for 2026. The first templates will be the patterns extracted from existing client engagements.

Is this open source?

Mixed. Most templates are free-for-use under a permissive license. A few of the heavier shells will be paid one-time.

Will there be updates?

Yes — versioned per template. We publish a changelog so you know what changed and why.

What about support?

Library templates are unsupported by design — that's why they're cheap or free. If you need support, that's an engagement.

005 — Adjacent modules

Often deployed alongside.

Modules pair well — one rarely arrives alone.

Tell us what you're maintaining at 11pm. We'll tell you which module fits.

A 30-minute call. No deck, no demo — just the work. If Library is the right shape, we'll say so. If not, we'll point at one that is.

Book a call →

Building blocks, for operators wiring it themselves.