The first line of the platform's code is written

The platform began on July 6. Its first week put accounts, clients, monitoring, keyword tracking, reporting, planning, approvals and a daily campaign agent in place, carrying over tooling already built in Workbench and the Portal.

On Monday, July 6, the first line of the platform’s code was written. The week that followed laid down accounts, clients, campaigns, monitoring, keyword tracking, reporting, planning, approvals and an agent that worked each campaign every day, much of it carried over from tooling we had already built in Workbench and the Portal. Nobody outside the team had logged in yet.

For our partners

1. Planning arrived on Friday: a plan is a container of work items by month, and a partner can approve it, remove items, and leave feedback that travels with the plan’s history. Saturday added a top-level approvals queue with shareable review pages, a My Work view, and per-type controls over what clients are asked to approve.
2. Reporting started as a first view on Tuesday, gained Google Ads and call tracking connections with their own reporting sections on Thursday, and by Friday had PDF export, a saved history, scheduled monthly delivery with a per-campaign day of month and recipient list, and a configurable cover page. Clients could download delivered reports from their portal.
3. Clients and campaigns, locations, and keyword tracking with a keyword research page landed on Tuesday. On Wednesday clients got their own logins, with a roster of who receives notifications, and a business lookup that identifies a client from its name and address.
4. The shell went up on Monday: sign-up with email verification, a workspace layout, a notification bell, and the first monitoring and prospects screens. Over Tuesday and Wednesday it gained an onboarding flow and checklist, branding and organization settings, and white-label domains so the app could sit on an agency’s own address.
5. Competitive Gap Analysis arrived on Thursday: a head-to-head review of a client against up to three competitors, on full crawls.
6. Saturday added Discoveries, a sales deliverable for prospects with a branded share page.
7. Website connections widened beyond WordPress to Webflow and Shopify.
8. The week closed with a decision about launch focus: monitoring, reporting and the SEO agent first, everything else held back as beta.

Behind the scenes

1. The campaign agent appeared on Wednesday and had its shape by Friday. Each campaign is assigned a profile (local business, multi-location, ecommerce) with an ordered set of phases, and each phase has a playbook.
2. Two guardrails landed early. Safe mode covers every plan, not only website-touching work, and the agent never works on client sites on a Saturday or Sunday: no agent should touch a site when no human is around to help.
3. Approvals were centralized into one policy and one list of requests, so anything that asks a partner for a decision works the same way.
4. The WordPress connector learned to insert internal links and list a page’s links, the first building block for internal-linking work. Citations tooling started the same day.

1. The campaign agent

The agent’s identity, skills and playbooks live as editable documents rather than code, so the team can sharpen how it works without a release. When the agent hands a task to a helper, the instructions for it travel with the task, so nothing depends on anyone remembering to attach them. Plan history follows the full chain of revisions, and skills got version history on Sunday.