Build a Professional Services Automation (PSA) portal — a Certinia-style web app for services estimation, resource management, and project management — backed by a set of custom objects in Salesforce (or your team's CRM/system of record), together with the tooling that provisions that schema and seeds it with data. The workflow has three parts: 1. The portal (browser app). Serve a web app at an authenticated route (e.g. /portal), restricted to members of the workspace. On load it should hydrate from live data by calling a separate read-only data endpoint; if that call fails, fall back to bundled demo data so the UI always renders. Cover the core PSA modules: accounts/contacts, projects and tasks, resources and assignments, and estimates with line items. Make it a polished, production-grade interface. Record edits can live in the browser session to start, with write-back as a later enhancement. 2. The data endpoint. Serve a read-only API route (e.g. /psa-data, same space auth) that queries the PSA custom objects in Salesforce (or your chosen system) and returns them as a single JSON document in the shape the portal expects. The portal's browser session should carry its auth cookie through to this endpoint. 3. Salesforce setup & schema tooling — all run manually, not on a trigger. Include utility steps that: Seed the org with a small, idempotent dummy dataset (accounts, contacts, projects, resources, estimates + line items, assignments, tasks). Create the custom fields on the objects via the Tooling API (for when objects were deployed without their fields). Grant the connector user field-level access to those fields via a permission set, so REST reads/writes can see them. Generate schema artifacts: a spreadsheet export, a deployable Metadata API package (zip), and a schema diff CSV. Read the org base URL from an environment variable rather than hardcoding it. Note the one-time setup order: deploy objects → deploy fields (if missing) → grant field access → seed data. Use Salesforce as the system of record and the Salesforce REST, Tooling, and Metadata APIs for reads, field creation, permissions, and schema work — or swap in your own CRM / database and its APIs. Keep all routes private to the workspace by default. The seed, field-deploy, and grant steps write to the external system; the portal and data endpoint are read-only. Tools used: Salesforce (connector), Salesforce REST API, Salesforce Tooling API