---
name: aisv-division-of-labour
description: What PlusROI owns versus what AI Smart Ventures owns on the Equinox rebuild, and the coordination rule — we talk to AISV directly; the client never relays between vendors.
metadata:
  type: project
---

# Division of labour with AI Smart Ventures (AISV)

Source: the proposal (2026-07-30), section "How This Splits With AISV" and the "Collaboration
with AI Smart Ventures" term; Rian's strategy notes (2026-07-27) recording AISV's clarification
that **AISV owns content strategy**; accepted by the client 2026-08-13.

## The split, as sold

| We handle (PlusROI) | AISV handles |
|---|---|
| Platform, templates, design system | Content strategy and final copy direction |
| Structured data and entity layer | Keyword and topic selection |
| Site architecture and URL structure | Publishing cadence and SEO execution |
| Forms, CTAs, conversion mechanics | Paid campaigns, email, CRM (Pipedrive) |
| Making sure everything they need to publish into exists and works | Marketing measurement and reporting |

In practice (proposal wording): we build the FAQ block and FAQ schema so their FAQ content has
somewhere to go; we build the tier and comparison structure (only if the Fractional General
Counsel landing page add-on is accepted) so they supply the tiers and numbers; we make sure the
WordPress REST API and post templates support their publishing tooling (OpenForge drafts posts
straight into WordPress in their Phase 01).

## Consequences that bind a build session

- **We draft placeholder copy; Equinox finalizes it with AISV's guidance.** Draft from the brand
  story (complete homepage copy exists), the deck, and existing site copy. Label drafts as drafts.
  Never spend build hours polishing prose; never wait on final copy (the "Material Completion"
  term means a launch-ready site is complete even if copy is still being finalized).
- **The REST API stays open for unauthenticated reads.** No hardening plugin or snippet that
  disables `/wp-json`, user enumeration, or application passwords. The post template must render
  OpenForge output on-brand with no manual formatting. What auth OpenForge uses is to be
  confirmed with AISV.
- **Content pruning is theirs (Phase 04).** All posts migrate; we never delete, merge, or rewrite.
- **Pipedrive beyond clean form routing and source attribution is theirs.** We re-attach the
  routing and pass source/UTM; stages, segmentation, and nurture are AISV's.
- **Ongoing SEO, ads, social, email, YouTube, Pinterest, LinkedIn, and the page-by-page metadata
  rewrite across the archive are theirs.** We build the capability (Yoast SEO — on the live site,
  not yet installed on staging as of 2026-09-02 — is installed on the new site and left editable
  per post), not the labour.
- **Their input is a prerequisite for some of ours** — the General Counsel tier numbers, FAQ content, topic hub
  direction, the assessment's name, the audience threshold, the service taxonomy. The proposal
  commits us to flag such dependencies early rather than let them move the launch date. Record
  each ask and its date in `.logs/handoff.md`.

## The coordination rule

"You shouldn't have to sit in the middle relaying technical requirements between two vendors,
so we'll coordinate with them directly throughout the build." — proposal. Rian met AISV before
quoting (email 2026-07-29). **Talk to AISV directly; never route a technical question to AISV
through Alicia or Michelle**, and never let the client become the messenger for AISV's answers.
Content-freeze coordination during the build (AISV publishes weekly on the live site) is also
agreed with AISV directly. No individual AISV contact is named in the sources — Rian holds it;
ask him (see `.memory/client-contacts.md`).

## Two AISV-document inconsistencies to flag to AISV, not resolve ourselves

1. The deck targets larger businesses than the brand story's "who it's for" copy does (no
   figures are recorded in this project). This drives the homepage qualification copy.
2. The service taxonomy has three cuts: brand story (4 groupings), live site (practice areas plus
   industries), deck (Owner / CFO / HR persona hubs). The Practice Areas page structure and the
   nav's services entry wait on AISV's answer.

Both were raised in the proposal's "Things We Need to Confirm" on 2026-07-30 and were unanswered
as of 2026-09-02.