NWS-360 — Build Brief

1. Terminology Corrections

The following term replacements must be applied across all project files — HTML, Markdown, schemas, code comments, and any new deliverables going forward.

Old Term	Northwoods Term	Abbreviation
Project Manager, Account Manager, PM, AM	Account Director	AD
Sales team, salesperson, sales rep	Business Development Manager	BDM

Files requiring updates

–portal/dashboard.html — line 908: “Account Manager” → “Account Director”
–nws-360_team_branded.html — line 730: “Account Manager” → “Account Director”; line 733: “Project Manager” → “Account Director” (these are the same role at Northwoods)
–estimating.md — line 145: replace “Account Manager” and “Project Manager” with “Account Director (AD)”

2. Schema Changes

2a. AD Portal — Internal Tracker

The internal AD portal (VPN-only, no separate auth) tracks two things per client per month: a deliverable checklist and hours spent. Data entered here syncs to what the client sees in their portal.

ClientMonth record

Field	Type	Notes
`clientId`	string	FK to client record
`month`	string (YYYY-MM)	Billing period
`adId`	string	Assigned Account Director
`hoursAllocated`	number	Contracted hours for the month (30–40)
`hoursUsed`	number	Hours consumed to date
`deliverables[]`	array	See Deliverable record below
`syncedToClientPortal`	boolean	Whether this data is visible to the client

Deliverable record

Field	Type	Notes
`id`	string	Unique deliverable ID
`title`	string	e.g., “Monthly SEO Health Check”
`service`	string	Service area: seo, accessibility, cmp, etc.
`status`	enum	`pending` \| `in_progress` \| `complete`
`completedBy`	enum	`human` \| `agent` \| `both`
`completedByName`	string?	Optional — name of human or agent identifier
`hoursLogged`	number	Hours charged against this deliverable
`dueDate`	string (ISO date)?	Optional — if deliverable has a fixed due date
`completedDate`	string (ISO date)?	Null until status is `complete`

Key decision: The completedBy field supports human, agent, or both — reflecting that any given deliverable may be completed by a person, an automated agent, or a collaboration of both. This answers OQ-E.

2b. Client Portal — Authentication

–Auth method: Magic link (email-based, no password)
–Not a launch blocker: First client(s) receive reports manually (PDF + call with AD and SMEs). Portal auth ships post-first-sale.
–Schema note: Client record needs an email field for magic link delivery. Auth token table is standard — token, expiry, clientId.

2c. Baseline Assessment Delivery

–Delivered by: Humans — the AD and relevant SMEs present to the client on a call. Client also receives a PDF.
–Agent role: Internal only — agent assists with data gathering and report generation, but humans deliver the final product to the client.
–Build implication: The baseline assessment output must be exportable to PDF. No need for a client-facing interactive baseline UI in the first release.

3. File and Layout Changes

portal/dashboard.html

–Sidebar footer label: “Account Manager” → “Account Director”
–No structural changes needed. The client dashboard remains the client-facing portal. The AD portal is a separate internal tool (see build order below).

nws-360_team_branded.html

–Replace both “Account Manager” and “Project Manager” bench items with a single “Account Director (AD)” entry, since these are the same role at Northwoods.

estimating.md

–Team composition line: “Account Manager, SEO Specialist, Front-end Dev, Project Manager, Back-end Dev” → “Account Director (AD), SEO Specialist, Front-end Dev, Back-end Dev”

Two Portals architecture — clarified

–Client Portal (portal/dashboard.html): Magic link auth, client-facing, shows synced data from AD portal. Exists today as a prototype.
–AD Portal (new, internal): VPN-only access, no separate auth needed. Used by ADs to track deliverable checklists and hours per client per month. Data entered here flows to the client portal. This is a new build item.

4. Prioritized Build Order

Guiding constraint: The first customer does not require a working portal. Reports will be delivered manually (PDF + call). Skill sheets matter to BDMs for sales conversations, so they are a near-term priority even though they are not a hard blocker on the first sale.

1 Sales Enablement + First Client Delivery

Goal: Close and serve the first NWS-360 client without any portal dependency.

–Skill sheets (one per service area) — BDMs need these to explain service value to prospects. Patrick assigns owners. Template exists via the CMP service page. BDM priority
–Baseline assessment tooling — Agent-assisted data gathering + PDF export. Humans (AD + SMEs) deliver to client on a call.
–Terminology pass — Update all existing files to use AD / BDM. Small effort, do it now so all future deliverables are clean.
–Monthly report template (PDF) — For manual delivery to first client(s) while portal is being built.

2 AD Portal (Internal)

Goal: Give ADs a tool to track deliverables and hours per client. VPN-only.

–ClientMonth + Deliverable schema — As defined in Section 2a above
–Deliverable checklist UI — ADs check off completed items, log hours, mark completedBy (human / agent / both)
–Hours tracker — Allocated vs. used, visible per client per month
–Client-sync flag — Toggle to control what data flows to the client portal

3 Client Portal (External)

Goal: Clients log in and see their dashboard, fed by AD portal data.

–Magic link auth — Email-based login, no password
–Dashboard shell — Prototype exists at portal/dashboard.html; wire it to real data from AD portal
–Module buildout — Performance, SEO, CMP, Accessibility, Security, Uptime, Baseline Inventory, AI Recommendations

4 Marketing Funnel (Lead Gen)

Goal: Public-facing free scan tool that feeds prospects into the sales pipeline.

–10-page scan tool — URL input, fast scans (CMP, accessibility, CWV, SEO, GA config, 404)
–Email capture + report delivery
–Paid deeper assessment gate (Tier 2) — Payment method still TBD

5. Resolved Open Questions

ID	Question	Answer	Build Impact
OQ-A	AD Portal scope	Tracks deliverable checklist + hours per client per month. Users are ADs. VPN-only access. Syncs to client portal.	New schema (Section 2a). New internal UI (Phase 2).
OQ-B	Client Portal auth	Magic link. Does not block first sale.	Auth is Phase 3 work. First client gets PDF + call.
OQ-C	Baseline assessment delivery	Humans deliver (AD + SMEs). Client gets call + PDF. Agent assists internally.	Need PDF export from agent output. No client-facing baseline UI in v1.
OQ-D	Skill sheet ownership	Patrick assigns owners. Soft blocker — BDMs need them for sales conversations.	Phase 1 priority. Use CMP service page as template.
OQ-E	Agent vs. human task completion	Mix of both. Either or both can be credited.	`completedBy` field: `human` \| `agent` \| `both`