Or start from a base someone already wired.

Customers linked to Onboarding Steps, with completion averaged up per customer and each step showing its customer's plan. Drive activation, no setup.

Customers linked to their support tickets, with an open-ticket count per customer and each ticket showing its customer's tier. Priority/status selects and a triage board.

Courses linked to Enrollments, with student count and average grade rolled up per course and each enrollment showing its course level. A relational LMS, ready to teach.

Expense Reports linked to line-item Expenses, with the total rolled up per report and each expense showing its report's status. Reimbursements, ready to run.

Cost Centers → Budget Lines with a planned and an actual amount on every line, both rolled up per cost center so Total Budget and Total Actual sit side by side. A lightweight FP&A budget-vs-actual tracker — add a formula column for a live variance after applying.

Accounts → Subscriptions → Invoices: track recurring revenue with MRR and active-subscription counts rolled up per account and billed totals per subscription. Plan and status selects drive the boards — a normalized recurring-revenue starter.

Customers → Invoices → Line Items, with each invoice's line items totalled and each customer's billing rolled up. Accounting on the same relational core — no separate tool.

Departments → Employees → Time Off, normalized: headcount and payroll roll up per department, and each employee's time-off days roll up from their requests. Employment and request statuses on the same relational core — a lightweight HRIS.

Job openings linked to candidates moving through stages, with a live candidate count per opening and each candidate showing its opening's status. Includes a stage board.

Policies → Claims → Loss Items: manage claims from intake to payout. Claim counts and total paid roll up per policy from the stored approved amount, and loss-item totals roll up per claim. Coverage, cause, and status selects drive the boards — a normalized claims starter that never rolls a rollup up.

Campaigns linked to their Content pieces, each piece inheriting its campaign's channel and each campaign counting its pieces. A content calendar that's also a database.

Events linked to their sessions, with a session count per event and each session showing its event's status. Track selects and a board by track for scheduling.

Shows linked to Episodes, with episode count and total runtime rolled up per show and each episode showing its show's host. A relational production tracker.

Members linked to Payments, with total paid and payment count rolled up per member and each payment showing its member's tier. A relational membership CRM.

Volunteers linked to Shifts: each shift logs a program, date, and hours, every volunteer rolls up their total hours and shift count, and each shift shows the volunteer's role. Track your roster and hours relationally, out of the box.

Grants linked to their deliverables, with awarded amounts and a deliverable count per grant, and each deliverable showing its grant's status. Progress board included.

Donors linked to Donations, with total given and gift count rolled up per donor and each gift showing its donor's type. A relational donor CRM, ready to fundraise.

Recipes → Batches → Packaging: batches per recipe with planned volume, and each batch's packaging runs (kegs / cans / bottles) and units rolled up. Fermentation status and QA at every level — a batch-production tracker on the relational core.

Vendors → Purchase Orders → PO Lines: each line's extended cost totals to its PO, and each vendor's spend and open-PO count roll up. Approval and receiving statuses on the same relational core — a lightweight purchasing system.

Vendors → Contracts → Obligations: contract value and count roll up per vendor, and each contract's obligations (payments, deliverables, renewals) roll up with their own status. Track the whole contract lifecycle on the relational core.

Products → Work Orders → Operations: work orders per product, and each order's operations and labour hours rolled up. Production status at every level — a lightweight shop-floor tracker on the relational core.

Employees → Assets → Tickets: assets assigned to people with count and value rolled up per employee, and open tickets rolled up per asset. Category, status, and priority selects on the same relational core — a lightweight asset register + help desk.

Technicians → Work Orders → Parts: dispatch jobs to technicians, track status and priority, and roll up open-order counts + labor hours per tech and parts cost per work order. A normalized service-management starter.

Vehicles → Service Records → Parts: keep a fleet serviced. Service counts and maintenance spend roll up per vehicle, and parts cost per service record. Vehicle-type and status selects drive the boards — a normalized fleet-maintenance starter.

Projects → Areas → Punch Items: drive a construction project to closeout. Open-item counts and remediation cost roll up per area from stored line items, and area counts and total budget roll up per project. Trade, priority, and status selects drive the boards — a normalized punch-list starter that never rolls a rollup up.

Clients → Matters → Time Entries: manage legal matters and billing. Matter counts roll up per client, and billed hours + fees roll up per matter from its logged time entries. Practice-area and status selects drive the boards — a normalized matter-management starter.

Products linked to Returns (RMAs): each return shows its product's SKU and category, and every product rolls up its return count and total refunds — so quality problems surface by product, out of the box.

Members and Classes linked through Bookings — the many-to-many junction at the heart of relational design. Each booking shows its member's tier and its class's type; members roll up their bookings and classes roll up how many seats are taken. A studio scheduler on the relational core.

Patients → Appointments ← Providers: schedule and track clinic visits. Appointment counts roll up per patient and per provider, and each provider's booked minutes sum from their appointments' durations. Status and visit-type selects drive the boards — a normalized scheduling starter with obviously-fictional sample data.

Guests → Reservations ← Tables: manage covers and seating. Reservation counts roll up per guest and per table, and each table's total covers sum from its reservations' party sizes. Service and status selects drive the boards — a normalized front-of-house starter.

Customers → Vehicles → Work Orders: run a repair shop. Vehicle counts roll up per customer, and each vehicle's order count + total spend roll up from its work orders. Status and priority selects drive the boards — a normalized service-shop starter.

Owners → Pets → Visits: run an animal clinic. Pet counts roll up per owner, and each pet's visit count + total billed roll up from its visits. Species and visit-type selects drive the boards — a normalized vet-practice starter with fictional sample data.

Programs → Applicants → Interviews: run an admissions pipeline. Applicant counts roll up per program, and each applicant's interview count + average score roll up from their interviews. Status and recommendation selects drive the boards — a normalized intake starter.

Internal requests routed to Teams, with each request inheriting its team's lead and each team counting its open requests. An intake tracker with real routing.

Products linked to orders, with units sold and revenue rolled up per product and each order showing its product's price. Order-status board for fulfillment.

Properties linked to Leases, with monthly rent rolled up per property and each lease showing its property's type. A relational rent roll, ready to run.

Objectives linked to Key Results, with progress averaged up per objective and each key result showing its objective's owner. Run the quarter, no setup.

Epics linked to Features, with effort rolled up per epic and each feature showing its epic's status. A relational roadmap, out of the box.

Projects linked to Tasks, with effort rolled up per project and each task showing its project's status. The relational core, working out of the box.

Portfolios linked to Projects linked to Tasks — a three-level system with RAG health at every level, budget rolled up to the portfolio and task effort rolled up to each project, plus an Agile/Scrum/Waterfall methodology tag for a mixed (hybrid) portfolio.

Epics → Stories → Tasks for Agile teams: story points roll up per epic, subtasks per story, and sprint/status selects drive Scrum and Kanban boards. A ready-to-run backlog and board on the relational core.

All 195 UN member and observer states with ISO codes, capital, region, currency and calling code, plus the capital's coordinates. Point a relation column at it and every customer, site or shipment row carries its country's currency and region for free — and a form's country picker can cascade into a states picker. Installed as a copy: later corrections here do not reach a table you already created.

The 50 states plus DC, with USPS code, capital, Census region and the capital's coordinates. Point a relation column at it instead of retyping a state dropdown — then every row that references a state gets its region and capital for free. Installed as a copy: later corrections here do not reach a table you already created.

Every currency used by the Countries table, with its ISO 4217 code, name, symbol and how many decimal places it takes. Relate a Countries row to it and an invoice knows the currency and its precision from the country alone — the yen and the CFA francs take none, the Gulf dinars take three. Installed as a copy: later corrections here do not reach a table you already created.

Every unit CONVERT() understands: its code, what it measures, how many base units it is, and the other spellings accepted for it. Generated from the formula engine's own table, so it cannot claim a unit the engine does not take. Use it as a picker to relate against, or to look up a code before writing =CONVERT(). Installed as a copy: later corrections here do not reach a table you already created.

Agents → Deals ← Clients: run a brokerage pipeline. Deal counts roll up per agent and per client, and each agent's sales volume sums from their deals' prices. Stage and side selects drive the boards — a normalized transaction-pipeline starter (distinct from property management).

Accounts linked to Deals and Contacts, with pipeline value rolled up per account and each deal showing its account's industry. A relational CRM, no setup.

Test Suites linked to Test Cases: each case tracks priority, type, and its last result, while every suite rolls up its case count and shows each case its suite's module and owner. Plan and track testing relationally — a complement to the bug tracker.

Product areas linked to bugs, with open-bug counts per area and each bug showing its area. Severity and status selects, plus a status board for triage.