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