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