Most of what looks like a marketing problem two years into a partnership turns out to have been an infrastructure problem the whole time. That’s because in order to publish and measure marketing effectively, you need a website, the connections between the tools you already run, and the measurement layer underneath everything.
Aside from the website, this chapter is the least romantic part of the build but it’s the one that determines whether the next year of publishing produce anything you can point to. A story with no engine behind it stays in a document.
The framing that matters here is faithfulness. Everything built in this chapter exists to take one settled message and reproduce it accurately across a thousand small surfaces—a page, a form, a confirmation email, a tracking parameter on a link somebody clicked at ten at night.
The three sections
§ 2.1 Website
The site itself, the pages that follow it, and the domain and hosting underneath.
§ 2.2 Integrations
The plumbing between your CRM, your email platform, your forms, and everything else.
§ 2.3 Analytics
The tracking layer, the recurring reporting, and search visibility.
The artifact
Chapter 2 closes with a website that is live, indexed, and wired to measure. All three conditions, not just the first. A site that launched but does not appear in search, or launched but cannot tell you who arrived and from where, has not finished the chapter.When this happens
Chapter 2 typically lands in months two through five, depending on the size of the build. The website is the long run and the one with the most review cycles in it. There is an important exception. If you arrive with no CRM and no real analytics, we will often pull § 2.2 and § 2.3 ahead of the website. Instrumenting is cheaper and faster than designing, it does not wait on approval cycles, and it starts the measurement baseline in week two instead of month five. After the artifact, § 2.1 becomes a steady trickle of updates and landing pages, § 2.2 gets touched whenever your stack changes, and § 2.3 runs continuously for the life of the partnership.What this chapter asks of you
Less of your time than Chapter 1, and more of your patience. The two things that reliably delay this chapter are both administrative. Credentials for third-party systems—the reliable delay in an integration project is almost never the build but rather the waiting on admin access to two platforms nobody remembers the password for. Add to that review turnaround on the website, where scattered feedback across many rounds is what turns a six-week build into a five-month one. A note on calendars. Domain and DNS work carries mandatory waiting periods that no amount of urgency shortens—sometimes servers need a few days to publish a site.Next: Chapter 3—Send
Putting the work into the world on a schedule, and the artifact that closes it.