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