The Template Library

Internal tools, sorted by the team that needs them.

Order trackers, ticket queues, onboarding checklists, approval flows. Pick the template that matches your team, copy the prompt, and let the builder do the first ninety percent.

31 templates11 teams1 prompt each

4 of 31 templates

Data Request Queue

Stop analytics requests arriving over chat — capture them properly, prioritise, and show the answer.

Data Analytics TeamProduct TeamMarketing Team

Key features

Structured request intakeBusiness-question framingPrioritisation scoringAnalyst assignmentAnswer and dashboard links

Build a Data Request Queue. Core objects: DataRequest (title, requester, team, business question, decision it informs, deadline, effort estimate, priority score, analyst, status New/Prioritised/In progress/Blocked/Delivered/Declined, answer summary, dashboard link). Screens: 1. Intake form that forces a business question and the decision it will inform. 2. Prioritisation board — requests scored by impact and effort, sorted, with drag to reorder. 3. Request detail — thread with the requester, answer summary and links to the resulting dashboard or query. 4. Delivered archive, searchable, so repeat questions get an instant answer. Rules: a request cannot move to In progress without an analyst and an effort estimate. Design: dashboard with left sidebar, dark mode, mono labels for scores.

Metrics Definition Catalogue

One agreed definition per metric, with owner and source, so two dashboards stop disagreeing.

Data Analytics TeamFinance TeamProduct Team

Key features

Metric definitions with formulasOwner and source systemVersion history of definitionsRelated dashboards and queriesSearch by name or synonym

Build a Metrics Definition Catalogue. Core objects: Metric (name, synonyms, plain-English definition, formula, grain, source system, owner, refresh cadence, caveats, related dashboards, status Draft/Approved/Deprecated) and DefinitionVersion (metric, body, changed by, changed at, reason). Screens: 1. Catalogue — searchable list grouped by domain, matching on name and synonyms. 2. Metric detail — definition, formula in a monospace block with a copy button, caveats callout, and links to dashboards. 3. Change history for each metric with a reason per change. Rules: only approved metrics appear in the default catalogue view; deprecated ones show a clear banner pointing to their replacement. Design: documentation-style dashboard, left sidebar, monospace formulas, dark mode support.

Experiment Tracker

Every A/B test with its hypothesis, metric, result and decision — recorded before anyone forgets.

Data Analytics TeamProduct TeamMarketing Team

Key features

Hypothesis and success metricVariant and traffic splitRun dates and sample sizeResult and confidenceShip / rollback decision log

Build an Experiment Tracker. Core objects: Experiment (name, owner, surface, hypothesis, primary metric, guardrail metrics, variants with traffic split, start date, end date, sample size, status Planned/Running/Concluded/Abandoned, result lift, confidence, decision Ship/Rollback/Iterate, learnings). Screens: 1. Experiments list with status filters and a running-now section. 2. Experiment detail — hypothesis and metric definitions up top, results panel below, decision and learnings at the bottom. 3. Learnings library — concluded experiments searchable by surface and metric, showing only hypothesis, result and learning. Rules: an experiment cannot be concluded without a result, a decision and a written learning. Design: dashboard with left sidebar, dark mode, results shown with mono numerals and a clear lift indicator.

Campaign Performance Tracker

Log each campaign's spend, results and learnings so the next one starts from evidence.

Marketing TeamData Analytics TeamSales Team

Key features

Campaign register with budgetChannel-level spend and resultsCost per lead and ROICreative and copy linksPost-campaign learnings

Build a Campaign Performance Tracker. Core objects: Campaign (name, objective, owner, start date, end date, budget, status) and ChannelResult (campaign, channel, spend, impressions, clicks, leads, customers, revenue). Screens: 1. Campaigns list with budget, spend to date and a simple ROI figure. 2. Campaign detail — channel results table with computed CTR, cost per lead and cost per customer, plus links to creative. 3. Comparison view — campaigns side by side on cost per lead and ROI. 4. Learnings section per campaign, required before it can be closed. Rules: all derived metrics are computed, never entered. Flag campaigns tracking over budget. Design: dashboard with left sidebar, mono numerals, restrained use of accent for winners, dark mode support.