Internal tools, sorted by the team that needs them.

Build an internal Order Tracking System. Core objects: Order (reference, customer name, customer email, items, total, currency, status, placed date, promised date, carrier, tracking number, notes). Statuses: Pending, Paid, Packed, Shipped, Delivered, Cancelled, Refunded. Screens: 1. Orders table — searchable by reference, customer name or email; filter chips for status; highlight orders past their promised date in the accent colour. 2. Order detail — full customer and item breakdown plus a vertical status timeline showing who changed what and when. 3. New order form with validation. Rules: every status change writes an entry to the timeline with a timestamp and the user who made it. Show a small dashboard strip at the top with counts per status. Add CSV export of the current filtered view. Design: clean dashboard layout, left sidebar navigation, dark mode support, data-dense tables with generous row spacing.

Build an internal Inventory Management Tool. Core objects: Item (SKU, name, category, unit, cost, supplier, reorder point) and Movement (item, type in/out/adjustment, quantity, location, reason, date, user). Screens: 1. Inventory table — current quantity per item per location, computed from movements. Filter by category and location, search by SKU or name. Rows below the reorder point are flagged. 2. Item detail — stock by location, full movement history, and quick "receive stock" / "issue stock" actions. 3. Movements log with filters by type and date range. Rules: quantity is always derived from movements, never edited directly. Show a top strip with total SKUs, items below reorder point, and total stock value. Design: dashboard layout with a left sidebar, mono labels for numeric columns, dark mode support.

Build an Internal Ticketing System. Core objects: Ticket (title, description, requester, assignee, team, category, priority low/medium/high/urgent, status Open/In progress/Waiting/Resolved/Closed, created date, due date) and Comment (ticket, author, body, date). Screens: 1. Queue view — table with filter chips for status, priority and team, plus a search box. Show an SLA countdown per ticket based on priority (urgent 4h, high 1 day, medium 3 days, low 7 days) and flag breaches. 2. Ticket detail — description, metadata sidebar, status/assignee controls, and a threaded comment feed. 3. New ticket form. Rules: status and assignee changes append a system entry to the comment feed. Add a "My tickets" filter. Design: dashboard with left sidebar, calm dark theme, priority shown as small uppercase mono badges.

Build an Employee Onboarding Tracker. Core objects: Hire (name, role, department, manager, start date, status), ChecklistTemplate (name, tasks) and Task (hire, title, owner role e.g. HR/IT/Manager/Facilities, due offset in days from start date, status Not started/In progress/Done/Blocked, notes). Screens: 1. Hires board — cards or table showing each new hire with a progress bar, start date, and count of overdue tasks. 2. Hire detail — the full checklist grouped by owner role, with checkboxes, due dates computed from the start date, and a notes field per task. 3. Templates screen to create and edit reusable checklists; creating a hire copies the chosen template. Rules: progress is the percentage of tasks marked Done. Highlight overdue and blocked tasks in the accent colour. Design: dashboard layout, left sidebar, dark mode support, soft cards with clear section headers.

Build a Leave Management System. Core objects: Employee (name, team, manager, annual allowance), LeaveRequest (employee, type Annual/Sick/Parental/Unpaid, start date, end date, working days, reason, status Pending/Approved/Rejected/Cancelled, decided by, decided at). Screens: 1. My leave — remaining balance, a request form with a date range picker that computes working days, and a list of my requests. 2. Approvals inbox for managers — pending requests with approve/reject buttons and a required comment on rejection. 3. Team calendar — month view showing who is away, with a warning when more than two people from the same team overlap. Rules: balance = allowance minus approved annual leave days. Never allow overlapping requests for the same employee. Design: dashboard with left sidebar, dark mode support, calendar cells using subtle accent fills.

Build an Internal Request System. Core objects: RequestType (name, owning team, form fields, approval steps) and Request (type, requester, submitted values, current step, status Submitted/In review/Approved/Rejected/Fulfilled, history). Screens: 1. Request catalogue — cards for each request type (Software access, Equipment, Budget spend, Legal review, Facilities fix) with a short description. 2. Dynamic request form rendered from the selected type's fields. 3. My requests — status timeline for each submission. 4. Reviewer inbox — filtered to the reviewer's team, with approve/reject and comment. Rules: a request moves to the next approval step only when the current one is approved; rejection ends the chain and notifies the requester. Every action is written to an immutable history log. Design: dashboard with left sidebar, mono uppercase status badges, dark mode support.

Build a Customer Feedback Inbox. Core objects: Feedback (source email/call/chat/review, customer, body, sentiment positive/neutral/negative, themes as tags, product area, date, linked ticket). Screens: 1. Inbox — chronological list with filter chips for sentiment, theme and product area, plus full-text search. 2. Themes view — each theme with its volume, sentiment split, and a sample of quotes. 3. Weekly digest — the top five themes of the last seven days with counts and representative quotes. Rules: allow bulk tagging from the inbox. Show a simple bar chart of feedback volume per theme. Design: dashboard with left sidebar, dark mode, quotes rendered as bordered pull quotes.

Build an internal Knowledge Base Manager. Core objects: Article (title, category, body in markdown, owner, status Draft/Published/Archived, last reviewed date, review interval in months, tags). Screens: 1. Browse — sidebar of categories, searchable article list, article reader with rendered markdown. 2. Editor — markdown editing with live preview, category, tags, owner and review interval. 3. Health view — articles past their next review date, articles with no owner, and articles never opened. Rules: next review date = last reviewed + review interval. Flag overdue articles clearly in the accent colour. Design: documentation-style dashboard, left sidebar, comfortable reading width, dark mode support.

Build a Policy Acknowledgement Tracker. Core objects: Policy (title, body, version, effective date, audience departments) and Acknowledgement (policy version, employee, acknowledged at, signature text). Screens: 1. Policies list — each with version, effective date and a completion percentage bar. 2. Policy detail — full text, the list of who has and has not acknowledged, and a chase action. 3. Employee view — outstanding policies to read, with a scroll-to-bottom-then-confirm flow. Rules: publishing a new version resets acknowledgements for that policy and marks it outstanding again. Add an export of the acknowledgement register. Design: dashboard with left sidebar, serious and legible typography, dark mode support.

Build a Contract Repository. Core objects: Contract (title, counterparty, type MSA/NDA/SOW/Vendor/Employment, owner, status Draft/In review/Signed/Expired/Terminated, start date, end date, notice period days, auto-renew boolean, value, currency, payment terms, attachments, notes). Screens: 1. Contracts table — search by title or counterparty, filter chips for type and status, sortable by end date. 2. Contract detail — all metadata, attachment list, and a renewal panel showing the last date to give notice (end date minus notice period). 3. Renewals dashboard — contracts expiring or requiring notice in the next 30/60/90 days. Rules: highlight contracts where the notice deadline is within 30 days. Never delete records; archive instead. Design: dashboard with left sidebar, mono for dates and amounts, dark mode support.

Build a Legal Intake and Review Queue. Core objects: LegalRequest (title, requesting team, request type Contract review/Marketing claim/Data privacy/Partnership/Other, description, urgency, attachments, risk level Low/Medium/High, reviewer, status New/Triaged/In review/Needs info/Approved/Approved with changes/Rejected, submitted at, closed at). Screens: 1. Intake form with type-specific questions. 2. Triage queue — new requests sorted by urgency, with a risk level selector and reviewer assignment. 3. Review workspace — request details, internal notes, outcome selection with required rationale. 4. Metrics strip — median turnaround time and open requests by risk level. Rules: turnaround = closed at minus submitted at, only counted for closed requests. Design: dashboard with left sidebar, restrained palette with accent used only for risk and status, dark mode support.

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 Quote and Proposal Generator. Core objects: CatalogItem (name, description, unit price, unit) and Quote (client, contact, items with quantity and discount, subtotal, tax rate, total, valid until, status Draft/Awaiting approval/Sent/Accepted/Declined/Expired, notes, terms). Screens: 1. Quotes list with status filters and totals. 2. Quote builder — pick items from the catalogue, adjust quantity and discount, watch the totals recalculate live. 3. Proposal preview — a clean printable document with cover section, scope, pricing table and terms. Rules: discounts above 20% require approval before the quote can be sent. Quotes past their valid-until date flip to Expired automatically. Design: dashboard with left sidebar for the app, but the proposal preview should be a clean document view suitable for PDF export.

Build an Expense Approval Tracker. Core objects: Expense (submitter, date, merchant, category, amount, currency, project or cost centre, receipt attachment, description, status Draft/Submitted/Approved/Rejected/Reimbursed, approver, decided at). Screens: 1. My expenses — submission form with receipt upload and a list of my claims by status. 2. Approvals inbox — expenses awaiting my decision, with the receipt shown side by side. 3. Finance view — all approved expenses, filterable by month, category and cost centre, with totals and a CSV export. Rules: expenses under 100 need one approval from the line manager; 100 and above also need finance approval. Rejections require a comment. Design: dashboard with left sidebar, mono for all amounts, dark mode support.

Build an Invoice and Payment Monitor. Core objects: Invoice (number, client, issue date, due date, amount, currency, status Draft/Sent/Part paid/Paid/Overdue/Written off, notes) and Payment (invoice, amount, date, method, reference). Screens: 1. Invoices table — filters for status and client, search by number, sortable by due date. 2. Ageing dashboard — receivables split into current, 1-30, 31-60, 61-90 and 90+ days overdue, with totals. 3. Client statement — all invoices and payments for one client with a running balance. Rules: status derives from payments and due date, never set by hand except Draft and Written off. Show a chase list of invoices overdue by more than 7 days. Design: dashboard with left sidebar, dense financial tables, mono numerals right-aligned, dark mode support.

Build a Budget Planning Board. Core objects: BudgetLine (department, category, fiscal year, quarterly planned amounts, owner) and Actual (budget line, month, amount, source note). Screens: 1. Plan grid — departments as rows, quarters as columns, editable planned amounts with row and column totals. 2. Plan vs actual — the same grid showing planned, actual and variance, with over-budget cells in the accent colour. 3. Department detail — monthly actuals against the plan with a simple line chart. Rules: variance = actual minus planned; show it both absolute and as a percentage. Lock planned amounts once a quarter is closed. Design: dashboard with left sidebar, spreadsheet-like grid but with generous spacing, mono numerals, dark mode support.

Build a Project Portfolio Dashboard. Core objects: Project (name, owner, sponsor, team, start date, target date, status Not started/On track/At risk/Off track/On hold/Done, summary), Milestone (project, title, due date, done) and Risk (project, description, impact, likelihood, mitigation, owner, status). Screens: 1. Portfolio grid — one card per project showing RAG status, next milestone, days to target and open risk count. 2. Project detail — milestone timeline, risk register and a status update feed. 3. Weekly review — a printable summary of all projects with this week's status commentary. Rules: a status change requires a short commentary. Automatically flag At risk when the next milestone is overdue. Design: dashboard with left sidebar, RAG shown with restrained colour, dark mode support.

Build a Meeting and Action Tracker. Core objects: Meeting (title, series, date, attendees, agenda, notes), Action (meeting, description, owner, due date, status Open/Done/Cancelled) and Decision (meeting, description, decided by). Screens: 1. Meetings list grouped by series, newest first. 2. Meeting workspace — agenda on the left, notes in the middle, actions and decisions captured inline with quick-add. 3. Actions view — all open actions across meetings, filterable by owner, with overdue items flagged. Rules: opening a new meeting in a series automatically carries over open actions from the previous one. Design: dashboard with left sidebar, fast keyboard-friendly capture, dark mode support.

Build a Resource Capacity Planner. Core objects: Person (name, role, weekly capacity hours, team), Allocation (person, project, week starting, hours) and Absence (person, start date, end date). Screens: 1. Capacity grid — people as rows, weeks as columns, each cell showing allocated hours out of capacity with a subtle fill bar; cells over capacity use the accent colour. 2. Project staffing — for one project, who is allocated and for how many hours per week. 3. Availability view — people with free hours in the next four weeks. Rules: absences reduce that week's capacity proportionally. Allocations are editable inline. Design: dashboard with left sidebar, horizontally scrollable grid with sticky first column, mono numerals, dark mode support.

Build a Bug Triage Board. Core objects: Bug (title, reporter, area, environment, steps to reproduce, expected, actual, severity S1-S4, status New/Triaged/Accepted/In progress/Fixed/Won't fix/Duplicate, assignee, duplicate of, first seen, occurrences). Screens: 1. Triage inbox — new bugs sorted by severity, with quick actions to accept, mark duplicate or decline with a reason. 2. Board — columns by status, cards showing severity badge and area. 3. Bug detail — full report, occurrence count, linked duplicates, and a comment thread. Rules: S1 bugs pin to the top of every view. Marking a duplicate links the two and merges occurrence counts. Design: dashboard with left sidebar, monospace for environment and steps, dark mode support.

Build a Deployment and Release Log. Core objects: Release (version, environment staging/production, deployed at, deployed by, changes list, risk level, rollback of, status Deployed/Rolled back/Failed, notes) and Incident (release, description, severity, started at, resolved at). Screens: 1. Timeline — reverse-chronological releases per environment with version, author and change count. 2. Release detail — the full change list, linked incidents, and a rollback action that creates a linked rollback record. 3. Release notes view — a clean, shareable summary of changes between two versions. Rules: never edit a released entry; corrections are appended as notes. Show time since last production release. Design: dashboard with left sidebar, monospace for versions and timestamps, dark mode support.

Build an On-Call and Incident Tracker. Core objects: Rota (week starting, primary, secondary), Incident (title, severity SEV1-SEV3, started at, acknowledged at, resolved at, services affected, summary, cause tags, responder) and ActionItem (incident, description, owner, due date, status). Screens: 1. Current on-call banner plus the rota for the next eight weeks. 2. Incidents list with severity filters, showing time to acknowledge and time to resolve for each. 3. Incident detail — chronological timeline, summary, cause tags and postmortem action items. 4. Trends — incident count and median resolve time per month, plus the most common cause tags. Rules: SEV1 incidents require a postmortem with at least one action item before they can be closed. Design: dashboard with left sidebar, calm dark theme, severity as mono uppercase badges.

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 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.

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 an Office Space and Desk Booking tool. Core objects: Space (name, type desk/meeting room/parking, zone, capacity, amenities) and Booking (space, person, date, start time, end time, recurring rule, checked in boolean). Screens: 1. Book — pick a date, see available spaces by zone as a simple grid, book in one click. 2. My bookings with cancel and check-in actions. 3. Occupancy report — utilisation per zone per weekday over the last month, plus a no-show rate. Rules: prevent double booking of the same space and time. Auto-release a desk booking not checked in by 11:00. Design: dashboard with left sidebar, zone grid with clear available/taken states, dark mode support.

Build a Maintenance Work Orders tool. Core objects: Asset (name, category, location, installed date, warranty until, service interval months), WorkOrder (asset or location, reported by, description, photos, priority, assigned contractor, scheduled date, completed date, cost, status Reported/Scheduled/In progress/Completed/Cancelled). Screens: 1. Report an issue — short form with location picker and photo upload. 2. Work order queue with priority and status filters, plus a scheduling calendar. 3. Asset detail — full maintenance history, total spend, and the next preventive service date. Rules: preventive work orders are generated automatically from each asset's service interval. Show total maintenance spend per month. Design: dashboard with left sidebar, photo thumbnails in cards, dark mode support.

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.

Build a Product Feature Request Board. Core objects: FeatureRequest (title, description, submitted by, area, votes, linked accounts with value, status Under review/Planned/In progress/Shipped/Not planned, merged into, roadmap item) and Vote (request, voter, account, note). Screens: 1. Board — requests sorted by weighted demand (vote count plus linked account value), with area filters and search. 2. Request detail — description, supporting notes from voters, linked accounts, and status with a public-facing update. 3. Merge flow — combine duplicates, transferring votes and linked accounts. Rules: changing status requires an update note that is shown to everyone who voted. Not planned requires a reason. Design: dashboard with left sidebar, compact request rows with vote counts in mono, dark mode support.

Build a Product Roadmap Planner. Core objects: RoadmapItem (title, outcome, success metric, horizon Now/Next/Later, quarter, owner, team, confidence High/Medium/Low, effort T-shirt size, dependencies, linked feature requests, status) and Change (item, field, from, to, reason, date). Screens: 1. Roadmap board — Now / Next / Later columns with cards showing outcome, confidence and effort. 2. Quarter view — items grouped by quarter and team, with dependency warnings when an item depends on something scheduled later. 3. Item detail — outcome, metric, linked requests and full change history. Rules: every item must state an outcome and a success metric before leaving Later. Moving an item between horizons requires a reason. Design: dashboard with left sidebar, confidence as mono uppercase badges, dark mode support.