Internal tools, sorted by the team that needs them.

Build a lightweight Sales Pipeline CRM. Core objects: Company, Contact (company, name, role, email), Deal (title, company, contact, owner, value, currency, stage Lead/Qualified/Proposal/Negotiation/Won/Lost, probability, expected close date, next action, next action date, lost reason) and Activity (deal, type call/email/meeting/note, body, date). Screens: 1. Pipeline board — drag-and-drop columns per stage, each column showing deal count and total value. 2. Deal detail — metadata, activity feed, and a next-action panel. 3. Forecast view — weighted pipeline (value x probability) grouped by expected close month. Rules: moving a deal to Won or Lost requires a close date, and Lost requires a reason. Flag deals with no activity in 14 days. Design: dashboard with left sidebar, dark mode, compact deal cards with mono values.

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.

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.

Build a Content Calendar. Core objects: ContentPiece (title, channel blog/newsletter/social/video, campaign, owner, reviewer, brief, target publish date, status Idea/Drafting/In review/Scheduled/Published, asset checklist, published URL). Screens: 1. Calendar month view with pieces on their target dates, colour-coded by channel. 2. Pipeline list grouped by status with owner filters. 3. Piece detail — brief, draft link, asset checklist (copy, image, thumbnail, alt text) and review comments. Rules: a piece cannot move to Scheduled until every asset checklist item is ticked and a reviewer has approved. Design: dashboard with left sidebar, calendar cells with subtle channel accents, dark mode support.

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.